Skip to content

docs: fix V25 rationale and caps range after the PR #120 review - #125

Merged
dapiced merged 1 commit into
mainfrom
dom/vigilant-curie-tp71vy
Oct 18, 2026
Merged

dapiced merged 1 commit into
mainfrom
dom/vigilant-curie-tp71vy

Conversation

@dapiced

@dapiced dapiced commented Oct 18, 2026

Copy link
Copy Markdown
Owner

Summary

Two fixes from the review of the docs merge (#120):

  • PLAN.md: the Future directions item "Widen the text vocabulary" said the memory guard made the typed-array rewrite unnecessary. That isn't what happened in V25: the rewrite was dropped because measurement showed the pipeline was never the bottleneck, and the named memory guard was added as a separate fix. The item now agrees with the V25 row and the limits page.
  • README.md: "seven caps" sat next to a range that stopped at Cap 6. The sentence now says the first six took the lab from the MVP to the real world, then covers Cap 7 on its own.

Left as they were, to be decided editorially:

  • Where V12 sits on the limits page ("Set aside by choice" versus postponed).
  • The day/month date format on the English page, which follows the convention PLAN.md already uses.

Checks

Prettier was re-run. The changelog and docs page tests pass (88 tests).


Generated by Claude Code

The Future directions entry now gives the real reason V25 dropped the
typed-array rewrite (the pipeline was never the bottleneck), and the
README caps sentence no longer pairs 'seven' with a range ending at Cap 6.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qh8Z4qa9JFUH2Enuu4rvgy
@dapiced
dapiced marked this pull request as ready for review October 18, 2026 14:10
@dapiced
dapiced merged commit 4fc31f7 into main Oct 18, 2026
7 checks passed
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.

2 participants