Goal: organize Stage 3 provider-context work into small design and validation issues before implementation begins.
Related gates: #79 must define readiness before implementation work starts.
Suggested merge order:
1. #95 Add provider-context dependency map to contributor backlog.
2. #84 provider adapter package boundaries and #85 provider fixture/mock contract after #79/#22.
3. #83 provider error/offline fallback taxonomy and #86 GitHub token permission matrix.
4. Provider fixture design: #87 changed-files fixture contract and #89 check-runs fixture contract.
5. Output and UX design: #90 PR context JSON extension, #88 Markdown PR summary contract, #91 why/explain/ci command UX boundaries.
6. Additional integration design: #93 CI artifact directory fixture layout, #92 GitLab parity boundary, #94 agent evidence bundle schema.
Issue map:
- #83 provider error and offline fallback taxonomy. Depends on #79 and #84.
- #84 provider adapter package boundaries. Depends on #79 and #22.
- #85 provider fixture and mock contract. Depends on #79 and #22.
- #86 GitHub token and permission matrix. Depends on #79 and #22.
- #87 changed-files fixture contract. Depends on #21, #84, and #85.
- #88 Markdown PR summary content contract. Depends on #29 and #90.
- #89 check-runs fixture contract. Depends on #23, #84, and #85.
- #90 PR context JSON extension contract. Depends on #25, #26, #39, and #79.
- #91 why/explain/ci command UX boundaries. Depends on #27, #28, and #79.
- #92 GitLab parity boundary. Depends on #33, #84, and #85.
- #93 CI artifact directory fixture layout. Depends on #36 and #79.
- #94 agent evidence bundle schema. Depends on #34, #90, and #79.
- #95 provider-context dependency map in contributor backlog.
Acceptance criteria:
- Stage 3 planning issues exist with explicit dependencies.
- Every child issue has stage, area, difficulty/help, and status labels.
- The backlog document references the provider-context planning lane.
- Stage 3 implementation remains gated by Stage 2.1 readiness.
Goal: organize Stage 3 provider-context work into small design and validation issues before implementation begins.
Related gates: #79 must define readiness before implementation work starts.
Suggested merge order:
1. #95 Add provider-context dependency map to contributor backlog.
2. #84 provider adapter package boundaries and #85 provider fixture/mock contract after #79/#22.
3. #83 provider error/offline fallback taxonomy and #86 GitHub token permission matrix.
4. Provider fixture design: #87 changed-files fixture contract and #89 check-runs fixture contract.
5. Output and UX design: #90 PR context JSON extension, #88 Markdown PR summary contract, #91 why/explain/ci command UX boundaries.
6. Additional integration design: #93 CI artifact directory fixture layout, #92 GitLab parity boundary, #94 agent evidence bundle schema.
Issue map:
- #83 provider error and offline fallback taxonomy. Depends on #79 and #84.
- #84 provider adapter package boundaries. Depends on #79 and #22.
- #85 provider fixture and mock contract. Depends on #79 and #22.
- #86 GitHub token and permission matrix. Depends on #79 and #22.
- #87 changed-files fixture contract. Depends on #21, #84, and #85.
- #88 Markdown PR summary content contract. Depends on #29 and #90.
- #89 check-runs fixture contract. Depends on #23, #84, and #85.
- #90 PR context JSON extension contract. Depends on #25, #26, #39, and #79.
- #91 why/explain/ci command UX boundaries. Depends on #27, #28, and #79.
- #92 GitLab parity boundary. Depends on #33, #84, and #85.
- #93 CI artifact directory fixture layout. Depends on #36 and #79.
- #94 agent evidence bundle schema. Depends on #34, #90, and #79.
- #95 provider-context dependency map in contributor backlog.
Acceptance criteria:
- Stage 3 planning issues exist with explicit dependencies.
- Every child issue has stage, area, difficulty/help, and status labels.
- The backlog document references the provider-context planning lane.
- Stage 3 implementation remains gated by Stage 2.1 readiness.