Skip to content

A9: v0.5.0 corpus without gradient-papers (deferred to 0.5.1); RELEASE_LINUX mem-mcp @ 0e9d488 - #269

Closed
SaulBuilds wants to merge 2 commits into
release/0.5.0-hermes-upskillfrom
dgx/a9-corpus-no-gradient
Closed

SaulBuilds wants to merge 2 commits into
release/0.5.0-hermes-upskillfrom
dgx/a9-corpus-no-gradient

Conversation

@SaulBuilds

Copy link
Copy Markdown
Contributor

For A9 (#262). Owner decision 2026-10-06: the v0.5.0 knowledge corpus ships without gradient-papers, and it is re-added in 0.5.1.

  • Corpus spec and dirty-check fix: these are in citrate-memories, since that repo builds the corpus. See corpus(v0.5.0): defer gradient-papers to 0.5.1; scope git dirty check to included files citrate-memories#20. gradient-papers is commented out of corpus/hermes-knowledge.toml. mem-corpus now limits its -dirty check to the files a source reads (its include list), so agentile (AGENTILE.md at the metarepo root) records a clean commit even when untracked child checkouts sit next to it.
  • docs/LICENCE_REVIEW.md §4.8: I added an update saying gradient-papers is "deferred to 0.5.1 by owner decision 2026-10-06" and that the agentile dirty flag is fixed. The original review text is unchanged.
  • release/licences.json: corpus:gradient-papers becomes planned:corpus:gradient-papers, so licence-inventory.mjs --corpus accepts a corpus that doesn't include it. scripts/licence-inventory.test.mjs passes (26/26).
  • docs/RELEASE_LINUX.md: mem-mcp now comes from citrate-memories 0e9d488 (main, which has import-corpus), not ff12cab, which predates import-corpus.

The corpus tarball and its sha256 are posted on #262. Pins in src-tauri/runtime-deps.sha256 stay with the Mac lane.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Vv2gVzy5XLFKg48yckN9YQ

@SaulBuilds
SaulBuilds requested a review from a team as a code owner October 6, 2026 16:06
…RELEASE_LINUX names mem-mcp 0e9d488

- docs/LICENCE_REVIEW.md 4.8: gradient-papers "deferred to 0.5.1 by owner
  decision 2026-10-06"; agentile dirty flag fixed in citrate-memories#20 (the
  dirty check is scoped to the files a source reads). Review text kept; the
  update is appended.
- release/licences.json: corpus:gradient-papers -> planned:corpus:gradient-papers
  so the licence inventory accepts a corpus without that source; gap text updated.
- docs/RELEASE_LINUX.md: mem-mcp from citrate-memories main @ 0e9d488 (has
  import-corpus) instead of ff12cab (predates it).

Corpus source change itself lives in citrate-memories (corpus/hermes-knowledge.toml):
CitrateNetwork/citrate-memories#20.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Vv2gVzy5XLFKg48yckN9YQ
@SaulBuilds

Copy link
Copy Markdown
Contributor Author

Owner reversed the gradient-papers deferral (papers are public at CitrateNetwork/gradient-papers and ship in 0.5.0), so the LICENCE_REVIEW §4.8 deferral note and the planned: change shouldn't land. Please close or reduce this to the RELEASE_LINUX.md memories pin. See #266.

…in 0.5.0)

The owner reversed the deferral, so the LICENCE_REVIEW note and the planned:
licence entry are dropped; corpus:gradient-papers stays.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Vv2gVzy5XLFKg48yckN9YQ
@SaulBuilds

Copy link
Copy Markdown
Contributor Author

Closing: the owner reversed the gradient-papers deferral (papers are public at CitrateNetwork/gradient-papers and ship in the v0.5.0 corpus, #272). The RELEASE_LINUX.md memories pin already landed with #272.

@SaulBuilds SaulBuilds closed this Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant