Docs System 0.0.2

Docs System 0.0.2 centralizes local documentation at http://localhost:4820, with project URLs under /projects//docs/.

• Adds a signed macOS background application and login service using a persistent local signing identity.
• Shares browser and MCP edits through one managed runtime, with project-scoped storage and draft locks.
• Adds viewer hot reload, health-checked runtime replacement, failed-build fallback, and persistent project registration.
• Documents service operation and independent Core product versioning in the native Docs corpus.

All 11 Docs System package manifests use 0.0.2. Other Core products retain their independent versions. This is a source release; no npm packages are published. The signed development service requires the documented Core checkout and a configured local signing certificate.

Validation: 52 targeted tests passed, the managed runtime bundled successfully, and the Docs MCP TypeScript check passed against the isolated release sources with installed dependencies. Live installation checks covered HMR, failed-build recovery, restart persistence, and pinned signatures. Browser visual verification was interrupted.

The attached manifest records the exact release commit and package inventory.

docs-system v0.0.1

Initial independently versioned source release of docs-system.

All packages owned by this product start at 0.0.1 and version together. Other Core products have their own release cadence.

Packages

• codecaine-docs-framework — 0.0.1
• @codecaine-ai/docs-cli — 0.0.1
• @codecaine-ai/docs-index — 0.0.1
• @codecaine-ai/docs-kernel — 0.0.1
• @codecaine-ai/docs-mcp — 0.0.1
• @codecaine-ai/docs-model — 0.0.1
• @codecaine-ai/docs-publish — 0.0.1
• @codecaine-ai/docs-server — 0.0.1
• @codecaine-ai/docs-viewer — 0.0.1
• @codecaine-ai/docs-workbench — 0.0.1
• @codecaine-ai/docs-framework-skill — 0.0.1

Release scope

Version metadata is initialized on the existing GitHub main source baseline 7e8bb6bc02dce7d34cd35a4271677930fcc926e5. This release does not include uncommitted local development changes or unpublished local commits. Existing workspace dependency wiring remains in place; these are GitHub source releases, not npm publications or standalone installers.

Validation

All product package manifests were checked for 0.0.1. Semantic comparison confirmed that only version fields changed; existing lockfile workspace version entries were synchronized. git diff --check passed. Runtime test suites were not rerun for this metadata-only change.

The attached manifest records the exact release commit and package inventory.