The ready_issues VIEW was using old logic that didn't propagate blocking through parent-child hierarchies. This caused inconsistency with the GetReadyWork() function for users querying via sqlite3 CLI. Changes: - Updated VIEW to use same recursive CTE as GetReadyWork() - Added test to verify VIEW and function produce identical results - No migration needed (CREATE VIEW IF NOT EXISTS handles recreation) The VIEW is documented in WORKFLOW.md for direct SQL queries and is now consistent with the function-based API. Resolves: bd-60 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
4.7 KiB
4.7 KiB