Repository navigation
feat(statechart): ask before installing mise - #31
Conversation
Upstream's skill assumes mise is installed. Without it, the run fails with "spawn mise ENOENT", and agents then searched the disk, downloaded Java, or installed mise without asking. Before modelling, the agent now checks for mise on PATH or TLA2TOOLS. If neither is there, it asks whether to install mise for the user. It continues on yes and stops with the TLA2TOOLS alternative on no. Upstream's own setup line stays verbatim; the added paragraph is recorded as an adaptation.
|
Verdict: PASS+NOTES Reviewed head 1. Diff scope. PASS. Five files changed, all in the allowed set: 2. Claim fact-check. PASS. Paragraph in
Changed sentence in
3. Real surface runs. PASS. Fixture copied to a fresh directory per arm,
4. Repository checks. PASS. Notes, non-blocking.
Transcripts from the four headless sessions are kept at |
Why
/statechartshould work like Lauren's skill, and it should never install anything you didn't approve. Upstream assumes mise is already installed. Without it, the run fails withspawn mise ENOENT, and agents improvised: one downloaded a Java runtime, another installed mise without asking.What changed
miseorTLA2TOOLS. If neither is there, it asks before it installs mise for your user.TLA2TOOLSalternative. It never searches the disk or downloads Java itself.upstream.json, and the README says so.Scope
Blast Radius
Only
/statechartruns on a machine with neither mise norTLA2TOOLSchange. They now pause for a yes or no. An unattended run on such a machine, like a routine or an autopilot pass, ends with that question instead of failing withspawn mise ENOENT.Verification
PATH, and separately withTLA2TOOLSset, this branch asked nothing and went straight to TLC and the chart.bun run check:contentandbun run typecheckpass. The Benny proof was regenerated for the checker edit.