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
I2661
A publication that did not arrive is a finding the next reader meets, never a green step
Where it stands
devtask.issue- Readiness
- ready no dependency and no gate holds it; nobody has started it
- Status
- READY
- Can start
- startable
- Milestone
- Milestone status
- ACTIVE
- Wave
0- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
0of2
Moves
plan.transitionWhat it is
- Objective
- Make the gap between 'the workflow succeeded' and 'the site serves the commit' visible where a lander looks, the minute it exists.
- Why
- The owner, 2026-10-13: 'investigate what is slow ... solve it systemically, prevent it next time' and 'this must be analysed and solved through .ai/; it must not happen again'. Measured that day: a merge reached production 45 to 61 minutes later, and two landings of the evening were not served an hour after they merged.
- Now
- Measured 2026-10-13 on pages runs 38451796942 and 38446047641: the step that waits for /build.json to name the commit (scripts/pages verify --timeout 600) ran 602 s both times, to its limit, and is continue-on-error, so the deploy job ended green while production served the previous commit. The pages-live gate reads the live site only on the next validation run, which waited in the same queue.
- Wanted
- When the wait ends without the site serving the commit, the run says so in its summary and as an annotation, the timing row records 'not served', and a deployment record names the commit production does serve; a lander's verification reads that record. The wait itself is no longer the whole bound when the cause is known to be a queue: it reports what GitHub's deployment is waiting for.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- A run whose publication did not arrive within the bound is distinguishable from one that did without opening its log: summary, annotation and timing row
- scripts/pages verify names what the site serves and, when GitHub's own deployment is queued, that it is queued and since when
- A case breaks the wait with a site that never changes and proves each of the three signals
- Validation
bin/majordomus plan validatescripts/ci/shell-lintbash test/run.sh <the new case>- Evidence required
not_served_is_visible_caseone_real_run_with_a_late_publication- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
.github/workflows/pages.ymlscripts/pages.ai/repo/ci/pages.yamldocs/PAGES_STATUS.md.ai/repo/project/issues/I2661.yaml- Not
Failing the deploy job for a wait this repository does not controlPublishing by artifact, which is I2660- Depends on
- unknown: the record declares no `depends_on`
- Priority
- p1
- 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-10-13
- Updated
- 2026-10-13
- 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
| Level | Code | Message | Reproduce |
|---|---|---|---|
| WARN | scope_conflict | shares .github/workflows/pages.yml with I2662; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares .github/workflows/pages.yml with I2786; they may not run concurrently | majordomus plan validate |