null d7fe58883c fix: restore docs/TOOLS.md, deleted by a stray test commit ... Commit 6fc12b6 was a throwaway used to prove the pre-commit hook would accept a deletion-only commit. It was meant to be discarded locally, and it was — but the post-commit hook had already pushed it, so the deletion reached origin while the local reset removed the commit from my branch. Restored forward rather than force-pushed. The commit is on the remote, and rewriting published history to hide a two-minute mistake is a worse trade than a fix that explains itself. The lesson is why this message is longer than the diff. `git reset --hard` after a commit the post-commit hook has already pushed does not undo the push — and it silently discarded the uncommitted hook fix I was in the middle of proving, which is why the second proof then failed for a reason that had nothing to do with the guard. Commit the work before proving the guard, not after.		2026-08-18 15:00:17 -05:00
..
architecture	feat: fertility that declines rather than stretches	2026-08-18 14:56:05 -05:00
data	chore: adopt the project template and add the Kotlin/Compose skeleton	2026-08-18 02:16:47 -05:00
design	feat: the Today screen and its six states, with the number as the hero	2026-08-18 03:50:28 -05:00
history	docs: record Round 2 QA and the Batch 03 log entry	2026-08-18 04:05:58 -05:00
planning	chore: adopt the project template and add the Kotlin/Compose skeleton	2026-08-18 02:16:47 -05:00
qa	docs: record Round 2 QA and the Batch 03 log entry	2026-08-18 04:05:58 -05:00
security	docs: name not-yet-existing paths without backticks so doc-claims passes	2026-08-18 02:18:25 -05:00
DOC_TRUST_MAP.md	docs: name not-yet-existing paths without backticks so doc-claims passes	2026-08-18 02:18:25 -05:00
TOOLS.md	fix: restore docs/TOOLS.md, deleted by a stray test commit	2026-08-18 15:00:17 -05:00
WORK_CYCLE.md	docs: name not-yet-existing paths without backticks so doc-claims passes	2026-08-18 02:18:25 -05:00