null 0d280d5415 docs: a check-in needs the project UUID, not the slug ... WORK_CYCLE.md's check-in example passed "projectId":"<slug>", which every other route on this API takes. This one does not: a slug is rejected with {"error":{"code":"unknown","message":"Something went wrong."}} — a message that names no field and reads like an outage. Cost two failed posts before the cause was found, on the run that wrote the entry above. The section now reads the id off the project first, and the extraction command in it was run against the live API rather than written from memory. Also records that there is no route to amend a check-in once posted, so the body has to be right on the first send. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>		2026-08-18 16:35:06 -05:00
..
architecture	docs: correct 57 claims the code and tracker disagreed with	2026-08-18 16:33:14 -05:00
data	docs: correct 57 claims the code and tracker disagreed with	2026-08-18 16:33:14 -05:00
design	docs: correct 57 claims the code and tracker disagreed with	2026-08-18 16:33:14 -05:00
history	docs: correct 57 claims the code and tracker disagreed with	2026-08-18 16:33:14 -05:00
planning	docs: correct 57 claims the code and tracker disagreed with	2026-08-18 16:33:14 -05:00
qa	docs: correct 57 claims the code and tracker disagreed with	2026-08-18 16:33:14 -05:00
security	docs: correct 57 claims the code and tracker disagreed with	2026-08-18 16:33:14 -05:00
DOC_TRUST_MAP.md	docs: correct 57 claims the code and tracker disagreed with	2026-08-18 16:33:14 -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