# Test results and live boundary

Run recorded at 2026-09-26T02:15:53Z.

**188 Python tests and 78 browser assertions passed.** One additional source-surface validation command passed. Re-running the packaged copies added 45 Python tests and 78 browser assertions; these repeats are not double-counted.

| Suite | Tests / checks | Result |
|---|---:|---|
| worker | 20 | PASS |
| heartbeat | 8 | PASS |
| installer | 17 | PASS |
| receipt | 24 | PASS |
| autonomy_status | 22 | PASS |
| root_integration | 20 | PASS |
| receipt_publisher | 39 | PASS |
| private_environment | 31 | PASS |
| private_boundary | 3 | PASS |
| static_fallback | 4 | PASS |
| current_status_surfaces | 1 | PASS |
| browser | 78 | PASS |

## What the tests establish

The new worker completed the real Commons business workflow, produced a receipt accepted by the unchanged receipt validator, completed a second full renewal cycle, and cleaned up an abandoned trial before creating a new one. Tests cover lost-response retry intent, same-identity recovery, two actual OS processes reopening the same journal, replica recovery, corruption and symlink rejection, negative authorization probes, stale heartbeats, and placeholder rejection.

The installer tests preserve unrelated hosting directives and cron jobs, reject unknown source changes and unsafe paths, exercise exact-file rollback, preserve concurrent cron changes, and confirm that existing receipt bytes are not extended or replaced.

## What has not been established

No production deployment or production mutation was made in this session. The full workflow tests use real application code over a SQLite SQL test adapter. Runtime fingerprint and Passenger restart observations in those tests are fixtures. Native MySQL/MariaDB and native Apache/Passenger execution were not exercised. Installer tests simulate host commands and public readback. The installer and worker must establish those facts on the existing host before production readiness can be claimed.

The public-documentation participant is a separate public-SDK implementation and process under the same host owner. This is not third-party organizational independence, outside adoption, hardware-isolated credential custody, or certification.

## Live observations during this repair

On the final read-only web check, `/status/current.json` still returned the static `FETCH_RUNTIME_STATUS` pointer, and the web fetch of `/api/concresca/readiness` reported HTTP 404. This is the existing deployment, not a live test of the new package. User deployment of the earlier diagnostic ZIP is acknowledged; it is not being disputed.

Public sources checked: `https://concresca.com/status/current.json`, `https://concresca.com/api/concresca/readiness`, and the official Passenger Apache configuration reference at `https://www.phusionpassenger.com/docs/references/config_reference/apache/`.

## Preserved boundaries

The receipt validator, core Commons business implementation, continuity implementation, records implementation and protected-environment loader are byte-identical to the deployed diagnostic source archive. The new worker does not weaken these contracts. It supplies current observations through their existing interfaces and adds a separate automation-liveness requirement.

All local command results and hashes are in `VALIDATION.json`; raw output is under `test-logs/`.