Merge remote-tracking branch 'origin/mantra' into claude/subgroups-multiple-parents-053be4

docs/README.md

@@ -17,8 +17,15 @@ silent, or a decision that looked arbitrary and was not.
 | [mls-skipped-keys.md](./mls-skipped-keys.md) | why a group event that arrives a moment late is dropped for good, which flows trigger it, the quartz fix, and the partial mitigation in this app |
 | [long-running-sync.md](./long-running-sync.md) | the chat subscriptions that stay open instead of pulling once per screen — why the request queue could not simply hold one, and how the group filter follows the room list |
 | [dead-code.md](./dead-code.md) | code in the sync and relay stack that nothing calls, why each piece is still there, and which of it is a bug rather than a leftover |
+| [nsec-sign-in.md](./nsec-sign-in.md) | signing in with an existing nostr key — why an nsec can never have a wallet behind it, the ten call sites that make it small, and the sign-in machine that was already built and unreachable |
+| [npub-sign-in.md](./npub-sign-in.md) | signing in with only a public key — what a key that cannot sign can still see here, why that is a preview rather than a browser, and the four decisions the word settles |
+| [multiple-profiles.md](./multiple-profiles.md) | several profiles on one device — why a profile is a credential and a seed is a wallet attached to one, why a switch is a restart rather than a swap, the two entrances the app lacks, and the inbox a switch would silently lose |
 | [jvm-target.md](./jvm-target.md) | what desktop support cost, phased — why the native chain was already done, why an empty source set in our phoenix fork was the real blocker, and why DAO tests need none of it |
+| [npub-profile-preview.md](./npub-profile-preview.md) | showing the person before a direct message is started from a pasted npub — why the preview is a screen keyed by public key, what "found" means when a row can be a placeholder, and the phase that makes the button honest about a key package that never comes |
 | [material-design-conformance.md](./material-design-conformance.md) | what the M3 foundations actually require, measured against all 43 screens — the colour pairing that renders the app's own proposals invisible, and eight phases that put the decisions back in the theme |
+| [curated-to-mantra.md](./curated-to-mantra.md) | pulling the Curated fork's thirty-nine commits back under Mantra's names — which lines of work to take, the three decisions, and a measured way to replay a twice-rebranded history without touching seven hundred files by hand |
+| [curated-to-mantra-profiles.md](./curated-to-mantra-profiles.md) | the second pull: the fork's several-profiles line, ten commits and its first schema migration — which of it is a fix Mantra has today, who allocates a schema version number when two trees share one history, and the one conflict, which was Mantra's own |
+| [curated-to-mantra-preview.md](./curated-to-mantra-preview.md) | the third pull: the profile preview and the extended FAB, eleven commits — a brand token hidden in CamelCase, a commit half in a removed line taken as a partial pick, and the two conflicts the compiler found where git saw none |
 
 Start with the ceremony if you are new to this area; the Marmot notes all assume it.
 Read the skipped-keys note before debugging any "the other device never got it"
@@ -40,3 +47,33 @@ subgroup does, because no ceremony is involved.
 The Material Design note is a phased plan that has not been built, and is the
 only one about what the app looks like rather than what it does; read the
 jvm-target note first if you want to know why its adaptive-layout phase exists.
+The curated-to-mantra note is a phased plan that has been built, save for its last
+phase, which is a decision: it is about the repository rather than the app, and reads
+alone, except that its first decision leans on the derivation note's one rule. Two of
+the lines it pulled -- the group's nostr identity and the curated lists -- were taken
+out again the same day, and its record says what went and what stayed. The nsec and
+npub sign-in notes arrived with it and record what they built. The profiles pull note
+is the same exercise a second time, planned with its dry run already done and built
+the same day; read it after the first, because it assumes the method and the three
+decisions and only says what changed — chiefly that the tree is no longer a superset,
+and what the check for an exact pull becomes when it is not. The preview pull note is
+the third and shortest; read it for the two kinds of resolution the first two never needed.
+The nsec sign-in note is a phased plan that has been built; it inherits the
+key-storage decision from the jvm-target note and drives the navigation state
+machine `NavigationViewModel.processLocalAccount` implements, so read it with the
+code open, and read its table of where the build chose differently first.
+The npub sign-in note is a phased plan that has been built, and reads as that
+plan's out-of-scope note answered: it takes the `Identity` type and the sign-in
+machine as given and asks what an identity with no secret is for, before it asks
+how to build one; read its table of where the build chose differently first.
+The multiple-profiles note is a phased plan that has been built, and reads as the
+third of the sign-in notes: it asks what happens when the device holds two
+identities, and its first phase changes one rule the other two share — a seed's
+key becomes a credential like any other — so read it with `StoredIdentity.merge`,
+`SovereignWalletViewModel.switchToIdentity` and the startup screen open, and read
+its table of where the build chose differently first.
+The npub profile preview note is a phased plan that has been built, and is the
+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.