ds4-context-engine 0.2.0-rc.1 → 0.2.0

package/README.md

@@ -16,7 +16,7 @@ bounded active context with provenance
 Pi provider
 ```
 
-> **Project status:** M0–M20 and release-candidate hardening are available in prerelease `0.2.0-rc.1`: quality measurement, structural/hybrid retrieval, cross-session project memory, learned-ranking shadow evaluation, the runtime adapter kit, opt-in local KV reuse, schema-10 upgrades, long-session gates, and frozen 0.2 contracts. Stable `0.1.2` remains available; all lines target Pi `0.84.3`.
+> **Project status:** Stable `0.2.0` includes M0–M20 and release hardening: quality measurement, structural/hybrid retrieval, cross-session project memory, learned-ranking shadow evaluation, the runtime adapter kit, opt-in local KV reuse, schema-10 upgrades, long-session gates, and frozen 0.2 contracts. The maintenance line targets Pi `0.84.3`.
 
 ## Why DS4
 
@@ -86,13 +86,7 @@ Install the latest stable public npm package with:
 pi install npm:ds4-context-engine
 ```
 
-Install the opt-in 0.2 release candidate from the `rc` dist-tag with:
-
-```bash
-pi install npm:ds4-context-engine@rc
-```
-
-All prerelease packages (`ds4-context-engine`, `ds4-context-core`, and `ds4-context-reference-adapter`) use the same exact version.
+The stable `0.2.0` packages (`ds4-context-engine`, `ds4-context-core`, and `ds4-context-reference-adapter`) use the same exact version. Both adapters require the matching core version.
 
 ### Local checkout
 
@@ -340,7 +334,7 @@ The following example shows the main configuration groups. Omitted values use th
 }
 ```
 
-Invalid or unknown values are ignored with a warning. Model overrides merge deterministically from `*` to `provider/*` to an exact `provider/model` profile. The 0.2 release line freezes this additive surface as `ds4-context-config-v1`; existing keys, validation, and defaults are pinned by the compatibility golden.
+Invalid or unknown values are ignored with a warning. Model overrides merge deterministically from `*` to `provider/*` to an exact `provider/model` profile. Routine session open/close, database, rebuild, and project-index summaries are emitted only at `debug`, so the default `info` level keeps session changes quiet while preserving actionable warnings. The 0.2 release line freezes this additive surface as `ds4-context-config-v1`; existing keys, validation, and defaults are pinned by the compatibility golden.
 
 ## Privacy and provider storage
 
@@ -398,7 +392,7 @@ npm run check
 npm run quality:compare
 npm run pack:check
 # Post-publication, with an exact version rather than a dist-tag:
-npm run registry:check -- 0.2.0-rc.1
+npm run registry:check -- 0.2.0
 npm pack --dry-run
 npm pack --dry-run --workspace ds4-context-core
 npm pack --dry-run --workspace ds4-context-reference-adapter
@@ -446,6 +440,7 @@ scripts             package and release-readiness checks
 - [Roadmap 0.2.0](docs/ROADMAP_0.2.0.md)
 - [Release process](docs/RELEASING.md)
 - [0.2.0 release readiness](docs/RELEASE_READINESS_0.2.0.md)
+- [0.2.0 release notes](docs/releases/0.2.0.md)
 - [0.2.0-rc.1 release notes](docs/releases/0.2.0-rc.1.md)
 - [Architecture decisions](docs/ADR/README.md)
 - [Original development plan](DS4_Context_Engine_Extension_Piano_Sviluppo.md)
@@ -454,7 +449,7 @@ scripts             package and release-readiness checks
 
 The original M0–M13 roadmap is complete. `ds4-context-core` contains the compiled runtime-neutral implementation. M14 context-quality metrics, M15 rich symbol indexing, M16 hybrid semantic retrieval, M17 cross-session project memory, M18 learned-ranking shadow evaluation, M19's runtime adapter/conformance kit, and M20 opt-in local KV eligibility/replay are implemented on `main`. Learned active ranking remains promotion-gated, Pi reports local KV as unsupported, and static ranking/native completion stay authoritative on every failure.
 
-The [0.2.0 roadmap](docs/ROADMAP_0.2.0.md) is in release-candidate hardening. The [readiness record](docs/RELEASE_READINESS_0.2.0.md) maps every release gate to tests and operator commands. Sensitive or transport-specific behavior remains opt-in, and the 0.1 lexical planner stays available as the deterministic fallback.
+The [0.2.0 roadmap](docs/ROADMAP_0.2.0.md) is complete. The [readiness record](docs/RELEASE_READINESS_0.2.0.md) maps every release gate to tests and operator commands. Sensitive or transport-specific behavior remains opt-in, and the 0.1 lexical planner stays available as the deterministic fallback.
 
 ## Contributing
 

package/docs/RELEASE_READINESS_0.2.0.md

@@ -1,6 +1,6 @@
 # DS4 0.2.0 Release Readiness
 
-This document is the release-candidate hardening record for the 0.2 line. A prerelease is not a stable-release declaration. A candidate is complete only after the commands below pass on a clean commit and the exact published registry artifacts pass the post-publication check.
+This document is the completed hardening record for the stable 0.2 line. The `0.2.0-rc.1` candidate passed the commands below on a clean commit, and the stable release requires the same gates plus exact verification of the published `0.2.0` registry artifacts.
 
 ## Frozen compatibility surface
 
@@ -93,7 +93,7 @@ rm -rf "$BASELINE_DIR"
 After publishing all three packages in dependency order, verify registry bytes rather than local tarballs:
 
 ```bash
-npm run registry:check -- 0.2.0-rc.1
+npm run registry:check -- 0.2.0
 ```
 
 The registry check accepts an exact version, never a mutable dist-tag. It installs all three public packages plus the supported Pi SDK into a fresh project, validates matching exact core dependencies, imports core and local-KV exports, runs compiled reference conformance, runs the packaged quality corpus, and starts the published Pi extension through isolated offline RPC state.

package/docs/RELEASING.md

@@ -69,7 +69,9 @@ Review `package.json`, both workspace package manifests, and `package-lock.json`
 
 ## Publish
 
-Authenticate with npm, verify the active account, and publish in dependency order:
+Publishing is manual-only. GitHub Actions workflows must remain validation-only: do not add npm credentials, `NODE_AUTH_TOKEN`, `NPM_TOKEN`, `id-token: write`, `packages: write`, or an `npm publish` step. The CI workflow explicitly denies OIDC and package-write permissions.
+
+Authenticate with npm using an interactive OTP or a granular publish token with bypass 2FA, verify the active account, and publish in dependency order:
 
 ```bash
 npm whoami

package/docs/ROADMAP_0.2.0.md

@@ -1,6 +1,6 @@
 # DS4 0.2.0 Roadmap
 
-Status: **release candidate published**. `0.2.0-rc.1` is the latest prerelease; no stable release date is committed.
+Status: **complete**. Stable `0.2.0` is released with all compatibility and release gates satisfied.
 
 Version 0.2.0 focuses on evidence quality, safe project-wide reuse and runtime portability. It extends the released 0.1.0 architecture without changing its canonical-state or failure guarantees.
 
@@ -248,6 +248,14 @@ Status: **implemented and released in `0.2.0-rc.1`**. See [`RELEASE_READINESS_0.
 - Registry package smoke tests, documentation and release notes.
 - Freeze config, database and adapter-contract schemas for 0.2.0.
 
+### `0.2.0`
+
+Status: **stable release completed**. See the [release notes](releases/0.2.0.md) and the final [`RELEASE_READINESS_0.2.0.md`](RELEASE_READINESS_0.2.0.md) evidence record.
+
+- Promotes the validated release candidate without changing frozen 0.2 contracts or default behavior.
+- Publishes matching stable versions of the core, reference adapter and Pi adapter.
+- Verifies exact registry artifacts in a clean consumer after publication.
+
 ## Release gates
 
 Version 0.2.0 is ready only when (the live evidence matrix is maintained in [`RELEASE_READINESS_0.2.0.md`](RELEASE_READINESS_0.2.0.md)):

package/docs/releases/0.2.0.md

@@ -0,0 +1,43 @@
+# DS4 Context Engine 0.2.0
+
+Status: **stable release under the npm `latest` dist-tag**.
+
+DS4 Context Engine 0.2.0 promotes the validated `0.2.0-rc.1` candidate without changing its frozen contracts, safe defaults, or canonical-state guarantees.
+
+## Highlights since 0.1.2
+
+- deterministic metadata-only context-quality metrics and comparison corpus;
+- structural project chunks and richer symbol relations;
+- opt-in local or explicitly consented remote hybrid semantic retrieval;
+- opt-in cross-session project memory replay from canonical Pi JSONL;
+- learned ranking with `off`, shadow, promotion-gated active, and static fallback modes;
+- `runtime-adapter-v1`, a reusable conformance kit, and the callback/JSONL reference adapter;
+- opt-in exact local prefix/KV reuse for adapters with a host-owned volatile runtime port;
+- shared-SQLite WAL/write coordination and renewable fenced project-index leases.
+
+## Stable-release evidence
+
+- exact schema-v10 (0.1) to schema-v15 upgrade coverage;
+- complete rebuild coverage from canonical session, adapter, and project sources;
+- full configuration, migration, adapter, capability, and local-KV compatibility golden;
+- 1,201-message repeated-planning coverage for hard limits, canonical integrity, and bounded derived retention;
+- local/remote provider-switch, privacy, continuation, and cache-invalidation coverage;
+- feature-disabled p95 comparison against exact `ds4-context-core@0.1.2` within the 10% release threshold;
+- clean package-consumer validation and exact-version post-publication registry verification for all three packages.
+
+## Compatibility and defaults
+
+- Node.js `>=22.19.0`;
+- Pi `0.84.3`;
+- configuration contract `ds4-context-config-v1`;
+- SQLite projection schema `15`;
+- runtime adapter contract `runtime-adapter-v1`;
+- matching `0.2.0` versions are required for adapters and `ds4-context-core`.
+
+Existing 0.1 configuration remains valid. Semantic retrieval, cross-session memory, context-quality recording, learned ranking, and local KV reuse remain disabled by default. Pi JSONL, reference-adapter JSONL, and live project files remain canonical; SQLite, embeddings, ranking models, artifacts, and runtime KV state remain local and disposable.
+
+## Upgrade and rollback
+
+Opening a 0.1 database applies forward migrations 11–15 without rewriting canonical history. A 0.1 binary cannot open schema 15. To roll back, stop every process using the shared database, retain canonical JSONL and project files, and let 0.1 create a fresh derived database or use a different `storage.databasePath`. Never alter migration checksums or delete reference-adapter canonical JSONL.
+
+See [`../RELEASE_READINESS_0.2.0.md`](../RELEASE_READINESS_0.2.0.md) for the complete gate matrix, limitations, and rollback procedure.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ds4-context-engine",
-  "version": "0.2.0-rc.1",
+  "version": "0.2.0",
   "description": "Non-destructive, provider-independent context management for Pi.",
   "type": "module",
   "license": "MIT",
@@ -57,7 +57,7 @@
     ]
   },
   "dependencies": {
-    "ds4-context-core": "0.2.0-rc.1"
+    "ds4-context-core": "0.2.0"
   },
   "peerDependencies": {
     "@earendil-works/pi-ai": "0.84.3",

package/src/extension/runtime.ts

@@ -567,7 +567,7 @@ export class Ds4ContextRuntime {
 
       this.phase = this.config.context.mode;
       this.setStatus(ctx, `DS4 ctx: ${this.config.context.mode}`);
-      this.logger.info("session.opened", {
+      this.logger.debug("session.opened", {
         sessionId: this.session.sessionId,
         persisted: Boolean(this.session.sessionFile),
         projectPath: this.session.projectPath,
@@ -2162,7 +2162,7 @@ export class Ds4ContextRuntime {
         projectPath: resolve(ctx.cwd),
         fallbackReason: "Project indexing is skipped for filesystem roots and the user home directory",
       };
-      this.logger.warn("project_index.skipped", {
+      this.logger.debug("project_index.skipped", {
         reason: "broad-root",
         projectPath: resolve(ctx.cwd),
       });
@@ -2194,7 +2194,7 @@ export class Ds4ContextRuntime {
         return;
       }
       this.lastProject = this.projectKnowledge.diagnostics();
-      this.logger.info("project_index.opened", {
+      this.logger.debug("project_index.opened", {
         files: sync.discoveredFiles,
         indexedFiles: sync.indexedFiles,
         currentSnippets: sync.currentSnippets,
@@ -2587,7 +2587,7 @@ export class Ds4ContextRuntime {
     this.closeDatabase();
     if (ctx) this.setStatus(ctx, undefined);
     this.phase = "closed";
-    this.logger.info("runtime.closed", { sessionId: this.session?.sessionId });
+    this.logger.debug("runtime.closed", { sessionId: this.session?.sessionId });
   }
 
   private getCompactionDiagnostics(ctx: ExtensionContext): CompactionDiagnostics {

package/src/pi-adapter/session-indexer.ts

@@ -229,7 +229,7 @@ export class PiSessionIndexer {
       read.malformedLines,
       started,
     );
-    this.logger.info("session_index.rebuilt", { sessionId: session.sessionId, ...result });
+    this.logger.debug("session_index.rebuilt", { sessionId: session.sessionId, ...result });
     return result;
   }
 

package/src/pi-adapter/version.ts

@@ -1,4 +1,4 @@
-export const EXTENSION_VERSION = "0.2.0-rc.1";
+export const EXTENSION_VERSION = "0.2.0";
 export const SUPPORTED_PI_VERSION = "0.84.3";
 export const OBSERVER_PLANNER_VERSION = "observer-model-aware-v1";
 export const PLANNER_VERSION = "managed-learned-ranking-v1";