@skein-code/cli 0.3.23 → 0.3.24

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -9,7 +9,7 @@ one of the milestones below.
9
9
 
10
10
  - Product name: `Skein`; primary executable: `skein`.
11
11
  - Compatibility executables: `mosaic` and `mosaic-code`.
12
- - Current repository version: `0.3.23`.
12
+ - Current repository version: `0.3.24`.
13
13
  - Runtime requirement: Node.js `>=22.16.0` (the runtime uses unflagged
14
14
  `node:sqlite` with FTS5, and current CLI/build dependencies require this
15
15
  Node 22 baseline).
@@ -41,8 +41,8 @@ npm audit --omit=dev
41
41
  npm run release:verify -- --output-dir artifacts/package
42
42
  ```
43
43
 
44
- The latest verified package is `skein-code-cli-0.3.23.tgz`. The verifier writes
45
- its SHA-256 to `artifacts/package/skein-code-cli-0.3.23.tgz.sha256`, and CI
44
+ The latest verified package is `skein-code-cli-0.3.24.tgz`. The verifier writes
45
+ its SHA-256 to `artifacts/package/skein-code-cli-0.3.24.tgz.sha256`, and CI
46
46
  retains the checksum beside the package metadata. The checksum is deliberately
47
47
  not copied into this packaged document because doing so would change the
48
48
  archive it describes.
@@ -124,6 +124,20 @@ the model explicitly calls `mcp_activate` for a configured server. The release
124
124
  does not add per-server trust scopes, provider billing A/B, or Context
125
125
  Compaction 2.0.
126
126
 
127
+ Version `0.3.24` completes the Context Compaction 2.0 engineering slice. Each
128
+ handoff rebuilds a deterministic facts envelope from the Task Contract,
129
+ working state, changed files, last-run verification, permission and failure
130
+ audit, retained artifact handles, and bounded older user corrections. Generated
131
+ narrative is fallible and optional; empty or contradictory output cannot erase
132
+ the authoritative facts, and the complete transcript remains persisted.
133
+ Automatic compaction calls the provider only when three predicted future prompt
134
+ reuses yield positive net estimated savings; explicit `/compact` remains a
135
+ manual override. Provider-reported or locally estimated compaction usage is
136
+ included in session totals and a separate content-free receipt. JSON/JSONL and
137
+ the Context Inspector expose the resulting decision without retaining prompt or
138
+ source text. Paid same-model task-success A/B remains required before closing
139
+ P0-E or making a provider-billing savings claim.
140
+
127
141
  ### P0-D: Repository reuse and calibrated duplication enforcement
128
142
 
129
143
  Version `0.3.14` added the prompt ladder and pre-write `ReuseReceipt`. Version
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skein-code/cli",
3
- "version": "0.3.23",
3
+ "version": "0.3.24",
4
4
  "description": "A context-first, model-agnostic coding agent with an auditable terminal workspace.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -16,6 +16,10 @@
16
16
  },
17
17
  "skein": {
18
18
  "releaseNotes": [
19
+ "Context compaction now rebuilds authoritative task, working-state, verification, permission, failure, and artifact facts outside generated narrative",
20
+ "Automatic compaction runs only when three predicted prompt reuses produce positive net token savings while explicit compact commands remain available",
21
+ "Compaction provider usage is included in session totals with separate content-free actual or estimated receipts",
22
+ "Empty or lossy narratives cannot erase deterministic facts, and the complete persisted transcript remains unchanged",
19
23
  "Normal chat startup now exposes a compact mcp_activate catalog instead of eagerly connecting MCP servers",
20
24
  "MCP activation connects one selected server, discovers remote tools, and loads at most eight relevant schemas",
21
25
  "Explicit MCP diagnostics can still connect eagerly while all MCP activation and remote calls remain network operations",