debugger crew

[system]
You are Repo Scout. Use terminal_exec to run quick read-only commands (git status, ls, npm run --silent, rg) and summarize what you found. Do not propose fixes — just describe the workspace state. JSON only.
Operating procedures (apply where relevant; do not state them back verbatim):
- [tool-safety-checklist] Tool-safety checklist
    No real external action without an ApprovalItem (no auto-send, no auto-submit).
    • No live trading — all execution is simulated and clearly marked.
    • No outbound emails, messages, or form submissions from inside an agent.
    • Log every tool call (input + output + status) for audit.
    • Include source/data provenance in any output that depends on a tool result.
- [hermes:web-research-analyst] Web research analyst
    When asked to research: cite sources, prefer primary documents, separate facts from inference, and end with 'Open questions'.
Approved memory (operator-sanctioned context — apply where relevant; keep your output focused):
- [demo] Operator timezone: Europe/London (UK) [operator, timezone] (hermes): Schedules and follow-ups should default to UK time unless the user specifies otherwise.
- [demo] Bug Hunter — concise bullets in reports [report, concise, brief, bullets]: QA reports should be brief: bullets, not prose. One line per issue, severity prefix, link to step.
- Approved paper-trade pattern [paper-trade, pattern, approved]: Operator approved a simulated trade with explicit invalidation and stop. Keep this pattern: thesis → invalidation → stop → target → confidence.
- Approved paper-trade structure [paper-trade, structure]: Operator accepted a simulated trade with explicit invalidation, stop, target, and confidence. Keep this exact shape.
- [demo] Use verbose, detailed bug reports [report, detailed, verbose]: Write detailed multi-paragraph bug reports with full reproduction context — long form is preferred over bullets.

You may call these tools:
- terminal_exec: Run a single shell command server-side, scoped to the project workspace. Read-only diagnostics are allowed unapproved (git status, npm run lint, npx tsc --noEmit, rg, ls, etc.). Risky commands require an approval. Destructive intents are hard-blocked. Outputs are truncated; timeouts apply.

Tool-call protocol — respond with one of:
  { "toolCalls": [ { "toolName": "<name>", "input": { ... } } ] }
  { "final": { ... your structured output ... } }
Tool calls are executed server-side; their results will be fed back to you for the final response.

[user]
Mission: Run typecheck and lint diagnostics on the workspace, then report the top errors with concrete fix recommendations.

Call terminal_exec on a few read-only commands first (e.g. { "command": "git status", "reason": "current working tree state" } and { "command": "git log -n 5 --oneline", "reason": "recent commits" }), then return JSON: { "summary": "...", "findings": [...], "actions": [...], "confidence": 0.0-1.0 }

{
  "summary": "Workspace appears to be in a minimal or empty state. Git is not installed, and package.json is missing or incomplete (no 'lint' script found). TypeScript compilation failed due to npm path issues. No source files were found in the workspace.",
  "findings": [
    "Git not installed - cannot check version control status",
    "No package.json found or incomplete - 'npm run lint' failed",
    "TypeScript compilation failed - npm path errors",
    "No source files detected in workspace"
  ],
  "actions": [
    "Install git and configure properly",
    "Create or fix package.json with valid scripts",
    "Resolve npm path permissions and install dependencies",
    "Add source files to the workspace"
  ],
  "confidence": 0.8
}

[system]
You are Build Runner. Run typecheck and lint with terminal_exec. Capture exit codes, error counts, and short error excerpts. JSON only.
Operating procedures (apply where relevant; do not state them back verbatim):
- [tool-safety-checklist] Tool-safety checklist
    No real external action without an ApprovalItem (no auto-send, no auto-submit).
    • No live trading — all execution is simulated and clearly marked.
    • No outbound emails, messages, or form submissions from inside an agent.
    • Log every tool call (input + output + status) for audit.
    • Include source/data provenance in any output that depends on a tool result.
- [hermes:web-research-analyst] Web research analyst
    When asked to research: cite sources, prefer primary documents, separate facts from inference, and end with 'Open questions'.
Approved memory (operator-sanctioned context — apply where relevant; keep your output focused):
- [demo] Operator timezone: Europe/London (UK) [operator, timezone] (hermes): Schedules and follow-ups should default to UK time unless the user specifies otherwise.
- [demo] Bug Hunter — concise bullets in reports [report, concise, brief, bullets]: QA reports should be brief: bullets, not prose. One line per issue, severity prefix, link to step.
- Approved paper-trade pattern [paper-trade, pattern, approved]: Operator approved a simulated trade with explicit invalidation and stop. Keep this pattern: thesis → invalidation → stop → target → confidence.
- Approved paper-trade structure [paper-trade, structure]: Operator accepted a simulated trade with explicit invalidation, stop, target, and confidence. Keep this exact shape.
- [demo] Use verbose, detailed bug reports [report, detailed, verbose]: Write detailed multi-paragraph bug reports with full reproduction context — long form is preferred over bullets.

You may call these tools:
- terminal_exec: Run a single shell command server-side, scoped to the project workspace. Read-only diagnostics are allowed unapproved (git status, npm run lint, npx tsc --noEmit, rg, ls, etc.). Risky commands require an approval. Destructive intents are hard-blocked. Outputs are truncated; timeouts apply.

Tool-call protocol — respond with one of:
  { "toolCalls": [ { "toolName": "<name>", "input": { ... } } ] }
  { "final": { ... your structured output ... } }
Tool calls are executed server-side; their results will be fed back to you for the final response.

[user]
Mission: Run typecheck and lint diagnostics on the workspace, then report the top errors with concrete fix recommendations.
Repo scout summary: {
  "summary": "Workspace appears to be in a minimal or empty state. Git is not installed, and package.json is missing or incomplete (no 'lint' script found). TypeScript compilation failed due to npm path issues. No source files were found in the workspace.",
  "findings": [
    "Git not installed - cannot check version control status",
    "No package.json found or incomplete - 'npm run lint' failed",
    "TypeScript compilation failed - npm path errors",
    "No source files detected in workspace"
  ],
  "actions": [
    "Install git and configure properly",
    "Create or fix package.json with valid scripts",
    "Resolve npm path permissions and install dependencies",
    "Add source files to the workspace"
  ],
  "confidence": 0.8
}

Call terminal_exec for { "command": "npx tsc --noEmit", "reason": "typecheck" } and { "command": "npx next lint", "reason": "lint" }. Then return JSON in shape { "summary": "...", "findings": [...], "actions": [...], "confidence": 0.0-1.0 }.

{
  "summary": "Workspace diagnostics failed due to missing Node.js toolchain. Typecheck (npx tsc --noEmit) failed with npm path errors (ENOENT: no such file or directory, mkdir '/home/sbx_user1051'), and lint (npx next lint) failed with 'command not found'.",
  "findings": [
    "TypeScript typecheck failed: npm error ENOENT, unable to create directory '/home/sbx_user1051'",
    "Lint check failed: 'next' command not found"
  ],
  "actions": [
    "Install Node.js and npm to resolve toolchain issues",
    "Ensure proper permissions and paths for npm to create directories",
    "Install Next.js dependencies if applicable"
  ],
  "confidence": 0.7
}

[system]
You are Error Analyst. From the Build Runner output, group errors by likely root cause and name the files involved. Use terminal_exec sparingly to confirm a hypothesis (e.g. cat a small file). Do not propose fixes yet. JSON only.
Operating procedures (apply where relevant; do not state them back verbatim):
- [tool-safety-checklist] Tool-safety checklist
    No real external action without an ApprovalItem (no auto-send, no auto-submit).
    • No live trading — all execution is simulated and clearly marked.
    • No outbound emails, messages, or form submissions from inside an agent.
    • Log every tool call (input + output + status) for audit.
    • Include source/data provenance in any output that depends on a tool result.
- [hermes:web-research-analyst] Web research analyst
    When asked to research: cite sources, prefer primary documents, separate facts from inference, and end with 'Open questions'.
Approved memory (operator-sanctioned context — apply where relevant; keep your output focused):
- [demo] Operator timezone: Europe/London (UK) [operator, timezone] (hermes): Schedules and follow-ups should default to UK time unless the user specifies otherwise.
- [demo] Bug Hunter — concise bullets in reports [report, concise, brief, bullets]: QA reports should be brief: bullets, not prose. One line per issue, severity prefix, link to step.
- Approved paper-trade pattern [paper-trade, pattern, approved]: Operator approved a simulated trade with explicit invalidation and stop. Keep this pattern: thesis → invalidation → stop → target → confidence.
- Approved paper-trade structure [paper-trade, structure]: Operator accepted a simulated trade with explicit invalidation, stop, target, and confidence. Keep this exact shape.
- [demo] Use verbose, detailed bug reports [report, detailed, verbose]: Write detailed multi-paragraph bug reports with full reproduction context — long form is preferred over bullets.

You may call these tools:
- terminal_exec: Run a single shell command server-side, scoped to the project workspace. Read-only diagnostics are allowed unapproved (git status, npm run lint, npx tsc --noEmit, rg, ls, etc.). Risky commands require an approval. Destructive intents are hard-blocked. Outputs are truncated; timeouts apply.

Tool-call protocol — respond with one of:
  { "toolCalls": [ { "toolName": "<name>", "input": { ... } } ] }
  { "final": { ... your structured output ... } }
Tool calls are executed server-side; their results will be fed back to you for the final response.

[user]
Mission: Run typecheck and lint diagnostics on the workspace, then report the top errors with concrete fix recommendations.
Repo scout: {
  "summary": "Workspace appears to be in a minimal or empty state. Git is not installed, and package.json is missing or incomplete (no 'lint' script found). TypeScript compilation failed due to npm path issues. No source files were found in the workspace.",
  "findings": [
    "Git not installed - cannot check version control status",
    "No package.json found or incomplete - 'npm run lint' failed",
    "TypeScript compilation failed - npm path errors",
    "No source files detected in workspace"
  ],
  "actions": [
    "Install git and configure properly",
    "Create or fix package.json with valid scripts",
    "Resolve npm path permissions and install dependencies",
    "Add source files to the workspace"
  ],
  "confidence": 0.8
}
Build runner: {
  "summary": "Workspace diagnostics failed due to missing Node.js toolchain. Typecheck (npx tsc --noEmit) failed with npm path errors (ENOENT: no such file or directory, mkdir '/home/sbx_user1051'), and lint (npx next lint) failed with 'command not found'.",
  "findings": [
    "TypeScript typecheck failed: npm error ENOENT, unable to create directory '/home/sbx_user1051'",
    "Lint check failed: 'next' command not found"
  ],
  "actions": [
    "Install Node.js and npm to resolve toolchain issues",
    "Ensure proper permissions and paths for npm to create directories",
    "Install Next.js dependencies if applicable"
  ],
  "confidence": 0.7
}

If you need to peek at a small file, call terminal_exec { "command": "cat <path>", "reason": "..." } once. Otherwise return JSON in shape { "summary": "...", "findings": [...], "actions": [...], "confidence": 0.0-1.0 }.

{
  "summary": "Workspace diagnostics indicate fundamental environment issues preventing typecheck and lint operations. The core problems appear to be missing or improperly configured Node.js toolchain components.",
  "findings": [
    "TypeScript typecheck failed due to npm path errors (ENOENT: no such file or directory, mkdir '/home/sbx_user1051')",
    "Lint check failed with 'next' command not found error",
    "Missing or incomplete package.json configuration for lint script",
    "Git not installed, preventing version control operations"
  ],
  "actions": [
    "Install Node.js and npm to resolve toolchain issues",
    "Ensure proper permissions and paths for npm to create directories",
    "Install Next.js dependencies if applicable",
    "Install git and configure properly",
    "Create or fix package.json with valid scripts"
  ],
  "confidence": 0.7
}

[system]
You are Fix Planner. For each root cause from Error Analyst, write a concrete recommended fix: file path, the change, and the expected impact. Do NOT edit files. Output is a plan. JSON only.
Operating procedures (apply where relevant; do not state them back verbatim):
- [tool-safety-checklist] Tool-safety checklist
    No real external action without an ApprovalItem (no auto-send, no auto-submit).
    • No live trading — all execution is simulated and clearly marked.
    • No outbound emails, messages, or form submissions from inside an agent.
    • Log every tool call (input + output + status) for audit.
    • Include source/data provenance in any output that depends on a tool result.
- [hermes:web-research-analyst] Web research analyst
    When asked to research: cite sources, prefer primary documents, separate facts from inference, and end with 'Open questions'.
Approved memory (operator-sanctioned context — apply where relevant; keep your output focused):
- [demo] Operator timezone: Europe/London (UK) [operator, timezone] (hermes): Schedules and follow-ups should default to UK time unless the user specifies otherwise.
- [demo] Bug Hunter — concise bullets in reports [report, concise, brief, bullets]: QA reports should be brief: bullets, not prose. One line per issue, severity prefix, link to step.
- Approved paper-trade pattern [paper-trade, pattern, approved]: Operator approved a simulated trade with explicit invalidation and stop. Keep this pattern: thesis → invalidation → stop → target → confidence.
- Approved paper-trade structure [paper-trade, structure]: Operator accepted a simulated trade with explicit invalidation, stop, target, and confidence. Keep this exact shape.
- [demo] Use verbose, detailed bug reports [report, detailed, verbose]: Write detailed multi-paragraph bug reports with full reproduction context — long form is preferred over bullets.

[user]
Mission: Run typecheck and lint diagnostics on the workspace, then report the top errors with concrete fix recommendations.
Root causes: {
  "summary": "Workspace diagnostics indicate fundamental environment issues preventing typecheck and lint operations. The core problems appear to be missing or improperly configured Node.js toolchain components.",
  "findings": [
    "TypeScript typecheck failed due to npm path errors (ENOENT: no such file or directory, mkdir '/home/sbx_user1051')",
    "Lint check failed with 'next' command not found error",
    "Missing or incomplete package.json configuration for lint script",
    "Git not installed, preventing version control operations"
  ],
  "actions": [
    "Install Node.js and npm to resolve toolchain issues",
    "Ensure proper permissions and paths for npm to create directories",
    "Install Next.js dependencies if applicable",
    "Install git and configure properly",
    "Create or fix package.json with valid scripts"
  ],
  "confidence": 0.7
}

Return JSON: { "summary": "<one paragraph plan summary>", "findings": ["<file: change rationale>"], "actions": ["<file path + concrete change>"], "confidence": 0.0-1.0 }

{
  "summary": "The workspace requires fundamental Node.js toolchain setup to enable typecheck and lint operations. The plan addresses missing npm paths, Next.js dependencies, git installation, and package.json configuration.",
  "findings": [
    "Install Node.js and npm to resolve toolchain issues",
    "Ensure proper permissions and paths for npm to create directories",
    "Install Next.js dependencies if applicable",
    "Install git and configure properly",
    "Create or fix package.json with valid scripts"
  ],
  "actions": [
    "Install Node.js and npm: Follow official installation instructions for your OS to set up the Node.js runtime environment.",
    "Fix npm directory permissions: Run npm config set prefix ~/npm to configure npm to use a user-writable directory, then ensure ~/.npm/bin is in your PATH.",
    "Install Next.js: If using Next.js, run npm install next@latest react@latest react-dom@latest to add required dependencies.",
    "Install git: Use your system package manager (e.g., sudo apt install git on Debian/Ubuntu) to install git for version control.",
    "Fix package.json: Create or modify package.json to include a valid \"scripts\" section with your lint command, e.g.: {\"scripts\": {\"lint\": \"next lint\"}}"
  ],
  "confidence": 0.9
}

[system]
You are Report Agent. Compose a 4-6 sentence executive summary of the diagnosis and the fix plan. JSON only.
Operating procedures (apply where relevant; do not state them back verbatim):
- [tool-safety-checklist] Tool-safety checklist
    No real external action without an ApprovalItem (no auto-send, no auto-submit).
    • No live trading — all execution is simulated and clearly marked.
    • No outbound emails, messages, or form submissions from inside an agent.
    • Log every tool call (input + output + status) for audit.
    • Include source/data provenance in any output that depends on a tool result.
- [hermes:web-research-analyst] Web research analyst
    When asked to research: cite sources, prefer primary documents, separate facts from inference, and end with 'Open questions'.
Approved memory (operator-sanctioned context — apply where relevant; keep your output focused):
- [demo] Operator timezone: Europe/London (UK) [operator, timezone] (hermes): Schedules and follow-ups should default to UK time unless the user specifies otherwise.
- [demo] Bug Hunter — concise bullets in reports [report, concise, brief, bullets]: QA reports should be brief: bullets, not prose. One line per issue, severity prefix, link to step.
- Approved paper-trade pattern [paper-trade, pattern, approved]: Operator approved a simulated trade with explicit invalidation and stop. Keep this pattern: thesis → invalidation → stop → target → confidence.
- Approved paper-trade structure [paper-trade, structure]: Operator accepted a simulated trade with explicit invalidation, stop, target, and confidence. Keep this exact shape.
- [demo] Use verbose, detailed bug reports [report, detailed, verbose]: Write detailed multi-paragraph bug reports with full reproduction context — long form is preferred over bullets.

[user]
Mission: Run typecheck and lint diagnostics on the workspace, then report the top errors with concrete fix recommendations.
Full context: {
  "repo-scout": {
    "summary": "Workspace appears to be in a minimal or empty state. Git is not installed, and package.json is missing or incomplete (no 'lint' script found). TypeScript compilation failed due to npm path issues. No source files were found in the workspace.",
    "findings": [
      "Git not installed - cannot check version control status",
      "No package.json found or incomplete - 'npm run lint' failed",
      "TypeScript compilation failed - npm path errors",
      "No source files detected in workspace"
    ],
    "actions": [
      "Install git and configure properly",
      "Create or fix package.json with valid scripts",
      "Resolve npm path permissions and install dependencies",
      "Add source files to the workspace"
    ],
    "confidence": 0.8
  },
  "build-runner": {
    "summary": "Workspace diagnostics failed due to missing Node.js toolchain. Typecheck (npx tsc --noEmit) failed with npm path errors (ENOENT: no such file or directory, mkdir '/home/sbx_user1051'), and lint (npx next lint) failed with 'command not found'.",
    "findings": [
      "TypeScript typecheck failed: npm error ENOENT, unable to create directory '/home/sbx_user1051'",
      "Lint check failed: 'next' command not found"
    ],
    "actions": [
      "Install Node.js and npm to resolve toolchain issues",
      "Ensure proper permissions and paths for npm to create directories",
      "Install Next.js dependencies if applicable"
    ],
    "confidence": 0.7
  },
  "error-analyst": {
    "summary": "Workspace diagnostics indicate fundamental environment issues preventing typecheck and lint operations. The core problems appear to be missing or improperly configured Node.js toolchain components.",
    "findings": [
      "TypeScript typecheck failed due to npm path errors (ENOENT: no such file or directory, mkdir '/home/sbx_user1051')",
      "Lint check failed with 'next' command not found error",
      "Missing or incomplete package.json configuration for lint script",
      "Git not installed, preventing version control operations"
    ],
    "actions": [
      "Install Node.js and npm to resolve toolchain issues",
      "Ensure proper permissions and paths for npm to create directories",
      "Install Next.js dependencies if applicable",
      "Install git and configure properly",
      "Create or fix package.json with valid scripts"
    ],
    "confidence": 0.7
  },
  "fix-planner": {
    "summary": "The workspace requires fundamental Node.js toolchain setup to enable typecheck and lint operations. The plan addresses missing npm paths, Next.js dependencies, git installation, and package.json configuration.",
    "findings": [
      "Install Node.js and npm to resolve toolchain issues",
      "Ensure proper permissions and paths for npm to create directories",
      "Install Next.js dependencies if applicable",
      "Install git and configure properly",
      "Create or fix package.json with valid scripts"
    ],
    "actions": [
      "Install Node.js and npm: Follow official installation instructions for your OS to set up the Node.js runtime environment.",
      "Fix npm directory permissions: Run npm config set prefix ~/npm to configure npm to use a user-writable directory, then ensure ~/.npm/bin is in your PATH.",
      "Install Next.js: If using Next.js, run npm install next@latest react@latest react-dom@latest to add required dependencies.",
      "Install git: Use your system package manager (e.g., sudo apt install git on Debian/Ubuntu) to install git for version control.",
      "Fix package.json: Create or modify package.json to include a valid \"scripts\" section with your lint command, e.g.: {\"scripts\": {\"lint\": \"next lint\"}}"
    ],
    "confidence": 0.9
  }
}

Return JSON: { "summary": "<exec summary>", "findings": ["<top headline>"], "actions": ["<call-to-action for the operator>"], "confidence": 0.0-1.0 }

{
  "summary": "Workspace diagnostics indicate fundamental environment issues preventing typecheck and lint operations. The core problems appear to be missing or improperly configured Node.js toolchain components.",
  "findings": [
    "TypeScript typecheck failed due to npm path errors (ENOENT: no such file or directory, mkdir '/home/sbx_user1051')",
    "Lint check failed with 'next' command not found error",
    "Missing or incomplete package.json configuration for lint script",
    "Git not installed, preventing version control operations"
  ],
  "actions": [
    "Install Node.js and npm to resolve toolchain issues",
    "Ensure proper permissions and paths for npm to create directories",
    "Install Next.js dependencies if applicable",
    "Install git and configure properly",
    "Create or fix package.json with valid scripts"
  ],
  "confidence": 0.7
}