@ijfw/install 1.2.5 → 1.2.6
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/CHANGELOG.md +57 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,62 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [1.2.6] -- 2026-05-01
|
|
4
|
+
|
|
5
|
+
**Token sandbox + parallel workflow dispatch + DeepSeek frontier upgrade.** A new `ijfw_run` MCP tool keeps large command output out of your context window entirely — builds, test suites, grep runs, and log tails are sandboxed to disk and summarized in a few lines instead of flooding thousands of tokens. The `ijfw-workflow` execution engine gains a formal Wave Table that makes parallel agent dispatch deterministic rather than inferred. DeepSeek moves to `deepseek-v4-pro` — the actual frontier model — so the Trident gets Frontier AI checking Frontier AI.
|
|
6
|
+
|
|
7
|
+
### `ijfw_run` — command output sandbox
|
|
8
|
+
|
|
9
|
+
Large shell commands (builds, test suites, `grep -r`, log tails) routinely produce hundreds or thousands of lines that consume a disproportionate share of the context window. `ijfw_run` solves this at the tool level: run the command via `child_process.spawn` (never `exec` — no RAM buffer ceiling), stream output to `~/.ijfw/session-sandbox/`, and return a domain-aware summary to context instead of the raw flood.
|
|
10
|
+
|
|
11
|
+
**Domain-aware summarizers** detect output type by pattern and extract only what matters:
|
|
12
|
+
- **Test runner** (Jest/Vitest/pytest/go test/cargo test): pass/fail counts + failing test names only
|
|
13
|
+
- **Build** (tsc/cargo/webpack/vite/rollup): error lines only + exit code
|
|
14
|
+
- **Grep**: match count + top file paths
|
|
15
|
+
- **Log**: ERROR/WARN lines + counts
|
|
16
|
+
- **Raw fallback**: first 15 + last 10 lines + "N lines omitted"
|
|
17
|
+
|
|
18
|
+
Every summary appends the last 10 raw lines as a reliability backstop (catches segfaults, OOM kills, and non-standard failures that heuristics miss), and includes the command, exit code, duration, and a retrieval label. Commands at or under 40 lines / 50 KB return inline with zero overhead — `ijfw_run` only sandboxes when it pays off.
|
|
19
|
+
|
|
20
|
+
**Retrieval**: full output is indexed to `~/.ijfw/session-sandbox/{label}.txt` with a `.json` metadata sidecar. Retrieve with `ijfw_memory_search({ scope: "sandbox", label: "..." })` or list all current sandbox entries with `ijfw_memory_search({ scope: "sandbox" })`. Sandbox files auto-purge after 24 hours (TTL sweep runs on every `ijfw_run` call).
|
|
21
|
+
|
|
22
|
+
**Security**: all labels are sanitized before becoming filenames; sandbox files are written at mode `0o600` (user-read-only); all SQLite interactions use parameterized queries; ANSI escape codes are stripped before heuristic detection and before content is returned to the LLM context.
|
|
23
|
+
|
|
24
|
+
**Routing rule**: `ijfw-core` SKILL.md now carries the one-line routing rule — large-output commands → `ijfw_run`; git, navigation, and quick ops → Bash directly.
|
|
25
|
+
|
|
26
|
+
**`ijfw_memory_status` retired** to free the MCP tool slot. The case handler is preserved for backward compatibility; the tool no longer appears in `tools/list`. Status information remains available via `ijfw_memory_prelude`.
|
|
27
|
+
|
|
28
|
+
**New `sanitizeForSandbox()`** in `sanitizer.js`: a sandbox-specific sanitizer that preserves newlines (unlike `sanitizeContent` which collapses to `" | "`), strips ANSI codes, defangs structural markdown elements (`#` headings, fenced code delimiters, `<system>/<prompt>/<assistant>` tags), and truncates lines over 2000 characters. Used for all LLM-facing sandbox output.
|
|
29
|
+
|
|
30
|
+
**`sandbox-nudge.sh` PreToolUse hook**: registered alongside the existing `pre-tool-use.sh`, this advisory hook pattern-matches known large-output command prefixes (`npm test`, `jest`, `vitest`, `pytest`, `cargo build`, `cargo test`, `make`, `gradle`, `mvn`, `go test`, `node --test`, `tsc --`, `webpack`, `vite build`, `rollup`, `grep -r`, `find /`) and emits a one-line nudge. Advisory only — never blocks.
|
|
31
|
+
|
|
32
|
+
Files: `mcp-server/src/sandbox.js` (new), `mcp-server/src/server.js`, `mcp-server/src/sanitizer.js`, `mcp-server/test-sandbox.js` (new, 32 tests), `mcp-server/test.js` (slot-swap update), `claude/skills/ijfw-core/SKILL.md`, `claude/hooks/hooks.json`, `claude/hooks/scripts/sandbox-nudge.sh` (new).
|
|
33
|
+
|
|
34
|
+
### Parallel workflow dispatch — Wave Table
|
|
35
|
+
|
|
36
|
+
The `ijfw-workflow` execution engine had a structural gap: Step 5 (Plan) described dependency relationships in prose, which meant Step 6 (Execute) had to re-infer parallelism at dispatch time. Re-inference defaults to sequential to avoid mistakes. The result: agents that could run concurrently ran one-by-one.
|
|
37
|
+
|
|
38
|
+
**Step 5 now emits a Wave Table** as the first section of `plan.md`:
|
|
39
|
+
|
|
40
|
+
```
|
|
41
|
+
| Wave | Tasks | Mode | Depends on | Reason |
|
|
42
|
+
|------|-----------|------------|------------|---------------------|
|
|
43
|
+
| W1 | t1, t2, t3 | PARALLEL | — | independent files |
|
|
44
|
+
| W2 | t4 | SEQUENTIAL | W1 | needs t2 output |
|
|
45
|
+
| W3 | t5, t6 | PARALLEL | W2 | independent of each |
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
Wave mode is determined by a four-question dependency test before the table is written: (a) shared file writes? (b) one reads what the other writes? (c) output dependency? (d) otherwise → PARALLEL. The Wave Table is the execution contract — decided once at plan time.
|
|
49
|
+
|
|
50
|
+
**Step 6 reads the Wave Table directly**: PARALLEL waves → all tasks dispatched as Agent tool calls in a single response (they run concurrently); SEQUENTIAL waves → one Agent call, wait for result, advance. If `plan.md` has no Wave Table (legacy plans, quick-mode tasks), Step 6 builds one on the spot using the same four-question test before dispatching anything. The instruction is now unambiguous: parallel waves produce multiple tool calls in one response block, not one-by-one messages.
|
|
51
|
+
|
|
52
|
+
Files: `claude/skills/ijfw-workflow/SKILL.md`.
|
|
53
|
+
|
|
54
|
+
### DeepSeek Trident auditor upgraded to `deepseek-v4-pro`
|
|
55
|
+
|
|
56
|
+
The 1.2.5 DeepSeek roster entry used `deepseek-v4-flash` as the API model ID — a model that does not exist on DeepSeek Platform. Calls returned 4xx errors that surfaced as apparent timeouts. The entry is corrected to `deepseek-v4-pro`: DeepSeek's 1.6T-parameter frontier model (49B activated), supporting 1M context and dual thinking/non-thinking modes. `deepseek-chat` and `deepseek-reasoner` — the previous canonical aliases — are deprecated aliases for V4-Flash non-thinking and thinking modes respectively, scheduled for removal 2026-07-24. `deepseek-v4-pro` is the correct Trident-grade choice: Frontier AI checking Frontier AI.
|
|
57
|
+
|
|
58
|
+
Files: `mcp-server/src/audit-roster.js`.
|
|
59
|
+
|
|
3
60
|
## [1.2.5] -- 2026-04-30
|
|
4
61
|
|
|
5
62
|
**Trident roster opens to the community + actionable auditor errors + Obsidian-friendly memory + audit-cleanup pass.** A one-page contribution playbook plus two new worked examples ship the auditor roster from "what Sean ships" to "what the community can grow." DeepSeek and Kimi land as openai-compat API entries. The 1.2.4 visibility surface gets a translation layer that tells you exactly how to fix a stalled auditor. Memory layer reaffirmed as Obsidian-vault-compatible with a walkthrough. Six surfaces from a full-system Trident audit land alongside as polish. Plus a routine dev-dependency bump.
|