I3999 — A fixture holds the skills the site generator reads
fixture_repo copies .claude/skills, which scripts/generate-site-data reads for every skill its artifacts manifest names, so the cases that build a fixture and run the generator (10, 11, 37) pass on a checkout that has the skills.
READY wave 0 · p1 · implementation profile · runs alone
Ready. Every dependency is done, so majordomus plan start I3999 will be accepted.
Objective
fixture_repo copies .claude/skills, which scripts/generate-site-data reads for every skill its artifacts manifest names, so the cases that build a fixture and run the generator (10, 11, 37) pass on a checkout that has the skills.
Why
On 2026-10-23 cases 10_site_data, 11_site_derivation and 37_responsibility_surface failed with sed: .claude/skills/<id>/SKILL.md: No such file or directory. The generator reads those files since ADR 0165, they are the editors projection's output and so not canonical inputs, and fixture_repo copied only what --inputs names.
Current state
test/lib.sh fixture_repo copies the generator's inputs, the layer and the generated registry files, and not .claude/skills.
Desired state
A fixture holds the skills directory; a new case proves every skill file the manifest names is present in it.
Scope
- test/lib.sh
- test/cases/3999_a_fixture_holds_the_skills_the_generator_reads.sh
- .ai/repo/project/issues/I3999.yaml
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- Cases 10, 11 and 37 pass on a checkout that has .claude/skills
- Case 3999 fails when a fixture lacks a skill file the manifest names
Validation
- bin/majordomus plan validate
- env -u MAJORDOMUS_SHARE -u MAJORDOMUS_HTTP_HOST -u MJ_ROOT bash test/run.sh 3999_a_fixture_holds_the_skills_the_generator_reads
Evidence required
- fixture_holds_the_skills
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Timeline
- started
- —
- verified
- —
- completed
- —
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/I3999.yaml. Read it back with majordomus plan show I3999.