fbe645a305
The BACKLOG_NUMS associative array was built to track which issue numbers are in the backlog, but the DFS cycle-detection code used NODE_COLOR as a membership guard instead. This meant deps pointing to non-backlog issues were only skipped by coincidence (they weren't in NODE_COLOR either). Three changes: - Remove SC2034 suppression since BACKLOG_NUMS is now actually queried - Initialize NODE_COLOR from BACKLOG_NUMS keys (all backlog issues) instead of DEPS_OF keys (only issues with dependencies), so every backlog issue gets a proper DFS color - Replace the NODE_COLOR membership check with BACKLOG_NUMS in the DFS, so the guard explicitly asks "is this dep a backlog issue?" rather than relying on NODE_COLOR initialization as a proxy Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| best-practices | ||
| journal | ||
| AGENTS.md | ||
| preflight.sh | ||
| PROMPT.md | ||
| supervisor-poll.sh | ||
| supervisor-run.sh | ||
| update-prompt.sh | ||