{
  "issueNumber": 343,
  "branchName": "feat/343-release-strategy",
  "generatedAt": "2026-04-08T12:00:00Z",
  "stories": [
    {
      "id": "S1",
      "title": "Define release lifecycle model — phases, actors, gates, directive mapping",
      "priority": 1,
      "dependsOn": [],
      "acceptanceCriteria": [
        "Document defines release phases (planning → development → staging → validation → ship) with entry/exit criteria",
        "Each phase specifies which actor (agent/human/CI) owns it and what gates apply",
        "Existing directives (careful/auto/quick) are mapped to release-level gate behavior"
      ],
      "passes": false,
      "completedAt": null
    },
    {
      "id": "S2",
      "title": "Design multi-repo coordination model — RC branches, dependency graph, merge flow",
      "priority": 2,
      "dependsOn": [
        "S1"
      ],
      "acceptanceCriteria": [
        "RC branch naming and creation strategy documented for multi-repo scenarios",
        "Cross-repo dependency tracking approach defined",
        "Promotion flow (feature → RC → staging → master) documented with conflict resolution strategy"
      ],
      "passes": false,
      "completedAt": null
    },
    {
      "id": "S3",
      "title": "Design data models — ReleaseManifest, ReleaseTask, CrossRepoDependency schemas",
      "priority": 3,
      "dependsOn": [
        "S1",
        "S2"
      ],
      "acceptanceCriteria": [
        "ReleaseManifest schema defined with release ID, repo list, branch map, issue list, lifecycle state",
        "ReleaseTask schema links existing TaskEntity to a release with role/ordering metadata",
        "CrossRepoDependency schema captures repo-to-repo change dependencies",
        "All schemas include field reference tables with types and descriptions"
      ],
      "passes": false,
      "completedAt": null
    },
    {
      "id": "S4",
      "title": "Design pipeline/phase extensions — validate, promote phases and release-scoped signals",
      "priority": 4,
      "dependsOn": [
        "S1",
        "S3"
      ],
      "acceptanceCriteria": [
        "New phases (validate, promote) specified with integration points in PHASE_ORDER and PhaseRouterService",
        "Signal protocol extensions for release-scoped completion documented",
        "ClaudeInvocationService env var additions for release context specified"
      ],
      "passes": false,
      "completedAt": null
    },
    {
      "id": "S5",
      "title": "Design validation/gating model — E2E tier integration, failure handling, rollback",
      "priority": 5,
      "dependsOn": [
        "S4"
      ],
      "acceptanceCriteria": [
        "E2E tier execution as release gates documented (which tiers, when, on which branches)",
        "Failure handling strategy defined: auto-fix threshold, human escalation criteria",
        "Partial validation failure and promotion rollback paths documented"
      ],
      "passes": false,
      "completedAt": null
    },
    {
      "id": "S6",
      "title": "Design API/webhook changes — release CRUD, status, promotion endpoints",
      "priority": 6,
      "dependsOn": [
        "S3",
        "S4"
      ],
      "acceptanceCriteria": [
        "REST API endpoints for release management specified (create, update, query, promote)",
        "Webhook event handling for cross-repo PR merges and CI results documented",
        "Integration with existing ControlApiModule controller pattern confirmed"
      ],
      "passes": false,
      "completedAt": null
    },
    {
      "id": "S7",
      "title": "Write execution plan — ordered tasks with complexity, dependencies, milestones",
      "priority": 7,
      "dependsOn": [
        "S1",
        "S2",
        "S3",
        "S4",
        "S5",
        "S6"
      ],
      "acceptanceCriteria": [
        "Every task is specific enough to become a standalone GitHub issue",
        "Tasks have S/M/L complexity estimates and explicit dependency references",
        "Milestone structure defined (M1–M4) with parallelisation opportunities identified",
        "Execution plan is structured for both human review and agent-actionable breakdown"
      ],
      "passes": false,
      "completedAt": null
    }
  ]
}