singularity-forge/TODO.md

# TODO

Dump anything here.
TODO: feature requests for batch backlog ingestion + probe-based resolution Real dogfood for the auto-triage feature: this is the unstructured dump that the autonomous cycle should pick up and process into proper backlog items the next time it runs. Until auto-triage is wired up, the contents serve as a written spec for what's needed. Two flagship features: - Auto-triage TODO.md on each autonomous cycle. `commands-todo.js` already implements `/todo triage` (manual). Wire it to the autonomous orchestrator and skip when TODO.md == _EMPTY_TODO. - When the LLM would ask a clarifying question, replace with parallel combatant + partner probes (adversarial-challenge + collaborative- research) and only fall back to asking a human if probes diverge AND interactive mode is available. This unblocks unattended `headless new-milestone` (the gap that blocked batch backlog ingestion today). Plus five smaller items (headless milestone stall fix, bulk import-roadmap, TTY-free plan list, hand-authorable milestone scaffold, discoverable --answers schema) carried over from the centralcloud-ops SF-IMPROVEMENTS.md observations. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> 2026-05-11 19:09:26 +02:00			`# TODO`

TODO: triage should escalate Tier 1 items to real milestones Today's triage run confirmed the manual `/todo triage` workflow works, but it stops at tier-listing items in BUILD_PLAN.md — doesn't scaffold .sf/milestones/MNNN/ dirs for the Tier 1 ones. That's the gap that needs closing for the autonomous flow to actually create milestones from raw TODO dumps. Also captures the non-fatal phases-helpers.js extension load error that appeared at the top of the triage run output. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> 2026-05-11 19:15:33 +02:00			`Dump anything here.`
TODO: feature requests for batch backlog ingestion + probe-based resolution Real dogfood for the auto-triage feature: this is the unstructured dump that the autonomous cycle should pick up and process into proper backlog items the next time it runs. Until auto-triage is wired up, the contents serve as a written spec for what's needed. Two flagship features: - Auto-triage TODO.md on each autonomous cycle. `commands-todo.js` already implements `/todo triage` (manual). Wire it to the autonomous orchestrator and skip when TODO.md == _EMPTY_TODO. - When the LLM would ask a clarifying question, replace with parallel combatant + partner probes (adversarial-challenge + collaborative- research) and only fall back to asking a human if probes diverge AND interactive mode is available. This unblocks unattended `headless new-milestone` (the gap that blocked batch backlog ingestion today). Plus five smaller items (headless milestone stall fix, bulk import-roadmap, TTY-free plan list, hand-authorable milestone scaffold, discoverable --answers schema) carried over from the centralcloud-ops SF-IMPROVEMENTS.md observations. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> 2026-05-11 19:09:26 +02:00