[EHotwagner]

A reset submitted through the shared Host can finish while a following request is already materialized, so Process followed by Dispose cannot guarantee session retirement before another guest dispatch. Add LimitedInvokeAndRetire through the existing limited-request path: preserve the actual Process result, retire the whole session before public completion, and settle queued/held followers once without dispatch. Both Host facades guard reentrant mechanical effects against stale or disposed state.

Select coherent unpublished 0.4.0 metadata, classify against the actual published 0.3 pair once, and require explicit selected PackageConsumer versions. The current publisher consumes bounded originals from complete protected-source qualification; native required-check and installed joins retain their distinct acceptance boundaries. Historical publication/audit evidence remains immutable.

Validation:

• Independent exact-source reviews and final static/inert preflight, including focused producer, workflow, custody, baseline and installed refusal controls.
• Authentic trace preparation39004844417/a1: both model typechecks, 53 default and 16 selected schedules passed. Independent data-only review accepted all 71 generated files and their exact source-input join.
• Complete exact-head required CI and the normal 35-minute WASM source/model/package/browser qualification are required for this PR. Generation mode intentionally skipped that qualification; local CLR/model/native/browser execution remains held.

Canonical lineage: Game WASM-SHARED-01, existing .5-P2→S1 under the shared WASM foundation plan. This is the same outcome and dependency chain; publication, installed release acceptance and product pins remain separate.

The first PR head exposed one stale Project dependency range in Lifecycle.Tests; the correction updates only that range and adds its actual-version/refusal join to cheap preflight. The maintained static guard passes all 16 project ranges across 24 lockfiles. The original failed job is retained; its superseded ordinary validation was cancelled without claiming complete qualification.

The replacement full qualifier39006292599/a1 passed earlier contract/model/browser/package gates, then failed shared source compilation on ambiguous identity inference. The connected correction annotates all source/installed control boundaries, fixes singleton command accumulation with an omission control, and moves existing source/installed build and in-memory checks before costly stages once their exact inputs exist. Same-job source/tree/version/status/assembly guards protect reuse; the full model/browser suites and 35-minute limit remain. Original failure and bounded-log gap are retained; fresh exact-head complete CI remains required.

The early source stage at39008574356/a1 then exposed a conditional-record parsing error and an unconstrained projection search; the follow-up parenthesizes the field and explicitly types the effect searches. Same-head shell lint39008574510/a1 found mixed mkdir parent/mode flags, now separated while retaining fresh private-root refusal. Both original failures are retained; no later model/pack/browser work ran in that attempt.

Follow-up39008813238/a1 built source successfully, then its CLR callback control expected an incomplete refusal. The corrected control asserts the existing complete retired-owner/disposed refusal and unchanged state/mechanics/results; runtime behavior is unchanged. The actual failed assertion is retained, with fresh full qualification still required.

The complete new terminal-control cohort was then reconciled with current profile contracts after39009007033/a1 exposed BAR setup assumptions. One typed ready fixture derives profile ABI and asserts successful idle setup. Explicit SC2/BAR scenarios retain all applicable reentry coverage, BAR Busy settlement/no-dispatch behavior and a fresh subsequent terminal path. Full-cohort independent source review passed; actual repaired runtime/full qualification remains required.

The two original failed generation operations retain their outcomes and evidence. No full descendant-settlement claim is made from the successful fresh hosted job.