research(track-a): prove runtime reacquisition stability

[blakinio]

Draft-only Track A runtime research dispatch from exact main@8fca1c3eee453d0d4ef8a47e0f15c9dbae491b45.

Hypothesis: after clean task-owned restart/relogin, the exact-build structural world observer/read path can be reacquired from fresh PID/PIE/runtime state.

The task incorporates the #289 safety corrections: credentials must not be job-scoped into persistent child environments, and cleanup must verify namespace/display ownership. Historical #290 login procedure is revalidation-required input only.

Promotion authority is coordinator PR #300. No owner-funded Codex/API use is authorized.

[blakinio]

Coordinator disposition at current head 0270b1f3b6e75c995649b405758f058bae026c88: RETURN_FOR_EVIDENCE.

The namespace/credential/cleanup design is materially improved and standard CI for code-bearing head 9d5734ced2155cf01ab6cbdfabfb2eb2707b7152 is recorded green, but no restart/relogin semantic execution has occurred. Coordinator recheck of runtime run 31881287155 still shows only completed luacheck/cppcheck; no self-hosted reacquire job has materialized. Separately owned P0 run 31880617510 remains queued in the same official-client-re-runtime concurrency lane, so bypassing/cancelling it is not authorized.

Required evidence before reconsideration:

1. generation N structural IN_GAME/read proof under exact client fence;
2. task-owned clean teardown with namespace ownership verified;
3. fresh client generation N+1 with new PID and PIE base;
4. structural Worldmap/read-path reacquisition after relogin;
5. persistent child environment check proving credential variables are absent;
6. WARP/SOCKS confinement and cleanup proof;
7. negative-control baseline and terminal exact-head CI.

Until those execute, restart/relogin stability, bridge session lifecycle and R4 semantics remain UNKNOWN. Historical one-off movement or process survival does not satisfy this gate.

[blakinio]

Coordinator revalidation input (PR #300): the prior “newer child required” prerequisite is superseded by exact evidence.

FACT:

• launcher recovery run 31742909649 / job 94590422368 reached Tibia: Unknown -> NotInstalled and did not auto-install a child; this is an install-state result, not proof of a newer SHA;
• official-manifest reconstruction run 31745572204 / job 94599228206 SUCCESS reconstructed 1634 package + 7094 asset entries, 8728 files / 683565384 bytes, with bin/client size 51965216, SHA-256 e6c244bd39fe2e0632f6f000efd3147164696efa8e901718668e0442325ff7fe;
• later live-world run 31806312967 / job 94785974126 SUCCESS verified that same SHA before a reversible structural movement probe; Worldmap strip counts changed 0,33,88, with forward/inverse frame deltas 146599 / 150668 pixels.

BOUNDARY:

• keep PR research(track-a): prove runtime reacquisition stability #303 fenced to its existing exact build first; no client-update step is required unless the fresh task-owned reacquisition independently proves a build mismatch/rejection;
• do not reuse historical PID/PIE/object addresses;
• do not bypass/cancel the serialized P0 lane. Run 31880617510 remains queued, so research(track-a): prove runtime reacquisition stability #303 should stay waiting until that lane releases.

Durable coordinator evidence:
docs/agents/evidence/OTC-20260815-track-a-promotion-coordination/20260815-login-update-revalidation.md
docs/agents/evidence/OTC-20260815-track-a-promotion-coordination/accepted-historical-login-procedure.md
Coordinator commits: 9ae9eeeecc2414a5d972fa84ba55f5e2bea841c7, d582548ba7128d004f5d1dc41f216f2a2850022e.

[blakinio]

Coordinator disposition: CLOSE_SUPERSEDED / historical evidence only.

Current trusted programme state has moved to the canonical persistent-runtime admission model and the sole current physical RUNTIME lane is PR #358. #358's fresh read-only reconciliation on synology-otclient-01 proved lease status absent, lease generation 0, canonical registration ABSENT, and canonical_bootstrap_required without observing or mutating a client/display/network session.

PR #303 is based on stale main@8fca1c3eee453d0d4ef8a47e0f15c9dbae491b45, its task checkpoint has not advanced since 2026-08-15 21:36+02:00, and it embeds historical runtime values such as task display :115 and SOCKS 25354. Under current Track A governance those values are not current authority, and this Draft must not remain a concurrent physical-runtime owner beside #358.

The branch and its evidence remain preserved for historical/non-authoritative research reference. Closing this PR does not reject previously recorded experimental observations; it prevents stale workflow/runtime ownership from being resumed or mistaken for the canonical session. Any still-useful bounded evidence must be explicitly revalidated/promoted by the coordinator under current main. No physical cleanup or runtime mutation is authorized by this closure.