docs: clarify install-from-source version stamp and Claude Code schema fallback#410
Merged
Alan-TheGentleman merged 1 commit intoMay 27, 2026
Conversation
Two install-time confusions that Gentleman-Programming#67 surfaced: 1. The previous version-stamp tip suggested running both 'go install' AND 'go build -o engram[.exe]' back-to-back. The build output goes to the current directory, not PATH, so 'engram version' keeps reporting 'dev' from the earlier 'go install'. Rewrites the tip as two explicit alternatives (-ldflags on go install, or build + move onto PATH), with a warning that they are mutually exclusive. 2. Older Claude Code CLI versions reject 'claude plugin marketplace add' with schema errors on some manifest fields ('Invalid schema: plugins.0.source: Invalid input'). Adds a focused troubleshooting callout right under the marketplace command pointing at 'claude update' and Option C (Bare MCP) as the fallback for users who cannot upgrade. Verified locally that 'go install -ldflags=...' actually stamps the version (engram version prints local-<describe>) so the new instructions work as written. Closes Gentleman-Programming#67
Contributor
Author
|
Heads up: I do not have permission to add labels on this repo, so |
Alan-TheGentleman
approved these changes
May 27, 2026
Collaborator
Alan-TheGentleman
left a comment
There was a problem hiding this comment.
Reviewed the docs diff. The schema-error troubleshooting and the version-stamp clarification (B1 vs B2, avoiding the double binary on PATH) are accurate and match the actual go install behavior. Approving.
98f4e1d
into
Gentleman-Programming:main
8 checks passed
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
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.
🔗 Linked Issue
Closes #67
🏷️ PR Type
type:docs— Documentation only📝 Summary
docs/INSTALLATION.md(Windows and macOS/Linux) so it is no longer two consecutive commands that leave the user with two binaries andengram versionstill printingdev. The new tip presents two explicit, mutually exclusive options.docs/AGENT-SETUP.mdfor the Claude Code marketplace schema error, pointing atclaude updateand naming Bare MCP as the fallback.📂 Changes
docs/INSTALLATION.mdgo install -ldflags) and Option 2 (go build+ move) as separate alternatives. Warns the reader not to run both.docs/AGENT-SETUP.md🧪 Test Plan
go test ./...(no code changes; ran as a sanity check)go test -tags e2e ./internal/server/...(no code changes; ran as a sanity check)go install -ldflags="-X main.version=local-$(git describe --tags --always)" ./cmd/engramproduces a binary whoseengram versionreports the stamped value instead ofdev. The new instructions match observed behavior.✅ Contributor Checklist
Closes #67)type:*label (type:docs)Co-Authored-Bytrailers💬 Notes for Reviewers
.claude-plugin/marketplace.jsonuses"source": "./plugin/claude-code", not"source": "git-subdir", so the exact failure mode the issue cites is not reproducible againstmaintoday. I kept the troubleshooting callout intentionally generic ("schema errors on some manifest fields") and named theInvalid schema: plugins.0.source: Invalid inputtext only as one example, so the guidance still helps users on older CLIs who hit any related schema issue (including any future change to the manifest).claude update(which always upgrades to the latest) instead of a specific version that might be wrong.INSTALLATION.mdblocks already had a one-line version-stamp tip. The rewrite preserves the same intent but resolves the PATH gotcha the issue described.