diff options
| author | Craig Jennings <c@cjennings.net> | 2026-07-01 21:44:28 -0400 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-07-01 21:44:28 -0400 |
| commit | b91877b570a8e61f1b0ceaaab1243b7d82f1a7e1 (patch) | |
| tree | ad7731cc8f45616f297ade0ef2b99c906239421a | |
| parent | ad6c580144f71b3bbec4b8a1ed01e8e4303be299 (diff) | |
| download | archsetup-b91877b570a8e61f1b0ceaaab1243b7d82f1a7e1.tar.gz archsetup-b91877b570a8e61f1b0ceaaab1243b7d82f1a7e1.zip | |
docs(todo): log the DoT-cause and portal-button work on the captive-portal task
| -rw-r--r-- | todo.org | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -57,6 +57,9 @@ Full mechanism writeup, the working script, and the integration plan: [[file:doc *** 2026-06-30 Tue @ 11:40 -0400 Engine core landed (dotfiles a7d7559) Replaced =net portal='s old captive-helper hand-off with a =portal-login= repair tier: drop DoT to plain DNS, probe the portal URL (302 / meta-refresh), open a throwaway browser profile, spawn a detached watcher that restores DoT once online (or on timeout). =net portal --restore= is the manual fallback. 7 tests. So =net doctor= / the bar's =net portal= hookups already run the real flow now. Remaining: (1) name the DoT-blocking cause in =net diagnose=; (2) a dedicated "Log in to this network" button in the panel's Diagnose/Repair tab (today it rides the generic =net portal=); (3) live validation against a real captive portal (unit-tested only — didn't run it live to avoid disrupting a meeting). +*** 2026-07-01 Wed @ 21:44:05 -0400 Diagnose names the DoT block; panel gained Log in to This Network (dotfiles 51e0e2d) +Remainders 1 and 2 landed. The dns-resolve step names the DoT pin when resolution is dead and the drop-in exists (sysio.dot_forced), and routes next_action to the portal login. The panel's hidden Open Portal button became a first-class suggested-action "Log in to This Network", shown whenever the report holds a portal signal (portal step with or without a URL, or the DoT-blocked resolution) via the unit-tested viewmodel.wants_portal_login. TDD, 33 suites green. Remainder 3 (live validation against a real portal) still open. + *** 2026-06-30 Tue @ 14:59:53 -0400 Live test on velox surfaced two fixed bugs + a deeper follow-up Force portal (panel Repair tab) = =net-popup net portal= = the same portal-login tier. Tested live on @Hyatt_WiFi (already authorized, so no real intercept). Two bugs fixed in dotfiles (TDD, full suite green): - Chrome first-run wizard fired on every launch — =_open_portal= made a fresh tempfile profile but passed no first-run flags. Added =--no-first-run --no-default-browser-check= + a unit test. |