chore: rename Dark Matter references to MDK#170
Conversation
The upstream library moved from marmot-protocol/darkmatter to marmot-protocol/mdk. Update the cosmetic references in goggles to match: - Docs prose (README, api-v1, PRD) now says MDK instead of Dark Matter. - Sample fixtures, seed data, and tests emit "recorder": "mdk" in recorder_started events, and the example upload user agent is now MDK/1.2.3. No behavior change: ingestion treats the recorder value as a free-form string and never matched on the old name. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
WalkthroughRenames "Dark Matter"/"darkmatter" references to "MDK"/"mdk" throughout README, API and PRD documentation, JSONL audit-log fixtures, seed data scripts, and test files, including the ChangesDark Matter to MDK Rename
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
Ready to review this PR? Stage has broken it down into 3 individual chapters for you:
Chapters generated by Stage for commit 85959fa on Jul 4, 2026 12:53pm UTC. |
What changed
The upstream library moved from
marmot-protocol/darkmattertomarmot-protocol/mdk. This is the cosmetic rename pass in goggles to match:README.md,docs/api-v1.md, and all mentions indocs/audit-debugging-platform-prd.md(including the "MDK Audit Data Gaps" heading, and one grammar fix: "a Dark Matter emitted" → "an MDK-emitted").recorder_startedevent in all threefixtures/sample-audit-log-*.jsonlfiles now says"recorder":"mdk"."recorder": "darkmatter"→"mdk"inforensics/seed_data.pyandforensics/tests.py, and the example upload user agentDarkMatter/1.2.3→MDK/1.2.3.Why
Keeps sample data, seeded dev environments, and docs consistent with the renamed library so new contributors don't chase a name that no longer exists.
Notes for reviewers
recordervalue as a free-form string and nothing filters or asserts on it; the JSON schema types it as a plain string. Old uploads with"recorder": "darkmatter"remain valid and display as-is."recorder": "mdk"is the assumed new emitter string — if the mdk library actually stamps something else, updating fixtures is a one-line follow-up.schema_versionstring away frommarmot-forensics-audit/v2. If it did,SUPPORTED_AUDIT_SCHEMA_VERSIONSinforensics/ingest.pyneeds the new value or uploads will be quarantined.just check: 199 tests pass, ruff lint/format clean, no migration drift.🤖 Generated with Claude Code
Summary by CodeRabbit
Documentation
Bug Fixes