Fix timestamp formats conflict

PLANS.md

@@ -119,7 +119,9 @@ Each row is a delivery milestone, not a completion claim. Expand its record befo
 | 7   | Complete terminal management workflow                    | 6                                         | accepted    |
 | 8   | Alpine Testcontainers integration                        | 7; suitable disposable Docker environment | accepted    |
 | 9   | Real systemd acceptance and release readiness            | 8; disposable systemd VM                  | retired     |
-| 10  | Visible styled keyboard quick reference in bottom panel | 8; existing M7 TUI                        | in_progress |
+| 10  | Visible styled keyboard quick reference in bottom panel | 8; existing M7 TUI                        | accepted    |
+| 11  | Valid subnet routes shown as a capability limitation    | 10                                        | accepted    |
+| 12  | Aligned, responsive client table                        | 11                                        | accepted    |
 
 ### Milestone 1 — Rust foundation, settings, and domain states
 
@@ -3544,6 +3546,7 @@ Stop after this milestone; do not resume VM work, commit or deploy.
 
 ## Current progress and resume point
 
+- Bounded TUI maintenance TUI-TS-001 (2026-10-27): new-client form creation timestamps now have whole-second UTC precision before strict metadata rendering. A fixed fractional-second instant and a synthetic blank-IP form-to-draft workflow passed; saved bytes stayed unchanged. Independent review found no actionable issue, and pinned-toolchain Rust completion gates passed. [Timestamp repair evidence](docs/evidence/tui-creation-timestamp.md) identifies the source and release artifact. This repairs M7 behavior without claiming new Alpine or VM validation; earlier artifact identities remain historical after this Rust change.
 - Bounded TUI maintenance (2026-10-26): repaired list arrows opening client details. Up/Down now only move the highlight; Enter opens details and Esc returns. Initial navigation follows the renderer's first-row highlight. Independent review closed NAV-001 with no remaining scoped findings; validation is recorded in [navigation repair evidence](docs/evidence/tui-navigation.md). This does not advance M9 or supply VM/Alpine acceptance evidence; prior artifact identities remain historical after this Rust change.
 - Milestones 1–8 are accepted; milestone 9 is retired by user direction and unaccepted. Its real systemd/D-Bus checks remain unverified and are not a prerequisite to M10.
 - Milestone 10 is accepted: the styled keyboard quick reference passed independent review, focused synthetic/PTY checks and Rust completion gates.
@@ -3561,7 +3564,7 @@ Stop after this milestone; do not resume VM work, commit or deploy.
 
 - Milestone 8 delivered reviewed opt-in Alpine Testcontainers coverage for real IPv4 WireGuard peers, application lifecycle, saved/runtime separation, restoration, import/reissue, backup failures and the real Rustix reader. Host gates and three fresh real-container runs passed on one stable source fingerprint; M8-A1–A10 accepted. Real IPv6 behavior is unverified by user-authorized scope.
 - Milestone 9 is retired and unaccepted: the reviewed disposable VM preparation and guarded first start did not establish Debian/systemd acceptance. The exact VM was powered off after the user stopped work. M9.2–M9.3 were not started; M9-A1–A9 are unchecked.
-- Next action: stop after M12 and await user direction. Do not restart the VM, access production, commit, or deploy.
+- Next action: scoped timestamp repair is complete; await user direction. Do not restart the VM, access production, commit, or deploy.
 
 ## Plan maintenance