# RustProxy 0.32.8 - verification report

## Scope

UI-only Overview header/editor button alignment, deletion of the complete
`tools/checks/` source directory, retained source-upgrade preflight and the
0.32.8 version bump. No proxy request path, backend behavior, preferences
schema or dashboard JavaScript event handlers were changed.

## Checks performed

- **PASS** - Chromium headless checked the actual Overview HTML and CSS at
  viewport widths 320, 360, 375, 390, 430, 480, 600, 700, 768, 1024 and
  1440 px, with Normal and Compact button styles and four visibility/editing
  scenarios: 88 combinations. Title stays left, available actions align right;
  no overlapping buttons or page/header horizontal overflow was observed.
  This is a layout fixture, not a running API/backend acceptance test.
- **PASS** - All Overview and editor controls use the original semantic
  `quiet`, `outline` and `primary` classes. No CSS class names were added.
  Removed obsolete dedicated button selectors. The Overview/core/refresh/layout
  JavaScript files are byte-identical to 0.32.7, so existing event handling,
  save/cancel and editor locking implementations were not changed.
- **PASS** - Before removing the old QA directory, the 0.32.7 UI simulation
  suites `dashboard_layout_editor_0323_ui_test.mjs` and
  `dashboard_inline_layout_0323_ui_test.mjs` passed. The original
  `appearance_density_buttons_0327.py` source check also passed. These tests
  exercised simulated UI behavior, not a live RustProxy server.
- **PASS** - `python3 scripts/preflight.py`, `./dev.sh doctor`,
  `./dev.sh repair`, shell syntax of `dev.sh` and the dependency-resolution
  script, all bundled language JSON files, version consistency and source
  class/handler comparisons.
- **PASS** - Source-upgrade rehearsal from the supplied 0.32.7 release tree
  to 0.32.8 removed `tools/checks/` from the installed working tree, retained
  the previous sources under `.upgrade-backup/`, preserved `.env` and left
  `./dev.sh doctor` working. No live server/database was used in this rehearsal.
- **PASS** - All eight bundled SQL migration scripts applied twice in an
  in-memory SQLite database; `PRAGMA integrity_check` returned `ok`.

## Limits and outstanding acceptance

- Rust/Cargo was **not available** in the verification environment, so
  `./dev.sh check`, `./dev.sh test`, binary build and live proxy/UI regression
  checks were not run. These remain required before production acceptance.
- An unrelated legacy `dashboard_startup_0310_ui_test.mjs` assertion was already
  failing on the supplied 0.32.7 tree due to its expected
  `prefers-reduced-motion: reduce` CSS rule being absent. That test was removed
  with `tools/checks/`, not claimed as passing or fixed by this patch.
- The intentionally removed `tools/checks/` suites are no longer executed by
  `dev.sh`; `./dev.sh test` now runs Cargo validation and the Rust test suite.
  Independent API, stress, browser and real-runtime acceptance tests must be
  run externally when required.

## Test-suite maintenance follow-up (0.32.8)

This maintenance change affects test code and duplicate test helpers only. No
production Rust or Go source logic was changed.

- Renamed the invalid Rust test identifier beginning with `304_` to
  `response_304_with_private_policy_discards_cached_representation`. The
  revalidation regression itself is retained.
- Placed four passive-health regression tests back inside the existing
  `src/balance/tests.rs` `mod tests` scope, so they can use its private
  `settings(HealthMode)` fixture. No test assertions were removed.
- Removed two byte-for-byte duplicate files under `scripts/tests/`:
  `test_stream_tcp.py` and `test_stream_udp.py`. The canonical scripts under
  `scripts/` remain, including their documented commands and self-tests.
- Statically enumerated 655 Rust `#[test]`/`#[tokio::test]` cases after the
  edit, without duplicate test names or remaining numeric-leading test names.
  A name containing an old version or `legacy` is not evidence that its
  compatibility/regression coverage is obsolete.

**Checks passing in the available environment:**

- `python3 scripts/preflight.py`, `bash dev.sh doctor`, `bash dev.sh repair`.
- `go test ./...` in `docker-agent/`.
- `python3 scripts/test_stream_tcp.py selftest` and
  `python3 scripts/test_stream_udp.py selftest` (mock-peer harness checks only;
  these do not exercise RustProxy).
- Python AST parsing of all 14 scripts under `scripts/`, shell syntax checks
  for `dev.sh` and the Stream/dependency helper scripts.
- All eight bundled SQLite migrations executed twice in order on an in-memory
  database, with `PRAGMA integrity_check = ok` after both passes.

**Not verified:** The environment does not have `cargo` or `rustc`, and DNS
resolution is unavailable for downloading a toolchain. Consequently,
`cargo check --locked --all-targets` and `cargo test --locked --all-targets`
have not passed here. This maintenance does not close the live-runtime
acceptance gate or establish that every remaining test is passing.