session-report · RPT-A00E54B8AFC3
R8 continuation: validated release and corrected diagnostic URL
Source identity
- Record
RPT-A00E54B8AFC3- Original file
- Concresca-r8-continuation-notes.md
- Original SHA-256
378da6ce1d485435086a71f8a122910e79ac15e4dee083f8215dd11de062f610- Source family
- repair-conversation
- Public copy SHA-256
378da6ce1d485435086a71f8a122910e79ac15e4dee083f8215dd11de062f610- Original custody
- Exact bytes retained in the private project package under
docs/_evidence/; not a public download.
Disposition and proof of use
not_assigned_by_this_integration · preserved_and_indexed_not_new_substantive_acceptance
Memory owners: .uai/file-handoff.uai, .uai/report-synthesis.uai, .uai/research-review.uai. These are private repository records, not public web routes.
Jump to a report section
Report body
R8 continuation: validated release and corrected diagnostic URL
The deployment archive remains Concresca.com-20260927-FULL-ROOT-r8.zip.
It was not modified in this continuation. This document is not an overlay.
Newly executed checks
The extracted complete release passed 328 Python tests, 85 PHP assertions,
and 108 synthetic JavaScript assertions, without skipped tests. The whole-file
manifest verified. The archive contains 2,287 files and 1,060 directories.
SHA-256: d7efbab1685d0b6d4d858a10706a8e081e11222717dc6444eed65e4f83fdedc4.
An additional native Apache/PHP HTTPS fixture ran the unmodified r8 backend as an unprivileged web account with the full release. The fixture used the exact legacy static pointer whose SHA-256 matches the supplied report and the report's 0666 modes for .htaccess and the status pointer. It also injected two 0775 nested directories; those directory modes are test inputs, not host observations. The read-only prerequisite check left all modes unchanged. Authenticated activation then tightened the two files to 0644 and the two directories to 0755. Host-configuration, pointer, and synthetic expired-receipt bytes were preserved. The fixture deliberately had no private environment, so activation correctly stopped at that prerequisite without claiming routing or readiness. It did not create, extend, or approve acceptance evidence.
Correction to the earlier ping instructions
Use exactly:
https://concresca.com/concresca-diagnostics.php?action=ping
Do not append release_check, verification, or cache-busting parameters to
this PHP endpoint. Its existing allowlist accepts only the single action=ping
query. Native tests returned 200 for that exact URL and 400 QUERY_NOT_ALLOWED
when an extra parameter was added. This is a correction to the instructions,
not a reason to weaken authentication or replace the application again.
The normal diagnostics page has no query string:
https://concresca.com/concresca-diagnostics.php
Public check and next installation action
A live content fetch returned the r7 release identifier and r7 diagnostic build. The web fetch of readiness reported 404. The content fetches do not expose full HTTP headers, and their response does not prove where any newer files were uploaded. No r8 production activation has been observed in this continuation.
Deploy the existing full r8 archive into the same website document root, preserving the root .htaccess, private configuration, database, Python environment, mutable runtime state, and account-home diagnostic state. Do not empty the directory. Confirm the diagnostic footer ends in root-r8.
Unlock, select Check activation prerequisites, and use Activate installed release with the explicit authorization checkbox for either preflight_passed or permission_repair_required. A started job is inspected with Refresh activation result rather than starting duplicates. Download activation result supplies the redacted outcome. Never send the access code, cookies, or private configuration.
Boundary
No production host changes were made. Native LiteSpeed, Passenger, production MySQL, and live autonomous acceptance were not tested here. The packaged successful routing/rollback transaction tests use simulated host operations.