Prepare coherent 0.97.2 for diagnostic roadmap guidance

[EHotwagner]

Prepare the coherent 0.97.2 patch that carries the delivered work-roadmap diagnostic guidance in FS.GG.Drivers. CLI, Kit and Drivers retain the existing shared scalar, candidate qualification and sixteen-effect publication route. The promoted predecessor is genuine 0.97.1; its completed journal, accepted installed CLI/local cycle and all original effects remain immutable.

Reconcile the source/published registry frontier and selected release window, regenerate the affected inventories, and record the delivered ordinary pilot's bounded evidence. DIAG .2, .3 and .4 stay unchecked. Repository-native work-programme/pipeline-preflight are exempt from package obligations. No full DIAG, receiver or whole-programme coverage is claimed.

Validation: existing candidate (10), artifact (7), execution (12), fake journal/live-provider, effect-sealing and routine-eligibility controls passed. Pure projection/coherence, catalog/manifest/staging and routine-policy checks passed. Source rebased onto acceptance projection PR #4253 merge 62bb3f6; only the owner-plan append conflict was resolved, preserving the accepted projection. Full engine-dependent projection, build/pack/native/package qualification remain required in CI and the existing candidate route.

This is ordinary source preparation. It creates no journal, tag, package, release, installation or dispatch and authorizes none. Root retains future exact-main candidate, separate no-effect preflight, publication admission and installed receiver qualification. Public root GitHub Packages reads remain HTTP 403 separately from hosted verification; NuGet generated SHA-512 provenance remains unknown separately from payload matching. Missing historical parent-token telemetry evidence remains retained and unknown.

Local outage complement at unchanged ade9c1beb8d226cc09fab6ac8d22e90ed04286d1:

Local scope	Actual result
Shared-version and release-notes production validators	Both exit0, retained as scoped results from unqualified root02.
Drivers coherent-set and release-notes fixtures	Qualified separate root03:13/13 and29/29, both exit0, clean custody.
Claim-fence fixture and real routine verdict	Qualified root06:108 passed/0 failed, production exit0, clean custody.
Original full shell lint	Production actual exit0 and clean custody; clean manifest covers190 files and614 embedded steps, pinned ShellCheck0.11.0.
Shell fixture	Separate qualified fixture-only window:62 passed/0 failed, actual exit0;14.251923926s,153,141,248 bytes sampled RSS,7owned processes,0CLR; clean custody, no resource/storage failure.

The user explicitly selected sampled owned RSS8GiB for the original shell scope after the single-file analysis exceeded2GiB. CPU1/live32/CLR10, one480-second work/600-second whole clock, storage and custody bounds remained unchanged. Fixture acceptance included five independently verified storage deletions and one successful process-census reobservation; complete fresh scans supplied accepted storage results. These are sampled observations, with no hard peak or atomic snapshot claim.

The qualified shell production command is reused from original8g-root02 without repeating it; that containing window remains unqualified because fixture cleanup observation failed and its fixture exit was unknown. Earlier2GiB RSS refusals, batched/writes-only failures, storage failures and claim root04/root05 remain immutable. The private batching checkpoint was safely withdrawn; final PR source remains originalade9 with no batching changes.

These local command scopes add semantic and rejection coverage. Hosted exact-head/full coherent source/package/runtime gates remain pending and are not replaced by local results. Root owns fresh dependency-aware hosted recovery, merge, candidate/preflight/publication and installed receiver acceptance.

[EHotwagner]

Temporarily deferring this Drivers source PR to prioritize V2-DIAG-01’s required milestone projection. The Contracts source/feed failure remains unresolved; this is not delivery or supersession. The branch, exact head, checks and release obligations are preserved. The programme integrator will reopen this same PR when the projection has left the open queue, capacity is available, and the Contracts dependency has a supported resolution. No workflow run is cancelled and no branch is deleted.