Repository navigation
Description
Parent
Refs #15703
Source: PLAN Phase 9, topic ecosystem-specifics
Depends on
- Add the ecosystem-resolution contract, its decision record and the review rule #15706
- Cut the per-language property pages from testing:write as the pilot #15709
- Route codify findings by capability and hand the build to implement #15728
- Accept any recorded or inferred ecosystem id and any mutation tool value #15710
- Add ecosystem records to claude-code-proxy #15712, Add ecosystem records to ci-workflows #15713, Add ecosystem records to dotfiles #15714, Add ecosystem records to pr-pipeline-sandbox #15716, Add ecosystem records to github-iac #15717, Add ecosystem records to provisioning #15718, Add ecosystem records to standards #15719, Add ecosystem records to agent-automations #15720, Add ecosystem records to songwriting #15721, Add ecosystem records to ci-runner #15722, Add ecosystem records to cursor-plugins #15723, Add ecosystem records to claude-code-account-rotation #15724, Add ecosystem records to agent-plugins #15725, Add ecosystem records to the organization .github repository #15726, Add ecosystem records to codex-plugins #15727 (the owner's other lane repositories have their records)
Outcome
An unattended run executes only commands the repository states or its build files imply, logs each as an assumed: line with its source, installs nothing, writes no record, and reports a tie as unresolved. With no record and nothing inferable, the operation's cell reads skip (unresolved: <ecosystem>.<key>) and the run is INCOMPLETE.
Demo: run /toolchain:check --unattended in a fixture repository with one stated command and one ecosystem with nothing inferable; the first runs and is logged assumed:, the second reads skip (unresolved: ...), and nothing is written or installed.
This item changes what agents may do unattended; the owner approved that change with the plan. Its review gate is the security review, run at the frontier tier.
What changes:
/toolchain:checkand/toolchain:lintgain the--unattendedflag that/verification:confirmalready takes, and confirm passes it through. A run that cannot tell whether a person is present behaves as unattended.- Carrier rows for toolchain, corrections, discovery, review, implementation and verification are registered in the shared-copies list and regenerated, with a changelog fragment for each.
- In the check skill,
skip (unresolved: <ecosystem>.<key>)joins the environment class of the cell table and blocks "done". The install allowlist is unchanged. - The run-kind detector and codify's proof carve-out go in each carrier's routing site.
- The toolchain changelog fragment carries the migration note: unattended runs stop using bundled defaults here, what
skip (unresolved: ...)means, and how to add a record.
Method:
- Cases first, invoked with the
--unattendedflag only: a stated command runs and is loggedassumed:; an inferred command runs; with nothing runnable the phase readsskip (unresolved: ...)and no other command runs; a tie is reported unresolved; nothing is written (must-not-call graders for Write and Edit, plus a Bash input match for a redirect into the record path); nothing is installed. One more case: no flag and no non-interactive signal, but the run cannot tell whether a person is present; it must behave as unattended. - Content-dependent cases for the review ecosystem-specialist agent and the discovery explore fallback, which have none.
- Inference is limited to a manifest script, a task-runner target, or the build tool's own verb on a named entry point, with no added flag.
- Run budget: 1,600 runs (18 toolchain check and lint cases, 43 codify, 43 confirm, 5 discovery explore, about 8 implement and about 12 new, on the
opusandsonnetaliases, three runs per side, after two measuring runs). Select cases with--case, use--runs 3and a--max-cost-usdceiling, and start no batch after a usage-limit error. - Eval batches run in the one local eval-runner session in the main checkout. Open the pull request with the
do-not-mergelabel; the compare record releases it.
Decisions
- D5 (interview Q18, Q30): unattended lanes run only stated or inferred commands.
- D24: this item does not merge until every listed repository's records are merged and a
/toolchain:check allrun there shows noskip (unresolved: ...)cell. Owner: "I don't want anything to be 'we cannot accept incomplete.'" - Q42: the starting carrier set is testing, toolchain, corrections, discovery, review, implementation and verification.
- Constraint: no install, no text copied from CI files, each command logged as assumed with its source; an unsure run counts as unattended.
- Security and safety floors stay; removing or narrowing one is the owner's decision each time.
Key interfaces
- Lane record input: lines of the form
assumed: <ecosystem>.<key>=<value> (<file:line>), produced by an unattended run. - "
carrier(a plugin holding a synced copy of a contract text)." - Dependency direction: skills depend on contracts and reach each other only by
/plugin:skill.
Done when
- AC5: an unattended run executes only stated or inferred commands, logs each as assumed with its source, installs nothing, writes no record, and reports a tie as unresolved; every unattended case's verdict is pass in the compare record.
- AC4 (second clause): a repository with no record and nothing inferable shows a visible unresolved skip.
- The shared-copies list holds seven rows for the generic resolution text, and the shared-copy sync check passes.
- The check skill names the
--unattendedflag and the unresolved cell, and its install allowlist sentence is unchanged. - The security review gate passed; the pull request body names this repository's dogfooding step.
- AC7: nothing is cut here, so no control result is owed.
- AC10: no new enforcement-placing skill is added here.
Out of scope
- Deleting toolchain's bundled files (the next item on this path).
- The lane record writer.
- Any lane workflow file.
Metadata
Metadata
Assignees
Labels
Type
Fields
Work status
Priority
Activity
14 remaining items
melodic-automation-lanes commentedon Nov 13, 2026
Not admitted to the issue lane yet: Size large: the split into sub-issues at intake is pending (owner Q93).
melodic-automation-lanes commentedon Nov 14, 2026
Split at intake (owner Q93). This issue is Size Large, so its done-when is split into 3 sub-issues, each holding its task-list lines as written.
Automated split by the lanes App. Admission waits on this issue while a sub-issue is open; work-unblock closes it as completed once every sub-issue is closed as completed by a merge or a listed human and its done-when is covered.