diff options
| author | Craig Jennings <c@cjennings.net> | 2026-07-11 02:19:26 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-07-11 02:19:26 -0500 |
| commit | cdc9fa3f6bf61f562f77e552d2cde08311c4847c (patch) | |
| tree | db6e52dd4053e993f3c910e381bd8b21a6807631 /scripts | |
| parent | 8b5577bd3878a44d3888c42543d2bcfc518a817c (diff) | |
| download | archsetup-cdc9fa3f6bf61f562f77e552d2cde08311c4847c.tar.gz archsetup-cdc9fa3f6bf61f562f77e552d2cde08311c4847c.zip | |
chore: decompose net + bt doctor specs into build tasks, flip DOING
I ran spec-response Phase 6 on both READY specs. Each gets a SPEC_ID-bound parent task in todo.org with one child per implementation phase. Both specs flip from READY to DOING.
Only the read-only detection phases are buildable now, so they're marked solo: net Phase 0 (the control-plane probe) and bt Phases 0-1 (the two probes plus the firmware-hint Guide verdict). The privileged phases stay lower priority and carry a note: they're gated on the shared cross-panel run-time privilege model that doesn't exist yet. Shipping them before the Confirm floor would let --fix run root ops via passwordless sudo ungated.
I held off writing the manual-testing checklists. The phases that need live or reboot verification are the blocked ones, so their checklists would be planning work that can't start yet.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
