zooqueen 75c4f1f641 One product answers with one name, route, command and docs page ...

The CLI lines on the product pages were written from the product name -- hanzo
dns zones, hanzo kms keys -- and several were not commands the binary has. So the
command moves into lib/product.ts, which assembles the rest from what is already
stated: the catalog names the product and its route, pages.json names what the
catalog does not carry, and products-metadata answers for docs, where null means
docs publishes nothing and the link drops.

Every CLI line in that table was run against the binary. A product absent from it
has no command and its page prints none; nothing composes a verb out of a name.
Both blocks that draw it import the Product type rather than declaring their own,
which leaves the table the only place a command can be written.

The catalog also moves out of package.json into pnpm-workspace.yaml, where pnpm
reads it, so the versions are stated once.

2026-09-06 23:18:24 -07:00

..

layout.tsx

every page says what it is — and the deploy lane opens

2026-08-13 18:16:38 -07:00

page.tsx

One product answers with one name, route, command and docs page

2026-09-06 23:18:24 -07:00