Fix timestamp formats conflict

This commit is contained in:
2026-10-27 20:42:12 +02:00
parent 6d8d6d572d
commit af2d061880
4 changed files with 181 additions and 11 deletions
+47
View File
@@ -0,0 +1,47 @@
# TUI new-client creation timestamp repair
Validated on 2026-10-27 at 20:39 +02:00. Bounded maintenance task
TUI-TS-001 repairs the new-client form path from the accepted M7 workflow.
No production, Alpine, or VM execution was performed.
## Behavior and review
The form now clears nanoseconds on its UTC instant before RFC3339 formatting.
The metadata renderer and its exact `YYYY-MM-DDTHH:MM:SSZ` validation are
unchanged. A deterministic test supplies a fixed UTC instant with nonzero
nanoseconds, checks its exact whole-second output, and sends that output to
the metadata renderer. A synthetic workflow enters an alias and blank IPv4 and
IPv6 form fields, submits the resulting command through the application worker,
and observes a dual-stack draft client. It checks that saved settings, server
configuration, internal state, and vault bytes are unchanged. The test submits
no Commit or restart command. Independent GPT-6-Luna/high reviewer found no
actionable scoped findings after examining the actual diff and running both
focused regressions.
## Integrated checks and identity
Native `x86_64-unknown-linux-gnu` host; rustc/Cargo 1.97.1, rustfmt 1.9.0,
Clippy 0.1.97. Commands below ran from the repository root and exited 0:
- `cargo test --locked creation_timestamp_discards_fractional_seconds_and_renders_as_valid_metadata`: 1 passed.
- `cargo test --locked --test tui_workflow create_form_submits_automatic_dual_stack_client_without_changing_saved_state`: 1 passed.
- `cargo fmt --all -- --check`.
- `cargo clippy --locked --all-targets -- -D warnings`.
- `cargo test --locked`: 345 passed, 3 explicitly ignored, 0 failed, including 2 documentation tests.
- `cargo build --locked --release`.
- `git diff --check`.
Base commit: `6d8d6d572df73a534b9a8dc7c5af769f2447bcfa`. Dirty Rust
inputs are the two files below; documentation changes record this repair.
SHA256 of changed Rust files:
- `src/tui/forms.rs`: `322153ae33e85b8dc59d887ff7810751f15e2326ce77e7f1105c9aab947fe9be`
- `tests/tui_workflow.rs`: `9f14c4bf9b80e65c3f6f5ccae93192015d738590b672f11d26aa824feb103438`
Native artifact `target/release/wireguard-admin` SHA256:
`d59801b0de32038ae11bbfed3d4bd01f4c36fe4119e79f3b332fec5462793687`.
These fixture results do not verify a physical terminal, Alpine networking,
or real systemd/D-Bus behavior. The previously retired M9 acceptance remains
unverified. Previous Alpine and VM source/artifact identities do not identify
this revision.