Phase 5 of docs/project-feature.md. Three kinds appended to
`ChronicleEvent.APPLY_ORDER`, which is all the mechanism needs:
`CHRONICLABLE_KINDS`, `applyRank`, `inApplyOrder` and `isChroniclable` all derive
from that one list, and `signedEventsOf` already filters on it.
Appending is not arbitrary. A membership is a foreign key into both a project
and a version, so it has to apply after everything it can name, and putting the
three on the end gets that right by construction -- everything a project groups
is already above it. A page in the wrong order is a refused insert on the one
device with nothing to fall back on.
Then four existing tests failed, and each was telling the truth.
Three of them compare what a seeded room chronicles against CHRONICLABLE_KINDS
itself, so a kind added to the set and not to the seed fails them. That is the
point of writing them that way, so the project went into the canonical seed in
both chronicle suites rather than into a helper beside them.
The fourth is the one worth reading. `every chroniclable kind has a round-trip
test above` asserts that every kind a chronicle carries can also be rebuilt from
its row -- and projects deliberately cannot, because the rebuild exists for
rooms older than schema v13 and projects arrive at v21. So the meta-test now
excludes them explicitly, and the gap is pinned where it actually bites: `a
project is only ever chronicled off the record` holds a project whose
`GroupSignedEvent` is missing and shows the row is there and the chronicle is
not. That is reachable -- `recordSignedEvents` catches its own failure so a
ceremony that succeeded is not reported as failed -- and it is worth knowing is
possible rather than worth preventing.
`the rebuild alone reaches everything but the projects` pins the other side, so
anyone adding a `toProjectEvent` fails a test that tells them where the comment
explaining why is.
Also corrected a stale count in the allowlist's own comment: it said six of
thirteen nip30303 kinds reach a signing session while the list below it had
eight. Eleven of sixteen now, with `SubmissionEvent` named among the exclusions
since it is the envelope rather than the work.
1403 tests, no failures.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
5fac2fc7b7