Audit — task-breakdown.md minor typos
Post-R83 hygiene pass over docs/guides/implementation/task-breakdown.md identified two self-contained typos via single-file grep. Each occurs exactly once in the file.
Drift
| Line | Current | Correct | Source of truth |
|---|---|---|---|
| 584 | MAX_INTEGER_OPS=10000 |
MAX_INTEGER_OPS=10_000 |
Internal: L669 of the same file names the same constant as 10_000. Convention is numeric underscore separators for readability. |
| 797 | bps_apply(score, decay_rate) |
apply_bps(score, decay_rate) |
Canonical definition at L474: apply_bps(value, bps). Live code at src/domains/rules/integer-math.ts:110 exports apply_bps. The bps_apply form at L797 is a transposition typo. |
Scope
- File:
docs/guides/implementation/task-breakdown.mdonly. - Two one-line edits; zero semantic change to the specified behaviour (just names the correct function).
- No runtime code edits (the live code already uses the correct names).
Non-scope
- Additions of new spec content, threat models, BFT n≥4 notes, or any other “expand the spec” work — out of scope per instruction.
- Broader critique of speculative P2–P7 content — out of scope.
- Output-path consistency (
src/domains/rules/__tests__/…vssrc/__tests__/domains/rules/…) — present in the file but is a systematic pattern, not a typo; separate hygiene candidate.