**Historical pre-fix report.** The [completed initial qualification and candidate regression results](https://github.com/githubnext/ace2/issues/176#issuecomment-6037405361) supersede the in-progress status below.

Initial deployed pilot evidence on October 7, using source `ad3f7313ea18f2fd9c5f9e3fb2ca9c5b1df67861` and the dedicated real Cloudflare `ace-channel-pilot` service:

| Scenario | Status | Evidence | | --- | --- | --- | | T1: real model and local shell | Passed | A real provider/model run used the actual hosted-channel/workspace route and executed its shell work locally. | | T3: actual lane file read/write | Passed | The hosted run read and changed a file in the real local lane; work remained on the workspace. | | T4: detached, quiet in-flight shell | Failed — #183 | A 75-second silent shell kept running locally after idle hibernation reconstructed the hosted runtime and pi recorded the tool as interrupted. The workspace socket remained connected; there was no deploy or deliberate disconnect. | | T5: Kill after the call was orphaned by hibernation | Failed — #183 | A 120-second shell outlived pi's interrupted result and the agent's final reply. Kill returned successfully while the old shell and its sleep child remained alive. |

The #183 reproduction started the shell at 11:35:03 UTC, reconstructed the runtime at 11:35:38 UTC and observed the original shell's end marker at 11:36:18 UTC. A later wait was interrupted again after another recovery. The model avoided replaying the original command; this is not evidence that arbitrary side effects are safe to continue across that loss of pending-call state.

Bounded replay, process and runtime-generation artifacts are retained by the pilot operator. #183 is a child issue of this pilot and the first blocker linked from #13; it is also recorded in #5.

T5 started PID `20265` (sleep child `20268`) at 11:37:09 UTC in generation `fdc6b613:6`. Pi reported interruption roughly 30 seconds later; the model finished without retrying at 11:37:38 UTC. Hosted Kill at 11:38:12 UTC returned successfully with pi already idle, but both original processes remained alive afterward. The operator retained the T5 replay, process checks, Kill timestamp and shell marker evidence.

This is a demonstrated failure to cancel the call already orphaned by hibernation, not proof that ordinary Kill fails while a current active workspace call remains attached. The service busy/residency fix is being prepared. The complete evidence matrix and remaining upgrade, interruption, cancellation, idle and second-machine results will follow; no acceptance checkboxes are changed by this partial report.

October 7 deployed qualification update: the initial one-machine pilot and #183 regression checks are complete. [PR #186](https://github.com/githubnext/ace2/pull/186), head `4d534550b0a36d9c8272113018c71c0b9b199830`, is ready for review and unmerged. [GitHub CI passed](https://github.com/githubnext/ace2/actions/runs/37617302852) at 11:55:09 UTC; `bun types` and `bun run ci` also passed in the Ace operator channel.

The dedicated services are [ace-channel-pilot](https://ace-channel-pilot.iamnbutler.workers.dev) and [ace-directory-pilot](https://ace-directory-pilot.iamnbutler.workers.dev). Initial source was `ad3f7313ea18f2fd9c5f9e3fb2ca9c5b1df67861`. The service fix is the one in PR #186; the final deployment is `b58efd2d-579e-4c70-a9aa-c326bca1e086`, using the original service entry point with the temporary reset wrapper removed. The same hosted channel was retained throughout; existing non-pilot services were unchanged.

| Scenario | Observed result | | --- | --- | | T1/T3: real model and local lane tools | `anthropic/claude-sonnet-5-5` executed shell work on the local Mac and read/wrote an actual lane file. | | T6: deployment persistence | Full protocol replays and channel info, including usage, matched before/after service deployments. Earlier histories are exact prefixes of later histories. No replacement channel or store reset. | | T4/T5 before fix | Quiet work was interrupted by hibernation while its shell continued; subsequent Kill could not reach the orphaned call. Tracked in #183. | | T4 after final fix | A detached silent 75-second shell completed once in the same generation, with no client watching, interrupted result, retry or workspace drop. | | T7: idle afterward | After the run ended, the cell hibernated; a later successful tool used a new generation while the workspace socket survived. This observes residency/hibernation, not a billing benchmark. | | T8/T9: ordinary Stop/Kill | Both shell and child exited within three seconds; no completion marker appeared, pi recorded abort and the channel stayed usable. | | T11: delayed Kill regression | A 120-second silent shell had no clients for 56 seconds. Kill came from the original generation, removed shell and child within three seconds, and no completion marker appeared after the original deadline. | | T10: plain deploy during shell | The 60-second shell completed once across deployment. **No actual runtime reset was observed**, so this is continuity evidence rather than reset-recovery evidence. | | T13: actual reset during shell | Temporary pilot-only `ctx.abort()` caused a real socket drop and reconnect in about one second. The old processes were gone within five seconds, no end marker appeared, and pi recorded interruption without replaying the unsafe command. Prior history stayed intact. | | T14: actual reset during streamed model reply | Reset after the first streamed delta retained the stopped partial reply and resumed with a fresh complete reply. No tool side effects occurred; prior history stayed intact. This observed recovery behavior is not being filed as a defect without an established contrary expectation. | | T15: clean host shutdown/reconnect | With the workspace host stopped by SIGTERM, human chat persisted and tools returned “The workspace is offline.” Restart restored the connection and successful shell work. This is not a physical sleep/network-partition test. | | T16: unwrapped final deployment | The reset wrapper was removed; unchanged history and a successful shell run were verified on the final original service entry point. |

To repeat #183's regression: dispatch a silent shell longer than the former hibernation window, close all ordinary channel clients, confirm one start/result in the same generation, then repeat with Kill after at least 56 seconds and inspect both parent/child exit and absence of an end marker after the original deadline. After the run ends, verify an idle cell can hibernate and reopen. Genuine-reset checks require the separately identified pilot fault injection; a plain deployment must not be reported as an observed reset.

Still open: review/merge #186; another actual physical client/teammate machine, including attributed collaboration and pilot-directory discovery; physical workspace sleep/wake and network partition/recovery. No second host was simulated with another context on this machine. Keep this pilot open for those checks. The isolated pilot deployment, channel and workspace connection remain available for the next acceptance pass.