# Release validation — 1 November 2026

The consolidated production overlay passed **54 Laravel tests / 558 assertions**
when installed over an isolated fixture of the supplied original production
source. The test fixture used disposable SQLite, not production databases.
The same packaged mapper/policy passed **177 standalone assertions**.

Additional checks passed:

- **26 deployment/helper tests**, including four actual-source/predecessor
  upgrade-and-rollback fixtures, idempotence, payload/target drift, concurrent
  changes, interruption rollback, symlink/path boundaries, private backups,
  .env preservation and safe credential/SQL preparation.
- **9 PHP grant-boundary assertions**, rejecting broad objects, source columns,
  write privileges and unreviewed inherited roles.
- **6 mocked Power BI orchestration tests**.
- **31 PHP syntax checks**, **4 Blade compilation/lint checks**, JSON parsing
  and **37 Bash documentation-block syntax checks**.
- Native systemd unit syntax verified using a temporary rendered copy with the
  executable PHP test path available here. The shipped /usr/bin/php path must
  be verified on Ubuntu. Both fixed UTC timer expressions parsed successfully.

Each of the four installer fixtures preserved the synthetic .env and the exact
bytes of **26 original analysis view/controller files**. The original, base API,
local-HTTP and latest permissions/readable-fields states upgraded successfully
and rolled back exactly. Other application code/layout is outside the overlay.

The API suite covers scoped extraction, fresh credentials and revocation,
client IP/HTTPS policy, signatures/replay, cursor binding, byte/memory limits,
snapshot publication/retention, permission selectors and client management.
It checks readable business references/labels, public-row exclusion of
operational IDs, stable HMAC relationships, old-snapshot projection and no
live source reads during GET. Forty POST/PUT/PATCH/DELETE attempts across ten
Power BI paths returned 405 without case-database queries in the synthetic suite.

Production-specific scheduling is assigned to the supplied systemd services
and timers; the original Console Kernel backup task is preserved. Runtime
publisher and reader accounts do not need DROP; migrations use a separate
private temporary credential. The production configuration starts disabled,
requires a real replica and TLS, and explicitly disables local HTTP.

## Evidence limits and acceptance

No production SSH session, MySQL migration/grant execution, real replication
or remote database TLS handshake was performed here. Full-volume extraction,
pruning throughput, maximum-page cold/warm/p95 latency, application impact and
Power BI Desktop/Service/gateway completion remain target-environment gates.
The new deployment-helper PHP files were syntax checked; the real MySQL
preflight and migration paths require the server checks in the installation guide.
No current server-wide PHP/security compliance or absence of compromise is
certified by this release. Use the client handover template with observed results.

Fresh production installations run the two bundled Power BI migration paths.
An existing installation with those migrations applied needs no new database
migration merely for the readable-field revision; rebuild its snapshot once.
Preserve the existing application key and any valid production pseudonym key.

Machine-readable counts and boundaries are in validation/RELEASE_VALIDATION.json
and the passing consolidated-payload JUnit report is retained alongside it.
