diff options
Diffstat (limited to 'docs/specs/2026-07-11-net-doctor-expansion-spec.org')
| -rw-r--r-- | docs/specs/2026-07-11-net-doctor-expansion-spec.org | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/docs/specs/2026-07-11-net-doctor-expansion-spec.org b/docs/specs/2026-07-11-net-doctor-expansion-spec.org index 2727702..0df74b3 100644 --- a/docs/specs/2026-07-11-net-doctor-expansion-spec.org +++ b/docs/specs/2026-07-11-net-doctor-expansion-spec.org @@ -8,6 +8,7 @@ :PROPERTIES: :ID: ce29b103-ed9d-4f56-bf8c-9ed8fe680ff3 :END: +- [2026-07-23 Thu @ 08:40 -0500] IMPLEMENTED — Phase 4 (docs + rollout) closed by the dotfiles session, =138da7b=. Accepted against the phase's *stated acceptance criteria*, all three met: help complete, user guide (=net/README.md=), ratio rollout documented. The audit behind it found a real defect worth recording — =net repair='s action list named 9 of 19 registered actions, so ten tiers were reachable but undocumented, and =repair.py='s docstring carried the same stale copy; both now generate from the =ACTIONS= registry plus =viewmodel.STEP_NARRATION=, so they can't drift again. Two corrections to this spec from the build: the dep list is one item heavy — =gtk4-layer-shell= is no longer required, the net panel is a plain floating window now. And the Phase 4 *narrative* lists a panel help affordance that its acceptance criteria never did; no sibling panel (net, maint, settings, audio, bluetooth, panelkit) has one, so there is no convention to inherit and the shape is a genuine design call. It is tracked as its own =[#C]= in dotfiles rather than invented unilaterally, and it does not hold this phase open. - [2026-07-12 Sun @ 09:12 -0500] IMPLEMENTED — all v1 phases shipped on dotfiles main: Phase 0 read-only control-plane probe (=21ca3ff=), Phase 1 control-plane verdicts through the shared panelkit privilege model (=d73eba6=, =c9f8604=, =be15a81=), Phase 2 sharpened auth verdict (=12e3e76=). 813 net tests + 65 suites green against the fake harness. The privileged-fix live halves (real masked-NM/rival/keyfile states, real WPA3/hidden profiles) are handed off to the VM scenario harness (archsetup =a364c1e=) and the "Manual testing and validation" checklist in =todo.org= — findings there come back as bugs, not spec work. vNext items logged to =todo.org=. - [2026-07-11 Sat @ 02:30 -0500] DOING — decomposed into build tasks (spec-response Phase 6); parent task in =todo.org= bound by =:SPEC_ID:=. Phase 0 (read-only control-plane probe) is buildable now and =:solo:=; Phases 1-2 are gated on the shared cross-panel privilege model. The systemic connection-name redaction gap is a separate filed task. - [2026-07-11 Sat @ 02:00 -0500] READY — third skeptical re-review returned Ready with caveats, no blocking findings; all round-2 resolutions verified against the engine. Caveat accepted: Phases 1-2 depend on the shared cross-panel run-time privilege model, which doesn't exist yet, so only Phase 0 (read-only detection) is buildable today. The redaction de-scope (parity + separate systemic task) is the one product call for Craig's eye. |