Repository navigation
docs(capabilities): drop the version stamp, name each table once - #4033
Conversation
The capabilities page said it covered the unreleased in-tree version (0.21.34-dev) and the day it was generated, so the published page named a version users cannot install and changed on every release. It now carries neither and changes only when the facts or annotations do; the drift guard compares it whole. Each table heading names its section and target group, so search lists five distinct entries instead of five "Hosted provider sessions". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Size Report
Startup median (7 runs, lower is better):
|
|
The code looks good at 9b2644f. Not blocking, and you can take or leave it: in generate.ts the I did not run the generator, the capabilities-matrix gate or a site build, so byte-consistency of the page with generator output rests on your reported gate pass and on the diff showing only heading and stamp changes. I also did not observe how the new headings appear in search results. Smoke Tests is still in progress. The diff touches only the generator, its repo guard and a docs page, so it does not overlap the device smoke route. Please let Smoke Tests finish before merging. |
The page no longer carries a version, so the mark-released job's generate:capabilities run would only re-collect unchanged facts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The change at a50785d looks good. Since 9b2644f it also drops the release step that regenerated the page, which the stamp no longer needs. All 30 checks pass, and there are no review threads. The only change since the earlier review is in release.yml, which no PR check runs, so I read that step from the YAML only. I did not run the release workflow, the generator or the capabilities-matrix gate. Nothing else needs to change before merge. |
The headings lowercased each caption's first letter with a regex; the captions are now written as they appear, so the regex goes. The page is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Reviewed bce95a9: the code looks good, and there is nothing left for me to ask for. All 30 checks pass. I did not run the generator or the capabilities-matrix gate. I checked byte-identity by reading the old regex against the four captions and the committed page headings. |
Summary
The capabilities page said "It covers agent-device 0.21.34-dev, generated 2026-10-27": a version nobody can install (npm
latestis 0.21.33), and a line that changed the page on every release. The page now carries no version or date, so it changes only when the capability facts or their annotations change, and the drift guard compares it whole.Each table heading also names its section and target group ("Evidence and diagnostics: hosted provider sessions"), so docs search lists distinct entries instead of five identical "Hosted provider sessions".
4 files: the generator, its repo guard, the regenerated page, and release.yml, whose mark-released job no longer regenerates the page to restamp it. The guard drops the date-mask and version cases and now asserts that no stamp is present and that every heading is unique.
Validation
At bce95a9 (captions stored as they render, no regex; the page is byte-identical),
pnpm check:affected --run --head HEADpassed every runnable check. Earlier, at 9b2644f,pnpm check:affected --run --head HEADpassed every runnable check (fail-open full set: format, lint, typecheck, fallow, build, package, integration-node, vitest-related and the rest). Alsopnpm gate capabilities-matrix(12/12),pnpm gate docs-prose, andcheck-doc-linksagainst a fresh site build. After the release.yml change: the workflow tests (15/15), the release-plan and release-version tests (16/16) and the gate manifest pass. Docs, generator and release workflow only; no runtime code changes.🤖 Generated with Claude Code