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
I1511
The documentation surface answers in a checkout that has not built the site
Where it stands
devtask.issue- Readiness
- complete completion is recorded and every required evidence token is present
- Status
- DONE
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
0- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
1of1
Moves
plan.transitionWhat it is
- Objective
- Make /docs/ say what it needs rather than fail, so that a developer entering a fresh worktree does not meet a broken documentation surface as their first impression of the runtime.
- Why
- F4 of the audit's failure table. /docs/ is served from target/web/docs, which is a build output, so in any checkout that has not built the site the surface returns 503. Every other error this server produces is a model of what an error should say — the 404 body names the route and points at /openapi.json — and this one is the exception. It matters more than its size suggests because a fresh linked worktree is exactly where a new worker starts, and a documentation surface that is down is indistinguishable from a documentation surface that does not exist.
- Now
- GET /docs/ returns 503 with a 251-byte JSON body in a checkout whose site has not been built. Nothing on the way in says the surface has a build step.
- Wanted
- The surface either answers from something every checkout has, or returns an error that names the one command that would make it answer.
- Done when
- unknown: the record declares no `completion`
- Risk
- Low.
Acceptance
- A checkout that has not built the site gets an answer or an error naming the command that fixes it
- Nothing builds anything as a side effect of a GET
- Validation
bash test/run.sh- Evidence required
unbuilt_checkout_gets_a_useful_answer- Evidence present
unbuilt_checkout_gets_a_useful_answer
Scope
- Touches
apps/majordomus-cli/src/webdocs/COCKPIT.mdtest/cases- Not
Building the site as a side effect of serving. A read surface that triggers a build is the class of side effect the repository's own diagnostics rule forbids.- Depends on
- none
- Priority
- p2
- 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-11
- Updated
- 2026-10-14T07:58:59Z
- Started
- 2026-10-14T07:58:52Z
- Verified
- unknown: the record declares no `verified_at`
- Completed
- 2026-10-14T07:58:59Z
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.