feat(native-config): retain legacy local routing during Compose adoption

[roodboi]

Summary

Preserve existing local HTTP origins when explicitly adopting a supported legacy Compose project: literal dev_host, its declared OAuth alias, and saved open preference with typed local precedence. Private v14 receipts bind the original containers, SQL volume births, default bridges, ingress/proxy observations, route claims and source files. Lifecycle and rollback use those original resources; unsupported family intersections refuse.

Read-only routing proofs reuse a resource observation within one private phase, bracketed by complete ownership proofs. Both the pre-move entry and final active-receipt save use the actual full proof just completed. The final reuse spans only an exclusive temporary receipt write; the authoritative switching receipt stays unchanged. Source, manifest, receipt, claims, stopped state, cancellation and the same absolute 15s deadline remain checked. Scoped observations revoke before a complete fresh closing proof and final receipt snapshot, before active receipt rename. Other callers retain fresh entry proofs.

The maintained isolated ingress fixture covers two worktrees, TLS markers, SQL continuity, saved open, interrupted stop recovery and rollback without changing global DNS or trust. Owner-issued closed publication stage/reason diagnostics and explicit-opt-in process-policy replay diagnostics contain no raw errors or resource values.

Verification

• Parent b76092c1 normally joins the reviewed correction 742625a8 with literal next e267f3c4. Independent source review verified 47 own and 24 incoming paths with no overlap; all blobs and modes remain exact to their parents. Distinct v12/v13/v14 family guards remain intact.
• New publication controls: 3 passed, 0 failed, 16 assertions. The identical positive control fails against unchanged 0782b588 at its deadline check after six charged volume inspections and passes the correction with four. Separate controls retain refusal for an already-expired entry and volume rebirth reached inside the reused window, with zero original moves or lifecycle effects. This is a deterministic duplicate-work counterexample; the exact historical M3 conjunct remains unproven.
• Current a489a126 adds only five reviewed save-active proof/diagnostic/test/doc paths to b76092c1. Four closest controls pass with 23 assertions: the identical positive fails against unchanged b76092c1 at its original final publication deadline guard, while the correction observes four installed-native volume reads and commits active. Reached staged-receipt deadline, same-byte authoritative receipt rebirth and final volume rebirth retain switching/native-installed state and refuse before active rename. The diagnostic file passes 6 tests / 30 assertions, including closed fields and anti-forgery. The exact historical b76092c1 conjunct remains unknown.
• CLI typecheck, changed TypeScript lint, privacy and diff checks pass; current-base CLI typecheck also passes. Six existing complexity warnings remain. Initial style RED and the original-source counterexample are retained. Product deadlines and assertions were not widened.
• Earlier evidence remains scoped: 7 / 46 publication diagnostics; 62 / 330 family integration; 7 / 72 coalescing/drift; 79 / 232 maintained fixture; 94 / 1,041 binding; 19 / 59 preference/result capture; 14 / 391 process-policy diagnostics. The earlier compound positive reduced synthetic queries from 17,841 to 8,649 and volume inspections from 328 to 136. This is not a CPU or wall-time qualification.
• Exact historical 3fb9319d and 0782b588 hosted CI passed all 12 required checks. New-head checks are unearned until their own jobs complete; no historical CI is relabeled.
• The prior exact b76092c1 CLI-only build passed: child16292 exit0, no timeout/cancellation, recorded group absence and no scratch. Held-file readback binds CLI 09110943 and reused optimized compiler 4621a943 to that producing source. Its one admitted M3 trial passed the original publication-routing boundary, installed the native document, then refused at publication-save-active / legacy-state. A temporary active receipt exists; the authoritative journal remains switching/native-installed with held claims and pending null. The rejected conjunct is not proven. New fixed save substages and original deadline-guard attribution make a future failure more precise.
• Exact b76092c1 physical cleanup and its separate original observer passed: 580 paired successful command returns, 15 exact effects, no uncertainty, zero remaining fixture resources. Full cleanup before/after snapshots are byte-equal; independent originals match 5 stopped containers, 0 running, 14 networks, 27 volume births, 21 images and both tags. Known capture-owner returns require child exit and both EOFs without group-cleanup failure; no individual current PID/group-absence ledger was serialized. Physical restoration leaves the switching/native-installed journal unresolved.
• The matching 0782b588 M3 trial passed its saved TLS/SQL and known partial-stop sequence, then refused during publication-routing with reason legacy-state. Its receipt remains switching with native:null, held claims, no original moves and no native install. The saved timing is compatible with the 15s deadline but does not identify the actual rejected conjunct. Earlier REDs remain preserved.
• Exact 0782b588 physical cleanup and its separate original observer passed: 580 known successful returns, 15 effects, no uncertainty, zero remaining fixture resources. Original projections match 5 stopped containers, 0 running, 14 networks, 27 volumes, 21 images and both tags. Physical restoration leaves the switching journal unresolved.

Release Signal

• Commit / squash title: feat(native-config): retain legacy local routing during Compose adoption
• Release intent: feat
• Should this PR trigger a release signal? yes
• Equivalent release artifact: the Conventional Commit/squash title supplies the repository release signal. The release workflow owns publication.

Semantic Surfaces

• Does this change affect hack run, hack exec, env resolution, runtime-state reconciliation, or lifecycle shell/process behavior? yes
• Targeted tests: routing generation/execution/fixture/resolution, routing import, publication diagnostics and process-policy refusal controls.
• Matching contract: docs/reference/native-compose-adoption.md.

Risks / Follow-up

Maintained M3 two-worktree TLS/SQL adoption, lifecycle and rollback acceptance remains open. Current a489a126 still requires its own required CI, matching CLI-only artifact and separately admitted matching-artifact trial. Preserved 0782b588 and b76092c1 artifacts remain bound to their original failed trials; neither is relabeled as current. No engine retry or new build ran for this save-active correction. Broader mixed-corpus families and retired hosted/remote capabilities are not qualified.