al-compileOffline-compile an AL project with alc.exe and report diagnostics — the standalone verification for AL edits (AL has no unit-test harness here). Use when you changed AL in extensions/lethal-control or an emitted instrumented target and want to confirm it builds before the live gate. Invoke as /al-co
al-probeScaffold, publish and run a throwaway AL probe app against a LethAL BC container to MEASURE real Business Central behaviour instead of reasoning about it. Use when a claim about what BC actually does is load-bearing — before writing it into a spec, a comment, a roadmap row or a verdict rule. Knows t
control-appRebuild the LethAL Control BC extension and publish it to the target containers. Use after editing anything under extensions/lethal-control, after bumping its app.json version, or when a live gate refuses with "The deployed LethAL Control app reports version X, older than the Y this client requires"
coverage-differentialRun the two-mode differential gate for any change to coverage collection, selection or attribution — one project twice, identical except the coverage mode, compared per mutant on a verified join. Use before claiming such a change is safe, because the frozen live gates cannot detect these regressions
live-gateRun the LethAL live integration gate against the Cronus BC container — the frozen per-mutant tables through both backends. Use when validating a layer end-to-end on live infra, or when the user says "run the live gate" / "run the itests live". Publishes to a live BC container, so it is user-invoked
measurement-campaignUse when running LethAL against a real project or customer app, measuring a real codebase's suite, comparing two live runs, or writing a pre-commitment for any of those. Drives live, billed environments.
recover-tierRecover a LethAL tier that is quarantined or holding a stranded operation marker — recycle the environment, force-reset the lease, clear the quarantine. Use when a run refuses with "tier ... is quarantined", "container-needs-recycle", or "operation-orphaned". Publishes to and force-clears state on a
releaseCut a LethAL release end to end — version bump, CHANGELOG section, README version references, the local and live gates, then the tag that triggers .github/workflows/release.yml. Use when asked to cut, tag, ship or publish a release, to bump the version, or when a release draft needs finishing. Cover
repo-scriptsUse BEFORE writing an inline shell or bun one-off for any of these: running the build/test loop (typecheck, clean dist, bun test), finding the next free roadmap id or setting a roadmap row's status, checking coord status (pause, questions, stale, doing, checkpoints, Cronus leases), summarising or di
lethal-mutation-testingRun LethAL mutation testing against a Business Central AL project and read the result. Use when asked whether an AL test suite actually catches bugs, to find weak or missing tests, or to check a suite before trusting a coverage number. Publishes a changed build to a BC server, so it needs a sandbox