feat(config): preserve linked-worktree legacy adoption identity

[roodboi]

Verified exact-root linked Git checkouts can prepare, switch, execute and roll back the static legacy Compose adoption slice while retaining their original container, network and named-volume identities. Private version-two receipts bind raw Git pointers and held administrative/common/primary directory identities; existing directory-checkout version-one receipts are unchanged.

Relevant managed-env, dotenv, typed local and alias inputs in the inherited primary scope refuse by filename before effects. Explicit inheritance opt-out, CI and slim execution retain their existing exclusions. Successful managed/generated inheritance remains open; ordinary import preview still refuses linked .git files.

The maintained native-compose-adoption-worktrees scenario uses two real linked checkouts and distinct original PostgreSQL volumes/rows. It checks inherited-input refusal separately from static adoption, partial-stop recovery, retained-container execution, stopped-container limits and independent rollback. Exact cleanup rechecks the prepared daemon and captured resource identities; failed fixtures preserve private source/recovery evidence. The fixture's client worker mounts the exact original named volume read-only, readiness requires SQL usability, and marker seeding occurs only before adoption.

Validation:

• Frozen product c3dc948c: build, full typecheck/check/privacy, and whole tests passed: 3,273 pass, 73 skip, 0 fail, 18,436 assertions across 315 files. CLI tasks ran fresh; DB tasks reused their shared cache.
• Final fixture checkpoint a581c0a4: 92 focused tests, 399 assertions, 0 failures; CLI typecheck, changed test lint and staged privacy passed. All product/compiler source bytes remain identical to the qualified frozen product.
• SQL initialization and aggregate-inspection lifetime regressions fail with prior fixture behavior and pass with the final bounded helpers. Shared owner deadline/output/cancellation/reaping semantics remain unchanged.
• Maintained actual native-compose-adoption-worktrees passed on M3/macOS with a Linux Docker daemon: 1 pass, 0 fail, 0 skip in 60.6 seconds. Two original SQL stores and exact resource identities survived inherited-input refusal, partial-stop failure and repair, adopted execution, stopped-container limits and isolated rollback without reseeding. Exact owned cleanup and a separate fresh full inventory restored the original engine baseline. Earlier failed fixture runs remain private evidence and are not counted as acceptance.
• Reconciled fc95dedc onto next at cde49ab8. Task-owned product and fixture bytes match the actual-qualified checkpoint; shared recovery retention and all current scenario registrations are preserved. Fresh build (718 modules), full typecheck/check/privacy, seven changed-file lint checks and CLI-reference generation passed. CLI tasks ran fresh; DB tasks reused their shared cache. The final affected suite passed 454 tests, 3,145 assertions, 0 failures across 14 files, including adoption, private generation/recovery, saved commands, after hooks, probe lifetime and harness retention. The unchanged local whole suite and M3 live run were not repeated after reconciliation. Independent integration source review passed.
• All 13 exact-head hosted checks passed. Hosted CLI tests ran fresh: 3,510 pass, 104 skip, 0 fail, 20,715 assertions across 330 files; neither CLI nor DB tasks used cache. Hosted Linux Docker E2E passed all 23 scenarios with no skips, including the maintained two-linked-worktree adoption scenario in 23.5 seconds.

Full NC04 remains open for successful typed/managed inheritance, generated-source provenance, advanced lossless mappings, recreation and application migration. Publication remains cooperative and requires the upgraded launcher; this change does not claim an atomic freeze of external editors/engine mutations or universal old-client fencing.