laantungir/amethyst
1
0
Fork 0
mirror of https://github.com/vitorpamplona/amethyst.git synced 2026-07-22 07:48:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(buzz): sync README with canvas viewer + edit composer; note no reaction kind

Browse Source 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J8KBSw6smQRyXLiWHeDsZ8
This commit is contained in:
Claude
2026-07-22 02:26:43 +00:00
parent fb7bdf3057
commit f869834e9d
1 changed files with 19 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
quartz/src/commonMain/kotlin/com/vitorpamplona/quartz/buzz/README.md
View File

@@ -166,10 +166,25 @@ AUTHs that share the template — so an un-enrolled agent key gets virtual membe
its owner stays a member. The paste/hold + owner-side issue flows both live in
`AgentAttestationScreen`. (Store is in-memory for now; persisting per-account is a follow-up.)
Not yet wired (write path): the edit composer (40003) and forum/job/huddle/DM message
composers, plus Buzz-native reactions/deletes — all require changes to the central chat
composer and are deferred to a focused pass. The canvas (40100) is now requested and
consumed as overlay state but has no dedicated viewer yet.
The **canvas (40100)** now has a viewer: `BuzzWorkspaceState` exposes a `canvasUpdates`
flow and `amethyst/.../buzz/BuzzCanvasScreen` (`Route.BuzzCanvas`) renders the newest
markdown, reached from a Dashboard action in the relay-group top bar that appears only on
a Buzz relay once a canvas has arrived.
The **edit composer (40003)** is wired: `ChannelNewMessageViewModel` has a Buzz edit mode
(`editBuzzMessage`/`clearBuzzEdit`) whose next send publishes a 40003 targeting the
original (minimal, mirroring Buzz's `build_edit`); an "Edit" action gated to the user's
own 40002 messages threads to the composer through the shared chat feed via an optional
`onWantsToEditBuzz` callback (default-null, so no other chat surface is affected), and
`EditFieldRow` shows an editing banner. This closes the render↔create loop (edit overlays
already rendered).
Still not wired (write path): the forum/job/huddle/DM message composers — each a
send flow for a richer kind, and jobs/huddles are among the schema-inferred kinds, so
they want Buzz-side confirmation before UI. Buzz has **no** stream-message reaction kind
(reactions aren't part of its workspace model), so there is nothing to wire there.
Persisting held attestations per-account (currently in-memory) needs a KMP storage
abstraction and is a follow-up.
## Owner Attestation (NIP-OA) — implemented