Multi-agent feature delivery pipeline

Source: tests/bdd/features/pipeline.feature

Feature: Multi-agent feature delivery pipeline
  A feature flows through 5 agents: main -> priya -> forge -> atlas -> helm

  @bdd
  Scenario: Full pipeline from request to deployment
    Given a fresh beads environment with 6 agents

    # Phase 1: Human request arrives
    When "main-agent" creates a bead "Ship user dashboard" labeled "priya" with description "FROM HUMAN: CEO wants user dashboard by Friday"
    Then "priya" inbox contains 1 bead

    # Phase 2: Priya breaks down work
    When "priya" claims the bead
    And "priya" creates a child bead "Implement dashboard API" labeled "forge"
    Then "forge" inbox contains 1 bead
    And the child bead's parent is the original bead

    # Phase 3: Forge implements and hands off to atlas
    When "forge" claims the child bead
    And "forge" comments on the child bead "STATUS: Implementation complete"
    And "forge" adds label "atlas" to the child bead
    Then "atlas" inbox contains 1 bead

    # Phase 4: Atlas validates and hands off to helm
    When "atlas" comments on the child bead "STATUS: Tests passing, approved for deploy"
    And "atlas" adds label "helm" to the child bead
    Then "helm" inbox contains 1 bead

    # Phase 5: Helm deploys and closes
    When "helm" comments on the child bead "STATUS: Deployed to production"
    And "helm" closes the child bead with reason "Deployed successfully"
    Then the child bead status is "closed"