Add DKG Contestation Protocol

[iteotwawki]

Framework-agnostic contestation protocol for DKG Shared Memory: agents challenge and corroborate each other's knowledge claims with evidence, and a confidence model matures each claim along the trust gradient (self-attested -> endorsed -> consensus-verified) based on multi-agent scrutiny.

• Package: @iteotwawki/dkg-contestation@0.1.0 (provenance attestation present)
• Pinned commit: 6c4b3ddc99374938187ae60a3b9fe20fdf4e7dda
• WM/SWM only; no Verifiable Memory / on-chain writes (Round-1 scope)
• npm run validate: 0 errors; security-checks: 0 errors, no install scripts

What this PR does

Integration links

• Repo:
• Commit pinned:
• Published package:
• Design brief (bounty submissions):
• Demo (bounty submissions):

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