v0.4.7 — Native Specs: versioned documents and delivery lineage
Native Specs makes specifications first-class, versioned documents in CodePlans, connecting intended behavior to the capabilities actually delivered.
What's new
- Author and edit product-owned specs with draft, active, and archived states, typed associations, supersession, and optimistic revision checks.
- Link specs to assets, work items, and plans. Capability graduation pins the source spec revision, keeping delivered coverage distinct from newer intent.
- Use native spec readers, editors, asset tabs, and plan/work-item panels, plus seven new MCP tools (49 total).
- Render Markdown consistently across full pages and side panels, including paragraphs, line breaks, GFM tables, task lists, and fenced code.
- Import legacy spec URLs with product-scoped deduplication, provenance, review flags, failed-fetch placeholders, and safe reruns that preserve later native edits.
Upgrading
Install dependencies and apply the journaled 0017_native_specs migration for your configured SQLite or PostgreSQL database before starting the new application:
pnpm install --frozen-lockfile
pnpm db:migrateExisting URL-based specs remain readable. To import them into native documents, preview the report first, replacing YOUR_PRODUCT_ID with the product ID:
pnpm specs:migrate --product=YOUR_PRODUCT_ID --dry-run
# After reviewing the report:
pnpm specs:migrate --product=YOUR_PRODUCT_ID --applySee the Native Specs guide. Native Spec v1 retains the current body and revision; historical body diffs and Git write-back are not included.
Validation
The merged feature passed 222 tests, a production build, browser checks, and a disposable real PostgreSQL migration/behavior verification, including a second migration run. Standalone TypeScript checking retains five previously documented baseline errors; the feature introduced no new ones.
Implemented in #54. This release tags its merge commit, before the Wiki feature.
Full changelog: v0.4.6...v0.4.7