oldhand-build

Implements a planned change the lazy, correct way: reuse what the codebase has, then the standard library, the platform and installed dependencies, and only then the least new code, fixing the whole class of bug at the shared point. Takes a baseline of the repo checks before the first edit, leaves one focused regression check, proves that check guards the fix with a mutation run (mutate.py), and compares the checks with the baseline. Records unit, integration and mutation results in the Oldhand ledger and writes build.md in the task's .oldhand folder. Use when the user says "implement the plan", "build the planned change" or "go ahead with the plan", or approves a plan from oldhand-plan. Not for planning, for investigating without a fix, for end-to-end QA (oldhand-qa), or for committing and pushing (oldhand-ship). One stage of oldhand; for a whole ticket or fix, use oldhand.

License

MIT