@wrongstack/core 0.275.1 → 0.276.3

package/dist/{worktree-manager-A1Efnvs0.d.ts → worktree-manager-DBdl_5rs.d.ts}

@@ -1,4 +1,4 @@
-import { E as EventBus } from './brain-DCkB5_e7.js';
+import { E as EventBus } from './brain-BLOyN5ZP.js';
 
 /**
  * Lifecycle of a single worktree handle.
@@ -73,6 +73,7 @@ interface RunResult {
 interface WorktreeManagerOptions {
     projectRoot: string;
     events?: EventBus | undefined;
+    sessionId?: string | (() => string | undefined) | undefined;
     gitBin?: string | undefined;
     /**
      * Test seam. When provided, replaces the real `git` spawn so the manager's
@@ -89,6 +90,7 @@ interface WorktreeManagerOptions {
 declare class WorktreeManager {
     private readonly projectRoot;
     private readonly events?;
+    private readonly sessionIdSource;
     private readonly gitBin;
     private readonly runGit;
     /** Keyed by ownerId. */
@@ -262,6 +264,7 @@ declare class WorktreeManager {
     private fail;
     private setStatus;
     private emit;
+    private currentSessionId;
     private defaultRun;
 }
 /** Throw if `dir` resolves outside `projectRoot`. */

package/instructions/agents/shadow-agent.md

@@ -6,7 +6,7 @@ Your job is to inspect the fleet when the host explicitly assigns a Shadow pass,
 
 1. **Fleet Monitoring** (host-assigned one-shot checks)
    - The host assigns one-shot check tasks; it does not expect routine heartbeats
-   - On each assigned check, call `fleet_status` + `fleet_health`
+   - On each assigned check, call `fleet` with `action: "status"` and `action: "health"`
    - Track what each agent is doing (task descriptions)
    - Detect stuck agents (>5min no events), idle agents, crashed agents
 
@@ -95,7 +95,7 @@ When `hoop` command received:
 
 ## Startup Sequence
 
-1. Run one fleet snapshot with `fleet_status` + `fleet_health`
+1. Run one fleet snapshot with `fleet` (`action: "status"` + `action: "health"`)
 2. Check `mail_inbox` for explicit control messages
 3. If healthy, do not send mail; final answer may be exactly `shadow: quiet`
 
@@ -106,6 +106,6 @@ When `hoop` command received:
 
 ## Skills in scope
 
-- fleet_status, fleet_health — for fleet snapshots
+- fleet (action: status/health) — for fleet snapshots
 - terminate_subagent — for intervention
 - mail_send, mail_inbox — for messaging and monitoring

package/instructions/coordination/director-preamble.md

@@ -9,8 +9,8 @@ Core fleet tools available to you:
   - ask_subagent         — synchronously query a running subagent via the bridge
   - roll_up              — aggregate finished tasks into a markdown/json summary
   - terminate_subagent   — abort a stuck worker (use sparingly)
-  - fleet_status         — snapshot of all subagents and pending tasks
-  - fleet_usage          — token + cost breakdown per subagent and total
+  - fleet                — snapshot of all subagents and pending tasks (action: status)
+  - fleet                — token + cost breakdown per subagent and total (action: usage)
 
 Working rules:
   1. Decompose first. Before spawning, decide which sub-tasks are
@@ -22,7 +22,7 @@ Working rules:
      the user a single coherent answer at the end.
   4. Roll up before deciding. After await_tasks resolves, call roll_up so
      the results are folded back into your context in a compact form.
-  5. Budget is real. Check fleet_usage periodically. If a subagent is
+  5. Budget is real. Check `fleet` with `action: "usage"` periodically. If a subagent is
      thrashing, terminate it rather than letting cost climb silently.
   6. Never claim a subagent's work as your own without verifying it. If a
      result looks wrong, ask_subagent for clarification before passing it

package/instructions/modes/research-web.md

@@ -12,8 +12,8 @@ changes must be verified against live sources.
 - You realize your knowledge may be >6 months old on a fast-moving topic
 
 ### Research methodology
-1. **Search first, fetch selectively.** Use web_search with 5-8 results for
-   broad queries. Then web_fetch the 1-2 most authoritative results for detail.
+1. **Search first, fetch selectively.** Use `search` with 5-8 results for
+   broad queries. Then `fetch` the 1-2 most authoritative results for detail.
    Don't fetch every result — you'll burn tokens on noise.
 2. **Cross-reference.** One source is a data point. Two sources that agree
    is a signal. Three is confirmation. Flag single-source claims as tentative.
@@ -30,9 +30,9 @@ changes must be verified against live sources.
 When you discover current data mid-research, inject it so subsequent turns
 benefit without re-searching:
 
-web_search("Next.js middleware breaking changes 2025")
+search("Next.js middleware breaking changes 2025")
   → Surfaced: Next.js 15.2 changed middleware runtime from edge to node
-web_fetch("https://nextjs.org/docs/messages/middleware-upgrade-guide")
+fetch("https://nextjs.org/docs/messages/middleware-upgrade-guide")
   → Confirmed: middleware now runs on Node.js runtime by default
 context_manager: add_note(
   "## Research: Next.js middleware

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wrongstack/core",
-  "version": "0.275.1",
+  "version": "0.276.3",
   "license": "MIT",
   "description": "WrongStack core: kernel, types, defaults, and shared utilities for the WrongStack CLI agent.",
   "repository": {

package/skills/research-web/SKILL.md

@@ -32,7 +32,7 @@ provides the deep methodology and patterns the mode prompt can't fit.
 4. Respect the stop rule. 2-3 searches + 1-2 fetches per topic. If no clear
    answer after that, surface the ambiguity rather than research-looping.
 5. Cite every claim. Domain name minimum; date if visible on the page.
-6. Match tool to task. `web_search` for discovery, `web_fetch` for detail,
+6. Match tool to task. `search` for discovery, `fetch` for detail,
    `fetch` for raw API responses, `search` for source-code-specific queries.
 
 ## Research Workflow Taxonomy
@@ -43,8 +43,8 @@ Not every research task needs the same approach. Match the workflow to the need:
 **When**: "What's the latest version of React?" "Is package X still maintained?"
 **Pattern**:
 ```
-web_search("React latest stable version 2025")  →  discover version
-web_fetch("https://react.dev/versions")          →  confirm from authoritative source
+search("React latest stable version 2025")  →  discover version
+fetch("https://react.dev/versions")          →  confirm from authoritative source
 context_manager add_note("## Research: React version\n- 19.2.0 (March 2025)\n- Source: react.dev")
 ```
 **Budget**: 1 search + 1 fetch = ~2000 tokens. Done in one turn.
@@ -53,8 +53,8 @@ context_manager add_note("## Research: React version\n- 19.2.0 (March 2025)\n- S
 **When**: "How has Next.js middleware changed across 14.x → 15.x?"
 **Pattern**:
 ```
-Turn 1: web_search("Next.js middleware changes 14 to 15") → collect URLs
-Turn 2: web_fetch(upgrade guide), web_fetch(changelog)     → parallel fetches
+Turn 1: search("Next.js middleware changes 14 to 15") → collect URLs
+Turn 2: fetch(upgrade guide), fetch(changelog)     → parallel fetches
 Turn 3: cross-reference, inject structured findings
 ```
 **Budget**: 2 searches + 2-3 fetches = ~5000 tokens. Use parallel fetches.
@@ -68,10 +68,10 @@ See "Subagent Delegation" section below.
 
 | Tool | Best for | Avoid for |
 |------|----------|-----------|
-| `web_search` | Broad discovery, finding current URLs, getting an overview | Deep detail (use `web_fetch` after) |
-| `web_fetch` | Reading a specific page for detail, authoritative confirmation | Broad queries (use `web_search` first) |
-| `search` | Technical docs, source code, API references (DuckDuckGo) | General web queries (use `web_search`) |
-| `fetch` | Raw API responses (JSON), registry endpoints, structured data | HTML pages (use `web_fetch` for markdown conversion) |
+| `search` | Broad discovery, finding current URLs, getting an overview | Deep detail (use `fetch` after) |
+| `fetch` | Reading a specific page for detail, authoritative confirmation | Broad queries (use `search` first) |
+| `search` | Technical docs, source code, API references (DuckDuckGo) | General web queries (use `search`) |
+| `fetch` | Raw API responses (JSON), registry endpoints, structured data | HTML pages (use `fetch` for markdown conversion) |
 | `context_manager` | Injecting research findings into conversation for future turns | Research itself (this is the *output* tool) |
 
 ### Decision heuristic
@@ -83,7 +83,7 @@ See "Subagent Delegation" section below.
            ▼                ▼                 ▼
      "Discover URLs"   "Read a page"    "Raw API data"
            │                │                 │
-     web_search        web_fetch           fetch
+     search        fetch           fetch
            │                │
            └────────┬───────┘
                     ▼
@@ -238,8 +238,8 @@ Source A (GitHub issue comment): "This API is being removed in v4"
 
 | Action | Approximate cost | When to use |
 |--------|-----------------|-------------|
-| `web_search` (5 results) | ~500 tokens | Always first — cheap discovery |
-| `web_fetch` (single page) | ~1000-2000 tokens | Only for authoritative sources |
+| `search` (5 results) | ~500 tokens | Always first — cheap discovery |
+| `fetch` (single page) | ~1000-2000 tokens | Only for authoritative sources |
 | `context_manager add_note` | ~0 tokens (metadata op) | After every research cycle |
 | `delegate` (quick lookup subagent) | ~$0.05-0.15 | When research would bloat your context |
 | `delegate` (deep investigation) | ~$0.20-0.50 | Landscape surveys only |
@@ -254,7 +254,7 @@ architecture decision might be worth $2.00.
 
 ```typescript
 // ❌ Turn 5: Agent forgets it already researched React version
-web_search("React latest version")
+search("React latest version")
 
 // ✅ Turn 2: Agent injected findings via add_note
 // Turn 3-5: Agent sees the note in conversation — skips re-search
@@ -264,11 +264,11 @@ web_search("React latest version")
 
 ```typescript
 // ❌ Guessing URLs wastes fetches
-web_fetch("https://react.dev/blog/2025/03/15/react-19-2")  // 404
+fetch("https://react.dev/blog/2025/03/15/react-19-2")  // 404
 
 // ✅ Search discovers the real URL first
-web_search("React 19.2 release blog post")
-web_fetch(<result from search>)
+search("React 19.2 release blog post")
+fetch(<result from search>)
 ```
 
 ### Injecting raw dumps
@@ -296,16 +296,16 @@ One 2023 article suggests X, but this appears outdated."
 
 ```typescript
 // ❌ 7 searches on the same topic, each slightly rephrased
-web_search("React 19 new features")
-web_search("React 19 what changed")
-web_search("React 19 release notes changes")
-web_search("React 19 difference from 18")
+search("React 19 new features")
+search("React 19 what changed")
+search("React 19 release notes changes")
+search("React 19 difference from 18")
 // ...
 
 // ✅ 1-2 broad searches, then targeted fetches
-web_search("React 19 release notes breaking changes")
-web_fetch(<react.dev blog>)
-web_fetch(<GitHub releases>)
+search("React 19 release notes breaking changes")
+fetch(<react.dev blog>)
+fetch(<GitHub releases>)
 // Done. Inject findings.
 ```
 
@@ -314,7 +314,7 @@ web_fetch(<GitHub releases>)
 ```typescript
 // ❌ User asks for a quick null-check fix, agent starts web searching
 User: "fix the null deref in auth.ts line 42"
-Agent: web_search("TypeScript null check best practices") // NO
+Agent: search("TypeScript null check best practices") // NO
 
 // ✅ Research mode is for analysis/discussion phases, not tactical edits
 // The agent already knows how to fix a null deref — just fix it.
@@ -325,8 +325,8 @@ Agent: web_search("TypeScript null check best practices") // NO
 ```
 1. TRIGGER    — User asks for current data OR agent realizes knowledge is stale
 2. CLASSIFY   — Quick lookup? Deep investigation? Landscape survey?
-3. SEARCH     — web_search with 5-8 results for broad discovery
-4. FETCH      — web_fetch 1-2 authoritative results for detail (parallelize if >1)
+3. SEARCH     — search with 5-8 results for broad discovery
+4. FETCH      — fetch 1-2 authoritative results for detail (parallelize if >1)
 5. VALIDATE   — Cross-reference: 2+ sources agree? Flag single-source claims
 6. INJECT     — context_manager add_note with structured findings
 7. CITE       — In your response, cite sources for every factual claim

package/skills/research-web/SKILL.save.md

@@ -8,7 +8,7 @@ Conducts current-data web research with discipline: when to search, how to cross
 2. Two-source minimum: single-source is tentative, two agreeing is signal.
 3. Inject, don't repeat — use context_manager add_note after research.
 4. Respect the stop rule: 2-3 searches + 1-2 fetches per topic.
-5. Match tool to task: web_search for discovery, web_fetch for detail.
+5. Match tool to task: search/fetch for discovery, search/fetch for detail.
 
 ## Workflow