d-robotics/moss/patch-discipline

Patch discipline for moss

1. Read the real source before editing. Never guess behavior from file names.
2. Make the minimal change that fixes the problem. Match surrounding style; do not refactor neighbors in the same patch.
3. Every user-facing success message must come from a real probe, exit code, or post-condition — never a fixed string.
4. All subprocesses go through runProcess / spawnProcess from src/utils/run-process.ts; tool paths must not use execFileSync/execSync.
5. New tools must declare metadata.sideEffectClass (readonly vs mutating drives approval).
6. After a logic change: npm run build then run the touched spec (npm run test:filter -- --filter <module>). A bug fix needs a red-then-green regression spec.
7. Errors crossing tool/provider/CLI boundaries become MossError with the original cause preserved.