docs: govern project autonomy, backlog priority and roadmap publication (NO_BUMP)

[pcvantol]

Owner-requested design refinement

Separate the single-Mission inner loop from the project loop. Update the existing Live Project Roadmap contract and documentary DAG; do not create another scheduler, backlog authority or executable programme.

• Automatic source-backed lifecycle facts versus governed direction and committed priority.
• Milestone publication to the canonical project repository through the existing authorized EP delivery route, with independent runtime/repository freshness and no self-trigger loop.
• Three planned modes: MISSION_RELEASE, APPROVED_WORKLIST and DELEGATED_DEVELOPMENT. A mode is not an approval or grant; mandatory human/assurance/delivery gates remain intact.
• Findings become disposition-aware evidence-linked proposals; no automatic backlog insertion or reprioritization. Current acceptance defects cannot be hidden as follow-up work.
• Nine PLANNED Forge nodes, 36 shared PMT scenarios, strengthened offline graph/table/invariant guards. The companion Workspace change is being prepared on the same named branch.

Boundaries

Documentation, documentary DAG and documentary tests only. NO_BUMP. No runtime, CI workflow, policy activation, grant, queue, Mission state, provider invocation or installation change. Mission 3 acceptance and attempt scope remain unchanged. Current human-governed defaults are not silently replaced; delegated decision support remains a separately qualified planned capability.

Validation

Repository CI on this exact candidate is required before merge. No local full-suite execution is claimed: this environment cannot clone the repository. Documentary guards are not runtime, browser or project-loop qualification. Existing protected delivery and TDE requirements remain unchanged.