I1989 — init seeds a scope for the stack it finds, not for this repository's
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.
DONE wave 0 · p3 · implementation profile · parallel safe
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).
Current state
share/skeleton scope is stack-specific.
Desired state
init writes a scope that names what the adopter's tree contains, and says what it guessed.
Scope
- share/skeleton
- lib/init.sh
- docs/SCOPE.md
- test/cases
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- init in a fixture JavaScript repository writes no Elixir or Rust paths into its scope
Validation
- bin/majordomus plan validate
- MJ_TEST_JOBS=4 bash test/run.sh <the case this issue adds>
Evidence required
- init_scope_detected_case
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| init_scope_detected_case | test | MJ_TEST_JOBS=2 bash test/run.sh 3016_init_seeds_the_scope_of_the_stack_it_finds 93_scope_policy | tests: 2 passed, 0 failed: empty, JavaScript, Rust, Elixir and both (run 2026-10-14 13:30Z on master 4ec504616c plus this change) | 4ec5046 |
Timeline
- started
- 2026-10-14T13:31:18Z
- verified
- —
- completed
- 2026-10-14T13:31:37Z
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/I1989.yaml. Read it back with majordomus plan show I1989.