PR #21767 real dev verification, 2026-10-27
Main: 570d4b03ee (github/main)
PR: 270c54675db52b2e17ab12d593c358d662994d95

Setup: git worktree add ../main github/main; vp i in each checkout.
Background vp run dev, isolated homes. Main web/server: 8693/16733. PR: 5733/13773.
Real git repo /home/user/acp-verification added through web UI on both servers.
Real Codex gpt-6.1-sol selected through UI. No mocks, fixtures, or seeded conversations.

Main reproduction command:
node apps/server/src/bin.ts thread start --base-dir /home/user/main/.t3 --provider grok --model grok-build --title 'ACP placement main retry' /home/user/acp-verification 'Reply ACP_MAIN_OK. Do not change files.' --json
Observed real Grok 1.0.70 process PID 39293:
/home/user/.nvm/versions/node/v24.22.1/bin/grok agent --always-approve stdio 
/proc/39293/cgroup: 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-t3code.slice/app-t3code-agents.slice/app-t3code-agents-a29d81d75689.slice/t3code-codex-f4478b2e.scope/t3-acp-32857-b0f8b074c8cb4fe88f657e59bffd60dd
Result: lifecycle cgroup nested beneath server's scope, not this dev instance's owned agents slice.

PR verification: same CLI path, --base-dir /home/user/t3code/.t3.
Observed real Grok process PID 46995:
/home/user/.nvm/versions/node/v24.22.1/bin/grok agent --always-approve stdio 
/proc/46995/cgroup: 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-t3code.slice/app-t3code-agents.slice/app-t3code-agents-5c7566105688.slice/t3code-acp-bf15ffd2.scope
Result: native ACP scope under app-t3code-agents-5c7566105688.slice, separate from server.

Both branches reach real ACP initialize but fail authentication:
ACP agent did not advertise configured authentication method "cached_token". Advertised: grok.com.
No authenticated Grok inference is claimed.
After PR failure and a repeated launch, all observed agent processes and native scopes are gone:
observed ACP PID 46995 still exists: false
observed ACP PID 47154 still exists: false
observed ACP PID 47210 still exists: false
observed ACP PID 47260 still exists: false
observed ACP PID 47326 still exists: false
t3code-acp-bf15ffd2.scope
ControlGroup=
LoadState=not-found
ActiveState=inactive
t3code-acp-4a721e5d.scope
ControlGroup=
LoadState=not-found
ActiveState=inactive
t3code-acp-15f96dfa.scope
ControlGroup=
LoadState=not-found
ActiveState=inactive
t3code-acp-e13ec052.scope
ControlGroup=
LoadState=not-found
ActiveState=inactive
t3code-acp-1693f3c7.scope
ControlGroup=
LoadState=not-found
ActiveState=inactive

Neighboring UI behavior on PR:
1. Submit to Codex gpt-6.1-sol -> CODEX_PR_OK.
2. Ask provider to run sleep 120; UI shows Running sleep.
3. Click Stop generation -> Run interrupted / Stopped by user.
4. Send follow-up in same thread -> CODEX_RESUMED_OK.
Main real Codex turn also returned CODEX_MAIN_OK.

Blacksmith focused checks: 5 files / 131 tests passed.
vp test run packages/shared/src/AgentScope.test.ts apps/server/src/process/agentScope.test.ts apps/server/src/provider/acp/AcpJsonRpcConnection.test.ts apps/server/src/provider/acp/AcpSessionRuntime.processTree.test.ts apps/server/src/orchestration-v2/Adapters/AcpAdapterV2.test.ts
Includes real-systemd synthetic ACP regressions; these supplement, not replace, the app observations above.

Not verified: authenticated Grok turns and tool descendants, actual OOM/replacement failure in running app, no-systemd fallback, Pi/Muse inference, desktop/native mobile, macOS/Windows.
No source changes, commits or pushes.