datekeys-doc

Author	SHA1	Message	Date
dev	bf2187c690	Plan of format 3 in datekeys-ts: step 8 done Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	7 days ago
dev	0340f0f1c6	Plan of format 3 in datekeys-ts: step 7 done Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	7 days ago
dev	83fd9e1e2e	Plan of format 3 in datekeys-ts: step 6 done Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	1 week ago
dev	7c5781fca5	Plan of format 3 in datekeys-ts: step 5 done Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	1 week ago
dev	d08ffc0fd2	Plan of format 3 in datekeys-ts: step 4 done Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	1 week ago
dev	ce2f6b6bff	Plan of format 3 in datekeys-ts: steps 2 and 3 done Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	1 week ago
dev	05f8a96e7e	Plan of format 3 in datekeys-ts, and its first steps in the handoff The plan follows the one of the Go reference: the codec first, then the reader together with the testdata of spec-v0.10 in one commit, as the v0.9 did, since the guard of the harness wants every synced file read by a test; then the writer, the ZIP of the page and the two pages. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	1 week ago