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
I1407
One issue travels the whole path and back, as an executable case
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
- VERIFY
- Wave
3- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
1of1
Moves
plan.transitionWhat it is
- Objective
- Prove the milestone with a case that carries one synthetic issue from outcome to accepted completion and then traverses the same chain backwards, offline, against fixtures.
- Why
- Every claim in this milestone is about a chain, and a chain is only proved end to end. Testing each link separately is how a model passes its tests and still cannot answer which outcome a merged pull request served.
- Now
- test/cases/45_github_projection.sh covers the adapter's rendering and its refusal to overwrite. Nothing covers the path from milestone through branch, commit and pull request to accepted evidence.
- Wanted
- A case builds a synthetic repository, walks the chain forwards and backwards, and fails if any link cannot be derived.
- Done when
- unknown: the record declares no `completion`
- Risk
- Low, once the links exist.
Acceptance
- The forward path is derived: milestone, issue, branch, worktree, commits, pull request, checks, evidence, accepted
- The backward path is derived from a merged commit to the acceptance criteria it satisfied and the outcome it served
- The case runs offline against fixtures and is deterministic
- Completion is refused when evidence is absent even though the remote issue is closed, proved by the case
- Validation
bash test/run.shmajordomus usecase coverage- Evidence required
chain_proved_both_ways- Evidence present
chain_proved_both_ways
Scope
- Touches
test/casesapps/majordomus-cli/tests.ai/repo/use-cases- Not
A test that reaches the network by default- Depends on
- Priority
- p1
- Profile
- implementation
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-09
- Updated
- 2026-09-09T22:00:58Z
- Started
- 2026-09-09T22:00:42Z
- Verified
- 2026-09-09T22:00:54Z
- Completed
- 2026-09-09T22:00:58Z
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.