Twinned from https://github.com/cfsh/ninefold/issues/975 by tools/beads/import_github.py's reconcile pass.
Suggestions from ninefold-reviewer's review of #968
design_docs/tools/status.py's _doc_status (around lines 139-147) treats parse_task_table's two distinct failure signals identically: "no task table found" (fine, doesn't qualify) and "Issue column missing" (a real authoring-convention violation). operationalize_design.py surfaces the latter loudly (design_docs/tools/operationalize_design.py:209-210); status.py folds it into the same silent skip, so ./dev.py designs --all gives no diagnostic for a doc that has a task table but is missing its Issue column — it just vanishes, indistinguishable from a doc never meant to be tracked. Worth a stderr warning when result.error == "Issue column missing", the same way operationalize_design.py does. Low severity — the window is narrow (docs without a Project pointer, between merge and their --apply follow-up PR) and self-resolves once T7 documents the Issue-column authoring convention — but a real, near-term-possible gap today since T7 hasn't landed.None.
No comments.