Forma v0.1.34

Scope

Publish the next coordinated Public Preview patch after releases/forma-v0.1.33. This cutline adds an explicit, read-only forma tools schema.validate path for structured JSON, YAML, and JSONL artifacts, clarifies the workspace and Agent contracts around that tool, and refreshes the supported frontend toolchain.

Included Changes

• Add a compiled-in, read-only forma tools registry with list, describe, and schema.validate contracts shared by the CLI and RPC surfaces.
• Validate one explicit JSON, single-document YAML, or JSONL file against a local JSON Schema with structured diagnostics, JSON Pointer paths, line locations, and no network $ref resolution or auto-fix.
• Keep structured-artifact validation separate from the native Forma Schema DSL used for Markdown frontmatter and configured space constraints.
• Clarify public workspace and Agent guidance, add the CLI tools documentation route, and extend executable documentation and workspace-fixture coverage.
• Refresh the coordinated Node, pnpm, frontend, and Wrangler dependencies and keep CLI, VS Code, and Zed versions aligned at 0.1.34.

Automatic artifact declarations and workspace-wide forma check integration remain explicitly deferred; the manual tool is the current MVP and the stable seam for a future opt-in phase.

Validation

1. mise run version:check -- v0.1.34 and mise run release:record-check -- v0.1.34 pass from the exact candidate.
2. Forma configuration, content, and workspace-health checks pass with zero errors and zero warnings.
3. CI=true mise run check passes from the exact aligned candidate.
4. The coordinated forma-0.1.34.vsix packages and passes isolated installation, activation, and LSP smoke gates with a matching forma 0.1.34 binary.
5. Main CI passes for the exact candidate commit before the annotated tag is created.
6. The protected Release workflow builds the expected cross-platform archives, standalone binaries, VSIX, and sibling SHA-256 assets from the exact source.
7. After publication, mise run release:verify -- v0.1.34 verifies the published asset inventory, checksums, CLI version, VSIX identity, and managed CLI installation.

Preparation Evidence

• Exact release source: candidate commit 299fdcc1578d422848aee5fc06c4873de6d06d51; annotated tag object 0cdd540b8519aa1047db6cfb5c1052b7f7cb9a82 peels to that commit.
• Local candidate gates: mise run version:check -- v0.1.34, mise run release:record-check -- v0.1.34, Forma check --json, and workspace health passed with zero errors and zero warnings. CI=true mise run check passed with 67 pnpm test files/404 tests, 48 Node script tests, 462 Rust tests, Zed WASM, TypeScript, ESLint, Prettier, WebApp, and VS Code builds.
• VSIX: forma-0.1.34.vsix packaged 57 files and passed isolated installation, activation, and LSP smoke validation as choral-io.forma@0.1.34.
• Exact main CI: run 33304258943 passed all jobs for the exact candidate commit, including the five-platform CLI release-build verification, VSIX smoke, static site, Web, Knowledge, and installer gates.

Published Evidence

• Release workflow: run 33304744556 passed exact-source validation, all five CLI artifact builds, VS Code packaging, source-bound assembly and promotion, published-release verification, and Marketplace publication.
• GitHub Release: Forma v0.1.34 is published as a non-draft, non-prerelease release with the expected 22 uploaded assets.
• Independent verification: mise run release:verify -- v0.1.34 passed for 22 assets and 11 payloads. The native macOS Arm64 CLI reported forma 0.1.34 with SHA-256 d216b5598c37795deefb85601266cbe67f4aaa49382f4604fb399f00bff8298a; the VSIX reported choral-io.forma@0.1.34, engine ^1.110.0, and SHA-256 fc9e8c7d0fdfbddc91d1af0dc49c29f327f20925236574c9132e79c7a5d101aa.
• Managed installation: the production editor-extension installation implementation downloaded, checksum-verified, installed, and executed the published forma-macos-arm64 payload as forma 0.1.34.
• Marketplace: the protected Marketplace job published choral-io.forma v0.1.34.

Rollout Plan

1. Completed and committed the aligned 0.1.34 candidate and its release metadata.
2. Pushed the candidate and passed exact-source main CI before tag creation.
3. Created and pushed the annotated tag v0.1.34 after the exact candidate was green.
4. Dispatched the protected Release workflow, approved its release-production and Marketplace environment gates, and published the source-bound GitHub Release and matching Marketplace extension.
5. Completed independent published-release verification and recorded the immutable evidence in a separate post-release commit.

Migration Or Operations Notes

• Existing workspaces require no migration; structured validation is opt-in through an explicit command.
• Keep JSON Schema files and structured data under the workspace boundary. Network and non-file $ref resolution is disabled.
• Keep Markdown frontmatter and space constraints on the native Forma Schema DSL; do not infer structured-artifact declarations from directory names.
• The release remains a Public Preview and preserves the coordinated CLI, VS Code, and Zed version contract.
• Remote SSH, Dev Container, WSL, code signing, notarization, Zed Registry publication, and non-native in-place replacement paths remain bounded acceptance areas unless exact release evidence closes them.

Release Notes

Forma v0.1.34 adds the explicit, read-only forma tools schema.validate workflow for structured JSON, YAML, and JSONL artifacts, clarifies the workspace and Agent contracts, and refreshes the coordinated toolchain.

Rollback Plan

Do not move or overwrite a published tag or asset. Before publication, return a failed candidate to remediation. After publication, use the official installer as the recovery path and publish a higher coordinated version for any correction.

Post-Release Follow-Up

• Reopen automatic artifact declarations and forma check integration only after repeated workspace evidence and an accepted opt-in contract.
• Continue the product-value roadmap through guided knowledge modeling and external validation rather than treating this technical contract release as product-value evidence.