Darkstone de53: fresh restore accepted, startup UNKNOWN
One fresh remote original attempted the exact new de53 continuation. Both streamed restore gates passed, but startup recorded CDP UNKNOWN Runtime.evaluate before the first screenshot. Current numeric health and BAT were therefore not observed. No encounter action, native New Save, kill, reload, replay, late attachment, or ordinary host quit request occurred. Normal host quit qualification remains UNPROVEN.
Evidence: scratch/runs/20261108-darkstone-de53-encounter-2105/.
Only this note changes tracked source. No causal production code was changed.
Exact new selection and runtime
The run derives its pair from the 2025 final-save-recovery.json and its
existing gzip artifacts, rather than reusing the old FINAL1910 identities:
| File | Bytes | SHA-256 |
|---|---|---|
| characters.lpl | 1,342,324 | 2c78a17064029385dee4206c9314673debb4de05205ae63d2ff144b9e6081546 |
| game641d_6af0de53.sav | 3,204,341 | cb2ca8093b2ffe45133cda87e3eea9ceafad66fd82246684ec40dd97306e66fc |
The small run-local pair adapter preserves the accepted streamed uploader and
transaction. Both original and compressed source identities are validated
before upload, remote raw bytes are hashed, and the local acceptance receipt
and remote startup require gate both precede the one launch. No raw local
checkpoint stage exists. New selection tests refuse the old character SHA,
old character size, and old game filename before upload.
The accepted provider selection is preserved with immutable Git blob fallbacks.
The physical helper closure adds the repaired transport adapter and its exact
base source; the lifecycle-inclusive barrier verifies 527 providers,
59,640,526 bytes. runtime-pins.json records every provider source PATH/HASH or
Git object. The selected Darkstone canonical module remains 6cf120d0…;
there is no Q2 CPU/module/readiness substitution or copied media/module.
Actual consumer/request integration derives from accepted 2054. The guarded browser source remains exact 2535a4fe…; the repaired transport base remains 0e804950…. The quit default remains 55,000 ms, with no cap extension or 100,000 ms request. No quit request was reached in this run. Kernel 5371233b12d3a63e13a9768529af43e5a61b7ff1682b2d3c09e4db6a976e12d0 and logger 979b3a8b… are selected. Browser/Chrome logs and both kernel journal and command log use gzip from their first bytes.
Concrete startup and shutdown failures
At 21:09:13.747 UTC, first-browser-failure.json records the CDP evaluation
ACK timeout. There is no readiness result or screenshot. The later automatic
failure-close observation has apps: [], only the launcher text, and no native
input events. Historical 35/35 is not a current reading. No guest save or VFS
observation was attempted after UNKNOWN.
The automatic failure handler issued its own browser close, rather than an ordinary queued host quit. Chrome PID 6478 / start 11715 has actual kernel terminal reap 3042, status 0; Node independently reports code 0 / signal null. The close helper records ACK, drained true, no signals, and 13,043 ms. Both captured Chrome streams reached EOF before automatic cleanup. Driver 6470 / start 11641 has actual reap 3125, status 256 (exit 1).
All 314/314 registered tasks have actual terminal reaps, but kernel custody
is incomplete. Autoattached task 7535 / start 17834 / TGID 6629 / PPID
6533 was registered at sequence 2439 without a parent custodian; this
unresolved lineage persists despite its actual terminal reap 2446, status
0. kernel-drain.json has empty remaining/unreaped sets and one unresolved
lineage entry. The supervisor 6469 / start 11634 has actual parent wait
return code 1 and stdout EOF. These observations do not establish that the
lineage defect caused the earlier CDP timeout.
The existing driver's automatic failure-close path removed the profile
after the startup UNKNOWN and wrote cleanup.json with pending UNKNOWN.
Thus the owner's requested retain-profile-on-failure condition was not met.
No retained-profile claim or successful ordinary quit/cleanup ACK qualification
is made. The profile was already absent when terminal evidence was collected;
it cannot be recovered from this run. The old 2025 retained profile is untouched.
Ports were not listening, the runtime lock was independently acquired and released, and no owned-path FD references were visible. 49 FD directories were permission-denied. This is not a global zero-writer proof. Process absence is not an actual wait; CLONE_UNTRACED flag coverage and Boat exec nonleader/service-parent terminal waits remain outside the demonstrated scope.
Recovery and normal box stop
All 35 remaining regular runtime files, without an extension filter, were inventoried, retrieved, and independently hash-verified before the stop request. Selected unchanged source inputs are referenced rather than duplicated. No symlinks were found. All gzip originals are checked for size, SHA-256, and CRC; producer browser-log, kernel-command-log, and supervisor-output receipts are compared against the recovered bytes. Kernel command log is finalized at EOF.
The independent observable watchdog was prearmed at 21:07:03.843 UTC, with an immutable 25-minute cap 21:32:03.843 UTC. One durable UUID preceded the one create request. Box ID and initial provider expiry 21:33:10.174 UTC were recorded before runtime. The watcher stopped the box promptly after the unique evidence was retrieved and hashed; its own parent wait returned 0.
Final box: bx_k4pmwxjb / ARCHIVED, provider expiry archiveAfter: null. Stop receipt stop_eb31971153a514b8, completed, forced: false, error null, ended 21:10:32.001 UTC. No box was resumed or deleted.
Validation and remaining work
New pair selection/preflight and exact guarded consumer checks pass, including changed-source refusal. 1,110 predecessor evidence references were reread and hashed, reusing accepted 25 focused / 81 regression / locked build and kernel repair proofs without identical reruns. Two preparation invocations failed before allocation (an obsolete-kernel fallback lookup and the kernel inventory filename); their logs remain alongside the passing corrections. The startup wait failed and remains failed; it was not retried as a new launch.
Git is the source archive: the run records the Git SHA, selected provider
PATH/HASH or Git objects, and small owned-input/document patches, with reverse
checks. There is no source-tree archive, peer WIP capture, media/module copy,
local Chrome, forced guest save, private guest call/write, configuration,
backend, binding, clock, seed, public deployment, subworker, old-run deletion,
or RAM gate. Sampled /home free space stayed above 1,500,000,000 bytes;
continuous global-floor enforcement is not claimed.
Next work needs a separate assignment to investigate startup CDP UNKNOWN, unresolved autoattach lineage, and failure-path profile retention before another original attempt. This single authorized run is finished; the exact original de53 gzip pair remains unchanged. Full27, parity, audio and FPS remain open.