PARADIGM MANHOUR PHP/MYSQL - VALIDATION, 10 NOVEMBER 2026

Executed locally using PHP 8.4.27 and MariaDB 11.8.6 (PDO MySQL/InnoDB).
- 11 runtime PHP files passed syntax validation.
- Production frontend build passed.
- 35 backend checks passed: full imports, exact config/payload/revision
  preservation, deleted/audit history, backup-before-restore, current/previous
  week editing and old locks, stale-row rejection, atomic batch rollback,
  idempotent save/restore retries, stale epoch/replay rejection, hide/unhide,
  move conservation, employee order/checks, role restrictions, Field lists,
  drawing rates, retired categories, expected-project family transfer, deletion,
  invalid import rollback and manual backups.
- 21 HTTP checks passed: authentication/cookies/logout, JSON object maps,
  cross-origin and content-type rejection, admin/editor/viewer permissions,
  simultaneous same-row conflict and different-row success, transfer status,
  backup download, subfolder assets/API routing and login throttling.
- 5 installer checks passed under simulated HTTPS server variables: HTTP
  rejection, wrong setup-key rejection, successful setup, reinstall blocking,
  and hashed access-code storage.
- Scheduled backup script ran successfully and produced private JSON backups.
- Full migration fixture: 779 project rows, 232 active employee rows, 1 deleted
  record and 3 source audit entries. A saved change was made in a temporary
  central-app database before export. The exporter left the source database
  bytes unchanged. PHP import/export comparison verified every source row,
  config, weekly value, revision, metadata field and source audit entry.
  This was a test fixture, not the user's running office database.
- Frontend check-counts, check-nov9 and check-nov6 passed against hosted source.
  The latest shared model, Excel writer and logo are identical to the central
  release. Checks cover duplicate names/counts, FTE sums, category graphs,
  logos, default team, signed balances and Actions-column structure.

Limits:
- No deployment or live-data transfer has been performed on the user's GoDaddy
  account. The package contains no production credentials or office records.
- Actual GoDaddy Apache/.htaccess, HTTPS certificate, PHP limits and cron
  execution must be confirmed after upload. Local HTTP tests used a disposable
  development configuration permitting localhost HTTP; installer-created
  production configurations require HTTPS.
- Browser visual/interactive and PDF print appearance were not tested.
- Simultaneous-save correctness was tested; capacity/load testing for the
  user's full office on their specific hosting plan remains necessary.
- Oracle MySQL itself was not run; database tests used compatible MariaDB.