@skein-code/cli 0.3.12 → 0.3.14
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.
- package/README.md +12 -1
- package/dist/cli.js +617 -81
- package/dist/cli.js.map +1 -1
- package/docs/ARCHITECTURE.md +10 -1
- package/docs/NEXT_STEPS.md +37 -18
- package/package.json +7 -4
package/README.md
CHANGED
|
@@ -43,6 +43,9 @@ inspectable index for code retrieval and no retrieval service dependency.
|
|
|
43
43
|
source spans, and rebuild it explicitly when needed.
|
|
44
44
|
- **Visible trust:** per-category permissions, deny rules, hooks, workspace path
|
|
45
45
|
enforcement, changed-file telemetry, and persisted tool results.
|
|
46
|
+
- **Repository reuse guard:** the first substantive implementation addition gets a warning-only,
|
|
47
|
+
content-free receipt of current helper candidates and read evidence; docs,
|
|
48
|
+
config, fixtures, generated files, deletions, and local edits stay quiet.
|
|
46
49
|
- **Bounded tool context:** large tool results cannot crowd the task out of the
|
|
47
50
|
model window. Skein keeps a token-budgeted head/tail receipt and, when the
|
|
48
51
|
producer captured the complete result, retains a redacted session-scoped
|
|
@@ -86,7 +89,7 @@ To build, verify, and install a local package artifact from this checkout:
|
|
|
86
89
|
|
|
87
90
|
```bash
|
|
88
91
|
npm run verify:package -- --output-dir artifacts/package
|
|
89
|
-
npm install -g ./artifacts/package/skein-code-cli-0.3.
|
|
92
|
+
npm install -g ./artifacts/package/skein-code-cli-0.3.14.tgz
|
|
90
93
|
```
|
|
91
94
|
|
|
92
95
|
To install the published package from npm:
|
|
@@ -408,6 +411,14 @@ are stale, moved, symlinked, binary, or outside the workspace. Retrieval is
|
|
|
408
411
|
evidence only: the model must still confirm factual claims with read or other
|
|
409
412
|
workspace tools.
|
|
410
413
|
|
|
414
|
+
When a Skein tool reports changed files, the runner immediately invalidates and
|
|
415
|
+
atomically refreshes only those local-index paths before the next model turn;
|
|
416
|
+
headless and TUI runs share this boundary. External edits are reconciled from
|
|
417
|
+
file set, size, mtime, and ctime before retrieval, so even a same-size update
|
|
418
|
+
whose mtime was restored cannot turn a stale zero-hit result into evidence.
|
|
419
|
+
Repeated identical empty or unchanged `search_code` calls open the existing
|
|
420
|
+
recovery circuit instead of spending additional turns without new evidence.
|
|
421
|
+
|
|
411
422
|
Retrieval budgets are adaptive and treat `context.maxTokens` as a ceiling:
|
|
412
423
|
focused requests start at 2k estimated tokens, ordinary implementation/debug
|
|
413
424
|
work at 4k, cross-module work at 8k, and only explicit exhaustive repository
|