Hotfix: unbreak release workflow + tighten README + restore Ralph vs Clone#3
Merged
Conversation
The version-pin sentence in README was a fragile coupling: every README copy edit could break the release workflow because bump-plugin-version.mjs scanned for an exact phrase, and a short rewrite during PR #2 caused the post-merge release run to fail before it could tag clone-plugin-v0.4.0. Replace the pinned line with a pointer to the Releases page (which is the authoritative source anyway), and remove updateReadmePins + its test fixture. Release workflow now only touches plugin.json and the two hook CLIENT_VERSION constants. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
… Installing section 199 -> ~140 lines. Removed sections that mostly served curious developers rather than people deciding whether to install: the Plugin structure file tree (the repo itself is the source of truth) and the .mcp.json snippet (users don't edit it). Folded "Installing & updating" into Quick start with a one-liner update command. Collapsed Requirements into a single sentence. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Bring back the comparison section that was dropped in 1ed2a0a, but reframed around the problem we built Clone Loop to solve: "Ralph replays — Clone predicts." Single mermaid diagram contrasts the two paths in one shot, followed by a 5-row decision table that makes the next-prompt source, context payload, and safety gate differences explicit. Adds ~50 lines to README; the value-prop framing makes the length earn its keep. 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
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.
Summary
PR #2 broke the post-merge release workflow because `bump-plugin-version.mjs`
relied on a phrase in README that the rewrite shortened. v0.4.0 was never
tagged. This PR fixes the regression and uses the same touch to tighten
the README further.
Commits
coupling are removed entirely. The Releases page is now the single
source of truth for version pins.
structure file tree (the repo is the source of truth) and the
`.mcp.json` snippet (users don't edit it). Folded Installing &
updating into Quick start.
in 1ed2a0a (pre-PR-Multi-turn + rich-iteration agent_input for Clone MCP #2). Restored with one mermaid diagram + a 5-row
decision table framed around the problem we built Clone Loop to solve.
Test plan
🤖 Generated with Claude Code