[bpamiri]

Summary

Fixes stale claims and commands on the wheels.dev home page (web/sites/landing/src/pages/index.astro). Each item was checked against develop.

where	was	now	source
"Get started" button, Guides card	guides.wheels.dev/v3-0-0/	guides.wheels.dev/v4-1-0/	4.1 is the current release (versions.ts). The guides and API sites have no version-less "latest" URL: /latest/ returns 404 on both.
API card	api.wheels.dev/v3-0-0/	api.wheels.dev/v4-1-0/	newest API_VERSIONS entry
Migrations feature	wheels dbmigrate latest / down, "always reversible"	wheels migrate latest / wheels migrate down "steps back one migration"	migrate is the 4.x command, and dbmigrate is kept only as a historical alias (Module.cfc). A migration is only reversible if its down() is written, so "always" overclaimed.
CLI feature	wheels server	wheels start	the documented dev-server command
Hero engine line	Lucee 7, Adobe CF 2023/2025, BoxLang	Lucee 6/7, Adobe ColdFusion 2023/2025, BoxLang, and RustCFML	start-here/cfml-engines.mdx (4.1 and 4.2 identical): the engines table and the CI matrix
Multi-engine feature	Lucee 5/6/7 …; "primary development target is Lucee 7"	the same four engines, "each tested in CI"; "the wheels CLI's built-in dev server runs Lucee"	same page: Lucee 5 isn't in 4.x's support table, and the CLI bundles Lucee
Guides card text	"v4.0-SNAPSHOT, v3.0, and v2.5 all available"	"for the current release, earlier release lines, and the version in development"	version-free, so it won't go stale at a cut
API card text	"Searchable across 8 framework versions"	"for the current release and earlier ones back to 1.4.5"	API_VERSIONS lists 10 versions, not 8; the new wording doesn't need recounting

Checked and left as they are:

• the brew tap wheels-dev/wheels / brew install wheels / wheels new install block (start-here/installing.mdx);
• "Started in 2006. Production-ready since 1.0 in 2009": first commit 2006-07-27, CHANGELOG.md [1.0] => 2009.11.24;
• "Apache 2.0 licensed" (LICENSE);
• GitHub "discussions": enabled on the repository;
• the shared header and footer links, which are all version-less.

At the 4.2.0 cut, the two v4-1-0 links should move to v4-2-0, alongside the versions.ts flip.

Build

• pnpm install --frozen-lockfile, then pnpm --filter @wheels-dev/site-landing build: 1 page built.
• The built dist/index.html has the new links, commands and engine lines.
• prettier --check is clean.
• The landing.png visual baseline will probably need refreshing for the text changes. I'll check the diff artifact first.

🤖 Generated with Claude Code

[bpamiri]

Review @ e16c3c3: APPROVE on content (web/landing). Merge gated on PR CI, Visual regression included

I checked each claim against the sources:

• The links resolve. https://guides.wheels.dev/v4-1-0/ and https://api.wheels.dev/v4-1-0/ both return 200, and /latest/ returns 404 on both sites, so pinning the current release line is the right call.
• The engine list matches the guides. The v4-1-0 start-here/cfml-engines.mdx lists the framework on Lucee 6/7, Adobe ColdFusion 2023/2025, BoxLang and RustCFML.
  • Its compatibility-matrix paragraph supports "each tested in CI": compat-matrix.yml covers Lucee 6, Lucee 7, Adobe 2023 and 2025, and BoxLang, and RustCFML has its own required lane.
  • "The wheels CLI's built-in dev server runs Lucee" matches its "Why the wheels CLI is Lucee-only" section.
  • Dropping Lucee 5 is right: it isn't in that table or the matrix.
• The commands are the 4.x ones. wheels migrate latest / wheels migrate down (down steps back one migration) and wheels start replace the 3.x dbmigrate / server names. Removing "always reversible" is right too, since a migration with an irreversible down() can't be reversed.
• API history. "back to 1.4.5" matches the API site's oldest docs tree (web/sites/api/src/content/docs/v1-4-5/).
• The card texts no longer name versions, so they won't go stale at the next release.

INFO (for the 4.2.0 cut): the four links are now pinned to v4-1-0. When 4.2.0 ships, they'll need to move to v4-2-0, alongside the versions.ts flip in draft #4322, unless a stable "latest" alias is added. Worth a line on the cut checklist.

PR CI at the time of review: 11 pass, 8 pending (including Visual regression, Lucee 7 + SQLite, RustCFML, Tutorial E2E and the deploy previews), 3 skipping. You expect the landing visual baseline to need a refresh. If Visual regression fails on the hero / cards diff, that's expected, but the baseline should be refreshed (the bot's auto-refresh or a follow-up) before or with the merge, not waived.

[bpamiri]

Re-ack @ f6234af: APPROVE (content unchanged); merge still gated on CI for this head

• The only change since e16c3c3 is the bot's chore(web): refresh visual baseline(s) (landing), which touches web/tests/visual-baselines/landing.png alone.
• I looked at the new baseline. The only visible change is the hero engine line, now "Runs on Lucee 6/7, Adobe ColdFusion 2023/2025, BoxLang, and RustCFML.", matching the reported text-only diff (hero line only). Nothing else on the page moved.

Note: gh pr checks currently reports no checks on f6234af. The refresh was pushed by github-actions[bot] with the workflow token, and commits pushed that way don't trigger new workflow runs. So this head has no PR CI yet, Visual regression included. It needs a run triggered on this head before it's merge-ready.

[bpamiri]

Re-ack @ a2e8ebc: APPROVE. This head is an empty commit on f6234af (identical tree), pushed only to trigger CI, and checks are now running on it. My approval of the content and the refreshed landing.png stands. Merge once PR CI, including Visual regression, is green.