internal/

Package arch implements the m/v waterline gates — the machine-checkable boundary between the engine-neutral `m` layer and the VistA-specific `v` layer (see docs/background/m-v-waterline-adr.md in the org `docs` repo).

Package config loads m-cli's project-level configuration — the [lint.*] and fmt sections of a `.m-cli.toml` (preferred) or a `[tool.m-cli]` table in pyproject.toml.

Package dispatch is the `m` busybox's sibling-binary dispatcher (spec §2.2, tracker [N12]).

Package engine is the runtime adapter — the only engine-bound code in m-cli (spec §8).

Package flow is m-cli's control-flow / dataflow infrastructure for the path-sensitive lint rules (spec §3.1; the Python tool's "Phase 7").

Package harness is the host-side trigger/render client for the resident pure-M harness (design §3.1, spec §9).

Package lint is m-cli's M source linter.

Package lsp is m-cli's Language Server (spec §3.1): LSP 3.x over stdio, reusing the lint and fmt engines so the editor shows exactly the diagnostics CI produces.

Package mcov is m-cli's coverage runner (spec §3.1/§8).

Package mfmt is m-cli's AST-preserving M source formatter (spec §3.1).

Package mtest is m-cli's test runner (spec §3.2): it discovers *TST.m suites, runs them through the Engine adapter, and parses the pure-M ^STDASSERT / TESTRUN output.

Package watch is the host-side half of `m watch` (spec §3.1, §9): a save triggered inner loop that re-runs the engine-neutral checks (lint, fmt) on changed files.

Package workspace is an in-memory cross-routine index of M source: every routine's labels (declarations) and outbound call sites (references).