Skip to content

Rendering slice 8: opencode-interleave-87f0eeef fixture#433

Merged
Juliusolsson05 merged 1 commit into
integration/rendering-pipelinefrom
feat/rendering-slice8-opencode-fixture
Jul 6, 2026
Merged

Rendering slice 8: opencode-interleave-87f0eeef fixture#433
Juliusolsson05 merged 1 commit into
integration/rendering-pipelinefrom
feat/rendering-slice8-opencode-fixture

Conversation

@Juliusolsson05

Copy link
Copy Markdown
Owner

Pins the render-spasm bundle shape: exactly-once rendering under interleave, unit-level policy protection, chronological order. 50/50, tsc clean. Self-merging per loop authorization.

🤖 Generated with Claude Code

Concurrent assistant messages on one SSE stream (the render-spasm
bundle): interleaved content renders exactly once in chronological
order — the committed assembled message wins its slot with the bridge
copy suppressed by exact text, the never-committed concurrent message
survives in full, and the drift-report hazard is pinned: opencode
committed rows carry message ids but the unit-level policy bit forbids
claude-style whole-turn suppression from eating the other message.

50/50 green; tsc node+web 0 errors via clean two-step gate.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@Juliusolsson05 Juliusolsson05 merged commit 0850ccc into integration/rendering-pipeline Jul 6, 2026
@Juliusolsson05 Juliusolsson05 deleted the feat/rendering-slice8-opencode-fixture branch July 6, 2026 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant