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
I1988
A use case's setup scripts live where the adopter declares, and its scenarios may run the adopter's own commands
Where it stands
devtask.issue- Readiness
- ready no dependency and no gate holds it; nobody has started it
- Status
- READY
- Can start
- startable
- Milestone
- Milestone status
- ACTIVE
- Wave
1- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
0of1
Moves
plan.transitionWhat it is
- Objective
- Declare the use-case setup directory in the manifest instead of hard-coding this repository's test/fixtures/commands/setup, and allow a scenario step to run commands the adopter declares, judged by the same effect classes as I1981.
- Why
- OSCILLA's test/fixtures/commands/setup/oscilla-tree.sh exists only because 'that path is fixed by the tool' (cb79d27), and its scenarios can run only bin/majordomus, so an adopter cannot prove its own product behaviour with use cases.
- Now
- lib/usecase.sh resolves setup scripts under a fixed path and runs only the tool.
- Wanted
- A manifest key names the setup directory; declared external commands are allowed in scenarios under the effect rules.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- A fixture adopter with setup scripts under its declared path runs its scenarios
- A scenario step running an undeclared external command is refused
- Validation
bin/majordomus plan validateMJ_TEST_JOBS=4 bash test/run.sh <the case this issue adds>- Evidence required
declared_setup_path_case- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
lib/usecase.shshare/schemasshare/skeletondocstest/cases- Not
- unknown: the record declares no `non_scope`
- Depends on
- 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-10-04
- Updated
- 2026-10-04
- 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
| Level | Code | Message | Reproduce |
|---|---|---|---|
| WARN | scope_conflict | shares share/schemas with I2401; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2403; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares docs with I2484; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares docs with I2700; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares share/schemas with I2701; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares docs with I2702; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares docs with I2704; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares docs with I2705; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares docs with I2706; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2708; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares docs with I2709; they may not run concurrently | majordomus plan validate |