I0104 — Move the claim from planned to guaranteed

Update docs/CLAIMS.yaml and the claim's detail page so the public surface states what is now true, with the file that implements it and the test that proves it.

DONE wave 3 · p2 · implementation profile · parallel safe

Part of M001 — A blocking question survives a handover.

Objective

Update docs/CLAIMS.yaml and the claim's detail page so the public surface states what is now true, with the file that implements it and the test that proves it.

Why

A capability that works and is still published as planned understates the tool; one published as guaranteed without a test overstates it. The matrix is the only place either is caught.

Current state

blocker-survives-handover is planned, with implementation and test both '-', and a note describing the gap.

Desired state

The claim is guaranteed, cites lib/question.sh and the case from I0103, and its detail page says what the behaviour does not cover.

Scope

docs/CLAIMS.yaml
docs/claims
docs/CONTINUITY.md

Out of scope

Any behaviour change

Dependencies

I0103DONE Implement the decision and prove it holds

Acceptance criteria

The claim is guaranteed and both paths exist
The detail page has a section saying what the behaviour does not cover
The generated site data regenerates without a stale file

Validation

scripts/generate-site-data --check
bash test/run.sh

Evidence required

docs_build

Evidence

covers	type	command	result	at commit
docs_build	build	scripts/generate-site-data --check && bin/majordomus doctor	in sync, doctor 0 failures — the claim is guaranteed with lib/check.sh and test/cases/50_blocker_across_handover.sh, its detail page states the case the behaviour is deliberately wrong in, and the doctrine summary matches the implemented gate	83b72cb

Risk

Promoting a claim is the moment the repository starts being believed on it.

Timeline

started: 2026-09-04T07:32:26Z
verified: 2026-09-04T07:34:55Z
completed: 2026-09-04T07:34:58Z

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I0104.yaml. Read it back with majordomus plan show I0104.