upstream(sync): Workflows stack — run history, reply-in-thread, editor (#5780, #6178, #6248)

[oscarlehuu]

Intent

Sync full Buzz workflow improvements — Crew has not forked workflow engine; expected clean merge.

Upstream PRs: block#5780, block#6178, block#6248

• Outcome: authoritative run history, send_message with reply_in_thread, visual workflow editor
• Aligns with call-by-name / thread automation (Agent-to-agent call by name (CoS wakes specialists; no founder Wake) #230)

Conflict matrix

Area	Risk	Crew files	Resolution
desktop/src/features/workflows/**	Low	likely untouched	Take upstream wholesale
crates/buzz-workflow	Low	no Crew delta	Take upstream
buzz-core NIP-10 parser (block#6178)	Low	shared	Take upstream; verify thread roots in Crew harness
Playwright	Low	playwright.config.ts	Add upstream spec globs per UPSTREAM-SYNC.md row

TDD plan

Phase 1 — RED (block#6178)

• Add/run upstream test: reply_in_thread sets NIP-10 markers; trigger_is_reply filter
• Command: cargo test -p buzz-workflow + workflow schema tests

Phase 2 — RED (block#5780)

• Run history pagination + error_code contract tests
• Desktop unit: truthful pending trace UI

Phase 3 — RED/GREEN (block#6248)

• Editor route deep-link + dirty-exit guard tests (upstream Playwright)
• GREEN: merge tag; NuncioCrew Gate

CI note

Workflow paths may be outside automatic Crew Gate — run manual NuncioCrew Upstream Sync if workflow crates change.

Parent

Buzz Tier 3 — promoted to Tier 2 (clean sync).

Unresolved

• Founder priority for workflow editor UX vs automation-only