feat(docs): generate and publish registry assets

[lloydrichards]

Goals/Scope

Generate the two public JSON assets for #272 in one docs build. Review the Vercel headers, route rules, and published-ID check.

Description

The docs build exports the catalog and the Draft 2020-12 schema from local definitions. New stack.effect.json files can include the hosted $schema link; old files still decode. The build rejects removed published IDs and unsupported capabilities.

Comments

Its deployed HTTP checks remain open: the production URLs return 404, and PR previews require Vercel SSO. Follow apps/docs/REGISTRY-DEPLOYMENT.md after deployment; do not close #272 from local build evidence.

[vercel]

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

Project	Deployment	Actions	Updated
stack-effect-docs	Ready	Preview	Sep 27, 2026 8:47pm UTC

[changeset-bot]

⚠️ No Changeset found

Latest commit: e1ad0bf

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pullfrog]

Important

The generated assets and routing look sound locally, but the hosted HTTP contract still needs preview verification before publication.

Reviewed changes in the current PR head:

• Public assets: Generates the official v1 catalog and Draft 2020-12 StackConfig JSON Schema from local definitions during docs development and builds.
• Compatibility checks: Adds optional $schema metadata and tests for existing catalog IDs and schema validation.
• Delivery configuration: Adds Vercel JSON, cache, CORS, preflight, 404, and SPA routing rules, plus deployment and rollback instructions.

⚠️ Hosted registry behavior is still unverified

The preview deployment reports ready, but an unauthenticated request for its catalog asset currently returns a 302 to Vercel SSO, not a JSON response. That is consistent with preview protection, but local builds and CI cannot establish the promised hosted 200/304, CORS/preflight, and missing-path 404 behavior; the production catalog URL still returns 404 before publication.

Technical details

# Qualify the deployed endpoints before publication

## Affected sites
- apps/docs/REGISTRY-DEPLOYMENT.md:7 — describes the preview and production HTTP checks, but no successful deployed checks are recorded.
- apps/docs/vercel.json:51 — custom preflight, filesystem, and missing-path routing has only local/CI build evidence.

## Required outcome
- Use an authenticated preview request or an approved deployment-protection bypass to verify both JSON endpoints, their content types, conditional GET/304, cross-origin GET and OPTIONS, and a missing registry path returning 404; check a docs deep link too.
- After promotion, repeat against the public production URLs before treating issue #272's publication criteria as complete.

  ^{｜ Fix it ➔ ｜ View workflow run ｜ Using GPT Sol ｜ 𝕏}