You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: realign rebase-casualty files with upstream master after the 8-PR merge wave (#142)
The 2026-06-11 rebase (#141) onto a master that had just merged our 8
give-back PRs left several bad conflict resolutions:
- packages/adapters/codex-local/src/server/runtime-config.ts was
TRUNCATED mid-function (TS1005) -> Docker build on main failed, no
image rolled. Restored to upstream (paperclipai#7919 is merged; zero delta).
- server/src/routes/issues.ts + heartbeat.ts and their test files kept
pre-revert paperclipai#7678 code and missed paperclipai#7855 scoped-wake semantics.
Restored to upstream (no documented fork delta in these files).
- ui/src/pages/IssueDetail.tsx + ui/src/lib/issue-chat-messages.test.ts:
same paperclipai#7678 remnants, restored.
- tools/agent-shim/stdout_framer.go: dead code upstream removed during
the paperclipai#7934 review; deleted here too (main_test.go realigned).
Preserved fork deltas untouched: cloud_tenant (middleware/auth.ts,
live-events-ws.ts), seed CLI, claude-local execute cwd fix (paperclipai#5823 still
open), workspace-restore-merge socket guard, Dockerfile plugin build,
paperclipinc registry names, workspace-init, fork CI workflows.
Verified: server build exit 0 (the exact CI failure), 58 server tests,
87 codex-local tests, 24 ui tests, go build+test agent-shim all green.
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: doc/execution-semantics.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -285,7 +285,6 @@ Plain text is not assignment. Writing an agent's name, role, or team label in a
285
285
286
286
Pause and tree-control previews should make the same distinction visible. They should report whether the affected subtree contains live running work, queued wakes, agent-owned work, or only human-owned/static issues, so a pause after a handoff does not look like it interrupted agent execution when no agent execution path existed.
287
287
288
-
289
288
### Adapter-backed workspace coherence
290
289
291
290
For adapter-backed execution, an active run or queued wake counts as a live path only when Paperclip can also prove that the selected workspace is coherent for that adapter invocation. A wake that cannot start in the intended workspace is only a failed delivery attempt, not a healthy liveness path.
`Removed stale Paperclip-managed model provider blocks from "${configTomlPath}"${reason}.`,
378
+
],
379
+
cleanup: async()=>{},
380
+
};
381
+
}
382
+
}
383
+
}
384
+
return{ notes,cleanup: async()=>{}};
385
+
}
386
+
387
+
if(!input.codexHome){
388
+
return{
389
+
notes: [
390
+
...notes,
391
+
"PAPERCLIP_CODEX_PROVIDERS is set but the adapter config explicitly sets env.CODEX_HOME; leaving the user-managed Codex home untouched (no model provider merge).",
0 commit comments