docs: record what building projects changed about the plan
Five places the build chose differently, and one thing the plan did not anticipate: a project reaches a chronicle only off the GroupSignedEvent record, because the deprecated rebuild has no `toProjectEvent` and deliberately never will. `recordSignedEvents` catches its own failure so a ceremony that succeeded is not reported as failed, which leaves a narrow window where the row exists and the signed event does not -- a project this device can show and can never hand on. There is a test holding that case open. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -73,10 +73,12 @@ smallest of the plans: it changes the entrance to the direct-message flow and
|
||||
nothing past it, so read it with `StartDirectMessageToNpubOrNip05Dialog` and
|
||||
`ChatRoomMessagingViewModel.initiateNewChat` open, its four decisions before its
|
||||
four phases, and its table of where the build chose differently first.
|
||||
The projects note is a phased plan that has not been built, and is the only one
|
||||
The projects note is a phased plan that has been built as far as its seventh
|
||||
phase, and is the only one
|
||||
whose starting point is outside this repository: the platform's server schema,
|
||||
`mantra-db-models`, has had the three models for years. It reads as the
|
||||
translation domain's unanswered question — the app can say what a chapter is and
|
||||
who translated it, and cannot say what any of it is for — so read it after the
|
||||
nip30303 conventions are familiar, its decisions before its phases, and its scope
|
||||
fork before either, because that one changes the shape of the rest.
|
||||
fork before either, because that one changes the shape of the rest, and its
|
||||
table of where the build chose differently first.
|
||||
|
||||
Reference in New Issue
Block a user