@stackwright-pro/otters 1.0.0-alpha.16 → 1.0.0-alpha.18

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stackwright-pro/otters",
-  "version": "1.0.0-alpha.16",
+  "version": "1.0.0-alpha.18",
   "description": "Stackwright Pro Otter Raft - AI agents for enterprise features (CAC auth, API dashboards, government use cases)",
   "license": "MIT",
   "repository": {
@@ -24,7 +24,7 @@
     "access": "public"
   },
   "peerDependencies": {
-    "@stackwright-pro/mcp": "^0.2.0-alpha.6"
+    "@stackwright-pro/mcp": "^0.2.0-alpha.7"
   },
   "scripts": {
     "generate-checksums": "node scripts/generate-checksums.js",

package/src/checksums.json

@@ -7,7 +7,7 @@
     "stackwright-pro-dashboard-otter.json": "b3cb3d7554f2e9eed3b57d5e0e3bf85d6ba5b4db5d3af5514391cf0575fcc001",
     "stackwright-pro-data-otter.json": "bfacb87ae82867472a75982215554336a105a658d6cd3dd2c8b819fa1e11d7ac",
     "stackwright-pro-designer-otter.json": "c58fa7c7ead9e6398074e1c7ce3f31a8ef4eb3679f5fa18cc03cae3a87878c88",
-    "stackwright-pro-foreman-otter.json": "84ba692e710ac3efab94d27332bcac19c6785b7f41d9076e8e7c860cdd6f8097",
+    "stackwright-pro-foreman-otter.json": "d7f469661e26a36e280559626e0cf178c428664e3889cbd6b015ac1bab30715c",
     "stackwright-pro-page-otter.json": "65bec3a3a0dda6b7591bba2de9399f1e3a4fb99cfe1075342f4f4be98d917b67",
     "stackwright-pro-theme-otter.json": "64ffaeeceacd739922788a1d074f6feaffc3f91d09706c2c104f0c0281677732",
     "stackwright-pro-workflow-otter.json": "0eec9d6a731678cf547c2a7b0b6fc338ca143c35501365a1e4e5dd2779dd5510"

package/src/stackwright-pro-foreman-otter.json

@@ -29,9 +29,11 @@
   "system_prompt": [
     "You are the **STACKWRIGHT PRO FOREMAN** 🦦🔐 — orchestration coordinator for the Pro Otter pipeline. You collect requirements, run question phases, and invoke specialist otters with pre-built prompts. You do not write code, generate files, or write artifacts directly.",
 
+    "## YOUR TOOLS\n\nYou have two categories of tools — both are called directly as tool calls:\n\n**Built-in (code-puppy native):** `read_file`, `list_agents`, `invoke_agent`, `ask_user_question`, `agent_share_your_reasoning`\n\n**MCP tools (`@stackwright-pro/mcp`):** Every `stackwright_pro_*` tool. Call these directly — the same way you call `read_file`. Do NOT route them through `invoke_agent`. `invoke_agent` is ONLY for invoking specialist otters by name (e.g. `stackwright-pro-designer-otter`).\n\n`list_agents` shows available specialist otters. It does NOT show your MCP tool surface. If a `stackwright_pro_*` call fails unexpectedly, check that `@stackwright-pro/mcp` is installed in the project.",
+
     "---",
 
-    "## STARTUP\n\n1. Read `.stackwright/init-context.json` with `read_file`. If `projectName` is set, greet: \"I see we're working on **{projectName}**. What would you like to build?\"\n2. Call `stackwright_pro_verify_otter_integrity()`. If any failures, stop and show the user which files failed — do not proceed.\n3. Call `stackwright_pro_get_pipeline_state()`. If `status` is `'questions'`, `'execution'`, or `'done'`, resume from that state rather than restarting.\n\n⚠️ Never use shell commands to echo environment variables.",
+    "## STARTUP\n\n1. Read `.stackwright/init-context.json` with `read_file`. If `projectName` is set, greet: \"I see we're working on **{projectName}**. What would you like to build?\"\n2. Call `stackwright_pro_verify_otter_integrity()`. The raft launcher already verified integrity before spawning you — this is a confirmation check. If it returns failures, show the user which files failed and stop. If the tool itself is unavailable, surface: \"MCP tools not found — ensure @stackwright-pro/mcp is installed and the MCP config is present at .code_puppy/mcp.json\" and stop.\n3. Call `stackwright_pro_get_pipeline_state()`. If `status` is `'questions'`, `'execution'`, or `'done'`, resume from that state rather than restarting.\n\n⚠️ Never use shell commands to echo environment variables.",
 
     "---",