CI verification: validate claude-code-memory entry - #1
Merged
Conversation
MCP server giving Claude Code agents persistent, verifiable Working Memory on DKG v10: trust-gradient status, PROV-O provenance chains, sub-agent attribution, Curator-gated SHARE, and ClaimReview output for oracle-readiness. Pinned to v1.0.2 (commit 22b5c6a), published to npm with build provenance. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Self-hosted CI run to demonstrate the registry
validate.yml(schema + security checks) passes on theclaude-code-memoryentry submitted upstream as OriginTrail#16. The upstream PR's workflow is gated behind first-time-contributor maintainer approval; this fork-internal run produces the same checks without that gate.