Commander1024/ESP32_Serial_Swiss_Army_Knife
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Close scope for remaining Phase 8D.19 work

Browse Source
This commit is contained in:
Commander1024
2026-09-13 20:25:01 +02:00
parent 8df1d2218b
commit 1608641d50
4 changed files with 10 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/phase8d19_implementation.md
+2 -2
View File
@@ -1,6 +1,6 @@
# Phase 8D.19 — first service slice: SSH ordinary controls
Date: 2026-09-13. User-authorized implementation; **SSH slice implemented, host-tested and build-verified. Independent review complete with no confirmed actionable defects; target sign-off pending. Phase 8D.19 as a whole remains incomplete.**
Date: 2026-09-13. User-authorized implementation; **SSH slice implemented, host-tested and build-verified. Independent review complete with no confirmed actionable defects; target sign-off pending. The user dropped the unimplemented remainder on 2026-09-13; existing SSH controls are retained. No further 8D.19 implementation is planned, and this scope closure is not target sign-off.**
Independent reviewer reran canonical SSH4, cookie SSH6+shared, dispatcher, lifecycle27, UI143+renderer/HTML/CSP and diff checks, all PASS. Parent final `pio run` confirmation PASS19.95s at100,404 B RAM/1,808,441 B flash; diff check PASS. Host doubles do not prove actual concurrent SSH cleanup, physical HTTPS/USB continuity or runtime margins.
@@ -18,7 +18,7 @@ Explicit exclusions:
- No shell-policy broadening. Canonical browser shell still rejects `ssh stop` and `ssh disconnect`: its SSH-specific deferral is not a WEB-owner action. Typed SSH requests have a separate, narrow current-admin admission boundary and reuse canonical SSH lifecycle/owner close semantics, not command strings.
- No new task, timer, generic runner, queue depth, stack size, socket/session capacity, dependencies, SDK/configuration or generated assets. No commit/upload/erase.
Remaining 8D.19: separately audit and select a web-transport slice for **other**, non-invoking sessions if useful. It must identify the precise originating login/transport, exclude invoking-session effects, and retain HTTPD-owner fd/epoch safety. USB actions are not promised: first establish whether its actual public ownership/API model permits any useful non-recovery-disrupting control. Do not expose generic broker disconnects or claim all-service parity. Self-affecting HTTPS/Wi-Fi actions remain 8D.20, identities 8D.21.
Scope closure (2026-09-13): the user dropped the remaining web-session/USB service-control expansion as unnecessary for this small device. No further owner audit or implementation of that remainder is planned. Retain the delivered SSH controls; do not expose generic broker disconnects or claim all-service parity. Self-affecting HTTPS/Wi-Fi actions belong to 8D.20, identities to 8D.21.
## HTTP contract and bounded dispatcher