iosm-cli 0.2.11 → 0.2.13

package/docs/cli-reference.md

@@ -132,9 +132,17 @@ These commands run inside interactive mode (`iosm`), not as top-level CLI subcom
   - carries compact checkpoint state between iterations (facts, rejected hypotheses, open questions, next checks)
   - auto-injects a grounding retry when early passes return no tool evidence, forcing live workspace probes
   - if query is omitted, reuses latest meaningful user request from session context
-- `/bg [list [limit]|status [id]|logs [id] [lines]|stop [id]]` — interactive background shell process manager:
+- `/bg` — interactive background shell process menu
+- `/bg [list [limit]|running [limit]|status [id]|logs [id] [lines]|stop [id]|stop-all|prune [hours]]` — direct background shell process commands:
   - run detached shell commands with `! <command> &`
-  - inspect process state, log tail, and stop running background jobs
+  - inspect process state, log tail, stop individual jobs, stop all running jobs, and prune old completed records
+- `/extensions` (`/ext`) — extension lifecycle manager:
+  - `/extensions list [--global]`
+  - `/extensions install <source> [--global]`
+  - `/extensions update [source]`
+  - `/extensions remove <source> [--global]`
+  - `/extensions enable <target> [--global]`
+  - `/extensions disable <target> [--global]`
 - `/swarm` — canonical gated execution runtime:
   - `/swarm run <task> [--max-parallel N] [--budget-usd X]`
   - `/swarm from-singular <run-id> --option <1|2|3> [--max-parallel N] [--budget-usd X]`
@@ -303,6 +311,7 @@ Best-practice patterns:
 - File mutation: prefer `edit` for surgical changes and `write` for full rewrites; use `fs_ops` for `mkdir/move/copy/delete`, with `force=true` only when replacement/no-op behavior is intentional.
 - Verification: prefer `test_run` / `lint_run` / `typecheck_run` over ad-hoc bash commands for deterministic runner resolution and normalized status reporting.
 - Long-running shell jobs: prefer detached `bash` (`run_in_background=true`) or interactive `! <command> &`, then monitor with `/bg` instead of blocking the foreground turn.
+- Project/server startup requests (for example "run project", "start dev server", watcher modes): default to detached background execution and return/process `backgroundTaskId` for status/log/stop follow-up.
 - DB operations: prefer `db_run` with named profiles; keep read flows in `query/schema/explain` and use `allow_write=true` only for `exec/migrate`.
 - Structured data transforms: use `jq`/`yq` to compute/preview transforms, then persist the final state through `edit`/`write`.
 - Semantic retrieval: use `semantic_search status` first when relevance looks stale, then run `query`; run `index`/`rebuild` when config or index freshness requires it.

package/docs/configuration.md

@@ -105,7 +105,8 @@ Settings are merged in this order (later wins):
     "enableContextDedupe": true,
     "maxContextCharsPerFile": 4000,
     "maxTotalContextChars": 12000,
-    "enableGitSnapshotContext": false
+    "enableGitSnapshotContext": false,
+    "gitSnapshotMaxChars": 2000
   },
   "permissions": {
     "autoApprove": false,
@@ -117,7 +118,7 @@ Settings are merged in this order (later wins):
 `githubTools.networkEnabled` controls whether `git_write` network actions (`fetch`, `pull`, `push`) are allowed.  
 `githubTools.token` is optional and, when set, is injected for GitHub HTTPS authentication during network git actions.
 `dbTools` defines named DB connection profiles consumed by `db_run`; for network adapters (`postgres`, `mysql`, `mongodb`, `redis`) use `dsnEnv` so secrets stay in environment variables instead of tool input.
-`promptContext` controls system prompt context compaction before model call: dedupe by normalized content hash, per-file char budget, total char budget, and optional git snapshot context inclusion.
+`promptContext` controls system prompt context compaction before model call: dedupe by normalized content hash, per-file char budget, total char budget, optional git snapshot context inclusion, and bounded git snapshot size.
 `permissions.extensionToolEnforcement` enables strict runtime permission tier checks for extension tools (off by default).
 
 ### `db_run` Setup (Recommended)
@@ -431,6 +432,7 @@ Example:
 - per-file cap (`maxContextCharsPerFile`)
 - total cap (`maxTotalContextChars`)
 - optional git snapshot context (`enableGitSnapshotContext`)
+- git snapshot cap (`gitSnapshotMaxChars`, default `2000`)
 
 Default values:
 
@@ -440,7 +442,8 @@ Default values:
     "enableContextDedupe": true,
     "maxContextCharsPerFile": 4000,
     "maxTotalContextChars": 12000,
-    "enableGitSnapshotContext": false
+    "enableGitSnapshotContext": false,
+    "gitSnapshotMaxChars": 2000
   }
 }
 ```

package/docs/interactive-mode.md

@@ -83,7 +83,8 @@ iosm --continue
 | `/agents` | Inspect custom/system agents | `/agents` |
 | `/subagent-runs` | List subagent run history | `/subagent-runs` |
 | `/subagent-resume` | Resume a subagent run | `/subagent-resume run-123` |
-| `/bg` | Background shell process manager (`list/status/logs/stop`) | `/bg status bg_...` |
+| `/bg` | Background shell process manager (interactive menu + `list/running/status/logs/stop/stop-all/prune`) | `/bg` |
+| `/extensions` | Extension lifecycle manager (`/ext` alias) | `/extensions list` |
 | `/team-runs` | List team orchestration runs | `/team-runs` |
 | `/team-status` | Check team run status | `/team-status team-456` |
 
@@ -114,7 +115,20 @@ In `/semantic setup`, the headers step is optional: press `Enter` on empty input
 `/ultrathink [-q N|--iterations N] [query]` runs `N` root-agent analysis passes in strict read-only mode (`N` defaults to `5`, max `12`), carries a compact checkpoint between passes, and emits concise per-iteration summaries with a final synthesis.
 `/ultrathink` without query reuses the latest meaningful user request from session context.
 If early passes produce no tool evidence, ultrathink injects an internal grounding retry so the agent probes the workspace with read-only tools before continuing.
-Run detached shell jobs with `! <command> &` (example: `! npm run dev &`) and manage them using `/bg`, `/bg status <id>`, `/bg logs <id> [lines]`, `/bg stop <id>`.
+Run detached shell jobs with `! <command> &` (example: `! npm run dev &`) and manage them via `/bg` interactive menu or direct commands:
+- `/bg list` or `/bg running`
+- `/bg status <id>`
+- `/bg logs <id> [lines]`
+- `/bg stop <id>` or `/bg stop-all`
+- `/bg prune [hours]` (remove old completed records; keeps running jobs)
+Manage extension lifecycle from interactive mode:
+- `/extensions list` (or `/extensions list --global`)
+- `/extensions install <source> [--global]`
+- `/extensions update [source]`
+- `/extensions remove <source> [--global]`
+- `/extensions enable <target> [--global]`
+- `/extensions disable <target> [--global]`
+For agent-driven execution, prompts like "start/run project", "start dev server", or watcher startup are treated as detached background jobs by default unless foreground output is explicitly requested.
 `/swarm` enforces `Scopes -> Touches -> Locks -> Gates -> Done`. If effective contract is missing, it blocks execution and opens a bootstrap menu (auto-draft, guided Q&A, or manual `/contract` editor).
 `/orchestrate --parallel` defaults `--max-parallel` to `--agents` when omitted and auto-selects `meta` workers when profiles are not explicitly set (outside read-only host contexts).
 For orchestrate assignments, `delegate_parallel_hint` is carried into child task calls; high hints should trigger nested delegate fan-out or explicit `DELEGATION_IMPOSSIBLE`.

package/docs/sessions-traces-export.md

@@ -129,7 +129,7 @@ Traces are stored as `<session-id>.jsonl` files. Each line is a JSON event:
 ```jsonl
 {"type":"session_start","timestamp":"2026-03-09T15:42:00Z","sessionId":"abc123"}
 {"type":"user_message","timestamp":"2026-03-09T15:42:05Z","content":"Analyze the project"}
-{"type":"system_prompt_context_compose","timestamp":"2026-03-09T15:42:05Z","context_before_chars":16422,"context_after_chars":11998,"dedupe_hits":2,"truncated_files":["README.md"],"dropped_files":1}
+{"type":"system_prompt_context_compose","timestamp":"2026-03-09T15:42:05Z","context_before_chars":16422,"context_after_chars":11998,"dedupe_hits":2,"truncated_files":["README.md"],"dropped_files":1,"git_snapshot_included":true,"git_snapshot_chars_before":2450,"git_snapshot_chars_after":2000,"git_snapshot_truncated":true,"git_snapshot_max_chars":2000}
 {"type":"tool_call","timestamp":"2026-03-09T15:42:06Z","tool":"ls","input":{"path":"."}}
 {"type":"tool_result","timestamp":"2026-03-09T15:42:06Z","tool":"ls","output":"..."}
 {"type":"bash_end","timestamp":"2026-03-09T15:42:07Z","command":"npm run dev","backgroundTaskId":"bg_1770000000000_ab12cd34"}
@@ -139,7 +139,7 @@ Traces are stored as `<session-id>.jsonl` files. Each line is a JSON event:
 
 Notable runtime events:
 
-- `system_prompt_context_compose` shows prompt-context preprocessing stats (before/after chars, dedupe hits, truncation, dropped files).
+- `system_prompt_context_compose` shows prompt-context preprocessing stats (before/after chars, dedupe hits, truncation, dropped files) plus git snapshot diagnostics when enabled.
 - `bash_end.backgroundTaskId` is populated when a shell command was started in detached background mode.
 
 ### Analyzing Traces

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "iosm-cli",
-	"version": "0.2.11",
+	"version": "0.2.13",
 	"description": "Standalone IOSM CLI with agent tooling, session management, and IOSM artifact orchestration",
 	"type": "module",
 	"iosmConfig": {