@hailer/mcp 1.3.14 → 1.3.23

package/dist/public-chat/system-prompt.js

@@ -85,26 +85,16 @@ Confidence with humility. "I think this would help because X" — never "you nee
 Every reply:
 - 1-3 sentences (the answer)
 - 2-3 numbered options (what to do next)
+- Options are written FROM THE VISITOR'S perspective — as if the visitor is saying it. "I want to see pricing", "Show me sales templates", "I need a project tracker" — NOT "Tell me what you need" or "I'll find templates for you" (that's the bot talking, not the visitor).
 
-First turn — discovery before demonstration:
-- Your greeter (rendered client-side before the user types) asked them a qualifying question: "what brought you here today? Sizing it up for your team, hunting for a specific tool, or just curious how it works?"
-- The user's FIRST message is their answer. It's an archetype signal — but it's not enough. You can't tell them how Hailer would work for THEIR business until you know what their business actually does today.
-- Your first reply must do three things, in order, in one short message (under 15 words — the hard length rule applies here too):
-  1. **Reflect** what they told you back — one specific phrase from their answer ("a way to keep client projects together", "something that replaces three different tools") so they feel heard.
-  2. **Map** to an archetype silently (see Visitor archetypes) and quietly bias the rest of the session toward that lens.
-  3. **Ask about their current workflow and where it hurts.** This is the most important step. Phrase it naturally in their language — match the words they used in their first message. Examples (don't copy verbatim; adapt to their wording):
-     - "Tell me how your team handles [the thing they named] today — what does the process look like, and where does it usually fall apart?"
-     - "Walk me through a typical [deal / project / case / ticket] right now, start to finish. What's painful enough that you're looking?"
-     - "How is your team running [sales / projects / support] today? What's the tool stack, and where does it leak?"
-- DO NOT offer a demo, tour, slide deck, or "next move" on turn 1. You don't know enough yet to show them anything specific. Discovery first; demonstration after.
-- DO NOT list multiple options. One reflection + one open discovery question, that's it.
-- DO NOT mention the "Continue in Hailer" button in your first reply. The button is right there in the UI; the first reply earns the visitor's trust by listening, not by selling.
-
-1. Show me how it works
-2. I have a specific business need
-3. What makes Hailer different?"
-
-NEVER write a reply without numbered options.
+EVERY reply — including the very first one — MUST end with 2-3 numbered options. No exceptions.
+
+If the visitor says something generic like "hi", "hello", "hey" — respond with a short welcome and options:
+"Welcome! Hailer is a workspace where your team manages processes, communication, and data in one place. What would you like to do?
+
+1. Tell me more about Hailer
+2. I already know what I need
+3. Show me the marketplace"
 
 ═══ CONVERSATION FLOW ═══
 
@@ -112,6 +102,27 @@ Your goal: introduce Hailer, walk the visitor through key features, discover wha
 
 At any point the visitor can type their own question — answer it naturally. Remind them regularly (every 2-3 replies) that they can ask anything, not just click buttons. Add a short note like "Feel free to ask anything" or "You can always type your own question" at the end of your reply before the options.
 
+TELL ME MORE ABOUT HAILER:
+When the visitor says "Tell me more about Hailer" or similar ("what is Hailer", "how does it work", "show me more"):
+- Give a 3-5 sentence overview covering the key ideas: Hailer replaces scattered tools (CRM, project tracker, chat, spreadsheets) with one workspace. Workflows model your processes with phases and fields. Every record has its own discussion thread so context stays with the work. There's a marketplace with ready-made templates you can install and customize. Apps and AI agents extend the platform.
+- ALWAYS end with this exact sentence before the options: "Want to see it in action? Click 'Take a tour' in the top left corner — it walks you through the main features step by step."
+- Offer numbered options:
+1. I already know what I need
+2. Show me the marketplace
+
+Do NOT navigate anywhere. Do NOT launch a tour yourself. The tour button in the UI handles it.
+
+SHOW ME THE MARKETPLACE:
+When the visitor says "Show me the marketplace" or similar:
+- Navigate to apps page: <bot-action type="navigate" target="apps" />
+- In your reply text, tell them they can browse what's there OR describe what they need and you'll search for matching templates.
+- Offer concrete category options — NOT generic "I'm looking for a specific solution":
+1. Sales pipeline
+2. Project tracker
+3. HR & onboarding
+4. Customer support
+- The message text already invites them to type freely, so no need for a catch-all option.
+
 SHORTCUT — DIRECT BUSINESS NEED:
 If the visitor says "I already know what I need" or mentions their business, industry, or specific need at ANY point (e.g. "I run a construction company", "we need a sales pipeline", "I'm looking for project management", "HR tool for my team"), respond with a short question and concrete options.
 
@@ -139,7 +150,7 @@ Example for "I run a construction company":
 2. Crew scheduling and management
 3. Invoicing and billing"
 
-When they pick a specific option → do marketplace-search with TOOL keywords (not industry name) + navigate to apps.
+When they pick a specific option → do marketplace-search with TOOL keywords (not industry name) + ALWAYS navigate to apps (the marketplace page). NEVER navigate to workflow-list or kanban when showing marketplace results.
 
 ` +
     // Scripted tour STEP 1-6 moved to frontend tour state machine to save output tokens.
@@ -250,6 +261,7 @@ A bakery doesn't need a "bakery template". They need:
 Your job: translate "I'm a [business type]" into 2-3 concrete tool needs, then search for THOSE.
 
 Use multiple marketplace-search tags if needed — one per tool category. Use their language, not Hailer jargon.
+ALWAYS include <bot-action type="navigate" target="apps" /> to show the marketplace page. NEVER navigate to workflow-list, kanban, or Data Core when searching for templates.
 
 Example for "I'm a plumber":
 "For a plumbing business, you'd want job tracking to manage service calls, a client list to keep customer history, and invoicing to bill when the job's done.
@@ -259,9 +271,11 @@ Example for "I'm a plumber":
 <bot-action type="navigate" target="apps" />
 
 1. Tell me more about how job tracking works
-2. Show me other tools that might help
+2. Nothing matched — let me describe what I need
 3. I want to try this"
 
+After every marketplace-search, ALWAYS include "Nothing matched — let me describe what I need" as one of the numbered options. The search may return empty results and the visitor needs a way to continue.
+
 PRODUCT SELECTED — visitor chose a specific product from the marketplace:
 When you see a message like 'Install the template [name: Product Name] by Publisher in my workspace.' — this means the visitor browsed the marketplace and picked a specific product. The exact product name is inside [name: ...]. This OVERRIDES everything else in the conversation — forget what category they picked before, forget any previous context. Only the product name matters now. Respond:
 1. Say the product name will be installed: "[Product Name] will be installed in your workspace." — nothing else about what it does, what category it is, or how it works. Just the name.
@@ -304,7 +318,7 @@ You control the center area with navigate tags. Use them to SHOW what you're tal
 
 DEMO VIEWS — what's on each page and when to show it:
 
-workflow-list — Grid of workflow cards. Shows that Hailer organizes work into workflows (processes). Use when introducing Hailer or explaining the concept of workflows.
+workflow-list — DEPRECATED, DO NOT USE. This page shows a static placeholder, not real content. To explain workflows, use kanban view instead or just describe in text.
 
 kanban — A "Sales Pipeline" board with columns (New, Qualified, Proposal, Won). Cards represent deals/activities. Use when explaining how work moves through phases, or when visitor mentions sales/pipeline/tracking.
 
@@ -362,10 +376,11 @@ Examples:
 
 ═══ SCOPE ═══
 
-- Only discuss Hailer
+- You ONLY discuss Hailer and topics directly related to it. Nothing else.
+- If the visitor asks about anything unrelated to Hailer (weather, coding help, math, jokes, other products, general knowledge, personal questions), respond: "I can only help with Hailer-related questions. What would you like to know about the platform?" and offer the standard options.
+- Do NOT answer off-topic questions even partially. Do NOT say "I don't know but..." and then answer anyway. Just redirect to Hailer.
 - Privacy → knowledge base or privacy@hailer.com
 - Want a human? → https://form.hailer.com/846f393a84406e85dbc150ffdfff8352
-- Off-topic → gently redirect
 `;
 const BOT_ACTION_PROTOCOL = `Bot-action tags — embed these in your replies to control the demo UI. The visitor will NOT see the tag text.
 
@@ -378,7 +393,8 @@ Available tags:
   <bot-action type="marketplace-search" target="{query}" category="{category}" label="{button text}" />
   Categories: template, app, integration, ai-agent, support. Omit category to search all.
 
-Navigate targets: workflow-list, kanban, table, activity-detail, discussions, discussion-detail, feed, calendar, apps
+Navigate targets: kanban, table, activity-detail, discussions, discussion-detail, feed, calendar, apps
+NOTE: workflow-list is DEPRECATED — do not use it. Use kanban instead to show workflows.
 Rules:
 - Use one or two tags per reply, max — except for guided tours (see below). More than that is noise.
 - ONLY use highlight when the user is asking where something is or how to do something specific. Don't sprinkle them on regular Q&A.

package/dist/public-chat/system-prompt.js.map

@@ -1 +1 @@
-{"version":3,"file":"system-prompt.js","sourceRoot":"","sources":["../../src/public-chat/system-prompt.ts"],"names":[],"mappings":";AAAA;;;;;;;;;;;GAWG;;;AA4oBH,sDAEC;AA5oBD,2CAA8E;AAQ9E,MAAM,iBAAiB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8HzB;IACD,qFAAqF;IACrF,yFAAyF;IACzF,yDAAyD;IACzD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;MAuEE;IACF,EAAE,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqJJ,CAAC;AAEF,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoF3B;IACD,oFAAoF;IACpF,iGAAiG;IACjG,yDAAyD;IACzD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;MA6KE;IACF,EAAE,CAAC;AAEH,MAAM,gBAAgB,GAAG;;CAExB,CAAC;AAEF;;;;;;;GAOG;AACH,MAAM,aAAa,GAAwB;IACzC;QACE,IAAI,EAAE,MAAM;QACZ,IAAI,EAAE,iBAAiB,GAAG,IAAI,GAAG,mBAAmB;QACpD,aAAa,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE;KACrC;IACD;QACE,IAAI,EAAE,MAAM;QACZ,IAAI,EAAE,gBAAgB,GAAG,mCAAuB;QAChD,aAAa,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE;KACrC;CACF,CAAC;AAEF,SAAgB,qBAAqB;IACnC,OAAO,aAAa,CAAC;AACvB,CAAC;AAEY,QAAA,eAAe,GAAG,kCAAsB,CAAC"}
+{"version":3,"file":"system-prompt.js","sourceRoot":"","sources":["../../src/public-chat/system-prompt.ts"],"names":[],"mappings":";AAAA;;;;;;;;;;;GAWG;;;AA4pBH,sDAEC;AA5pBD,2CAA8E;AAQ9E,MAAM,iBAAiB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyIzB;IACD,qFAAqF;IACrF,yFAAyF;IACzF,yDAAyD;IACzD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;MAuEE;IACF,EAAE,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyJJ,CAAC;AAEF,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqF3B;IACD,oFAAoF;IACpF,iGAAiG;IACjG,yDAAyD;IACzD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;MA6KE;IACF,EAAE,CAAC;AAEH,MAAM,gBAAgB,GAAG;;CAExB,CAAC;AAEF;;;;;;;GAOG;AACH,MAAM,aAAa,GAAwB;IACzC;QACE,IAAI,EAAE,MAAM;QACZ,IAAI,EAAE,iBAAiB,GAAG,IAAI,GAAG,mBAAmB;QACpD,aAAa,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE;KACrC;IACD;QACE,IAAI,EAAE,MAAM;QACZ,IAAI,EAAE,gBAAgB,GAAG,mCAAuB;QAChD,aAAa,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE;KACrC;CACF,CAAC;AAEF,SAAgB,qBAAqB;IACnC,OAAO,aAAa,CAAC;AACvB,CAAC;AAEY,QAAA,eAAe,GAAG,kCAAsB,CAAC"}

package/package.json

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

package/.claude/skills/hailer-project-protocol/SKILL.md

@@ -1,398 +0,0 @@
----
-name: hailer-project-protocol
-description: Complete Hailer project management workflow schemas, field definitions, and protocols for SDK projects
-version: 1.1.0
----
-
-# Hailer Project Management Protocol
-
-This skill contains the complete Hailer project management workflow schemas, field definitions, and protocols for working with Hailer SDK projects.
-
----
-
-<critical-rules>
-## Overview
-
-Every Hailer workspace uses project management workflows. Claude installs and maintains these automatically using MCP or SDK.
-
-**CRITICAL: Real-Time Updates**
-- Update Hailer items IN REAL-TIME as work progresses
-- Do NOT batch updates - update immediately when status changes
-- When completing a task, update Hailer BEFORE moving to next task
-
-**Context File Hierarchy**
-1. **SESSION-HANDOFF.md** - Previous session state (read first when resuming)
-2. **DEVELOPMENT.md** - Local backup/snapshot of Hailer state
-3. **Hailer Workflows** - Source of truth for project data
-</critical-rules>
-
----
-
-## Workflow 1: Project Planning
-
-**Workflow name:** `Project Planning`
-
-### Phases (in order)
-1. `Planning`
-2. `In Progress`
-3. `On Hold`
-4. `Completed`
-
-### Fields
-
-| Field Name | Field Type | Configuration |
-|------------|------------|---------------|
-| Title | Text | - |
-| Description | Long text | - |
-| Type | Predefined options (single) | Options: `Project`, `Feature`, `Session Handoff`, `PRD` |
-| Project | Activity link | Links to: `Project Planning` workflow |
-| Child Features | Linked from | Linked from: `Project Planning` → `Project` field |
-| Dev Tasks | Linked from | Linked from: `Dev Tasks` → `Feature` field |
-| Goal | Long text | - |
-| Documentation | Long text | - |
-| Technical Notes | Long text | - |
-| Blockers | Long text | - |
-| User Stories | Long text | PRD: As a [user], I want [X] so that [Y] |
-| Acceptance Criteria | Long text | PRD: Checklist of "done" conditions |
-| Technical Constraints | Long text | PRD: Performance, security, compatibility |
-| Out of Scope | Long text | PRD: What this feature does NOT include |
-
-- **Project**: Features use this to link UP to their parent Project
-- **Child Features**: Automatically shows Features that link to this Project
-- **Dev Tasks**: Automatically shows Tasks/Bugs that link to this Feature
-
----
-
-## Workflow 2: Dev Tasks
-
-**Workflow name:** `Dev Tasks`
-
-### Phases (in order)
-1. `Backlog`
-2. `Todo`
-3. `In Progress`
-4. `Review`
-5. `Done`
-
-### Fields
-
-| Field Name | Field Type | Configuration |
-|------------|------------|---------------|
-| Title | Text | - |
-| Description | Long text | - |
-| Type | Predefined options (single) | Options: `Task`, `Bug`, `Tech Debt` |
-| Priority | Predefined options (single) | Options: `HIGH`, `MEDIUM`, `LOW` |
-| Feature | Activity link | Links to: `Project Planning` workflow |
-| Blocked By | Activity link | Links to: `Dev Tasks` workflow |
-| Blocks | Linked from | Linked from: `Dev Tasks` → `Blocked By` field |
-| Related Items | Activity link | Links to: `Dev Tasks` workflow |
-| Related From | Linked from | Linked from: `Dev Tasks` → `Related Items` field |
-| Files Modified | Text | - |
-| Commits | Text | - |
-
-- **Feature**: Links UP to parent Feature in Project Planning
-- **Blocked By**: Links to other Dev Tasks that block this one
-- **Blocks**: Automatically shows Dev Tasks that this task blocks
-- **Related Items**: Links to related Tasks/Bugs (e.g., Bug → Task that caused it)
-
----
-
-## Protocol: Starting in a Workspace
-
-### Step 1: Check for Existing Workflows
-
-**AUTOMATIC CREATION: If workflows don't exist, CREATE THEM.**
-
-Look for workflows named exactly:
-- `Project Planning`
-- `Dev Tasks`
-
-### Step 2: Create Workflows if Missing
-
-**This is NOT optional - create them automatically.**
-
-Notify user: "Setting up project management workflows for this workspace..."
-
-#### Create Project Planning Workflow
-
-```typescript
-{
-  name: "Project Planning",
-  phases: ["Planning", "In Progress", "On Hold", "Completed"],
-  fields: [
-    { name: "Title", type: "text" },
-    { name: "Description", type: "textarea" },
-    { name: "Type", type: "textpredefinedoptions", options: ["Project", "Feature", "Session Handoff", "PRD"] },
-    { name: "Project", type: "activitylink", linkedWorkflow: "Project Planning" },
-    { name: "Goal", type: "textarea" },
-    { name: "Documentation", type: "textarea" },
-    { name: "Technical Notes", type: "textarea" },
-    { name: "Blockers", type: "textarea" },
-    { name: "User Stories", type: "textarea" },
-    { name: "Acceptance Criteria", type: "textarea" },
-    { name: "Technical Constraints", type: "textarea" },
-    { name: "Out of Scope", type: "textarea" }
-  ]
-}
-```
-
-#### Create Dev Tasks Workflow
-
-```typescript
-{
-  name: "Dev Tasks",
-  phases: ["Backlog", "Todo", "In Progress", "Review", "Done"],
-  fields: [
-    { name: "Title", type: "text" },
-    { name: "Description", type: "textarea" },
-    { name: "Type", type: "textpredefinedoptions", options: ["Task", "Bug", "Tech Debt"] },
-    { name: "Priority", type: "textpredefinedoptions", options: ["HIGH", "MEDIUM", "LOW"] },
-    { name: "Feature", type: "activitylink", linkedWorkflow: "Project Planning" },
-    { name: "Blocked By", type: "activitylink", linkedWorkflow: "Dev Tasks" },
-    { name: "Related Items", type: "activitylink", linkedWorkflow: "Dev Tasks" },
-    { name: "Files Modified", type: "text" },
-    { name: "Commits", type: "text" }
-  ]
-}
-```
-
-### Step 3: Verify PRD Fields Exist
-
-If `Project Planning` workflow exists but is missing PRD fields, ADD THEM:
-- User Stories
-- Acceptance Criteria
-- Technical Constraints
-- Out of Scope
-
-### Step 4: Read Current State
-
-Before starting work:
-1. Check for SESSION-HANDOFF.md - read if exists (previous session context)
-2. Check for active Project (Type = `Project`, Phase = `In Progress`)
-3. If no Project exists, ask user for project name and create one
-4. Fetch In Progress Features and Tasks
-5. Check for recent Session Handoff (Type = `Session Handoff`)
-6. Summarize state to user
-
----
-
-## Protocol: During Development (Real-Time Updates)
-
-### Starting New Work
-1. Ensure a Feature exists (Type = `Feature`)
-   - Set `Project` field to link to parent Project
-2. Create Task in Dev Tasks (Type = `Task`)
-   - Set `Feature` field to link to parent Feature
-3. **IMMEDIATELY** move Task to `In Progress`
-4. Keep only ONE task `In Progress` at a time
-
-### Completing Work
-1. **IMMEDIATELY** update Task:
-   - `Files Modified`: List changed files
-   - `Commits`: Add commit hashes
-2. **IMMEDIATELY** move to `Done`
-3. If new work discovered → create new Tasks in `Backlog`
-
-### Finding Bugs
-1. **IMMEDIATELY** create item in Dev Tasks (Type = `Bug`)
-2. Set `Feature` to link to relevant Feature
-3. Set `Priority` based on severity
-4. Optionally set `Related Items` to link to Task that caused it
-
-### Blocked Tasks
-1. Set `Blocked By` to link to blocking Task(s)
-2. Update Description with blocker details
-3. When blocker resolved, clear `Blocked By` and continue
-
-### Technical Decisions
-Update the Feature's `Technical Notes` field with:
-- Architecture decisions and rationale
-- Important discoveries
-- Trade-offs considered
-
-### Documentation
-When feature is complete or stable, update `Documentation` field with:
-- How it works
-- Usage instructions
-- Configuration options
-
----
-
-## Protocol: Session Handoff
-
-### When to Create
-- Context reaches 70-80%
-- Before ending a long session
-- User requests it
-
-### Create Session Handoff Item
-In Project Planning workflow:
-
-| Field | Value |
-|-------|-------|
-| Title | `Session Handoff - YYYY-MM-DD HH:MM` |
-| Type | `Session Handoff` |
-| Project | Link to active Project |
-| Phase | `Completed` |
-| Description | See template below |
-| Technical Notes | Key discoveries and decisions |
-| Blockers | Unresolved issues, next steps |
-
-**Description template:**
-```
-## Completed This Session
-- [List completed tasks]
-
-## In Progress
-- [Current work state]
-
-## Next Steps
-- [What to do when resuming]
-```
-
-### Local SESSION-HANDOFF.md
-Also create/update `SESSION-HANDOFF.md` in project root:
-
-```markdown
-## Session Handoff - YYYY-MM-DD HH:MM
-
-### Completed This Session
-- [What was accomplished]
-
-### Current State
-- [Work in progress, any partial implementations]
-
-### Blockers / Issues Found
-- [Problems encountered, unresolved errors]
-
-### Next Steps
-- [Immediate actions for next session]
-
-### Key Decisions Made
-- [Important context that shouldn't be lost]
-
-### Files Modified
-- [List of changed files with brief description]
-```
-
----
-
-## Protocol: Creating Items
-
-### New Project
-| Field | Value |
-|-------|-------|
-| Title | Project name (ask user) |
-| Type | `Project` |
-| Phase | `In Progress` |
-| Description | Project overview |
-| Goal | What success looks like |
-
-### New Feature
-| Field | Value |
-|-------|-------|
-| Title | Feature name (use arrow prefix for related features: `Sales Orders → Automations`) |
-| Type | `Feature` |
-| Project | Link to parent Project |
-| Phase | `Planning` or `In Progress` |
-| Description | Scope and requirements |
-| Goal | Acceptance criteria |
-| Documentation | How it works (fill when complete) |
-| Technical Notes | Architecture decisions |
-
-### New PRD
-| Field | Value |
-|-------|-------|
-| Title | `PRD: [Feature Name]` |
-| Type | `PRD` |
-| Project | Link to parent Project |
-| Phase | `Planning` |
-| Description | Executive summary |
-| Goal | Success metrics |
-| User Stories | As a [user], I want [X] so that [Y] |
-| Acceptance Criteria | - [ ] Criterion 1<br>- [ ] Criterion 2 |
-| Technical Constraints | Performance, security, compatibility needs |
-| Out of Scope | What this does NOT include |
-
-### New Task
-| Field | Value |
-|-------|-------|
-| Title | Specific, actionable description |
-| Type | `Task` |
-| Feature | Link to parent Feature |
-| Priority | `MEDIUM` (default) |
-| Phase | `Backlog` or `Todo` |
-| Description | Implementation details |
-
-### New Bug
-| Field | Value |
-|-------|-------|
-| Title | Clear bug description with context |
-| Type | `Bug` |
-| Feature | Link to affected Feature |
-| Priority | Based on severity |
-| Phase | `Backlog` or `Todo` |
-| Description | Steps to reproduce, expected vs actual |
-| Related Items | Link to Task that caused it (if known) |
-
----
-
-## Protocol: DEVELOPMENT.md Sync
-
-When user requests sync (`/project-status`):
-
-1. Fetch all data from Hailer workflows:
-   - Active Project
-   - All Features with their phases
-   - All Dev Tasks (grouped by phase)
-   - Recent Session Handoffs
-
-2. Generate DEVELOPMENT.md:
-```markdown
-# [Project Title] Development Status
-
-**Last Updated:** YYYY-MM-DD
-**Hailer Sync:** YYYY-MM-DD HH:MM
-
----
-
-## Active Feature
-**Name:** [Feature Title]
-**Goal:** [Feature Goal]
-**Status:** [Phase]
-
----
-
-## Current Sprint
-
-### In Progress
-- [ ] [Task Title] (Feature: [Feature Name])
-
-### Completed This Session
-- [x] [Task Title] (YYYY-MM-DD)
-
-### Blocked
-- [ ] [Task Title] - **Blocker:** [reason]
-
----
-
-## Backlog
-- [ ] [Task Title] (Feature: [Feature Name], Priority: [Priority])
-
----
-
-## Known Issues
-| Priority | Issue | Status |
-|----------|-------|--------|
-| HIGH | [Bug Title] | [Phase] |
-
----
-
-## Technical Notes
-[Aggregated from Features' Technical Notes fields]
-
----
-
-## Session Notes
-[Local notes not synced to Hailer]
-```

package/.opencode/package-lock.json

@@ -1,117 +0,0 @@
-{
-  "name": ".opencode",
-  "lockfileVersion": 3,
-  "requires": true,
-  "packages": {
-    "": {
-      "dependencies": {
-        "@opencode-ai/plugin": "1.3.17"
-      }
-    },
-    "node_modules/@opencode-ai/plugin": {
-      "version": "1.3.17",
-      "resolved": "https://registry.npmjs.org/@opencode-ai/plugin/-/plugin-1.3.17.tgz",
-      "integrity": "sha512-N5lckFtYvEu2R8K1um//MIOTHsJHniF2kHoPIWPCrxKG5Jpismt1ISGzIiU3aKI2ht/9VgcqKPC5oZFLdmpxPw==",
-      "license": "MIT",
-      "dependencies": {
-        "@opencode-ai/sdk": "1.3.17",
-        "zod": "4.1.8"
-      },
-      "peerDependencies": {
-        "@opentui/core": ">=0.1.96",
-        "@opentui/solid": ">=0.1.96"
-      },
-      "peerDependenciesMeta": {
-        "@opentui/core": {
-          "optional": true
-        },
-        "@opentui/solid": {
-          "optional": true
-        }
-      }
-    },
-    "node_modules/@opencode-ai/sdk": {
-      "version": "1.3.17",
-      "resolved": "https://registry.npmjs.org/@opencode-ai/sdk/-/sdk-1.3.17.tgz",
-      "integrity": "sha512-2+MGgu7wynqTBwxezR01VAGhILXlpcHDY/pF7SWB87WOgLt3kD55HjKHNj6PWxyY8n575AZolR95VUC3gtwfmA==",
-      "license": "MIT",
-      "dependencies": {
-        "cross-spawn": "7.0.6"
-      }
-    },
-    "node_modules/cross-spawn": {
-      "version": "7.0.6",
-      "resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.6.tgz",
-      "integrity": "sha512-uV2QOWP2nWzsy2aMp8aRibhi9dlzF5Hgh5SHaB9OiTGEyDTiJJyx0uy51QXdyWbtAHNua4XJzUKca3OzKUd3vA==",
-      "license": "MIT",
-      "dependencies": {
-        "path-key": "^3.1.0",
-        "shebang-command": "^2.0.0",
-        "which": "^2.0.1"
-      },
-      "engines": {
-        "node": ">= 8"
-      }
-    },
-    "node_modules/isexe": {
-      "version": "2.0.0",
-      "resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz",
-      "integrity": "sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==",
-      "license": "ISC"
-    },
-    "node_modules/path-key": {
-      "version": "3.1.1",
-      "resolved": "https://registry.npmjs.org/path-key/-/path-key-3.1.1.tgz",
-      "integrity": "sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==",
-      "license": "MIT",
-      "engines": {
-        "node": ">=8"
-      }
-    },
-    "node_modules/shebang-command": {
-      "version": "2.0.0",
-      "resolved": "https://registry.npmjs.org/shebang-command/-/shebang-command-2.0.0.tgz",
-      "integrity": "sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==",
-      "license": "MIT",
-      "dependencies": {
-        "shebang-regex": "^3.0.0"
-      },
-      "engines": {
-        "node": ">=8"
-      }
-    },
-    "node_modules/shebang-regex": {
-      "version": "3.0.0",
-      "resolved": "https://registry.npmjs.org/shebang-regex/-/shebang-regex-3.0.0.tgz",
-      "integrity": "sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==",
-      "license": "MIT",
-      "engines": {
-        "node": ">=8"
-      }
-    },
-    "node_modules/which": {
-      "version": "2.0.2",
-      "resolved": "https://registry.npmjs.org/which/-/which-2.0.2.tgz",
-      "integrity": "sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==",
-      "license": "ISC",
-      "dependencies": {
-        "isexe": "^2.0.0"
-      },
-      "bin": {
-        "node-which": "bin/node-which"
-      },
-      "engines": {
-        "node": ">= 8"
-      }
-    },
-    "node_modules/zod": {
-      "version": "4.1.8",
-      "resolved": "https://registry.npmjs.org/zod/-/zod-4.1.8.tgz",
-      "integrity": "sha512-5R1P+WwQqmmMIEACyzSvo4JXHY5WiAFHRMg+zBZKgKS+Q1viRa0C1hmUKtHltoIFKtIdki3pRxkmpP74jnNYHQ==",
-      "license": "MIT",
-      "funding": {
-        "url": "https://github.com/sponsors/colinhacks"
-      }
-    }
-  }
-}