Summary
Web CD does not watch the Workbench package even though app/Dockerfile copies and builds it. A Workbench-only change can pass checks and merge without producing a refreshed Web image.
Verified reproduction
Scope / acceptance
- Cover Workbench source changes in the existing Web CD workflow's path filter; inspect the remaining declared build inputs for the same mismatch without broad CI refactoring.
- Validate the workflow with existing CI checks. Prove that a Workbench-only change selects Web CD; keep unrelated changes filtered out.
- After the fix, explicitly publish an image for the intended source revision if needed. A successful image build is not evidence of a running deployment.
Negative constraints
No product lifecycle/state-machine work, no runtime deployment, no secrets/host metadata, and no CI gate relaxation. Keep image publication and deployment as separate operations.
Summary
Web CD does not watch the Workbench package even though
app/Dockerfilecopies and builds it. A Workbench-only change can pass checks and merge without producing a refreshed Web image.Verified reproduction
319bebe37425c2b20c994f952358f7c538c6185eon 2026-09-05; its entire changed-file set is underapp/workbench/.checksrun succeeded: https://github.com/TokenDanceLab/AgentHub/actions/runs/33954105140.github/workflows/cd-web.ymlhas noapp/workbench/**entry inon.push.paths; the latest successful Web CD run remains the preceding commita944fc0feece7915e6a967959ec136d1c73415cf: https://github.com/TokenDanceLab/AgentHub/actions/runs/33951708167app/DockerfileincludesCOPY workbench/package.jsonandCOPY workbench ./workbench, so this is a real build-input coverage gap, not an unused directory.Scope / acceptance
Negative constraints
No product lifecycle/state-machine work, no runtime deployment, no secrets/host metadata, and no CI gate relaxation. Keep image publication and deployment as separate operations.