[ScriptedAlchemy]

Fixes #4433. Parent link: none (stack S5 link 1, base master).

Problem

diagnostics_producer.rs copied each producer run into a process-global LAST_RUNS: Mutex<BTreeMap<PathBuf, ..>> with no removal path; availability reads joined it by pathname, so a successor owner at the same path would report its predecessor's run.

Fix

• New TypeScriptProducerStatusV1 + TypeScriptProducerStatusHandleV1 (immutable Arc snapshot behind a lock). One handle is created per project owner at open, passed to the producer (via TypeScriptProducerStateV1::new) and to the owner's OwnedPrimitiveRuntime (via ProductionPrimitiveOpenRequestV1).
• typescript_diagnostics_availability and the two diagnostics-absence problem builders read from the owner's handle.
• Deleted LAST_RUNS, last_runs, last_record, last_producer_run, record_producer_run. Teardown retires the status with the owner; a superseded producer can only publish into its own handle.
• Reset-required routes (no producer) get a fresh empty handle, i.e. "not run".
• Per-tsconfig checked/failed/no-compiler/NoTsconfig distinctions are unchanged; findings still come from generation-bound publication only.
• Not added: an attempted-generation field (Published already carries the generation; nothing reads another).

Verification

• bazel test //crates/tracedecay-application:unit_test --test_arg=diagnostics_producer: 5 passed, incl. new a_successor_owner_does_not_inherit_the_predecessors_status and a_status_handle_publishes_to_its_owner_only; existing primitives::runtime diagnostics tests pass.
• bazel build --config=clippy //crates/tracedecay-application/... //crates/tracedecay:all succeeds.

🤖 Generated with Claude Code

Retained Work configuration follow-up

The retained Work configuration repair from #4546 applies to the same five source/test files here, which were byte-identical before the repair. This follow-up carries those exact reviewed file versions into this branch; it does not claim a separate observed CI failure on #4545.

When a route is reopened after a sibling commits new configuration, Work registration now refreshes policy, topology, routing, and evidence admission under a captured-incumbent and canonical current-configuration fence. Exact store, actor, grant, scope, and Work authority remain required. The retained fan-out recovery view receives the admission update while preserving its owners and signal.

The real route-eviction/compiler journey keeps its existing assertions and budgets and additionally checks stable grant identity, current registration, stale and sibling refusal, and retained current authority after refusal. Pinned formatting, whitespace checks, normal pre-commit/commit-msg hooks, and independent source review passed. The transplanted blobs exactly match the reviewed Work repair. Complete native execution remains a hosted CI requirement because local disk and memory limits prevent the full build.

Configuration publication race follow-up

A changed retained Work runtime now verifies and publishes its configuration under the configuration store's existing canonical writer lane. The store reads durable current state through a registered immediate transaction, revalidates its retained authority, and invokes a synchronous registry transition before releasing the lane. The captured-incumbent comparison remains in place to prevent a delayed registrar from replacing a newer installed runtime.

The registry transition only reconciles an existing component; missing, reserved, closed, or fenced slots are refused. It performs no new owner build or asynchronous wait. Complete routing and recovery admission are refreshed together. The read-only transaction is dropped synchronously after the callback, using the existing rollback-before-writer-release contract, with no post-publication await.

Initial and unchanged retained pins preserve their existing lifetime. Work settings retain their daemon-restart semantics: a durable commit after successful publication is allowed, while a superseded candidate cannot claim to be current at publication.

The existing real route-eviction/compiler-status journey now pauses candidate B, commits C through the actual configuration surface, resumes B and requires its typed refusal with installed A unchanged, then installs and verifies C. Existing assertions and budgets remain intact. Pinned formatting, whitespace checks, normal commit hooks, and independent source/authority/lock-order review passed. The complete native journey was not executed locally and must pass hosted CI.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 22182a8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR