Skip to content

docs(capabilities): drop the version stamp, name each table once - #4033

Merged
thymikee merged 3 commits into
mainfrom
capabilities/drop-version-stamp
Oct 29, 2026
Merged

thymikee merged 3 commits into
mainfrom
capabilities/drop-version-stamp

Conversation

@thymikee

@thymikee thymikee commented Oct 28, 2026 •

Copy link
Copy Markdown
Member

Summary

The capabilities page said "It covers agent-device 0.21.34-dev, generated 2026-10-27": a version nobody can install (npm latest is 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 HEAD passed every runnable check. Earlier, at 9b2644f, pnpm check:affected --run --head HEAD passed every runnable check (fail-open full set: format, lint, typecheck, fallow, build, package, integration-node, vitest-related and the rest). Also pnpm gate capabilities-matrix (12/12), pnpm gate docs-prose, and check-doc-links against 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

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>
@vercel

vercel Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
agent-device-website Ready Ready Preview Oct 29, 2026 6:53am UTC

Request Review

@github-actions

github-actions Bot commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Size Report

Metric Base Current Diff
Installed (including dependencies) 5.56 MB 5.56 MB 0 B
Package (unpacked) 5.56 MB 5.56 MB 0 B
Package (download) 1.69 MB 1.69 MB -5 B

Startup median (7 runs, lower is better):

Scenario Base Current Diff
CLI --version 30.1 ms 30.1 ms -0.0 ms
CLI --help 57.1 ms 58.2 ms +1.0 ms

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 3 files

View guided diff | Turn on auto-fix | Re-trigger cubic

@thymikee

Copy link
Copy Markdown
Member Author

The code looks good at 9b2644f. Not blocking, and you can take or leave it: in generate.ts the GROUPS.caption values are stored capitalized, and the only consumer lowercases the first letter with a regex. Would it be simpler to write the captions as they render ('mobile targets', 'TV targets', 'desktop and web targets', 'hosted provider sessions'), use ### ${section.title}: ${caption}, and delete the regex and its comment?

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.

@thymikee thymikee added the ready-for-human Valid work that needs human implementation, judgment, or maintainer merge label Oct 28, 2026
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>
@thymikee

Copy link
Copy Markdown
Member Author

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>
@thymikee

Copy link
Copy Markdown
Member Author

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.

@thymikee
thymikee merged commit e6627ee into main Oct 29, 2026
30 checks passed
@thymikee
thymikee deleted the capabilities/drop-version-stamp branch October 29, 2026 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-human Valid work that needs human implementation, judgment, or maintainer merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant