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
I1989
init seeds a scope for the stack it finds, not for this repository's
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
- ACTIVE
- Wave
0- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
1of1
Moves
plan.transitionWhat it is
- Objective
- Make the scope skeleton neutral, or detected from the adopter's files, rather than seeded with Elixir and Rust paths and a size cap that excludes committed build output.
- Why
- OSCILLA's scope.yaml was seeded with priv/**/*.exs, mix.exs and Cargo.toml, excludes **/dist/ and caps max_bytes at 1 MiB, while its deliverable is a committed 2.6 MB dist/index.html; scripts/** had to be added by hand (1655002, 1a4d708).
- Now
- share/skeleton scope is stack-specific.
- Wanted
- init writes a scope that names what the adopter's tree contains, and says what it guessed.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- init in a fixture JavaScript repository writes no Elixir or Rust paths into its scope
- Validation
bin/majordomus plan validateMJ_TEST_JOBS=4 bash test/run.sh <the case this issue adds>- Evidence required
init_scope_detected_case- Evidence present
init_scope_detected_case
Scope
- Touches
share/skeletonlib/init.shdocs/SCOPE.mdtest/cases- Not
- unknown: the record declares no `non_scope`
- Depends on
- unknown: the record declares no `depends_on`
- Priority
- p3
- 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-14T13:31:37Z
- Started
- 2026-10-14T13:31:18Z
- Verified
- unknown: the record declares no `verified_at`
- Completed
- 2026-10-14T13:31:37Z
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.