Add Buzz DKG Integration

[Zigoljube]

What this adds

Registry entry for Buzz DKG Integration — a daemon that joins Buzz rooms as an external Nostr member, turns pinned / @dkg distill-mentioned threads into single-root PROV-O Knowledge Assets (WM → finalize → full atomic SWM share), gates VM publication behind an authorized approval reaction with nine code-enforced invariants, and answers in-room questions (@dkg ask) with evidence exclusively from the room's designated Context Graph — refusal-first, citations validated in the scoped view before posting.

• Repo: https://github.com/Zigoljube/buzz-dkg-integration (pinned commit aa115bd697a7a1d2a0c690c28b9410b5eef04959)
• Design brief: https://github.com/Zigoljube/buzz-dkg-integration/blob/main/docs/DESIGN.md
• Demo (recorded live loop): https://github.com/Zigoljube/buzz-dkg-integration/blob/main/docs/media/buzz-dkg-live-loop.gif (+ node-UI walkthrough alongside)
• Evidence package: staged gate reports + transcripts under docs/gates/ (source audit with pinned SHAs → isolated spike → daemon with 48 tests and a zero-mock acceptance demo → production dry run → one approved SWM share → one approved, spend-capped VM publication: UAL did:dkg:base:8453/0x633e5a7c5e612d9981538f60d824cc03be97e2ab/2201)

Round-1 scope note: the CI warning about /vm/publish in writeAuthority is expected and justified in security.notes — the daemon's continuous behavior is WM/SWM-only ("chat threads → Shared Memory", a suggested Round-1 build); VM is strictly the promotion path (promotionPath), disabled by default in code and exercised exactly once under operator approval for the evidence package.

Scope & faithfulness

• Uses only supported public interfaces (node HTTP API); no internal DKG package imports; no node patching; no direct SPARQL writes bypassing the assertion lifecycle/Curator
• memoryLayers / v10PrimitivesUsed accurate
• v10 vocabulary used exactly (Context Graph, Assertion, Knowledge Asset, Curator, WM/SWM/VM)

Security declarations (Section 8a)

• networkEgress complete (operator-configured Buzz relay only, besides the local node)
• writeAuthority complete incl. Curator ops (SHARE per capture; PUBLISH mode-gated, see notes)
• credentialsHandled complete (service's own Nostr key; DKG token env-supplied, never logged)
• No install scripts (no npm package at all — install.kind: manual, run from source)
• Pinned SHA is the exact build commit

Contributor attestation

• Own work, Apache-2.0
• No undeclared data exfiltration
• Understand delisting policy for misrepresentation
• Minimum 6-month maintenance window post-acceptance (bounty submission, cfi-dkgv10-r1)

🤖 Generated with Claude Code

https://claude.ai/code/session_0144eZ5xWb9kWFX9Dkzrme9P