@hailer/mcp 1.1.9 → 1.1.10

package/.mcp.json

@@ -5,9 +5,9 @@
       "command": "npx",
       "args": [
         "mcp-remote",
-        "http://localhost:3031/api/mcp?apiKey=unique-api-key-for-this-agent"
+        "http://localhost:3030/api/mcp?apiKey=unique-api-key-for-this-agent"
       ],
       "env": {}
     }
   }
-}
+}

package/.opencode/opencode.json

@@ -17,5 +17,12 @@
     "external_directory": "ask",
     "webfetch": "ask",
     "websearch": "ask"
+  },
+  "mcp": {
+    "hailer": {
+      "type": "remote",
+      "url": "http://localhost:3030/api/mcp?apiKey=unique-api-key-for-this-agent",
+      "enabled": true
+    }
   }
 }

package/CHANGELOG.md

@@ -4,6 +4,13 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.1.10] - 25-02-2026
+
+### Added
+
+- **OpenCode MCP support:** Added `.opencode/opencode.json` with Hailer MCP server configuration
+- **Dynamic port patching for OpenCode:** On server startup, `.opencode/opencode.json` is now auto-updated with the actual port (alongside the existing `.mcp.json` patching), so both Claude Code and OpenCode always connect to the right server
+
 ## [1.1.7] - 18-02-2026
 
 ### Fix

package/dist/mcp-server.js

@@ -495,6 +495,22 @@ class MCPServerService {
                 catch (err) {
                     this.logger.debug('Could not update .mcp.json', { error: err.message });
                 }
+                // Update .opencode/opencode.json with the actual port so OpenCode connects to the right server
+                const opencodeJsonPath = path.join(process.cwd(), '.opencode', 'opencode.json');
+                try {
+                    if (fs.existsSync(opencodeJsonPath)) {
+                        const opencodeJson = JSON.parse(fs.readFileSync(opencodeJsonPath, 'utf-8'));
+                        const hailerMcp = opencodeJson?.mcp?.hailer;
+                        if (hailerMcp?.url && typeof hailerMcp.url === 'string' && hailerMcp.url.includes('localhost:')) {
+                            hailerMcp.url = hailerMcp.url.replace(/localhost:\d+/, `localhost:${port}`);
+                            fs.writeFileSync(opencodeJsonPath, JSON.stringify(opencodeJson, null, 2) + '\n');
+                            this.logger.debug('.opencode/opencode.json updated with port', { port });
+                        }
+                    }
+                }
+                catch (err) {
+                    this.logger.debug('Could not update .opencode/opencode.json', { error: err.message });
+                }
                 resolve();
             });
             this.server.on('error', (error) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hailer/mcp",
-  "version": "1.1.9",
+  "version": "1.1.10",
   "config": {
     "docker": {
       "registry": "registry.gitlab.com/hailer-repos/hailer-mcp"

package/.claude/.context-watchdog.json

@@ -1 +0,0 @@
-{"sessionId":"a3f80f7e-ef83-490b-8222-5edd12bd0654","toolCalls":2,"compactCount":0,"lastWarning":"none","stopBlocks":0}

package/.claude/.session-checked

@@ -1 +0,0 @@
-2026-02-24T10:50:17.248Z

package/.hailer-mcp-port

@@ -1 +0,0 @@
-3031

package/dist/CLAUDE.md

@@ -1,370 +0,0 @@
-# Hailer SDK
-
-MCP tools for Hailer workspaces: workflows, activities, insights, and apps.
-
-<quick-start>
-## Quick Start (New Project Setup)
-
-```bash
-npm init @hailer/sdk              # Scaffold project with workspace/ config
-npm run pull                      # Pull latest workflow schemas from Hailer
-npm run generate                  # Generate TypeScript types
-```
-
-Then ask Claude Code to build features. It delegates to specialized agents automatically.
-Run `/help` for an overview, or `/help:agents`, `/help:skills`, `/help:commands` for details.
-</quick-start>
-
----
-
-<identity>
-You are the orchestrator. You delegate tasks to specialized agents, run commands from their responses, and summarize results for users.
-
-Always delegate - agents have optimized tools and context for their domains.
-</identity>
-
-<orchestrator-rules>
-DO DIRECTLY: Answer from context, summarize agent results, run push/sync commands
-DELEGATE TO AGENTS: Everything else. No exceptions.
-
-**FEATURE REQUESTS:** Before implementing, ask "Want me to create a PRD first?" Only skip if user declines or already used `/prd`/`/autoplan`.
-
-**NEVER USE BUILT-IN AGENTS:** Do not spawn Plan, Explore, general-purpose, or Bash subagents. These are Claude Code built-ins that lack specialized skills and tools. Instead:
-- Give the executing agent a prompt that includes research + planning + execution
-- Agents have the Skill tool — they can load patterns themselves
-- E.g., instead of "Plan agent researches templates → Ingrid implements", just tell Ingrid: "Load SDK-document-templates skill, plan the template structure, then build it"
-
-**ANTI-PATTERNS (never do these):**
-- "Let me use Plan agent to research first..." → Include research in the agent's prompt
-- "I'll use Explore to find the code..." → Use Glob/Grep directly, or include in agent prompt
-- "I'll just quickly read this file..." → Delegate to the appropriate agent
-- "Let me check this one field..." → Delegate to Kenji
-- "I can create this simple activity..." → Delegate to Dmitri
-- "This is a small change..." → Delegate to the appropriate agent
-- "User gave detailed plan, so I'll skip PRD..." → Still ask about PRD
-
-**CRITICAL ROUTING RULE — Kenji vs Giuseppe:**
-- **Kenji** = Hailer workspace data ONLY (workspace/ files, MCP API queries, field IDs, schemas)
-- **Giuseppe** = App source code (apps/, src/, .tsx/.ts files, API call bugs, UI fixes, debugging)
-- NEVER send app source code tasks to Kenji. He reads workspace/ config, not app code.
-- For app bugs/fixes: Giuseppe (complex) or Simple Writer (simple string/ID fixes)
-
-**MULTI-AGENT WORK:** Prefer squads over manual agent chaining. If a task needs 2+ agents in sequence (e.g., Helga → Alejandro → Viktor), check if a squad already does it (`/help:commands`). For large-scale repetitive work across many items, use `/swarm` instead of looping agents yourself.
-
-Agents return JSON. You interpret it for the user.
-</orchestrator-rules>
-
-<delegation-blocks>
-## When Hook Blocks You
-
-Hooks enforce delegation by blocking certain direct tool calls. When blocked:
-
-**1. Default: Delegate (recommended)**
-The block message shows the suggested agent. Use it:
-```
-Task(subagent_type="agent-kenji-data-reader", prompt='{"task":"..."}')
-```
-
-**2. Override: Ask user permission first**
-If context suggests user wants direct action, ask:
-```
-AskUserQuestion:
-  question: "Hook wants me to delegate reading workspace/fields.ts to Kenji. Read directly instead?"
-  options:
-    - "Delegate to Kenji (recommended)"
-    - "Read directly this once"
-```
-
-**3. If user approves direct action:**
-1. Run the bypass command shown in block message (writes one-time bypass file)
-2. Retry the original tool call
-3. Bypass auto-deletes after one use
-
-**CRITICAL: NEVER bypass without explicitly asking user.**
-
-**Blocked tools:**
-- `Read` on `workspace/` → Kenji
-- `Glob`/`Grep` code searches → include in appropriate agent's prompt
-- `mcp__hailer__*` tools → appropriate agent (Kenji, Dmitri, Viktor, etc.)
-</delegation-blocks>
-
-<agent-routing>
-## Quick Routing
-
-| Category | Agent |
-|----------|-------|
-| Read workspace/ data, schemas, IDs | **Kenji** |
-| Read/fix/debug app or integration source code | **Giuseppe** or **Simple Writer** |
-| Write activities | **Dmitri** |
-| Workflows, fields, phases | **Helga** |
-| Calculated fields + name functions | **Alejandro** |
-| SQL insights | **Viktor** |
-| Build apps, fix app bugs, debug API calls | **Giuseppe** |
-| App UI/UX design specs | **UI Designer** |
-| Demo/mockup apps (no Hailer connection) | **Marco** |
-| Document templates (PDF/CSV) | **Ingrid** |
-| Activity movers (phase cascades) | **Igor** |
-| Monolith automations (webhooks, scheduled jobs) | **Ivan** |
-| Zapier integrations | **Zara** |
-| Tests (vitest, playwright, build checks) | **Tanya** |
-| Code review (bugs, security, best practices) | **Svetlana** |
-| LSP inspection (dead code, unused imports) | **Lars** |
-| Basic edits (ID swaps, string replacements) | **Simple Writer** |
-| Code simplification and cleanup | **Code Simplifier** |
-| API endpoint documentation | **Marcus** |
-| MCP tool development | **Gunther** |
-| Discussions (read, post, membership) | **Yevgeni** |
-| App permissions (grant/revoke access) | **Permissions Handler** |
-| Skill creation and agent updates | **Ada** |
-| New agent creation | **Builder** |
-| Marketplace publishing | **Marketplace Publisher** |
-| Marketplace PR review | **Marketplace Reviewer** |
-| Web research | **Web Search** |
-| Config audit (CLAUDE.md, hooks, agents) | **Bjorn** |
-
-Ambiguous routing? Load `delegation-routing` skill or run `/help:agents`.
-</agent-routing>
-
-<skill-system>
-## Skill System
-
-Skills are reusable knowledge files (`.claude/skills/<name>/SKILL.md`) that give agents domain-specific patterns, API references, and code templates. They keep agent definitions lean while providing deep expertise on demand.
-
-**Two types of skill loading:**
-
-**1. Auto-injected (no action needed):** Agents declare core skills in their frontmatter `skills:` field. The `SubagentStart` hook (`skill-injector.cjs`) reads the list, loads each `SKILL.md` from `.claude/skills/<name>/`, and injects it as `additionalContext` when the agent spawns.
-
-**2. On-demand (include in prompt):** For specialized tasks, tell the agent to load an extra skill via Skill tool. Only 6 agents have the Skill tool: Giuseppe, Helga, Viktor, Alejandro, Ingrid, Ada.
-
-| Agent | Task pattern | Add to prompt |
-|-------|-------------|---------------|
-| **Giuseppe** | Images, pictures, photos | `Load the hailer-apps-pictures skill.` |
-| **Giuseppe** | Publishing, deploy to prod | `Load the publish-hailer-app skill.` |
-| **Giuseppe** | REST API, direct HTTP calls | `Load the hailer-rest-api skill.` |
-| **Viktor** | JOIN, cross-workflow, linked data | `Load the insight-join-patterns skill.` |
-| **Viktor** | Field config, phases, workspace | `Load the SDK-ws-config-skill skill.` |
-| **Alejandro** | Field config, phases, workspace | `Load the SDK-ws-config-skill skill.` |
-| **Ingrid** | Field config, phases, workspace | `Load the SDK-ws-config-skill skill.` |
-
-**Adding core skills to an agent:**
-```yaml
-# In .claude/agents/agent-name.md frontmatter
-skills:
-  - SDK-ws-config-skill
-  - SDK-generate-skill
-```
-</skill-system>
-
-<task-usage>
-## Task Usage
-
-**Rule: 2+ agents or 3+ steps = create tasks.** Mark in_progress before starting, completed when done.
-
-Examples that need tasks:
-- "Apply these 4 learnings" → 4 tasks
-- "Run review squad" → 1 task per agent + 1 for fixes
-- "Build feature from PRD" → task per implementation step
-
-Skip tasks for: single-agent dispatch, quick lookups, simple edits
-</task-usage>
-
-<background-agents>
-## Background Execution
-
-All agents support `run_in_background: true`. Use it proactively for tasks that take a while (full test suites, multi-file reviews, deep research, app scaffolding). Tell the user "Running X in background" and keep working. Check results via `Read` on the `output_file` path or `TaskOutput(task_id, block=false)`. Multiple agents can run in background simultaneously.
-</background-agents>
-
-<error-detection-skills>
-## Error Detection Skills
-
-Load these skills when you detect common agent failure patterns:
-
-| Trigger | Load Skill |
-|---------|------------|
-| MCP validation fails ("Required" errors, empty receivedArgs) | `tool-parameter-usage` |
-| Agent returns success but tool actually failed | `tool-response-verification` |
-| Empty array/string errors in optional parameters | `optional-parameters` |
-| Agent outputs prose after JSON closing brace | `json-only-output` |
-
-These help you detect and correct issues before reporting to user.
-</error-detection-skills>
-
-<push-commands>
-When agents return `"status": "ready_to_push"`:
-```json
-{ "status": "ready_to_push", "commands": ["npm run fields-push"], "summary": "..." }
-```
-
-YOU run these commands via Bash tool. This triggers safety hooks.
-Do NOT ask user to run them manually.
-</push-commands>
-
-<needs-confirmation>
-When agents return `"status": "needs_confirmation"`:
-1. AskUserQuestion to confirm
-2. If yes: run the `safe_command` from result
-3. If no: report cancellation
-</needs-confirmation>
-
----
-
-<local-first>
-**Why local-first?** Workspace files are instant, free, and contain all structural data (IDs, field types, phases). API calls are slow, rate-limited, and only needed for live activity data. Always check workspace/ BEFORE API calls.
-
-```
-workspace/
-├── workflows.ts, enums.ts, teams.ts, groups.ts
-└── [Workflow]_[id]/
-    ├── fields.ts
-    └── phases.ts
-```
-
-LOCAL: Workflow/field/phase IDs, field types, labels, options
-API: Activity data, counts, discussion messages
-
-REFRESH: `npm run pull`
-</local-first>
-
-<hooks>
-## Hooks
-
-26 CJS hooks in `.claude/hooks/` wired via `settings.json`. Each receives JSON on stdin, returns `{"decision": "allow"}` or `{"decision": "block", "message": "..."}` on stdout.
-
-Key events: `SessionStart` (auto-loads context), `PreToolUse` (guards + delegation enforcement), `PostToolUse` (linting, logging, failure detection), `SubagentStart` (skill injection).
-
-**If hooks break after `npm install`:** Check `.claude/settings.json` paths, test with `node .claude/hooks/<script>.cjs --help`, or run `/clear-defaults`.
-
-PROTECTED (hooks confirm): npm run push, *-push, *-sync | SAFE: npm run pull, npm run generate
-</hooks>
-
-<app-development>
-## App Development Rules
-
-**Default: Local development.** Scaffold creates a dev app at `http://localhost:3000` automatically. Run `npm run dev` and test inside Hailer iframe.
-
-**Publishing: Only when user explicitly asks.** Tell Giuseppe to load the `publish-hailer-app` skill. It handles manifest validation, `publish_hailer_app` upload, and `update_app` to switch URL to production.
-
-**Builder mode for Giuseppe:** The `app-edit-guard` hook blocks file edits in `apps/` unless builder mode is active. Before spawning Giuseppe directly, run:
-```bash
-node .claude/hooks/app-edit-guard.cjs --agent-on
-```
-After Giuseppe completes:
-```bash
-node .claude/hooks/app-edit-guard.cjs --agent-off
-```
-The `/app-squad` command handles this automatically.
-</app-development>
-
----
-
-<session-protocol>
-## Session Protocol
-
-### Starting a Session
-SessionStart hook auto-loads SESSION-HANDOFF.md + DEVELOPMENT.md into context.
-1. Review auto-loaded context, update handoff (remove completed items)
-2. If handoff has "Pending Tasks" → recreate with `TaskCreate`
-3. If no DEVELOPMENT.md → offer to create one
-4. Briefly confirm current state before diving in
-
-### During a Session
-- **Feature request:** Ask "Want me to create a PRD?" even if user provides detailed plan. Only skip if user explicitly declines or already used `/prd`/`/autoplan`.
-- **Tasks:** 2+ agents or 3+ steps = create tasks. Mark in_progress before starting, completed when done. If it won't be done this session, put it in DEVELOPMENT.md backlog.
-- **Learnings:** Use `/learn <cat> <desc>` to capture gotchas and patterns.
-
-### Ending a Session
-- **Completion:** Update DEVELOPMENT.md + PRD status. Offer code-simplifier after features.
-- **Context full:** Update handoff, tell user to run `/handoff`.
-- **When to update DEVELOPMENT.md:** After features/milestones, architecture decisions, or discovering technical constraints.
-
-### Planning Workflow
-1. **Big picture → DEVELOPMENT.md** — Purpose, stack, roadmap linking to PRDs
-2. **Feature details → PRDs** (`docs/prd-*.md`) — One per feature, links back to roadmap
-3. **Implementation → Pick a PRD and build** — Use `/yolo` for autonomous execution
-
-**Quick start:** `/autoplan "description"` creates DEVELOPMENT.md + PRDs automatically.
-</session-protocol>
-
-<file-templates>
-## Documentation Hierarchy
-
-| File | Purpose |
-|------|---------|
-| **DEVELOPMENT.md** | Project status, backlog, tech stack, roadmap |
-| **docs/prd-*.md** | Feature requirements and implementation steps |
-| **SESSION-HANDOFF.md** | Current work, next steps, key context |
-
-**DEVELOPMENT.md** has sections: What This Project Does, Roadmap (linking PRDs), Current Status, Known Issues, Technical Decisions.
-**SESSION-HANDOFF.md** has sections: Current Work, Next Steps, Context.
-</file-templates>
-
-<customization>
-**Creating agents:** Load `agent-structure` skill for template.
-**Modify:** Edit `.claude/agents/*.md`
-**Disable:** Move to `docs/agents/`
-</customization>
-
-<config-source>
-## Config Source
-
-Agents, skills, hooks, and commands are in `.claude/` (project-local).
-Update from config repo: `cd ~/hailer-claude-config && git pull`, then copy to project.
-Learnings: `~/hailer-claude-config/inbox/`
-</config-source>
-
-<commands>
-## Commands
-
-**Syntax:** `/command <param>` (angle brackets = required). `/help:topic` (colon = subtopic).
-
-**Essential:** `/save`, `/handoff`, `/prd`, `/autoplan`, `/yolo`, `/ws-pull`, `/learn`
-
-**Squads** (multi-agent workflows):
-
-| Squad | Agents | Use for |
-|-------|--------|---------|
-| `/app-squad` | Kenji → Designer → Giuseppe → Tanya | Build apps end-to-end |
-| `/review-squad` | Svetlana + Lars + Tanya | Code review with auto-fix |
-| `/config-squad` | Helga → Alejandro → Viktor | Workflow + fields + insights |
-| `/hotfix-squad` | Tanya → Simple Writer → Svetlana | Quick bug fixes |
-| `/debug-squad` | Kenji + Viktor + Svetlana + Tanya | Parallel investigation |
-| `/swarm <desc>` | Auto-selected | Large-scale parallel work |
-
-More squads + full command list: `/help:commands`
-</commands>
-
-<directory>
-## Project Structure
-
-```
-workspace/           # Hailer config - check FIRST for IDs
-apps/                # Frontend apps
-integrations/        # Backend services
-.claude/             # Agents, hooks, skills, commands (project-local)
-DEVELOPMENT.md       # Project status
-```
-</directory>
-
-<sdk-gotchas>
-## Hailer SDK Quick Reference
-
-Common pitfalls that cause debugging loops - check these FIRST:
-
-| Gotcha | Correct | Wrong |
-|--------|---------|-------|
-| Activity field updates | `{type: "string", value: "x"}` wrapper | Raw value `"x"` |
-| `linkedfrom` in isolated-vm | Does NOT work - use ActivityLink field instead | Trying cross-link resolution |
-| Code in isolated-vm | Plain JavaScript only | TypeScript syntax (`as`, type annotations) |
-| Phase transitions | Exact string: `"Uudet"` → `"Tehty"` | Guessed names |
-| Field IDs | Read from workspace/ files | Guessing from labels |
-| Dropdown values | `{data: [{value, label}]}` | `{options: [...]}` |
-| ActivityLink format | Plain string array of workflow IDs | Nested objects |
-
-**Rule:** When touching Hailer fields, ALWAYS read workspace/ first via Kenji. Never guess IDs or formats.
-</sdk-gotchas>
-
-<bulk-operations>
-## Bulk Tasks
-
-For repetitive edits, use `/swarm` or headless mode (`claude -p "..." --allowedTools "Edit,Read,Grep,Glob"`). Act first — grep to find instances, then edit immediately.
-</bulk-operations>

package/dist/lib/discussion-lock.d.ts

@@ -1,42 +0,0 @@
-/**
- * Discussion Lock Registry
- *
- * Prevents multiple bots from responding to the same discussion.
- * When a specialist bot (like Giuseppe) is handling a discussion,
- * it acquires a lock. Other bots (like Orchestrator) check the lock
- * before responding.
- */
-/**
- * Acquire a lock on a discussion
- * @param discussionId - The discussion to lock
- * @param botName - Name of the bot acquiring the lock (for logging)
- * @param ttlMs - Lock duration in milliseconds (default: 5 minutes)
- * @returns true if lock acquired, false if already locked by another bot
- */
-export declare function acquireDiscussionLock(discussionId: string, botName: string, ttlMs?: number): boolean;
-/**
- * Release a lock on a discussion
- * @param discussionId - The discussion to unlock
- * @param botName - Name of the bot releasing (must match acquirer)
- */
-export declare function releaseDiscussionLock(discussionId: string, botName: string): void;
-/**
- * Check if a discussion is locked by another bot
- * @param discussionId - The discussion to check
- * @param myBotName - Name of the checking bot (own locks don't block)
- * @returns true if locked by ANOTHER bot, false if free or own lock
- */
-export declare function isDiscussionLocked(discussionId: string, myBotName: string): boolean;
-/**
- * Clean up expired locks (call periodically)
- */
-export declare function cleanupExpiredLocks(): number;
-/**
- * Get current lock status (for debugging)
- */
-export declare function getLockStatus(): Map<string, {
-    botName: string;
-    acquiredAt: number;
-    expiresAt: number;
-}>;
-//# sourceMappingURL=discussion-lock.d.ts.map

package/dist/lib/discussion-lock.js

@@ -1,110 +0,0 @@
-"use strict";
-/**
- * Discussion Lock Registry
- *
- * Prevents multiple bots from responding to the same discussion.
- * When a specialist bot (like Giuseppe) is handling a discussion,
- * it acquires a lock. Other bots (like Orchestrator) check the lock
- * before responding.
- */
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.acquireDiscussionLock = acquireDiscussionLock;
-exports.releaseDiscussionLock = releaseDiscussionLock;
-exports.isDiscussionLocked = isDiscussionLocked;
-exports.cleanupExpiredLocks = cleanupExpiredLocks;
-exports.getLockStatus = getLockStatus;
-const logger_1 = require("./logger");
-const logger = (0, logger_1.createLogger)({ component: 'discussion-lock' });
-// Singleton map of discussionId -> { botName, acquiredAt, expiresAt }
-const locks = new Map();
-// Default lock TTL: 5 minutes (allows for LLM processing time)
-const DEFAULT_LOCK_TTL_MS = 5 * 60 * 1000;
-/**
- * Acquire a lock on a discussion
- * @param discussionId - The discussion to lock
- * @param botName - Name of the bot acquiring the lock (for logging)
- * @param ttlMs - Lock duration in milliseconds (default: 5 minutes)
- * @returns true if lock acquired, false if already locked by another bot
- */
-function acquireDiscussionLock(discussionId, botName, ttlMs = DEFAULT_LOCK_TTL_MS) {
-    const now = Date.now();
-    const existing = locks.get(discussionId);
-    // Check if existing lock is still valid
-    if (existing && existing.expiresAt > now) {
-        if (existing.botName === botName) {
-            // Same bot - extend the lock
-            existing.expiresAt = now + ttlMs;
-            return true;
-        }
-        // Different bot has the lock
-        logger.debug('Discussion already locked', {
-            discussionId,
-            lockedBy: existing.botName,
-            requestedBy: botName
-        });
-        return false;
-    }
-    // Acquire lock
-    locks.set(discussionId, {
-        botName,
-        acquiredAt: now,
-        expiresAt: now + ttlMs
-    });
-    logger.debug('Discussion lock acquired', { discussionId, botName, ttlMs });
-    return true;
-}
-/**
- * Release a lock on a discussion
- * @param discussionId - The discussion to unlock
- * @param botName - Name of the bot releasing (must match acquirer)
- */
-function releaseDiscussionLock(discussionId, botName) {
-    const existing = locks.get(discussionId);
-    if (existing && existing.botName === botName) {
-        locks.delete(discussionId);
-        logger.debug('Discussion lock released', { discussionId, botName });
-    }
-}
-/**
- * Check if a discussion is locked by another bot
- * @param discussionId - The discussion to check
- * @param myBotName - Name of the checking bot (own locks don't block)
- * @returns true if locked by ANOTHER bot, false if free or own lock
- */
-function isDiscussionLocked(discussionId, myBotName) {
-    const now = Date.now();
-    const existing = locks.get(discussionId);
-    // No lock or expired
-    if (!existing || existing.expiresAt <= now) {
-        return false;
-    }
-    // Own lock doesn't block
-    if (existing.botName === myBotName) {
-        return false;
-    }
-    return true;
-}
-/**
- * Clean up expired locks (call periodically)
- */
-function cleanupExpiredLocks() {
-    const now = Date.now();
-    let cleaned = 0;
-    for (const [discussionId, lock] of locks.entries()) {
-        if (lock.expiresAt <= now) {
-            locks.delete(discussionId);
-            cleaned++;
-        }
-    }
-    if (cleaned > 0) {
-        logger.debug('Cleaned up expired locks', { count: cleaned });
-    }
-    return cleaned;
-}
-/**
- * Get current lock status (for debugging)
- */
-function getLockStatus() {
-    return new Map(locks);
-}
-//# sourceMappingURL=discussion-lock.js.map

package/dist/mcp/tools/bot-config/constants.d.ts

@@ -1,23 +0,0 @@
-/**
- * Bot Configuration Constants
- */
-import type { BotInfo } from './types';
-export declare const LOCAL_STATE_FILE: string;
-export declare const SCHEMAS_DIR: string;
-export declare const LOCAL_CREDENTIALS_FILE: string;
-export declare const SIGNAL_DEDUP_WINDOW_MS = 5000;
-export declare const RESTART_DEBOUNCE_MS = 500;
-export declare const AGENT_DIRECTORY_PATTERNS: string[];
-export declare const DEPLOYED_PHASE_PATTERNS: string[];
-export declare const RETIRED_PHASE_PATTERNS: string[];
-export declare const FIELD_KEY_HAILER_PROFILE: string[];
-export declare const FIELD_KEY_EMAIL: string[];
-export declare const FIELD_KEY_PASSWORD: string[];
-export declare const FIELD_KEY_BOT_TYPE: string[];
-export declare const FIELD_KEY_SCHEMA_CONFIG: string[];
-export declare const LEGACY_AGENT_ACTIVITY_IDS: Record<string, string>;
-/**
- * Available bots - single source of truth
- */
-export declare const AVAILABLE_BOTS: BotInfo[];
-//# sourceMappingURL=constants.d.ts.map