Repository navigation
docs: pin tg 0.77.0, max 0.66.0, zoom 0.31.0, memo 0.81.0, drive 0.19.0; retire the max catch-up correction - #331
Merged
Merged
Conversation
….0; retire the max catch-up correction All five releases adopt cli-core 0.370.0, whose scenario check refuses shell characters left unquoted in a step. max 0.66.0 ships its catch-up step quoted (`max review 'date>1d' --unanswered 4h`), so the site's own correction for it is retired and the RU/ES scenario translations carry the quoted step. drive's and memo's guideRefs overrides are retired: their commits are in v0.19.0 and v0.81.0. Translations ported from each tag's docs diff (changelogs; drive commands `--json=id,name`; memo mcp; max/tg release links), fingerprints accepted, roadmap reviews recorded for max, tg, zm. Co-Authored-By: Claude Opus 5.5 (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
1 participant
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.
Task
Move wirecat.dev to the releases that fix the scenario sources the site found in #330, and drop the site's own patch for max's
catch-upstep.Why
max 0.65.0's
scenarios/catch-up.mdhadmax review date>1d --unanswered 4h. A shell reads>as a redirect: it writes a file named1dand drops the filter. The site patched it inscripts/docs-corrections.json. cli-core#1675 (0.370.0) makescheckGuiderefuse unquoted shell characters in any step, and gives memo's cross-tool scenario titles one source (MEMO_SCENARIOS). max 0.66.0 ships the quoted step; memo 0.81.0 capitalisesperson-briefanddecision-trail; drive 0.19.0 listsdecision-trailunder Works with.What
tools.json: max v0.65.0 → v0.66.0, tg v0.76.0 → v0.77.0, zm v0.30.0 → v0.31.0, memo v0.78.0 → v0.81.0, drive v0.18.0 → v0.19.0. drive's and memo'sguideRefsare retired: their commits are in the new tags.scenariosentry fordate>1d. RU/ES max scenario translations carry the quoted step.--json=id,name.docs/release-notes-review.json(roadmaps unchanged). Review record:docs/reviews/2026-10-20-scenario-quoting-pins.md.Remaining source discrepancies: none found.
Testing
Run locally, all pass:
pnpm lint,search:check,sync,docs:release-notes,test(325),docs:contracts(all five npm releases captured),docs:check(strict: 0 reference gaps, 0 invalid examples),typecheck,build,check:links. The builtout/en/docs/max/scenarios.htmlshowsmax review 'date>1d' --unanswered 4h.🤖 Generated with Claude Code