diff --git a/doc/architecture/runner-rich-acp-capabilities.md b/doc/architecture/runner-rich-acp-capabilities.md
index cf1f93742fc..7c788248bb5 100644
--- a/doc/architecture/runner-rich-acp-capabilities.md
+++ b/doc/architecture/runner-rich-acp-capabilities.md
@@ -17,9 +17,13 @@ bound MCP names to provider-safe aliases, and rejects malformed native UI
 requests explicitly. Its four native question forms use an owned tool.
 
 Credential-free tests cover the new policy boundaries, real pinned native
-processes, clean runtime builds and Product E2E assertions. Pi v7 has passed its paid local hello case; Copilot v4 reached a paid question
-but failed continuation. The remaining authenticated current-profile cases,
-platform coverage and Daytona Product E2E are still required. No Daytona resources have been started for this task.
+processes, clean runtime builds and Product E2E assertions. Pi v7 has passed its
+paid local hello case. Copilot v4 has passed local hello, question continuation,
+plan approval and controller-restart recovery on the integrated `bd4cc29c3`
+runtime; file-edit qualification failed during session startup. The first Pi
+Daytona attempt created and retired one sandbox but failed before inference
+because its launcher omitted the build-owned remote artifact paths. Remaining
+authenticated cases, platform coverage and Daytona Product E2E are still required.
 
 The [harness priorities report](https://pages.paperclip.ing/2026-09-25-harness-priorities/)
 recommends Cursor and Copilot, followed by Pi, using the existing qualified ACPX
@@ -42,10 +46,10 @@ candidate scorecards from historical runtime policies.
 
 | Current candidate | Latest observed result | Remaining work |
 | --- | --- | --- |
-| Cursor v4, source `2e0b0fec0` | All three closures verify. Native instruction acknowledgement is enforced on new/load and automatic reload. Bounded todo projection preserves all IDs/statuses and marks shortened details. Exact-head Apex reports 5/5 | Final combined pack and daemon, authenticated current-profile Product tests, remaining platform and Daytona proof; paid tests await the account spend-limit decision |
-| Copilot v4, source `2042ca14c` | Fresh/load model-request capture proves native instructions reach the executable. Lifetime ownership prevents instruction-write races. Native session notices preserve bounded fields without inventing originating-turn attribution. Exact-head Apex reports 5/5 | The paid v4 question on combined source `807feaecf` displayed and accepted the answer, then rejected the new run’s registered agent-file root. The shared prerequisite now permits authenticated per-run context refresh while retaining session identity; rebuild and repeat continuation |
+| Cursor v4, source `2e0b0fec0` | All three closures verify. Native instruction acknowledgement is enforced on new/load and automatic reload. Bounded todo projection preserves all IDs/statuses and marks shortened details. Exact-head Apex reports 5/5 | Authenticated current-profile Product tests, remaining platform and Daytona proof; paid tests await the account spend-limit decision |
+| Copilot v4, source `2042ca14c` | Fresh/load model-request capture proves native instructions reach the executable. Lifetime ownership prevents instruction-write races. Native session notices preserve bounded fields without inventing originating-turn attribution. Exact-head Apex reports 5/5 | The continuation fix is paid-tested on `bd4cc29c3`: hello, semantic question/answer, plan approval and controller restart passed (six matchers each). File editing failed during `session.open`; diagnose before retrying. Remote and remaining platform qualification are open |
 | Pi v7, combined source `807feaecf` | Paid local hello passed all six matchers with one provider run, zero retries and zero invariant failures. Delayed exclusive-key billing stabilized at $0.000646464; all 46 observed owned processes retired. Exact-head Apex reports 5/5 | Native-question, agent-files, permission, planning, restart and remote qualification, then final-source checks. The historical hello allowed one automatic retry despite a zero-retry declaration; none occurred. New launchers must explicitly enforce zero retries |
-| All three, Linux/Daytona | The stored Daytona key and analytics endpoint work. A diagnostic Linux provider-pack build passes with bounded pnpm concurrency after the original out-of-memory failure. No task sandboxes have been created | Complete and verify the immutable Linux image from final integrated source, then retain sandbox-specific usage and cleanup evidence |
+| All three, Linux/Daytona | The stored Daytona key and analytics endpoint work. The immutable `bd4cc29c3` image is built and its installed manifest verified. Pi attempt 01 created one sandbox and failed before inference; cleanup and sandbox-specific billing were retained | Complete remote runtime admission and repeat the fixed Pi hello with a new reservation, then qualify the remaining remote cases |
 
 Cursor and Copilot ignore generic ACP `_meta.systemPrompt`; setting `AGENT_HOME`
 in the process environment does not make it part of model instructions. The v4
@@ -68,11 +72,21 @@ regressions. The broad failed attempt remains retained; it is not converted into
 a passing full run. On combined source `97217c531`, token gates, repository-wide
 typecheck and build pass; its broad test run completed with 14,052 passing tests,
 six failed tests and nine failed files (including collection failures). That
-archive lacked Git metadata, and failure classification remains in progress.
+archive lacked Git metadata. A filtered private install also resolved Vitest
+against unsupported Vite 6; four unchanged suites (116 tests) pass with its
+intended Vite 8 dependency. Other broad-run failures remain retained rather
+than being credited as passing.
 On `807feaecf`, typecheck/build and CI reproduced a test-fixture typing error;
 shared prerequisite commit `bb56af7fb` fixes it. These sources predate the latest
 review and continuation fixes.
-Final-source full checks and current-head CI remain required.
+On integrated `bd4cc29c3`, full build, recursive typecheck and token gates pass;
+the full test suite and runner verification remain in progress. The shared PR
+now includes test-only repairs for connection setup context and waiting for the
+startup row’s persisted PID; targeted tests, typechecks and token gates pass.
+The private embedded Postgres package required its declared postinstall to
+restore shipped dylib symlinks before live startup; a credential-free server
+health check and subsequent paid question passed with the repair hashed in
+their evidence. Final full-suite results and current-head CI remain required.
 
 The Copilot attempt increased the visible included-credit counter from 5 to 6;
 additional usage remained disabled at a $0 budget. Per-run USD is unknown.
@@ -95,6 +109,29 @@ coverage and cleanup remain recorded. The $100
 shared budget and provider allocations remain in force; one successful hello
 does not establish production qualification.
 
+The corrected Copilot question on `bd4cc29c3` passed all six matchers with two
+runs on the same provider session, no invariant failures and all 59 observed
+owned processes retired. Its included-credit counter moved from 7 to 8; the
+subsequent four-case campaign moved from 8 to 11. That campaign passed hello,
+plan approval and question continuation after controller restart, then stopped
+at file-edit startup timeout. No automatic retries occurred. All campaign
+processes retired and post-run runtime/dependency checks passed. Additional
+GitHub usage remained disabled at $0/$0; these account counters do not supply a
+native per-run dollar receipt. The plan and question journeys use authenticated
+Paperclip semantic tools; they do not establish a native Copilot ask-user
+responder.
+
+Pi Daytona attempt 01 used the previous `807feaecf` image and never reached
+provider inference. Exclusive OpenRouter usage stayed unchanged. The owned
+sandbox’s closed usage interval cost $0.000407164 in delayed sandbox-specific
+analytics, and the resource was observed absent throughout the cleanup window.
+The failed attempt and launcher teardown diagnostic are retained. The next
+image is built from `bd4cc29c3`, with digest
+`sha256:bff4c3f291087a0eeae37e4c20dd51857b92833eaf73ba3aca4157f37de1e109`.
+Its installed Linux provider-pack digest is
+`sha256:08ad9f6a6fb9c14c87e3bc5b20d01876986178c768433d709a45540e8d40a4be`.
+An image build and manifest check are not paid remote qualification.
+
 ## Registered persistent agent files
 
 Candidate ACP processes receive `AGENT_HOME` only from the authenticated