fix: enable XML processing in container entry
This commit is contained in:
@@ -0,0 +1,23 @@
|
||||
# Verify every production container entrypoint
|
||||
|
||||
## Trigger
|
||||
|
||||
The deployment snapshot explicitly enabled XML processing in the Compose Web command,
|
||||
but the Dockerfile default CMD omitted `--enable-processing`. A platform that built and
|
||||
ran the image directly therefore served the page with processing disabled even when all
|
||||
runtime environment values were present.
|
||||
|
||||
## Lesson
|
||||
|
||||
A deployment feature flag is not verified merely because one orchestrator profile
|
||||
contains it. Every supported executable entrypoint must agree: image CMD, Compose
|
||||
command and any documented platform override. Runtime readiness remains a separate
|
||||
gate and must not be replaced by a static flag assertion.
|
||||
|
||||
## Action
|
||||
|
||||
- Parse the Dockerfile CMD in an automated test and require the intended processing flag.
|
||||
- Assert that unrelated mutation flags remain absent.
|
||||
- Keep the source CLI default closed and require `/api/health` to report
|
||||
`processing_ready=true` after deployment.
|
||||
- Tell operators that replacing CMD/command also replaces the feature flag.
|
||||
@@ -4,6 +4,7 @@ Use this index for second-order workflow lessons.
|
||||
|
||||
| Date | Reflection | Trigger | Action | Detail |
|
||||
|---|---|---|---|---|
|
||||
| 2026-07-29 | Verify every production container entrypoint | XML processing was enabled in Compose but omitted from Dockerfile CMD, so direct image launches stayed closed | Add a regression test for Dockerfile CMD and document platform command overrides | [Case](cases/2026-07-29-verify-all-container-entrypoints.md) |
|
||||
| 2026-07-29 | Remote Agent success is not a database commit | Repeated live runs ended remotely without an MCP submission | Add a multi-signal acceptance gate and preserve failed-run cleanup evidence | [Case](cases/2026-07-29-remote-success-is-not-a-database-commit.md) |
|
||||
| 2026-07-29 | Internal parameters are not user inputs | Human correction of the monthly-report workflow | Update docs and promote the boundary to ADR-001 | [Case](cases/2026-07-29-internal-parameters-are-not-user-inputs.md) |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user