@hailer/mcp 1.1.12 → 1.1.13

package/.opencode/commands/handoff.md

@@ -1,137 +0,0 @@
----
-description: Create or update session handoff for continuity
-argument-hint: [optional summary]
----
-# Session Handoff
-
-Context is getting full or session is ending. Create/update handoff for next session.
-
-## Step 0: Capture Learnings (Auto-Learn)
-
-Before creating handoff, scan for learnings from this session.
-
-**Run the learn-auto logic:**
-1. Scan conversation for: error→fix patterns, user corrections, explicit insights, agent failures
-2. Present any findings to user for confirmation
-3. Write confirmed learnings to inbox
-
-This ensures valuable insights aren't lost when session ends.
-
-If no learnings found or user skips, continue to Step 1.
-
----
-
-## Step 1: Gather Current State
-
-Collect:
-- What was worked on this session
-- Current state of in-progress work
-- Any blockers or issues found
-- Uncommitted changes (`git status`)
-- Next steps
-
-## Step 2: Graduate Auto Memory
-
-Check if the project has auto memory entries to graduate.
-
-**Find the memory file:**
-1. Get project root from working directory
-2. Transform path: replace `/` with `-` (e.g., `/Users/timoahonen/my-project` → `-Users-timoahonen-my-project`)
-3. Memory path: `~/.claude/projects/<transformed-path>/memory/MEMORY.md`
-
-**If MEMORY.md exists and has content:**
-1. Read it
-2. For each entry, decide:
-   - **Project-specific gotcha** (field ID quirks, workflow-specific behavior) → Move to SESSION-HANDOFF.md "Context to Preserve"
-   - **Reusable pattern** (SDK behavior, API gotchas, agent tips) → Capture via `/learn-hub` or note for inbox
-   - **Already in a skill or CLAUDE.md** → Remove (it graduated in a previous session)
-   - **Stale or wrong** → Remove
-3. Remove graduated/stale entries from MEMORY.md
-4. Keep only entries that are still being validated (discovered this session, not yet confirmed)
-
-**Goal:** MEMORY.md is a scratch buffer, not permanent storage. At handoff, everything graduates out.
-
-## Step 3: Check for Active Tasks
-
-Run `TaskList`. If tasks exist:
-- Export pending/in_progress tasks to handoff
-- Summarize completed tasks in "What Was Done"
-
-## Step 4: Update Documentation (if applicable)
-
-**Did this session complete any features?**
-
-If YES:
-- Update the PRD file (docs/prd-*.md): change Status to "Complete", check off completed items
-- Update DEVELOPMENT.md Roadmap: mark feature as Complete
-- Update "Current Status"
-- Add any technical decisions
-- Note new issues discovered
-
-## Step 5: Create/Update SESSION-HANDOFF.md
-
-If file exists → UPDATE it (remove stale items, keep relevant context)
-If not exists → CREATE it
-
-```markdown
-# Session Handoff
-
-**Last Updated:** YYYY-MM-DD HH:MM
-
-## What Was Done
-- [Completed items with context]
-
-## Current Work
-- [What's actively being worked on]
-- [State of in-progress features]
-
-## Pending Tasks
-_From TaskList - will be recreated next session_
-- [ ] Task description
-- [ ] Task description
-
-## Blockers / Issues
-- [Problems encountered]
-- [Things that need investigation]
-
-## Next Steps
-1. [First thing to do when resuming]
-2. [Second thing]
-3. [Third thing]
-
-## Key Decisions
-- [Decision]: [Why]
-
-## Files Modified
-- `path/to/file` - [what changed]
-
-## Context to Preserve
-- [Important notes that shouldn't be lost]
-- [Gotchas discovered]
-```
-
-## Step 6: Save Progress
-
-If git is initialized and there are changes:
-```
-/save "Session handoff: [brief summary]"
-```
-
-## Step 7: Report
-
-Tell user:
-```
-Session handoff complete:
-- SESSION-HANDOFF.md updated
-- DEVELOPMENT.md updated (if features completed)
-- [X] files have uncommitted changes
-
-To continue: Start new session - handoff will be read automatically.
-```
-
-## Notes
-
-- **UPDATE, don't delete** - SESSION-HANDOFF.md accumulates context
-- Remove items that are no longer relevant
-- Keep decisions and gotchas even after tasks complete
-- Next session reads handoff, then updates it (removes completed items)

package/.opencode/commands/health.md

@@ -1,49 +0,0 @@
----
-description: Run project health check and config audit
-allowed-tools: Task, Bash, Read
----
-# Project Health Check
-
-Run a quick audit of the current project configuration.
-
-**Check the following:**
-
-1. **Workspace sync status**
-   - Run `npm run pull` to check connectivity
-   - Compare local workspace/ timestamps with server
-
-2. **CLAUDE.md accuracy**
-   - Does CLAUDE.md exist?
-   - Are listed agents present in .claude/agents/?
-   - Are referenced skills present in .claude/skills/?
-
-3. **Hooks integrity**
-   - Are all hooks in settings.json present in .claude/hooks/?
-   - Do hook files have execute permissions?
-
-4. **Dependencies**
-   - Run `npm outdated` to check for updates
-   - Check if node_modules exists
-
-5. **Git status**
-   - Any uncommitted changes?
-   - Is branch up to date with remote?
-
-**Output format:**
-
-```
-## Health Check - [Project Name]
-
-[x] Workspace synced (last pull: X minutes ago)
-[x] CLAUDE.md valid (15 agents, 10 skills)
-[x] Hooks intact (8/8 present)
-[ ] Dependencies outdated (3 packages)
-[x] Git clean
-
-### Issues Found
-- @hailer/sdk outdated: 0.8.3 → 0.8.5
-- Missing hook: xyz.cjs referenced but not found
-
-### Recommendations
-- Run `npm update @hailer/sdk`
-```

package/.opencode/commands/help-agents.md

@@ -1,151 +0,0 @@
----
-description: Agent usage help for Hailer MCP
----
-
-# Agents Help
-
-Display agent usage instructions to the user.
-
-## Output
-
-```
-╭─────────────────────────────────────────╮
-│          HAILER MCP - AGENTS            │
-╰─────────────────────────────────────────╯
-
-Agents are AI specialists that handle specific tasks. The orchestrator
-(Claude) delegates work to them based on the task type.
-
-HOW IT WORKS:
-
-  1. You ask Claude to do something
-  2. Claude identifies the right agent
-  3. Claude spawns the agent with your task
-  4. Agent does the work, returns JSON result
-  5. Claude interprets result and reports back
-
-─────────────────────────────────────────────────────────────────────────
-
-AGENT RELATIONSHIPS (who calls who):
-
-  Kenji → Dmitri       Kenji gets IDs, Dmitri creates/updates
-  Kenji → Helga        Kenji gets structure, Helga modifies config
-  Kenji → Alejandro    Kenji gets field IDs, Alejandro creates functions
-  Kenji → Viktor       Kenji gets schema, Viktor creates insights
-  Kenji → Giuseppe     Kenji gets data structure, Giuseppe builds app
-  Marco → Giuseppe     Marco validates mockup, Giuseppe builds production
-  Ada ← (any failure)  Ada creates skills from repeated failures
-
-  Common chains:
-  • Add field:     Kenji → Helga → (push) → Kenji (verify)
-  • Create app:    Kenji → Viktor → Giuseppe → Tanya
-  • Activity CRUD: Kenji → Dmitri
-
-─────────────────────────────────────────────────────────────────────────
-
-AGENT TOOL ACCESS:
-
-  MCP Tools Only (restricted):
-    Kenji     - list_workflows, count_activities, list_activities
-    Dmitri    - create_activity, update_activity
-    Permissions - list_apps, add/remove_app_member, search_users
-    Yevgeni   - discussion tools (list, fetch, post, invite)
-
-  Code Tools (Bash, Read, Write, Edit):
-    Giuseppe  - App building (+scaffold_hailer_app)
-    Gunther   - MCP tool building
-    Helga     - Workflow config
-    Igor      - Activity movers
-    Ivan      - Monolith automations
-    Marco     - Mockups
-    Ingrid    - Document templates
-
-  Read-Only (Read, Glob, Grep):
-    Svetlana  - Code review
-    Bjorn     - Config audit
-    Tanya     - Test runner (+ Bash for test execution)
-
-  Light Edit (Read, Edit, Glob):
-    Simple Writer - Basic edits only (haiku model, fast)
-    Code Simplifier - Simplify code for clarity (sonnet model)
-
-  Special:
-    Lars      - LSP only (code inspection)
-    Ada       - Read, Write, Edit, Glob (skill creation)
-
-─────────────────────────────────────────────────────────────────────────
-
-AGENT CATEGORIES:
-
-  Data Operations:
-    agent-kenji-data-reader    - Read workflows, fields, activities (LOCAL FIRST)
-    agent-dmitri-activity-crud - Create/update activities
-    agent-yevgeni-discussions  - Read/post discussion messages
-    agent-permissions-handler  - Manage app access
-    agent-simple-writer        - Basic code edits (ID swaps, string replacements)
-
-  Configuration:
-    agent-helga-workflow-config     - Manage workflows, fields, phases
-    agent-alejandro-function-fields - Calculated fields + name functions
-    agent-viktor-sql-insights       - SQL-like reports
-    agent-ingrid-doc-templates      - PDF/CSV document templates
-
-  Development:
-    agent-giuseppe-app-builder - Build Hailer apps (production)
-    agent-marco-mockup-builder - Build demo apps (validation)
-    agent-gunther-mcp-tools    - Build MCP tools
-    agent-igor-activity-mover  - Phase cascade microservices
-    agent-ivan-monolith        - Monolith automations
-    agent-zara-zapier          - Zapier integrations
-
-  Quality:
-    agent-svetlana-code-review - Code review (READ-ONLY)
-    agent-tanya-test-runner    - Run tests
-    agent-lars-code-inspector  - Find bugs, dead code (LSP)
-    agent-bjorn-config-audit   - Audit configuration
-    agent-code-simplifier      - Simplify code for clarity
-
-  Meta:
-    agent-ada-skill-builder       - Create skills from failures
-    agent-builder-agent-creator   - Create new agents
-    agent-marcus-api-documenter   - Document API endpoints
-    agent-marketplace-publisher   - Publish plugins
-    agent-marketplace-reviewer    - Review plugin PRs
-
-─────────────────────────────────────────────────────────────────────────
-
-CRITICAL BOUNDARIES:
-
-  Kenji vs Dmitri:
-    Kenji = READ (schema, lists, counts)
-    Dmitri = WRITE (create, update)
-    Dmitri needs IDs from Kenji first!
-
-  Marco vs Giuseppe:
-    Marco = DEMO apps (non-functional, for validation)
-    Giuseppe = PRODUCTION apps (real data, functional)
-    Use Marco first to validate concept, then Giuseppe
-
-─────────────────────────────────────────────────────────────────────────
-
-EXAMPLE USAGE:
-
-  "Create a customer activity in the CRM workflow"
-  → Kenji (get IDs) → Dmitri (create activity)
-
-  "Build a dashboard app showing orders"
-  → Kenji (get schema) → Giuseppe (build app)
-
-  "Add a calculated total field"
-  → Kenji (get field IDs) → Alejandro (create function)
-
-  "Review my code changes"
-  → Svetlana (code review)
-
-─────────────────────────────────────────────────────────────────────────
-
-SEE ALSO:
-  /stats         - View agent usage statistics
-  /help plugins  - Install more agents
-  /help commands - All slash commands
-```

package/.opencode/commands/help-commands.md

@@ -1,32 +0,0 @@
----
-description: All slash commands for Hailer MCP
----
-
-Display this commands reference:
-
-```
-HAILER MCP - ALL COMMANDS
-
-HELP:
-  /help              Show help topics
-  /help-plugins      Plugin system guide
-  /help-agents       Agent usage guide
-  /help-commands     This reference
-  /help-tools        MCP tools reference
-  /help-faq          Common questions
-
-PLUGINS:
-  /marketplace-setup       Clone/update marketplace
-  /list-plugins            List available plugins
-  /install-plugin <name>   Install a plugin
-  /uninstall-plugin <name> Remove a plugin
-  /publish-plugin          Publish to marketplace
-
-DEVELOPMENT:
-  /tool-builder      Build a new MCP tool
-  /ws-pull           Pull workspace config from Hailer
-
-Examples:
-  /list-plugins
-  /install-plugin tanya-test-runner
-```

package/.opencode/commands/help-faq.md

@@ -1,29 +0,0 @@
----
-description: Frequently asked questions
----
-
-Display this FAQ:
-
-```
-HAILER MCP - FAQ
-
-Q: Why restart after installing a plugin?
-A: Agents load at startup. Use 'claude -c' to keep context.
-
-Q: Can I create my own agents?
-A: Yes. Add markdown to .claude/agents/
-
-Q: How to publish an agent?
-A: Use /publish-plugin. Creates auto-reviewed PR.
-
-Q: Where is config stored?
-A: Agents: .claude/agents/
-   Skills: .claude/skills/
-   Hooks:  .claude/hooks/
-   Settings: .claude/settings.json
-
-Q: How to update a plugin?
-A: /uninstall-plugin <name> then /install-plugin <name>
-
-SEE ALSO: /help-plugins, /help-agents
-```

package/.opencode/commands/help-plugins.md

@@ -1,28 +0,0 @@
----
-description: Plugin system help for Hailer MCP
----
-
-Display this plugin help:
-
-```
-HAILER MCP - PLUGIN SYSTEM
-
-COMMANDS:
-  /marketplace-setup       Clone/pull marketplace repo
-  /list-plugins            List available plugins
-  /install-plugin <name>   Install plugin to .claude/
-  /uninstall-plugin <name> Remove plugin
-  /publish-plugin          Publish to marketplace
-
-PLUGIN TYPES:
-  Agents   - AI specialists (.claude/agents/)
-  Skills   - On-demand docs (.claude/skills/)
-  Hooks    - Event scripts (.claude/hooks/)
-
-WORKFLOW:
-  1. /list-plugins
-  2. /install-plugin <name>
-  3. Restart: claude -c
-
-SEE ALSO: /help-agents, /help-faq
-```

package/.opencode/commands/help-skills.md

@@ -1,7 +0,0 @@
----
-description: Skills reference for Hailer MCP
----
-
-# Skills Reference
-
-[See content from .claude/commands/help:skills.md - displays skills reference with same formatting]

package/.opencode/commands/help-tools.md

@@ -1,40 +0,0 @@
----
-description: MCP tools reference for Hailer MCP
----
-
-Display this tools reference:
-
-```
-HAILER MCP - TOOLS REFERENCE
-
-WORKFLOW:
-  list_workflows, list_workflows_minimal, list_workflow_phases
-  get_workflow_schema, install_workflow
-
-ACTIVITY:
-  list_activities, show_activity_by_id, create_activity
-  update_activity, count_activities
-
-DISCUSSION:
-  list_my_discussions, fetch_discussion_messages
-  add_discussion_message, join_discussion, leave_discussion
-
-INSIGHT:
-  list_insights, create_insight, preview_insight
-  get_insight_data, update_insight
-
-APP:
-  list_apps, create_app, update_app
-  scaffold_hailer_app, publish_hailer_app
-
-FILE:
-  upload_files, download_file
-
-USER:
-  search_workspace_users
-
-TEMPLATE:
-  list_templates, get_template, install_template, publish_template
-
-SEE ALSO: /help-agents, /help-commands
-```

package/.opencode/commands/help.md

@@ -1,28 +0,0 @@
----
-description: Show help topics for Hailer MCP
----
-
-# Hailer MCP Help
-
-Display available help topics to the user.
-
-## Output
-
-```
-╭─────────────────────────────────────────╮
-│         HAILER MCP HELP SYSTEM          │
-╰─────────────────────────────────────────╯
-
-Available topics:
-
-  /help agents     How agents work and delegation
-  /help skills     Skills reference (patterns, templates, fixes)
-  /help commands   All slash commands
-  /help tools      MCP tools reference
-  /help faq        Common questions
-
-───────────────────────────────────────────
-Type /help <topic> for details
-```
-
-## Always show this exactly as formatted above.

package/.opencode/commands/hotfix-squad.md

@@ -1,112 +0,0 @@
----
-description: Quick bug fix with Tanya, Simple Writer, and Svetlana
-argument-hint: "bug description"
-allowed-tools: Task, Bash
----
-# Hotfix Squad
-
-Sequential pipeline with iterative loop: Reproduce bug, apply fix, verify, review. Loops back if review fails.
-
-**Agents:**
-1. **Tanya** - Test runner (create failing test, verify fix)
-2. **Simple Writer** - Code editor (apply minimal fix)
-3. **Svetlana** - Code review (security audit of the fix)
-
-**Goal:** $ARGUMENTS
-
-## Protocol
-
-### Step 1: Tanya (Reproduce Bug)
-
-Spawn Tanya to create a test that demonstrates the bug:
-
-```
-Task(subagent_type="agent-tanya-test-runner", prompt="Create a test that reproduces this bug: $ARGUMENTS.\n\nThe test should:\n- Fail with the current code (red)\n- Clearly demonstrate the bug\n- Be minimal and focused\n\nDo NOT fix the bug yet. Just create the failing test and report the failure.")
-```
-
-Wait for result. The test should be failing (RED state).
-
-### Step 2: Fix-Verify-Review Loop
-
-Track iteration count. Max **3 iterations** before escalating to user with remaining issues.
-
-**Set:** `iteration = 1`
-
-#### Step 2a: Simple Writer (Apply Fix)
-
-Spawn Simple Writer with accumulated context from all previous iterations:
-
-```
-Task(subagent_type="agent-simple-writer", prompt="Fix the bug in: $ARGUMENTS.\n\nContext:\nTanya created a failing test that reproduces the bug:\n[PASTE TANYA'S TEST CODE AND FAILURE OUTPUT]\n\n[IF iteration > 1: Include ALL accumulated feedback:\n- Tanya's latest test results (pass/fail details)\n- Svetlana's review feedback (if review was reached in previous iteration)\n- What was already tried and why it didn't fully work\nThis prevents repeating previous mistakes.]\n\nMake the MINIMAL change needed to make the test pass (GREEN state). Do not refactor or improve surrounding code.")
-```
-
-#### Step 2b: Tanya (Verify Fix)
-
-Run the test to confirm the fix works:
-
-```
-Task(subagent_type="agent-tanya-test-runner", prompt="Re-run the test for: $ARGUMENTS. Confirm it now passes with Simple Writer's fix. Also run any related tests to check for regressions.")
-```
-
-If tests FAIL:
-- If `iteration < 3`: increment iteration, go back to **Step 2a** with the test failure output
-- If `iteration >= 3`: escalate to user (see Step 3)
-
-#### Step 2c: Svetlana (Security Review)
-
-Tests passed. Spawn Svetlana to audit the fix:
-
-```
-Task(subagent_type="agent-svetlana-code-review", prompt="Security review of the hotfix for: $ARGUMENTS.\n\nFix applied by Simple Writer:\n[PASTE SIMPLE WRITER'S CHANGES]\n\nIteration: [iteration] of 3\n\nCheck for:\n- Security vulnerabilities\n- Data validation issues\n- Authentication/authorization concerns\n- Edge cases that could be exploited\n\nReturn verdict: APPROVED or REQUEST_CHANGES with specific issues to fix.")
-```
-
-**If APPROVED:** proceed to Step 3 (report).
-
-**If REQUEST_CHANGES:**
-- If `iteration < 3`: increment iteration, go back to **Step 2a** with Svetlana's feedback
-- If `iteration >= 3`: escalate to user (see Step 3)
-
-### Step 3: Report
-
-```markdown
-## Hotfix Squad Complete
-
-### Loop Summary
-- Iterations: [count] of 3 max
-- Final status: FIXED / ESCALATED
-
-### Tanya (Test)
-- Bug reproduced: YES
-- Test status before fix: FAILED
-- Test status after fix: PASSED / STILL FAILING
-- Regressions found: [yes/no]
-
-### Simple Writer (Fix)
-- Files modified: [list]
-- Lines changed: [count]
-- Approach: [brief description]
-
-### Svetlana (Security)
-- Verdict: APPROVED / REQUEST_CHANGES
-- Critical issues: [count]
-- Warnings: [count]
-- [If REQUEST_CHANGES: list remaining issues]
-
-### Next Steps
-[If FIXED:]
-- Deploy to staging
-- Monitor error logs
-
-[If ESCALATED after 3 iterations:]
-- Manual intervention needed
-- Remaining issues: [list from Svetlana/Tanya]
-- Attempted fixes: [summary of what was tried]
-```
-
-## Notes
-
-- RED -> GREEN -> REVIEW loop ensures quality
-- Fix must be minimal - no refactoring
-- Max 3 iterations prevents infinite loops
-- Each iteration passes previous feedback to Simple Writer so it doesn't repeat mistakes
-- Security check is mandatory before reporting success