chore(mcp): complete WayforthRank/WRI scrub + bump 0.9.1 (staged republish — review before publish) - #62
Merged
Conversation
The #47 scrub fixed the repo + gateway but never reached the published wayforth-mcp (PyPI 0.9.0, served by Smithery as latest) — so WayforthRank/WRI is still live in the version users install. AND #47 missed the 'WRI' acronym in 5 more files (README, reliability/run/execute/compare) that were leaking in BOTH published and repo HEAD. This completes the scrub so ONE republish fully closes the exposure: WRI prose -> 'reliability score'/'Reliability' across README + 4 tool files. KEPT (output contract / public API, already exposed via the gateway, not a trade-secret-name leak): the wri_score / original_wri / fallback_wri response fields and the wayforth_set_wri_alert tool name. Version 0.8.14 -> 0.9.1 (one above published 0.9.0). After this, HEAD has ZERO uppercase WRI + ZERO WayforthRank anywhere in the package; a republish from HEAD is clean + reproducible. STAGED for review — do NOT publish yet. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
WayforthOfficial
added a commit
that referenced
this pull request
Jun 27, 2026
…63) Repo HEAD version fields had drifted BELOW what's actually published, so the repo disagreed with reality. For these three, the published artifact's CODE matches repo HEAD (verified by diffing the published artifacts) — only the version string was behind. This aligns them; no republish needed (the published versions already exist and match the code). sdk-python (PyPI wayforth-sdk) 0.8.14 -> 0.9.0 (code already == published 0.9.0) sdk-typescript (npm wayforth-sdk) 0.8.0 -> 0.9.0 (src == published 0.9.0; dist built at publish) create-wayforth-agent (npm) 0.9.0 -> 0.9.1 (code already == published 0.9.1) Version-string only; no code/formatting changes. wayforth-langgraph already in sync (0.9.0). The wayforth-mcp desync is a real exposure handled separately in #62 (it needs an actual republish). The TS-SDK 0.10.0 work is preserved on origin branch chore/consolidate-ts-sdk-source for a future cut. Co-authored-by: MytelligentPRV <assulindor@gmail.com> Co-authored-by: Claude Opus 4.8 (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
2 participants
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.
Staged for review — do NOT publish until you've seen this. Closes the live
WayforthRank/WRIexposure in the publishedwayforth-mcp.Why
The #47 scrub fixed the repo + gateway but never reached the published package: PyPI
wayforth-mcp 0.9.0(and Smithery, which serves latest viauvx) still shipsWayforthRank/WRIin tool descriptions. And #47 missed theWRIacronym in 5 more files (README.md,reliability.py,run.py,execute.py,compare.py) — leaking in both published and repo HEAD (my first "repo clean" check only matchedWayforthRank, notWRI— caught by the full grep you asked for).What this does (one publish closes it completely)
WRI→reliability score/Reliabilityacross README + 4 tool files.wri_score/original_wri/fallback_wriresponse fields and thewayforth_set_wri_alerttool name (renaming would break clients).0.8.14 → 0.9.1(one above published0.9.0).Proof
{svc['wri_score']},{failover.get('original_wri')}unchanged, only theWRIlabel →Reliability). All.pyparse.uv build):wayforth_mcp-0.9.1.tar.gz+.whl→ grep of both = 0WRI/WayforthRankhits. The republish is clean and reproducible from HEAD.WRIand zeroWayforthRankanywhere in the package.Judgment calls to confirm
wri_score/wrifield names (already public via the gateway JSON) — vs renaming them (a breaking output-contract change). I kept them.wayforth_set_wri_alerttool name (public API) — scrubbed only its description.Publish plan after you approve: merge →
uv publish0.9.1→ Smithery auto-picks it up (latest, no separate Smithery action).🤖 Generated with Claude Code