null b73bc85583 docs: record Batch 09, and close half the long-horizon QA gap ... ClaudeQACoverage has carried "long-horizon accuracy is tested only at the unit level" as a standing gap for four rounds. The simulated-history half is now closed by LearningCurveTest, and the entry says so -- along with what it found, since a harness that changed nothing would be a weaker claim than one that caught two real faults. The other half stays open and is stated plainly: a simulation exercises the engine, not the app. Nothing here proves a real install accumulates those cycles correctly over a year, that snapshots survive updates and time-zone changes, or that the accuracy card shows what the engine computed. That needs elapsed time on a device. Development log entry per WORK_CYCLE step 6, including the two corrections this batch made to its own plan: the coverage dip was a 40-seed artifact, and a swept constant shipped one value away from the measured one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>		2026-08-20 16:39:30 -05:00
..
architecture	feat: project the next year onto the calendar, and say what it assumes	2026-08-20 16:38:30 -05:00
data	feat: the wordmark has its space, and logo and banner say so	2026-08-18 22:12:33 -05:00
design	feat: project the next year onto the calendar, and say what it assumes	2026-08-20 16:38:30 -05:00
history	docs: record Batch 09, and close half the long-horizon QA gap	2026-08-20 16:39:30 -05:00
planning	docs: correct 57 claims the code and tracker disagreed with	2026-08-18 16:33:14 -05:00
qa	docs: record Batch 09, and close half the long-horizon QA gap	2026-08-20 16:39:30 -05:00
security	ui: add discreet launcher alias	2026-08-20 02:37:29 -05:00
DOC_TRUST_MAP.md	docs: separate the constants that are physiology from the ones that are tuning	2026-08-20 16:32:16 -05:00
TOOLS.md	docs: correct 57 claims the code and tracker disagreed with	2026-08-18 16:33:14 -05:00
WORK_CYCLE.md	docs: a check-in needs the project UUID, not the slug	2026-08-18 16:35:06 -05:00