shiyuyun/wyndham-ARR
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record XML upload activation

Browse Source
This commit is contained in:
Wyndham ARR
2026-07-29 18:36:59 +08:00
parent ad3d9878c5
commit d6f8a747fa
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.project-docs/50-evidence/topics/2026-07-29-public-deployment-repository.md
View File

@@ -17,7 +17,7 @@ Does the publishable source snapshot open XML processing through both supported
## Evidence
- Files: `Dockerfile`, `compose.yaml`, `deploy/Caddyfile`, `deploy/.env.production.example`, `deploy/README.md`, `arr_web/app.py`, `arr_web/run.py`, `tests/test_arr_web.py`.
- Git: initial deployment snapshot commit `a701de9f0eff7402fe1785c3b35de5652576152a` was pushed to `origin/main`; an independent `ls-remote` check is required after the documentation closeout commit as the final publication proof.
- Git: initial deployment snapshot commit `a701de9f0eff7402fe1785c3b35de5652576152a` and XML-entry fix commit `ad3d9878c5aa8d956339ef6871322000e694f5ca` were pushed to `origin/main`; independent `ls-remote` returned the fix SHA before the documentation closeout commit.
- Deployment command inspection: Dockerfile default Web CMD and Compose Web command both contain `--enable-processing`; Compose also contains `--secure-cookies`. Only Caddy maps host ports 80/443 in the documented Compose topology, while Web and MCP use internal `expose` ports.
- Regression: `tests/test_deployment_entrypoints.py` parses the Dockerfile JSON CMD, requires `--enable-processing`, and rejects accidental enablement of monthly, company-report or legacy Agent-writeback mutations.
- Tests: Python 3.12 full discovery ran 260 tests successfully; 2 environment-dependent artifact-tool tests were skipped.