releases

Forma v0.1.0-alpha.16

Performance-focused internal alpha with scoped discovery, bounded editor work, and a compact lazy Explorer.

Purpose

Publish the performance and workspace-scope improvements completed after releases/forma-v0.1.0-alpha.15 as an immutable internal prerelease. CLI, Core, RPC, WebApp, and VS Code extension artifacts use the same version because the extension now consumes new compact Explorer operations.

Scope

  • Discover Forma from the selected root .forma.md and recompute controlled file scope when imports or configured includes change.
  • Avoid scanning and watching unrelated workspace Markdown outside configured content scope.
  • Reuse one document analysis result for Preview links and diagnostics instead of resolving every link in a separate CLI process.
  • Bound Forma CLI concurrency to two, deduplicate identical work, cancel stale generations, and coalesce refresh bursts.
  • Retry a document diagnostic once after a content-scope invalidation cancels its active inspect command, while keeping the retry bounded and cancellation-aware.
  • Reuse an already loaded workspace configuration across Core discovery and operation projections.
  • Add workspace explorer and paginated workspace explorer-entries CLI/RPC operations.
  • Load taxonomy and View summaries initially, then fetch term entries lazily in pages of 100 with a hard maximum of 500.
  • Keep the complete dashboard operation available for consumers that need the full projection.
  • Add repeatable 1,000-entry and 5,000-entry performance benchmarks and aligned release-version automation.

Release Gates

  1. CI=true mise run check passes locally after the version update.
  2. mise run version:check -- v0.1.0-alpha.16 passes.
  3. Forma config, content checks, and workspace health pass.
  4. The clean full performance baseline remains within the documented latency, output, and peak RSS budgets.
  5. Tag CI passes version validation, five CLI builds, Extension Host tests, VSIX packaging, and packaged-artifact smoke validation.
  6. GitHub Release publishes five CLI archives, forma-0.1.0-alpha.16.vsix, and a checksum for every payload.
  7. Downloaded release payloads pass checksum, binary-version, and VSIX identity verification.

Known Boundaries

  • Graph rendering remains a separate focused project.
  • Semantic analysis and View projections refresh from saved Markdown.
  • Explorer output is compact and paginated, but each short-lived CLI operation still reconstructs its in-memory workspace analysis.
  • Local workspaces are the release gate. Remote environments remain best-effort until separately measured.

Validation

  • Dependency lockfiles installed successfully under the repository supply-chain policy.
  • Forma config inspection and workspace health passed before release preparation.
  • Performance Iterations 0 through 4 and Milestone A are recorded in planning/forma-performance-optimization-plan.
  • CI=true mise run check passed locally with aligned 0.1.0-alpha.16 versions, 83 TypeScript tests, 13 release-script tests, 164 Core tests, 22 RPC tests, 23 CLI library tests, 25 CLI integration tests, formatting, lint, type checks, and production builds.
  • A deterministic VS Code 1.128 regression probe confirmed that diagnostics recover when a content watcher cancels an active inspect command. The complete local VS Code 1.128 Extension Host suite then passed link navigation, ordinary-tag exclusion, editable View source, View Preview, and new-file diagnostics.
  • Main CI run 29232794756 passed Knowledge, Web, Rust, and VS Code Extension jobs at commit 77182527c5cf932181c111604c0ebd192c6944e7. Stable and minimum-version Extension Host tests, VSIX packaging, packaged-artifact smoke validation, and artifact upload all passed.
  • Annotated tag v0.1.0-alpha.16 points to the verified main commit. Release run 29232921295 passed version validation, five CLI builds, VS Code Extension tests, VSIX smoke validation, checksum generation, and GitHub Release publication.
  • GitHub prerelease v0.1.0-alpha.16 contains five platform archives, forma-0.1.0-alpha.16.vsix, and a sibling checksum for every payload, for 12 assets total.
  • All six downloaded payload checksums passed. The released macOS arm64 binary reports forma 0.1.0-alpha.16; the VSIX SHA-256 is 31e2520a36822142bfaa77d811c935c33e164771d30b48fa3357ce6d7c69ff0b, and its manifest reports choral-io.forma@0.1.0-alpha.16 with VS Code ^1.110.0 and homepage https://forma.choral.io.
  • Two clean post-release performance baselines from the exact release commit remained within every current 5,000-entry latency and 64 MiB peak-RSS budget. Several median latency comparisons were 5–17% slower than the Milestone A baseline, so the signal is recorded for paired old/new binary investigation rather than dismissed as noise or treated as evidence for a transport change.

Release Notes

Forma v0.1.0-alpha.16 focuses on keeping editor interaction predictable as a workspace grows. It scopes discovery to configured content, removes per-link process fan-out, bounds and deduplicates extension work, recovers diagnostics cancelled by content invalidation, reuses loaded Core configuration, and replaces the VS Code Explorer's full dashboard payload with compact summaries and paginated lazy entries.

Rollback Plan

Do not move or overwrite the Alpha 16 tag. If internal testing finds a release blocker, stop distributing Alpha 16, record the failure, and publish a new version after the correction is verified.

Post-Release Follow-Up

  • Before the next performance optimization, run paired 6ff64f09f741 and Alpha 16 binaries on the same quiescent host to isolate the observed 5,000-entry latency increase from host variance and dependency effects.
  • Measure VS Code Remote separately before changing the current short-lived CLI transport.