[EHotwagner]

The installed 0.6 qualifier could pass its consumer runtime and then fail evidence collection because its collector still used 0.5 package, Fable-module, SDK and receipt paths. Original installed39088631914/attempt1 remains failed on both feeds: each consumer passed36 browser cases, recorded runtime0/collection1/directcleanup0 with descendants unproved, and never reached the selected supervisor.

Derive the collector's exact current namespace once from audited tracked version.props, without an environment/CLI version selector or historical fallback. Apply it to the complete consumer/selected dependency-original, Fable, cache, SDK, merge and authenticated receipt joins. Preserve mandatory evidence, byte joins, role/context allowlists, first-cause behavior and every existing cap. Published P8a5e63ba, its packages/SDK, transaction and runtime remain immutable; the repaired collector and binder belong to the selected qualifier Q.

The finite P-to-Q audit admits exactly ten leaves: the prior seven, the maintained collector and its existing test file, and one exact new Atlas capture. All producer/runtime/workflow/version.props/SDK/promotion/pin inputs outside that closure are P-identical. No publisher, package replacement, broad source prefix or installed operation is selected by this PR.

Validation: independent exact source/Atlas review PASS at2e764dff2021d368d23041e9fd84c49b3514f89b; actual complete P-to-candidate audit equals the ten-leaf allowlist;36 prior Atlas records retained byte-identically. Clean inert source-mapping/workflow/18collector/37promotion controls pass in2.69seconds with one CPU and about42MiB peak RSS. Real CLI consumer→merge→selected→assemble fixtures and actual EXIT-trap→collector controls cover current package-member/SDK joins, hostile old-version environment, stale/mixed cache and namespace refusals, mismatched authenticated SDK, failure precedence and finite source/mode/delete/rename/link refusals. These fixtures execute no runtime or downloaded code.

Original preflight dirty-tree/local-address-space refusals and failed installed evidence remain retained. Fresh hosted source qualification is still required under the unchanged35-minute route. A later exact served-feed installed operation requires separate selection and genuine both-feed evidence; last accepted installed remains0.5. No installed0.6, native/image/product, descendant-settlement or old-timeout-cause claim follows.