# Revision 2: validation and remaining live boundary

Recorded: 2026-09-26T17:03:22.776014+00:00

**203 Python tests and 78 browser assertions passed.** One additional public-source-surface check passed. This count excludes earlier baseline runs and repeats of the packaged files. The 203 Python tests include three native Apache loopback tests.

| Suite | Tests / assertions / checks | Result |
|---|---:|---|
| repair_suites | 106 | 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 |

## Reproduction before correction

Eight newly added regression cases failed against revision 1 (four failures and four errors). The saved output is `test-logs/reproduced-before-fixes.log`. These exposed or specified the fixes for missing SDK-directory installation/rollback, relative Passenger restart paths, preservation of a specific safe installation error, permanent cleanup-attempt exhaustion, permanent public-client retry exhaustion, and bounded work per invocation. The same cases pass in revision 2.

The worker integration test still performs the real Commons business operations through the existing isolated SQLite adapter, completes a new verification cycle rather than extending an old receipt, recovers a lost response, and preserves exact saved request/credential custody. The new outage test resumes cleanup even after the old lifetime budget would have been exhausted. The public-client test simulates 21 failed attempts across fresh instances, then verifies a successful retry uses the same saved body and idempotency key.

## Fixture migrations are explicit

The supplied source's old receipt/projection tests treated a valid receipt alone as sufficient for production readiness. The repaired application intentionally also requires a healthy automatic verifier. Running those unchanged old positive fixtures produced expected failures. The packaged migrated copies add an explicit synthetic healthy-worker fixture to positive cases; a separate negative case requires the SAME valid receipt to remain not production-ready with an absent/failing worker. The old status-copy assertion was updated for the now-existing worker. Receipt validation, authentication, authorization, and the core Commons implementation were not weakened.

No production code was altered merely to restore an obsolete test expectation. The migrated tests are `tests/test_repair_evidence_contract.py` and `tests/test_repair_autonomy_projection.py`; they are tests, not installed application payload.

## Native checks and limits

A real Apache process listened on 127.0.0.1. Public fixture content returned HTTP 200, five existing private fixture paths were denied, and absent runtime routes returned HTTP 404 rather than fabricated readiness. The actual generated access-control block was exercised. Passenger was not installed in this test process, so its directives inside the conditional block were not exercised as a running Passenger application.

Full installer transactions and cron operations remain simulated. Native Passenger, native MySQL/MariaDB, the production hosting configuration, and live automatic renewal have not been verified in this session. The public-documentation participant is same-host/same-owner, not independent organizational certification. Local tests do not set any live verification flag.

## Read-only public observation

The public status endpoint still returned the static `FETCH_RUNTIME_STATUS` pointer. A web fetch of the readiness endpoint reported HTTP 404. This is not a determination of which package the user installed or what the installer returned. It establishes that live runtime verification is still unconfirmed.

Public sources: https://concresca.com/status/current.json and https://concresca.com/api/concresca/readiness

Passenger's documented relative restart-directory semantics were checked against its official Apache configuration reference: https://www.phusionpassenger.com/docs/references/config_reference/apache/#passengerrestartdir

## Completion criterion

The installed service must obtain a valid, current receipt for all 22 required observations, report a healthy verifier, return `productionReady: true`, and return HTTP 200 with `ok: true` from `/autonomyz`. Neither installation nor these local tests is substituted for that live outcome. No production writes or deployment were performed by this session.