[raiseCatError]

The cross-profile live test could begin a size probe before processing its previous command's completion, and could accept an older redrawn size row. A natural trace accepted a completed 60-column probe while expecting 50 columns. The test now confirms its uniquely tagged STATE command's durable completion and checks geometry from each tagged probe's own completed journal record.

Adds a canonical regression that runs the genuine host-profile test with event-driven completion delivery gating. The same gate reproduces the hosted journal-timeout message on unchanged original dev; corrected synchronization passes. This establishes a pre-existing reachable harness mechanism, while the historical CI failure's exact causation and natural frequency remain unconfirmed. No production or shared-helper behavior, dependencies, original timeouts, skips or expected geometry changed.

Validation: focused live fullscreen/resize/interaction tests, deterministic old-source red / corrected-source green, bounded six-case two-worker tracing and independent narrow review passed. Full canonical npm run verify: PASS, zero failures; existing skips and Arcade disposal TODO unchanged. Review findings on explicit readback diagnostics, child teardown margin and retaining compact failure traces are addressed.

Physical Ghostty/Zed QA remains NOT RUN. Existing user sessions remain alive. This does not close the other attribution/read/input risks in #473. Runtime is identical to merged dev c690de0; final merged-source benchmark results and limitations will be added to the performance handoff. No automatic merge.

Refs #473
Refs #505
Refs #507
Refs #509

[raiseCatError]

Stabilization status: exact PR head a57568be5e8b11cf927a00371c1b4783cadde53d passed normal PR CI40521828253. Full local canonical verification, focused live tests, deterministic old-source red/new-source green and bounded concurrent controls passed. Independent review findings are addressed; no production/shared-helper changes.

However, comprehensive CI40521955602 FAILED macOS3/3 in the existing inputOwnershipLive.test.ts zsh waiting-read case: timeout for ANSWER=hello, with the screen showing a read still running and a line held for approval. This is within #473's unresolved input-ownership family; it is not dismissed as harmless, attributed to the test-only patch, or covered by the host-profile correction. Fedora, Node22, Quality and both timing jobs passed, but the complete reliability gate is not green. No merge or hosted retry of these validation runs followed the failure.

The same read case passed once alone and in six bounded two-worker instrumented local runs. One permitted hosted diagnostic is now running at separate branch diag/input-ownership-20261027, head 901fe7465372216b5721291f59ccaa656d85805e: 40549379269. It captures only private-fixture lifecycle/probe metadata for six bounded target cases and the same complete shard, retaining failure logs/artifacts. Never merge this diagnostic branch or workflow replacement. A green diagnostic rerun alone will not establish a fix.

PR513 remains unmerged. Final merged-source benchmark timings remain paused because the comprehensive gate is unresolved; the separate actual merged-dev functional Unicode/raw-byte/copy/resize/Ctrl+C stress passed. Physical Ghostty/Zed QA remains NOT RUN; existing user sessions remain alive.

[raiseCatError]

The focused host-profile correction remains OPEN / UNMERGED in PR513, exact head a57568be5e8b11cf927a00371c1b4783cadde53d. Normal exact-head PR CI40521828253 passed. Complete local canonical verification, real fullscreen/resize/combined interaction tests, deterministic original-dev red/corrected-source green, bounded concurrent stress and independent review passed. No production/shared-helper change was made.

The complete reliability gate remains FAILED: comprehensive40521955602 failed the existing macOS3/3 inputOwnershipLive.test.ts zsh waiting-read testcase, timing out for ANSWER=hello with the read running and a line held for approval. Other platform shards, Node22, Fedora, Quality and both timing jobs passed. No retry of either validation run was requested.

The single permitted hosted diagnostic40549379269 passed all six bounded two-worker read cases, the full original shard and process-leak checks. Its89 captured OS samples all contained foreground processes and modes;41 on-demand look results were visible/hidden. These are passing controls, not the missing trace from the failing run, and do not establish a fix or historical cause. Local isolated plus six concurrent read controls also passed. The cause of this additional #473-family failure remains unresolved; no speculative runtime correction or deadline/coverage relaxation is justified by the captured evidence.

Diagnostic source/artifacts remain preserved at branch diag/input-ownership-20261027, head 901fe7465372216b5721291f59ccaa656d85805e, and T7 evidence root /Volumes/T7Tmp/ai-dev/nmsh-stabilization-20261027. Never merge that diagnostic branch or its workflow replacement. The focused PR contains only three test files and two documentation files. Original dev remains c690de055daeb7b33ed8b5e302ef01133b3e55b4; no implementation PR integration was repeated.

Final median/p95/RSS/CPU/startup/idle benchmark timings remain NOT RUN, because the comprehensive gate is not satisfactorily resolved. Built actual merged-dev functional stress did pass exact Unicode output/raw bytes, draft/input order, scrolling/copy, fast resize and Ctrl+C followed by another command. The original matched measurements and +6.7% history-typing p95 / +2.3% deletion p95 differences remain retained without causal attribution. Measurement workloads, CPU/idle extensions, provenance and plan are preserved for resumption; no fresh performance gain or unmeasured startup/idle result is claimed.

Physical Ghostty/Zed QA remains NOT RUN. Keep #473 and performance issues open. Existing sessions/stashes/unique work are preserved; only clean task-owned disposable worktrees/builds are removed after evidence preservation. No master/release/tag/deploy/Homebrew action occurred. Next step requires capturing the failing read/ownership decision (exec state, OS probe and routing) in its failing environment, not another uninstrumented lucky retry.

[raiseCatError]

Follow-up evidence, separate from PR validation: remote dev remains c690de055daeb7b33ed8b5e302ef01133b3e55b4; PR #513 remains OPEN/UNMERGED at unchanged a57568be5e8b11cf927a00371c1b4783cadde53d. Normal exact-head PR CI passed; comprehensive40521955602 remains FAILED. No validation retry, production change, timeout increase, skip, merge or release action. Physical Ghostty/Zed QA remains NOT RUN.

A fixed original-vs-merged two-worker comparison ran locally and once on hosted macOS/Node26.12.1: diagnostic40553536294. Both natural controls passed. Both controlled runnable probe-observation cells reproduced the exact waiting-read ANSWER=hello timeout. Ordered metadata traces verify submission/actual command PTY write, first key before exec acknowledgment, visible look results without reader inference, draft + Enter held for approval, and later genuine line-read inference. Only the submitted read command was written to the PTY (51 bytes); no answer bytes or shell completion followed.

The unchanged ownership code returns visible from echoing modes without proving a reader. Enter without reader evidence quarantines the line; a later request does not auto-send approval-held text. This establishes a pre-existing reachable inference window, not the untraced historical cause, its natural frequency, a regression attribution or a justified fix. The controlled samples are explicitly synthetic. Unknown-command text still cannot unexpectedly execute. Independent code/diagnostic/evidence review completed; diagnostic review findings were addressed. No production/test-acceptance correction was invented, and immediate-answer coverage remains intact.

Diagnostic head 929eb16c2b9b0c455b7ef3858c62c16f5682003e, branch diag/input-ownership-matched-20261027, must NEVER merge. Its green job means fixed evidence collection completed, including expected controlled testcase failures; it does not satisfy #513’s gate. Targeted two-worker hosted concurrency is not a fresh full-shard validation. The prior intermittent failure history and prior passing diagnostic shard remain relevant.

Next ownership step remains a natural failing lifecycle/probe/route trace, followed by a correction only if the evidence demonstrates a defect. No automatic forwarding of quarantined input or green-until-lucky CI loop.

Performance measurements have also completed independently; full results and caveats are in the concurrent #473/#505/#507/#509 handoffs. Physical QA remains NOT RUN.