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
I1122
A foreign repository, adopted, upgraded and given back
Where it stands
devtask.issue- Readiness
- blocked 4 of its dependencies are not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
7- Waiting on
- Holds back
- Behind it in all
1- Evidence
0of3
| In the way | Subject | Detail |
|---|---|---|
| issue | I1110 | I1110 is not DONE |
| issue | I1111 | I1111 is not DONE |
| issue | I1116 | I1116 is not DONE |
| issue | I1121 | I1121 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Prove the contract against a repository that is not this one: adopt it, verify the footprint, run it again, upgrade the tool, edit a bridge by hand, then remove the adoption and compare what is left against what was there before.
- Why
- Every claim in this milestone is about somebody else's repository. Proving it here, where the tool and the subject are the same tree, proves the easy half; the interesting failures are the ones this repository cannot exhibit.
- Now
- Nothing has been adopted anywhere but here.
- Wanted
- One test drives the whole lifecycle on a foreign fixture and asserts each stage, including the ones designed to refuse.
- Done when
- unknown: the record declares no `completion`
- Risk
- An end-to-end test with a fixture the implementation special-cases proves nothing. The fixture has to be indistinguishable from a real repository.
Acceptance
- Adoption of a repository with no prior Majordomus state adds the two namespaces and the declared bridges, and nothing else, verified against the tree rather than against the report
- The second adoption changes nothing
- An adoption made by an older version reconciles forward without rewriting a bridge that did not need to change
- A bridge edited by a person is refused rather than overwritten, and reported
- Removal returns the repository to what it was, apart from authored content, compared against a recorded starting state
- The fixture is ordinary in every respect and nothing in the implementation recognises it
- Validation
bash test/run.sh- Evidence required
foreign_adoptionupgrade_pathremoval_restores- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
test/cases- Not
A fixture the implementation recognises as a testDeclaring success from the exit code of an adoption- Depends on
- Priority
- p0
- Profile
- deep-work
- 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-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.