Confirm the published opencode-orchestrator@1.2.69 patch is available downstream and watch for any remaining /task TUI corruption reports.
Fixed the unsafe toast rendering path, published opencode-orchestrator@1.2.69, and prepared the post-release metadata sync commit for push.
Push the release commit, the follow-up metadata sync commit, and tag v1.2.69, then verify the remote branch is clean.
- Downstream install verification from a clean shell is still pending because only local build/test and npm publish have been completed in this session.
- Treat the root cause as a rendering-safety bug in the toast pipeline rather than a mission-loop bug.
- Sanitize toast titles, inline labels, and multiline bodies separately so task context remains visible without letting control sequences or oversized payloads reach the TUI.
- Keep raw task metadata untouched in storage and sanitize only at the UI boundary.
- Sanitizing only
/taskuser input, because delegated task descriptions and error payloads can also inject unsafe content. - Truncating task descriptions without stripping terminal control sequences, because escape bytes would still reach the TUI.
- Refactoring mission/task execution flow, because the evidence pointed to unsafe rendering payloads rather than broken orchestration state.
- The patch is validated by targeted unit tests and local build, not by an interactive OpenCode TUI session in this workspace.
- The tagged release commit does not include the README version-line sync, so the repository history keeps that as a follow-up commit after the published tag.
AGENT_MEMORY.mdREADME.mdsrc/core/notification/toast-sanitizer.tssrc/core/notification/task-toast-manager.tssrc/core/notification/toast-core.tstests/unit/toast-sanitizer.test.ts