…orkflow-to-correct-video-id-handling

Update n8n PMOVES.YT workflow for nested video response

* feat: enhance workflow router with platform context

Add RouterContext interface and improve router prompt to make smarter
routing decisions by providing platform-specific context:

- Add RouterContext interface with platformType, isPullRequest, title,
  labels, threadHistory, and workflowType fields
- Build context section in router prompt when context is provided
- Update orchestrator to pass context from available data (GitHub
  issue/PR metadata, thread history, isolation hints)
- Improve routing rules with explicit guidance for CI failures vs
  GitHub issues
- Add 8 new tests for context functionality

This fixes misrouting issues like PR #134 where "fix CI failures" was
incorrectly routed to fix-github-issue instead of assist.

* fix: address PR review feedback for workflow router context

- Add debug logging for regex extraction failures in orchestrator.ts
  Logs when title/labels extraction from issueContext fails, helping
  diagnose routing issues

- Fix misleading JSDoc comments in router.ts
  Clarify that RouterContext is constructed by orchestrator, not provided
  by platform adapters

- Fix type duplication by importing workflowType from IsolationHints
  Ensures RouterContext.workflowType stays in sync with IsolationHints

- Add orchestrator integration tests for context extraction
  Tests for title, isPullRequest, labels, and workflowType extraction
  from issueContext and isolationHints

- Add missing router tests for edge cases
  Tests for isPullRequest/workflowType precedence, empty labels array,
  empty string threadHistory, and all workflowType values

* feat: enhance workflow router with platform context

Add RouterContext interface and improve router prompt to make smarter
routing decisions by providing platform-specific context:

- Add RouterContext interface with platformType, isPullRequest, title,
  labels, threadHistory, and workflowType fields
- Build context section in router prompt when context is provided
- Update orchestrator to pass context from available data (GitHub
  issue/PR metadata, thread history, isolation hints)
- Improve routing rules with explicit guidance for CI failures vs
  GitHub issues
- Add 8 new tests for context functionality

This fixes misrouting issues like PR coleam00#134 where "fix CI failures" was
incorrectly routed to fix-github-issue instead of assist.

* fix: address PR review feedback for workflow router context

- Add debug logging for regex extraction failures in orchestrator.ts
  Logs when title/labels extraction from issueContext fails, helping
  diagnose routing issues

- Fix misleading JSDoc comments in router.ts
  Clarify that RouterContext is constructed by orchestrator, not provided
  by platform adapters

- Fix type duplication by importing workflowType from IsolationHints
  Ensures RouterContext.workflowType stays in sync with IsolationHints

- Add orchestrator integration tests for context extraction
  Tests for title, isPullRequest, labels, and workflowType extraction
  from issueContext and isolationHints

- Add missing router tests for edge cases
  Tests for isPullRequest/workflowType precedence, empty labels array,
  empty string threadHistory, and all workflowType values

#87)

## Summary
Third state for Mission Control between green completed and red failed.
Anchored on the 2026-05-16 engine sortie that completed all-green while
silently losing 13 spec files because no UI signal existed for
exit-0-with-`STATUS=*_failed`-stdout.

- Engine: `silent-failure-detector` scans bash/script stdout
post-exit-0. Triggers on (a) any `STATUS=*_failed` in nodes with
`load_bearing: true` (WO-167 doctrine), or (b) always-dangerous patterns
(`push_failed`, `commit_failed`, `pr_create_failed`,
`registry_write_failed`, `artifact_persist_failed`,
`bundle_save_failed`, `spec_save_failed`) on any node.
- Event: new `node_completed_with_warning` emitted instead of
`node_completed`. Persisted to event store; forwarded via SSE as
`dag_node` with `status=completed_with_warning` + warning detail.
- UI: DAG node renders yellow border + tint, native-title tooltip with
STATUS line + load-bearing context, inline chip showing matched
patterns. Workflow-level StatusBadge rolls up to yellow `completed
(warning)` when any node has the warning state. Per-step log surfaces
the STATUS line.
- Does NOT change the underlying `STATUS=*_failed` convention or graph
control flow — downstream nodes still see `completed`. Coexists with
WO-169 (PR #84) which strips these patterns in load-bearing nodes.

## Test plan
- [x] `bun test packages/workflows/src/silent-failure-detector.test.ts`
— 11/11 pass
- [x] `bun test packages/web/src/stores/workflow-store.test.ts` — 30/30
pass (warning fields preserved in store)
- [x] `bunx tsc --noEmit` clean in packages/workflows, packages/web,
packages/server
- [ ] Manual: fire a workflow with a load_bearing node that emits
`STATUS=spec_save_failed` on exit 0; confirm yellow node + yellow
workflow badge + tooltip
- [ ] Manual: fire a workflow with non-load-bearing node emitting
`STATUS=push_failed`; confirm yellow render (always-dangerous path)
- [ ] Manual: fire a workflow with `STATUS=custom_failed` on a
non-load-bearing node; confirm NO warning (correct opt-in semantics)

Closes #170 (bdc-xo).
Depends on #181 (Rule 27 / load_bearing doctrine).
Coexists with #84 (WO-169 push/PR retry guard).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>