[gh-modernization M2] Add governed roadmap intake and GitHub projection #2960

Final scoped lifecycle disposition — 2026-10-19

The current user-selected policy under #4701 retires this original recipe as not planned; it is not a completed implementation claim. Source PR4711 and selected109/020 distribution/installed joins are accepted at their recorded scope. The final issue comment records independent owners and preserved remainder. Original promise, owners, evidence and supersession history below remain intact. #4701/#4712 and original Unknown custody remain open.

Current lifecycle supersession — 2026-10-19

The current user-selected design under #4701 keeps roadmaps as scope/acceptance/navigation and native owning issues as the six-field delivery contract. Supersede this issue's mandatory fsgg.coord.roadmap-intake/v1 validate/plan/apply/inspect framework and automatic Epic/milestone projection as requirements of current organization work. Decomposition is evidence-driven: reuse existing outcomes/PRs and materialize only the next independently meaningful Delivery, not every roadmap milestone. It creates no second cycle/feedback/receipt ledger or automatic field/enrollment authority.

Reuse the still-valid properties in the existing admitted native route: semantic reuse/idempotence, exact source revision, native hierarchy/dependency correspondence, complete readback, stale-source refusal, partial-effect settlement without duplicate creates, and preservation of unrelated human values. ADR-0078's forward V2/no-V1-rollback boundary remains. #4701.2 owns a bounded writer extension only if an exact required transition lacks an already qualified path; it does not inherit this entire historical generic protocol proposal.

This is a scoped supersession verdict, not a claim that the old four-operation protocol shipped. Root first verifies no independent consumer requirement remains and that active callers/validators have migrated through #4702 and applicable installed acceptance. If the entire outstanding promise is then superseded, close this exact issue as NOT_PLANNED with this link/reason; otherwise retain the named independent remainder here. No closure is sent by this disposition.

Observed behavior

work-roadmap can execute an arbitrary Markdown roadmap rigorously, but admission has no typed operation that projects an Epic, milestones, dependencies, dates, and board membership into GitHub.

Root cause

Markdown is correctly the execution and evidence ledger, while the missing GitHub projection leaves roadmap structure ad hoc and undiscoverable to normal issue and Project tooling.

Acceptance

Implement fsgg.coord.roadmap-intake/v1 validate, plan, apply, and inspect operations; idempotently create or reuse an Epic and milestone sub-issues; project native dependencies and org fields; detect projection drift against the exact roadmap revision; keep cycle, feedback, critique, and update-receipt evidence authoritative outside mutable Project fields.

Verification

Fixtures cover initial creation, reuse, reordered milestones, dependency changes, partial apply, stale source revision, rollback, and live inspect; an example roadmap round-trips without duplicate issues or dual execution authority.

Class: capability
Severity: Medium
Blocked by: #2954

Paths: src/FS.GG.Coord.Core src/FS.GG.Coord.Cli src/FS.GG.Coord.GitHub .agents/skills/work-roadmap tests

Ratified v2 boundary

• Governed by ADR-0078: GitHub Substrate v2 is a new-only coordination authority.
• Rollback: before OpenV2, restore only the last verified bridge configuration through the protected epoch; after OpenV2, recovery is a reviewed forward v2 release and v1 authority never resumes.