datekeys-go 4a025d1 applies all 22 corrections of the final review of the
v0.9 draft, plus four places that repeated them. The author decided
correction 2 on 29-09: the section 56 rule is softened, so the streaming
readers of Go and TypeScript stay valid. Correction 10 drafts open question
4 as a MAY. Step 1 of the work order is done; next is the author's approval
of the text.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new section 0 records the reorganization of 29-09 and what is left for
the author: renaming App to datekeys-ts once no session holds it open,
opening sessions at the workspace root, deleting the duplicate
enquiry.php, and giving docs and web a remote if wanted.
Section 2.5 now says what was checked: the final review of the v0.9 draft
has 22 entries, not 21, and none is applied in 1189f2f, so all are
pending. It points to spec_v0.9/review.md and names the entry that needs
the author's decision (the section 56 MUST NOT).
The repository table follows the new folder names, and the rules and the
document list now point to the README.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The handoff, the plans and the protocol review come unchanged from
go/DateKeys-App at f660f0c, where they lived in docs/. They describe the
whole project, not the TypeScript implementation, and they are internal,
so they get their own private repository.
spec_v0.9/ holds the working papers of the v0.9 draft (datekeys-go 1189f2f):
the design note, the two design reviews, the drafting report and the final
review with its 22 pending corrections. They were only in a temporary
session folder.
The README maps the workspace and carries the project rules, which the
handoff used to hold in its section 3.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dev