Skip to content

Hotfix: unbreak release workflow + tighten README + restore Ralph vs Clone#3

Merged
Turtle-Hwan merged 3 commits into
mainfrom
fix/release-readme-pins
May 12, 2026
Merged

Hotfix: unbreak release workflow + tighten README + restore Ralph vs Clone#3
Turtle-Hwan merged 3 commits into
mainfrom
fix/release-readme-pins

Conversation

@Turtle-Hwan
Copy link
Copy Markdown
Contributor

@Turtle-Hwan Turtle-Hwan commented May 12, 2026

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

  1. fix: drop README version pins — `updateReadmePins` and its README
    coupling are removed entirely. The Releases page is now the single
    source of truth for version pins.
  2. docs: tighten README — 199 → ~140 lines. Dropped the Plugin
    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.
  3. docs: restore Ralph vs Clone comparison — that section was dropped
    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

  • `pnpm test` -> 23/23 passing.
  • Reviewer: confirm next merge to main produces clone-plugin-v0.4.0.

🤖 Generated with Claude Code

Turtle-Hwan and others added 3 commits May 12, 2026 16:50
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>
@Turtle-Hwan Turtle-Hwan changed the title Drop README version pins (release workflow hotfix) Hotfix: unbreak release workflow + tighten README + restore Ralph vs Clone May 12, 2026
@Turtle-Hwan Turtle-Hwan merged commit 8a14745 into main May 12, 2026
@Turtle-Hwan Turtle-Hwan deleted the fix/release-readme-pins branch May 12, 2026 16:45
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