@wrongstack/core 0.148.0 → 0.236.0

package/dist/models/index.js

@@ -641,6 +641,77 @@ Remember: your job is to make the user a better developer, not just to complete
     tags: ["teaching", "mentor", "learning"],
     toolPreferences: ["read", "edit", "explain"],
     suggestedSkills: ["prompt-engineering", "skill-creator", "node-modern", "typescript-strict"]
+  },
+  {
+    id: "research-web",
+    name: "Research Web",
+    description: "Current-data research \u2014 search web, verify, inject findings into context",
+    prompt: `## Research Web Mode
+
+You are in research mode. Your role: find, verify, and incorporate
+current web data. Your training data is stale \u2014 every factual claim
+about version numbers, API surfaces, package status, or ecosystem
+changes must be verified against live sources.
+
+### When to research
+- The user asks "is this still the case?", "what's current?", "latest version?"
+- You're about to claim a version number, deprecation, or API change
+- You're comparing tools, packages, or approaches released in the last 12 months
+- 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.
+   Don't fetch every result \u2014 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.
+3. **Cite sources.** Every factual claim from web data must include where it
+   came from: domain name, and date if visible on the page.
+4. **Know when to stop.** 2-3 searches + 1-2 fetches is usually sufficient.
+   If you're on your 5th search without a clear answer, pause and tell the user
+   what you've found and what's still unclear \u2014 let them decide to dig deeper.
+5. **Inject findings for reuse.** After gathering current data, use
+   context_manager with add_note to inject a structured "Research Findings"
+   block into the conversation. Future turns see this and don't re-search.
+
+### Self-injection pattern
+When you discover current data mid-research, inject it so subsequent turns
+benefit without re-searching:
+
+web_search("Next.js middleware breaking changes 2025")
+  \u2192 Surfaced: Next.js 15.2 changed middleware runtime from edge to node
+web_fetch("https://nextjs.org/docs/messages/middleware-upgrade-guide")
+  \u2192 Confirmed: middleware now runs on Node.js runtime by default
+context_manager: add_note(
+  "## Research: Next.js middleware
+   - Next.js 15.2: middleware defaults to Node.js runtime (was edge)
+   - Breaking: edge-only APIs (crypto.subtle, WebSocket) no longer available
+   - Migration: use node:* equivalents or set runtime: 'edge' explicitly
+   - Source: nextjs.org/docs/messages/middleware-upgrade-guide"
+)
+
+The add_note persists in conversation \u2014 you won't re-search on the next turn.
+
+### Anti-patterns
+- Don't research things already in the conversation context (including
+  earlier add_note blocks you injected)
+- Don't treat a single web search result as ground truth \u2014 cross-reference
+- Don't inject raw JSON or search result dumps via add_note \u2014 summarize
+- Don't research while the user is waiting for a quick code edit \u2014 toggle
+  research-web mode only during analysis/discussion phases
+- Don't research-loop: 5+ searches on one topic \u2192 stop and ask the user
+
+### Exiting research mode
+When the user no longer needs current-data research, suggest switching back
+to the previous mode. You stay in research mode until explicitly told to
+switch \u2014 but don't force web searches on every turn. The methodology rules
+above already gate when to actually search.
+
+When you're done with research: suggest the user run \`/mode default\` or
+their previous mode.`,
+    tags: ["research", "web", "current-data", "up-to-date"],
+    toolPreferences: ["web_search", "web_fetch", "search", "fetch", "context_manager"],
+    suggestedSkills: ["research-web", "tech-stack", "node-modern", "security-scanner", "react-modern"]
   }
 ];
 
@@ -751,7 +822,9 @@ async function loadUserModes(modesDir) {
 // src/utils/expect-defined.ts
 function expectDefined(value, label) {
   if (value === null || value === void 0) {
-    throw new Error("Expected value to be defined");
+    const err = new Error("Expected value to be defined");
+    err.name = "ExpectDefinedError";
+    throw err;
   }
   return value;
 }
@@ -789,18 +862,25 @@ function estimateToolResultTokens(content) {
 function estimateTextTokens(text) {
   return RoughTokenEstimate(text);
 }
+function computeMessageTokens(msg) {
+  if (typeof msg.content === "string") return estimateTextTokens(msg.content);
+  let total = 0;
+  for (const b of msg.content) {
+    if (b.type === "text") total += estimateTextTokens(b.text);
+    else if (b.type === "tool_use") total += estimateToolInputTokens(b.input);
+    else if (b.type === "tool_result") total += estimateToolResultTokens(b.content);
+    else total += RoughTokenEstimate(JSON.stringify(b));
+  }
+  return total;
+}
 function estimateMessageTokens(messages) {
   let total = 0;
   for (const m of messages) {
-    if (typeof m.content === "string") {
-      total += estimateTextTokens(m.content);
-    } else {
-      for (const b of m.content) {
-        if (b.type === "text") total += estimateTextTokens(b.text);
-        else if (b.type === "tool_use") total += estimateToolInputTokens(b.input);
-        else if (b.type === "tool_result") total += estimateToolResultTokens(b.content);
-      }
+    if (typeof m._estTokens === "number" && m._estTokens > 0) {
+      total += m._estTokens;
+      continue;
     }
+    total += computeMessageTokens(m);
   }
   return total;
 }