docs: catch up README/CLAUDE/changelog/opencode after today's merges - #112
Conversation
…merges Five PRs landed today that didn't have YAML entries yet; CLAUDE.md + README still referenced the pre-transfer jphein/mempalace ownership; the opencode integration recipe didn't cover the two gotchas that bit us tonight (npm-vs-opencode-cache patch target; the "looks like an error" stderr lines from local-palace spawns). YAML additions (newest first): - local-palace-retired-marker (#111 — 798cf14) - opencode-repo-config-empty-mcp (#110 — 7133eee) - opencode-repo-mcp-drop-comment-key (#109 — 637bb01) - opencode-repo-mcp-disable-flag (#108 — 47018e5; superseded by #110) - mcp-stub-resources-prompts-list (#107 — 6ca0670) CLAUDE.md changes: - Fork URL: `jphein/mempalace` → `techempower-org/mempalace` - Origin/upstream line reflects the May 2026 transfer - Palace data section: local palace is retired; production lives in postgres on disks.jphe.in - Python venv: `./venv/` → `./.venv/` (uv convention) - Issue tracker links updated to techempower-org README.md changes: - Quickstart and `Open upstream PRs` table use techempower-org URLs docs/integrations/opencode.md changes: - New "Patch target gotcha" subsection: opencode caches plugins under ~/.cache/opencode/packages/ independently of the global npm install; patches must apply there. - New "What 'looks like an error' but isn't" verification subsection listing the three stderr lines that surfaced today during debug. - New "If you see a different palace count" troubleshooting block: palace-count divergence between MCP and CLI usually means an old shell without PALACE_DAEMON_URL; on this fork the local palace is retired so the CLI now refuses with the marker text. FORK_CHANGELOG.md regenerated via scripts/render-docs.py. check-docs.sh clean (29 fork hash refs resolve; only existing MemPalace#1024 pr_state warning, unchanged). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request performs a comprehensive documentation and configuration sweep following recent infrastructure merges. It standardizes the project's fork identity, formalizes the retirement of legacy local storage, and resolves several integration gotchas encountered when using OpenCode with the new daemon-routed architecture. Highlights
Ignored Files
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the project documentation and changelog to reflect the transfer to the TechEmpower organization and the migration from a local ChromaDB store to a daemon-routed pgvector setup. Key changes include the implementation of a retired palace marker to prevent stale data access, the removal of conflicting OpenCode configurations, and the addition of stub MCP methods to reduce log noise. Review feedback correctly identified unnecessary backslash escapes in the YAML changelog that would cause rendering issues for the "$comment" field.
| bucket: Fixed | ||
| commit: 637bb01 | ||
| area: CLI | ||
| summary: "Drop \\$comment from .opencode/opencode.json — schema rejects unknown root keys" |
There was a problem hiding this comment.
The backslash in \$comment appears to be an unnecessary escape for a YAML double-quoted string. Since $comment is a literal field name in the OpenCode schema, it should be documented without the backslash to ensure it renders correctly in the generated changelog.
summary: "Drop $comment from .opencode/opencode.json — schema rejects unknown root keys"| area: CLI | ||
| summary: "Drop \\$comment from .opencode/opencode.json — schema rejects unknown root keys" | ||
| body: | | ||
| Commit ``47018e5`` (PR #108) added a ``\$comment`` field to |
There was a problem hiding this comment.
In a YAML block scalar (|), backslashes are interpreted literally. Additionally, inside Markdown code spans (backticks), the dollar sign does not require escaping. Documenting it as \$comment will cause the documentation to display a literal backslash in the final output.
Commit ``47018e5`` (PR #108) added a ``$comment`` field to
Summary
Documentation sweep after today's 10 fork-side + 2 palace-daemon merges. Brings the YAML/changelog up to date, removes the pre-transfer `jphein/mempalace` references, and captures the two gotchas we hit while debugging opencode tonight.
What's in this PR
`docs/fork-changes.yaml` + regenerated `FORK_CHANGELOG.md` — 5 new entries (newest first):
`CLAUDE.md`:
`README.md`:
`docs/integrations/opencode.md` — two new subsections capturing tonight's debug:
/.cache/opencode/packages/` independently of the global npm install; the JP-PATCH must apply there, not to `/.npm-global/lib/...`. The previous patches looked applied but had no effect on what opencode actually ran.Test plan
🤖 Generated with Claude Code