Q2 transitive closure and conditional native progress
Work begins at Git base 897f6547f, using the repaired published
f017d680e v2 preparer and its exact published authorities. Existing providers,
module selection, fresh runtime pins and allocation remain gated on Q31535's
final published RELEASE STOP. No existing provider has been edited.
The new offline regression imports the actual writer setup chain using only
an in-memory declared-provider candidate derived from the SHA-authenticated
1495 manifest. Each of seven imported providers is individually removed and
SHA-damaged; every case refuses. An undeclared binary read also refuses.
The owning-load adapter is authenticated against published e65895936.
Actual generated caller source compiles with explicit custody selection and
writer setup opt-in; default and unknown custody selections refuse. No runtime
pinset is produced by this control.
Actual composed-caller real Worker controls pass for primary 3e491c08 and
compatibility ecb45716, including admission, pending cancellation, signed
health -1, loss98, independent UP and sticky terminal behavior. Twenty-one
actual generated request controls pass without fabricated ACKs. The required
locked build passes. These authored controls are not native coverage proof;
nativeQualification remains false and all-writer/alias/peer/raw-host/parse/ABA
coverage remains UNKNOWN.
Exact predecessor bx_rup3afnj, UUID
fcb86e70-6cdf-4166-8a5c-c03951aa45fc, is API ARCHIVED under completed unforced
stop_4f9d8efe9188c04c. Retained physical drain proves124 owned/reaped,
closed ports, absent profile and no writers. Browser EOF and kernel reaps remain
separate; separate Node command EOF remains UNKNOWN. Initial expiry was
14:32:42.819Z; final expiry is not returned. Live inventory shows only the
inherited main box, with no1535 runtime.
Q31535's two owned paths (q3-current-module.cjs, q3-native-prelaunch.py) do
not intersect retained1495 Q2 providers. The two Q3 providers actually included
are q3-input-wire-observation.cjs and q3-native-launch-client.py. Any future
closure change still requires exact published authority after release.
Evidence is in scratch/runs/20261109-quake2-transitive-closure-native-progress-1555/.
Git and small binary patches are the source recovery mechanism; no source,
media or module archive is created. The bounded offline work is complete. The exact Q31535 final published
RELEASE STOP is still absent at14:28Z, so the task stops at that concrete gate.
No fresh runtime pins, module selection, fixture/cancellation run, original,
input, screenshot or allocation occurred. Guard defeat and onward-door
progress remain unverified. Box ID/state/expiry/stop receipt are
NOT_CREATED/NOT_APPLICABLE for this task; the inherited main box was not used.
The new run-scoped staged-root checker was exercised in memory: the complete actual setup passes; a missing adapter and disabled writer flag refuse. The actual caller cancellation suite and the independent UP-failure control pass. The runtime wrapper is prepared to execute this check against all transferred providers before Chrome, but it has not been run in a fresh box.
A run-input release-detector error was found before allocation: a loose search matched Q31535's OWN line quoting Q21495's release. The actual create assignment now requires Q31535's own anchored RELEASE STOP line. Executing that assignment refuses the actual board, quoted OWN and coordinator lines; only an exact synthetic release is accepted in the offline test. The earlier loose-match record is retained as an error, with an explicit corrected record. No release, pinset, API allocation or native claim was based on it.
The tested regression is published on main as ab545221c; strict SSH pull and
push succeeded. Existing Q2/Q3 providers and the repaired explicitv2 closure
remain untouched. The remaining prerequisite is Q31535's exact final published
release, followed by the authorized fresh closure validation/staging and sole
native fixture/cancellation test. Any original still requires that fixture to
pass. No historical cancellation proof qualifies a fresh run.