feat: sync latest ARR implementation
This commit is contained in:
@@ -29,6 +29,12 @@ Does the publishable source snapshot open XML processing through both supported
|
||||
|
||||
The repository snapshot now makes direct Docker-image launches and Compose launches consistent: both request XML processing, while the source CLI remains default-closed and the page opens upload only after the database, guarded OSS, SuperAgent and HMAC runtime initialize. The documented Compose topology protects Web traffic with Caddy HTTPS plus Basic Auth, and MCP retains application bearer authentication.
|
||||
|
||||
## Authentication Supersession Note — 2026-07-30
|
||||
|
||||
The paragraph above remains historical evidence for the 2026-07-29 published snapshot. Current ARR2 deployment no
|
||||
longer uses Caddy Basic Auth or an active MCP surface: Caddy terminates HTTPS, ARR Web owns login/session/CSRF/logout,
|
||||
and Compose injects `ARR_WEB_USERNAME` / `ARR_WEB_PASSWORD`. Use the current root and `deploy/` runbooks.
|
||||
|
||||
## Impact
|
||||
|
||||
The server must rebuild/redeploy the image; a platform-level CMD override must retain `--enable-processing`. `processing_ready=true` remains the deployment prerequisite, but business completion still requires SuperAgent tool rediscovery and an MCP `committed`/`already_committed` receipt with matching database facts.
|
||||
|
||||
Reference in New Issue
Block a user