A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I0928
A pull request cannot merge a deployment that would not work
Where it stands
devtask.issue- Readiness
- blocked 3 of its dependencies are not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
6- Waiting on
- Holds back
- Behind it in all
1- Evidence
0of2
| In the way | Subject | Detail |
|---|---|---|
| issue | I0919 | I0919 is not DONE |
| issue | I0921 | I0921 is not DONE |
| issue | I0930 | I0930 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Extend the existing verification workflow so that a pull request runs the deployment validation, the projection drift check, the production image build, the container smoke run, the resource policy assertions and the security checks.
- Why
- The gate is where these checks stop being optional. Adding a separate workflow for deployment would fragment a verification story the repository has already unified once.
- Now
- Two workflows exist: validation and pages. Neither knows anything about a deployment.
- Wanted
- One gate covers the deployment checks alongside everything else, uses the existing caching, and never deploys from a pull request.
- Done when
- unknown: the record declares no `completion`
- Risk
- A gate that takes an hour is a gate people bypass. The container build has to be cached well enough that the added time is proportionate.
Acceptance
- The pull request gate runs the tests, the deployment model validation, the projection drift check, the site build, the production image build, the container smoke run, the resource policy assertions and the security checks
- No pull request path can deploy to production
- Caching is used so the added checks do not make the gate unusable
- The added checks belong to the existing verification hierarchy rather than an unconnected script
- Validation
bash test/run.sh- Evidence required
pr_gategate_green- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
.github/workflows/validate.yml- Not
A second overlapping workflow fileDeploying to production from a pull request- Depends on
- Priority
- p0
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-06
- Updated
- 2026-09-06
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.