Add DKG Notebook Memory

[Codesensitive]

What this PR does

Adds DKG Notebook Memory for Round 1 (cfi-dkgv10-r1): selected Jupyter cells become private, content-addressed WM findings with stable source provenance, research-status labels and verified readback. Unmarked cells, outputs and attachments are excluded; notebook code is never executed.

Integration links

• Repo: https://github.com/Codesensitive/dkg-notebook-memory
• Commit pinned: 26675fdc6537efea1c70f18891260b98c651f8e2
• Published package: https://www.npmjs.com/package/dkg-notebook-memory/v/0.1.2
• Design brief (bounty submissions): https://github.com/Codesensitive/dkg-notebook-memory/blob/26675fdc6537efea1c70f18891260b98c651f8e2/docs/DESIGN.md
• Demo (bounty submissions): https://codesensitive.github.io/dkg-notebook-memory/

Scope & faithfulness

• Integration uses only the supported public interfaces (HTTP API, dkg CLI, MCP). It does not import internal DKG packages, patch node source, or write to SPARQL directly (bypassing the assertion lifecycle / Curator).
• memoryLayers correctly reflects which layer(s) the integration touches.
• v10PrimitivesUsed correctly reflects which primitives are exercised.
• Terminology matches the v10 vocabulary (Context Graph, Sub-graph, Assertion, Knowledge Asset, Knowledge Collection, Curator, Entity, WM/SWM/VM).

Security declarations (Section 8a)

• security.networkEgress lists every external host the integration contacts beyond the local DKG node.
• security.writeAuthority lists every DKG write operation the integration performs. Curator-authority ops (PUBLISH, SHARE, endorse, verify) are called out explicitly if used.
• security.credentialsHandled lists every third-party credential the installer will prompt for.
• The published package has no preinstall / install / postinstall scripts, or the exceptions are explained in security.notes.
• The package is published with build provenance (npm publish --provenance) when applicable.
• The pinned git SHA is the exact commit the published package was built from.

Contributor attestation

• This integration is my own work or properly licensed.
• It contains no intentional backdoors, malicious logic, or data-exfiltration paths beyond what is declared in security.networkEgress.
• I understand that the integration may be delisted for any material misrepresentation in the registry entry.
• I commit to a minimum 6-month maintenance window post-acceptance (bounty submissions).

Notes for the committee

AI-assisted implementation and submission, maintained by @Codesensitive, who has accepted the six-month support commitment. Submitted as community tier.

Validation: eight unit/transport tests pass locally and in the release workflow. A separate real DKG 10.0.18 daemon run passed all nine tests using actual HTTP and Oxigraph storage with a mock blockchain; no peer-network, chain, promotion or external-adoption claims. The recording demonstrates selected-cell export, verified writes, recall and repeat-safe behavior. The final CLI also supports the registry installer environment variables.

No runtime dependencies, install scripts or external network egress. An existing Context Graph is required. Selected source text still needs operator review for secrets; concurrent same-asset writes must be serialized.

Release workflow and provenance: https://github.com/Codesensitive/dkg-notebook-memory/actions/runs/35968690815