clavue 8.22.21 → 8.22.23

package/dist/provider-setup.js

@@ -7,7 +7,7 @@ import { createInterface } from 'node:readline/promises'
 import { stdin, stdout } from 'node:process'
 import { fileURLToPath } from 'node:url'
 
-const APP_VERSION = '8.22.21'
+const APP_VERSION = '8.22.23'
 const APP_NPM_PACKAGE_NAME = 'clavue'
 export const CURRENT_PROVIDER_PROFILE_ID = '__current_provider__'
 const SUPPORTED_LANGUAGES = new Set(['en', 'zh'])

package/docs/CONTEXT-ARCHITECTURE-V2.md

@@ -1,6 +1,6 @@
 # Context Architecture v2 — Cache-aware Boundary Migration
 
-> Status: design + incremental implementation behind CLAVUE_BOUNDARY_V2=1 (Responses priority for gpt-5.x).
+> Status: shipped default-on implementation; set CLAVUE_BOUNDARY_V2=0/false/no/off only as a rollback switch (Responses priority for gpt-5.x).
 > Core: append-only in-memory + archive.md blob, v2 boundary metadata (archivedRange, summaryBlobOffset, schemaVersion),
 > resume hydration, Responses stateful reset on compact + postCompactAnchor + isV2PostCompactAnchor in policy,
 > fingerprint includes v2_archived for logical prefix stability, Responses builder attaches _clavue_v2_archived + _has_pinned to metadata
@@ -161,7 +161,7 @@ Backwards compat:
 
 - Old sessions (no `schemaVersion: 'v2'` on boundary) → fall back to v1
   loader, which reads inline summary messages exactly as today
-- New sessions with `CLAVUE_BOUNDARY_V2=1` → write v2 format
+- New sessions write v2 format by default unless `CLAVUE_BOUNDARY_V2=0` disables it
 - Mixed mode (resumed v1 session, new compact triggers under v2 flag) →
   upgrade in place: write archive.md, drop inline summary, leave existing
   v1 boundaries valid for the loader
@@ -178,7 +178,7 @@ Block implementation on **all** of these, captured from real sessions
 | Compact frequency | count of `compact_boundary` per session-hour | Today's median |
 | Emergency-truncate trigger rate | `emergency_truncate` userContext count | Today's median |
 
-After v2 ships behind `CLAVUE_BOUNDARY_V2=1`, run AB for 1 week with the
+After v2 ships, run AB for 1 week with the
 same metrics. Promote to default only if cache hit rate ≥ 70% AND token
 cost down ≥ 30% AND no regression on the other two.
 
@@ -216,7 +216,7 @@ Phase A (1-2 days)   — telemetry only: log cache_hit_rate at every turn
                        under a `tengu_cache_observability` event. Build
                        the baseline dashboard.
 Phase B (3-5 days)   — implement archived_history_blob + new boundary
-                       protocol behind CLAVUE_BOUNDARY_V2=1. AB-test on
+                       protocol. AB-test on
                        internal sessions.
 Phase C (1 week)     — flip default to v2 for new sessions; resumed v1
                        sessions stay on v1 until next compact upgrades

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clavue",
-  "version": "8.22.21",
+  "version": "8.22.23",
   "description": "Clavue: execution-first AI coding CLI with direct repo tools, provider routing, native workflows, MCP integration, and long-session recovery",
   "keywords": [
     "clavue",
@@ -74,7 +74,7 @@
     "build": "npm run verify:dist-clean && npm run check && npm pack --dry-run",
     "build:knowledge": "node scripts/build-project-knowledge.mjs",
     "vendor:ripgrep": "node scripts/vendor-ripgrep.mjs",
-    "check": "npm run vendor:ripgrep && npm run validate:repo && npm run verify:dist && npm run verify:source-build && npm run check:source-purity && npm test",
+    "check": "npm run vendor:ripgrep && npm run validate:repo && npm run verify:dist-clean && npm run verify:dist && npm run verify:source-build && npm run check:source-purity && npm test",
     "check:hygiene": "npm run validate:repo",
     "check:source-purity": "node scripts/check-source-purity.mjs",
     "check:boundaries": "node scripts/check-architecture-boundaries.mjs",