[cfi-dkgv10-r1] Add github-dkg: GitHub knowledge → DKG v10 Working Memory

[haroldboom]

What this PR does

Adds github-dkg as a community integration. Ingests GitHub issues, pull requests, and review comments into DKG v10 Working Memory as Knowledge Assets, with full provenance and selectable promotion to Shared Working Memory.

Integration links

• Repo: https://github.com/haroldboom/github-dkg
• Commit pinned: f2b9f67c9518137e5fc197507205520f3e402c71
• Published package: github-dkg@0.1.0
• Design brief: https://github.com/haroldboom/github-dkg/blob/master/DESIGN_BRIEF.md
• Demo (3-min walkthrough): https://youtu.be/9Tgb4-OXGuk
• Colab notebook (offline mocks): https://colab.research.google.com/github/haroldboom/github-dkg/blob/master/demo.ipynb

What it does

• CLI (github-dkg ingest|ingest-one|search|promote) for one-shot or bulk ingestion of any repo's issues / PRs / reviews. --since supported on both endpoints (server-side for issues; sort=updated&direction=desc + early-stop for PRs since /pulls has no native since).
• GitHub Action (Docker, fires on issues / pull_request / pull_request_review) for automatic per-event ingestion. The bundled examples/workflow.yml shows the canonical SWM-promotion gate: only PRs labelled architecture-decision and merged to main.
• Each item becomes one tri-modal Knowledge Asset (markdown → structural triples + semantic embedding) via POST /api/memory/turn.
• Promotion to SWM via POST /api/assertion/{name}/promote is always explicit, never automatic.

Security highlights

• Network egress: only api.github.com and the local DKG node.
• No PUBLISH (Verified Memory) calls.
• GitHub rate-limit responses (403/429) surface as a typed GitHubRateLimitError rather than crash mid-traversal.
• No postinstall/preinstall scripts; hatchling-built wheel uploaded to PyPI via twine.
• 23/23 unit tests pass against the published wheel (verified in a fresh venv outside the source tree).

Sister submission

langchain-dkg — PR #4 is the same author's other Round 1 entry — a LangChain memory adapter backed by DKG v10. Together they form a write-side / read-side pair: github-dkg writes engineering tacit knowledge into the substrate, langchain-dkg gives any LangChain agent persistent memory backed by it.

Submission tag: cfi-dkgv10-r1

[haroldboom]

rc.8 compatibility check + CI

Verified github-dkg 0.1.0 against DKG v10-rc.8 (released 2026-05-15) — no client changes needed. The rc.4 → rc.8 release notes touch libp2p relay hardening, MCP agent-chat tools, and Base Sepolia contract redeploys, but leave /api/memory/turn, /api/memory/search, and /api/query (the entire surface this ingestor calls) unchanged.

Also added a GitHub Actions workflow that runs the 23 unit tests on Python 3.10 / 3.11 / 3.12 on every push and PR — green: https://github.com/haroldboom/github-dkg/actions

Happy to address any reviewer feedback when you get to this one.

[haroldboom]

Contributor Attestation

Restating the registry submission attestations against the pinned commit (5cda3aac) for reviewer convenience:

• Authorship & license. Sole author. MIT-licensed; LICENSE at the pinned commit matches the declared license.
• No backdoors / no exfil. security.networkEgress: ["api.github.com"]. Verified by inspection of src/github_dkg/: GitHubClient only talks to https://api.github.com (hardcoded _BASE at github_client.py:10); DKGClient only talks to DKG_BASE_URL (default http://localhost:9200). No other hosts.
• No install hooks. Plain hatchling wheel; pip install github-dkg==0.1.0 is a read-only filesystem operation. The bundled GitHub Action ships as a python:3.12-slim Dockerfile — image build is reproducible from the pinned commit.
• Tests verified against the published wheel. pip install github-dkg==0.1.0 into a fresh venv outside the source tree; 23/23 unit tests pass. GitHub Actions CI runs the suite on Python 3.10/3.11/3.12 for every push.
• Runtime dependency audit clean. pip-audit against the declared requires of github-dkg==0.1.0 (click, httpx): no known vulnerabilities.
• Curator-authority discipline. Only POST /api/assertion/{name}/promote (WM→SWM SHARE) is callable; bundled examples/workflow.yml gates promotion on a PR label (architecture-decision) so the choice is the team's, not the integration's. No PUBLISH (Verified Memory) calls anywhere in the codebase.
• Maintenance commitment. Minimum 6-month support window post-acceptance.

Two follow-ups planned before the next patch release:

1. PyPI Trusted Publishing via pypa/gh-action-pypi-publish@release/v1 with attestations: true for SLSA build provenance.
2. A "Positioning vs other Round 1 submissions" section in DESIGN_BRIEF.md framing this entry as complementary to the OpenClaw/Hermes-cluster integrations rather than competing.

[haroldboom]

Update — attested release shipped.

github-dkg@0.1.1 was published a few minutes ago via PyPI Trusted Publishing (workflow publish.yml) — this checks the build-provenance box that was open at the time of the original PR description.

Per-distribution attestations are fetchable from PyPI's integrity endpoint:

• https://pypi.org/integrity/github-dkg/0.1.1/github_dkg-0.1.1-py3-none-any.whl/provenance
• https://pypi.org/integrity/github-dkg/0.1.1/github_dkg-0.1.1.tar.gz/provenance

Both decode to a PEP-740 in-toto Statement v1 signed by the GitHub Actions runner. Signer identity in the bundle:

{"kind": "GitHub", "repository": "haroldboom/github-dkg", "workflow": "publish.yml", "environment": "pypi"}

Registry entry bumped: pin → b9c1ede, install.version → 0.1.1, security.notes now declares the attestation path.

Wheel content is byte-for-byte equivalent to 0.1.0 (the diff is the publish workflow + DESIGN_BRIEF section 10 added in cc66bad; neither ships in the wheel). All 23/23 unit tests still pass against the new wheel in a fresh venv. Existing 0.1.0 users can ignore this release; the value is the signed, attested distribution path for any future fix release.

[haroldboom]

🔐 Dependency-security audit — no action needed

As part of a supply-chain pass across both submissions, github-dkg's dependencies were audited against the OSV / OpenSSF malicious-packages and CVE datasets.

• Direct runtime deps are httpx and click only — neither is affected by any current advisory, and no malicious/compromised package is present.
• No release required for github-dkg; it stays pinned at v0.1.2 (Trusted-Publishing, PEP-740 attested).

(The sister submission langchain-dkg #4 did get a security-hardening release — langchain-core>=1.3.3 for CVE-2026-44843.)

[haroldboom]

Compatibility release — verified against DKG v10 node 10.0.0-rc.17.

Bumped github-dkg to v0.1.3 (attested via PyPI Trusted Publishing). The registry pin on add/github-dkg now points to commit 59e5fa9 and install.version → 0.1.3.

No source or API changes — this is a verification release. I reviewed the rc.2→rc.17 node changelog for every HTTP endpoint the ingester calls (POST /api/context-graph/create, /api/memory/turn, /api/memory/search, /api/assertion/{name}/promote, /api/query); the only request-shape change in that window — rc.12 dropping the deprecated participantIdentityIds/requiredSignatures from context-graph/create — is already non-breaking here. 23/23 unit tests green. PEP-740 attestation: https://pypi.org/integrity/github-dkg/0.1.3/

[haroldboom]

v0.1.4 — verified compatible with DKG v10 node 10.0.0-rc.19

Following the rc.19 testnet release, I re-audited the ingester against the node's daemon HTTP API. No source change required — this is a verification-only compatibility release.

I diffed every daemon route this ingester calls across both hops (rc.17 → rc.18 → rc.19):

Endpoint	rc.17 → rc.19
POST /api/memory/turn	byte-identical
POST /api/memory/search	byte-identical
POST /api/query	byte-identical
GET /api/agents (ping)	byte-identical
POST /api/context-graph/create	additive — now also accepts contextGraphId as an alias for id (#1102), backward-compatible
POST /api/assertion/{name}/promote (opt-in SHARE)	additive — new 503 CURATOR_UNCONFIRMED / 409 CURATOR_REJECTED codes (OT-RFC-49); request contract unchanged

• PyPI: github-dkg 0.1.4, published via Trusted Publishing with a PEP-740 attestation.
• Registry pin updated to commit a30f1d4; install.version → 0.1.4.
• 23/23 unit tests green; CI green on Python 3.10/3.11/3.12.