@hailer/mcp 1.1.16 → 1.1.17-beta.0

package/.claude/skills/hailer-monolith-automations/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: hailer-monolith-automations
-description: Understanding and building automations in the Hailer project-monolith
-version: 1.2.0
-triggers: monolith, automation, scheduled task, webhook automation, invoicing, data sync
+description: Understanding and building automations in the Hailer project-monolith, including activity mover phase cascade bots
+version: 1.4.0
+triggers: monolith, automation, scheduled task, webhook automation, invoicing, data sync, activity mover, phase cascade, linked activities
 ---
 
 # Hailer Monolith Automations
@@ -175,27 +175,6 @@ Sync data between Hailer and external systems.
 
 ## Common Patterns
 
-### Config from AWS Secrets Manager
-
-```typescript
-import { fetchConfig } from './fetch-secrets';
-
-// Config name matches AWS secret: "monolith-{name}"
-const config = await fetchConfig('monolith-my-automation');
-
-// Config structure example
-interface AutomationConfig {
-  credentials: {
-    email: string;
-    password: string;
-  };
-  triggerProcessId: string;
-  targetProcessId: string;
-  fieldMappings: Record<string, string>;
-  // ... custom config
-}
-```
-
 ### Hailer Client Connection
 
 ```typescript
@@ -215,26 +194,6 @@ const client = await Client.create({
 client.disconnect();
 ```
 
-### Activity Operations
-
-```typescript
-// List activities
-const { activities } = await client.request('v3.activity.list', [
-  { processId: workflowId, phaseId: phaseId },
-  { limit: 1000, filters: { status: { equalTo: 'Active' } }, returnFlat: true }
-]);
-
-// Create activities
-const created = await client.request('v3.activity.createMany', [
-  { processId: workflowId, phaseId: phaseId, name: 'New Activity', fields: { fieldId: value } }
-]);
-
-// Update activities
-const updated = await client.request('v3.activity.updateMany', [
-  { _id: activityId, fields: { fieldId: newValue }, phaseId: newPhaseId }
-]);
-```
-
 ### Structured Logging
 
 ```typescript
@@ -281,29 +240,6 @@ router.post('/my-automation', jsonParser, async (req, res) => {
 
 ---
 
-## File Structure
-
-```
-project-monolith/
-├── src/
-│   ├── run.ts              # Express server, all endpoints
-│   ├── schedules.ts        # All scheduled jobs
-│   ├── fetch-secrets.ts    # AWS Secrets Manager
-│   ├── logger.ts           # Winston logger
-│   ├── types.ts            # Common types
-│   ├── utils/
-│   │   └── hailer-utils.ts # Helper functions
-│   └── automations/
-│       ├── generic-handle-activities.ts  # Reusable CRUD
-│       ├── netvisor/       # Netvisor integrations
-│       ├── procountor/     # Procountor integrations
-│       ├── hailer/         # Hailer-internal automations
-│       └── {customer}/     # Customer-specific automations
-└── package.json
-```
-
----
-
 ## When to Use Monolith vs Other Options
 
 | Scenario | Solution |
@@ -311,7 +247,7 @@ project-monolith/
 | Simple webhook trigger → Hailer CRUD | **Monolith** |
 | Scheduled data sync | **Monolith** |
 | Accounting integration (Netvisor, Procountor) | **Monolith** (existing code) |
-| Real-time activity sync | **activity-mover** |
+| Phase cascade (move linked activities) | **Monolith activity-mover** (see Activity Mover Service section) |
 | SCIM user provisioning | **microsoft-entra** |
 | Kafka event processing | **digione-integration** |
 | Complex stateful integration | **Dedicated microservice** |
@@ -448,38 +384,6 @@ In Hailer admin:
 
 ---
 
-## Existing Automation Categories
-
-### Invoicing Automations
-- `hailer-invoicing-subscription-v2` - Scheduled subscription billing
-- `hailer-invoicing-billable-work` - Bill tracked time/expenses
-- `hailer-invoicing-project-won` - Invoice on project completion
-- `3pl-invoicing-v2` - 3PL storage billing
-- `kspt-invoicing-v2-webhook` - KSPT rental invoicing
-
-### Data Sync Automations
-- `netvisor-integration` - Netvisor ↔ Hailer sync
-- `procountor-integration-main` - Procountor invoicing
-- `severa-integration` - Severa project sync
-- `fin-forelia-*` - Forelia logistics/forestry
-
-### Activity Management
-- `generic-handle-activities` - Reusable create/update
-- `activity-archiver` - Archive old activities
-- `porvoo-archive` - City-specific archiving
-
-### Notifications & Alarms
-- `porvoo-alarms` - Status checks and alerts
-- `porvoo-notifications` - Send notification messages
-- `3pl-saldo-alarms` - Inventory level alerts
-
-### HR/Employee Automations
-- `siskon-siivous-intu-*` - INTU HR sync
-- `pohjaset-employee-task-automation` - Onboarding tasks
-- `siskon-siivous-synttarionnittelut` - Birthday greetings
-
----
-
 ## Built-in Automation Reference
 
 These are reusable, config-driven automations already in the monolith.
@@ -597,22 +501,6 @@ Webhook-based endpoints for bulk creating/updating activities via function field
 }
 ```
 
-**Field Payload Format:**
-
-For `/create-activities`:
-```json
-[
-    { "name": "New Activity", "fields": { "amount": 100 } }
-]
-```
-
-For `/update-activities`:
-```json
-[
-    { "_id": "activity-id", "fields": { "status": "completed" } }
-]
-```
-
 **CRITICAL: Double-Wrapped Array for Updates**
 
 The monolith generic handler spreads parsed JSON as arguments to `client.request()`. Function fields must output **double-wrapped array** `[[{_id, phaseId}, ...]]` so the first argument to `updateMany` is the array of updates.
@@ -672,6 +560,140 @@ return JSON.stringify([
 
 ---
 
+## Activity Mover Service
+
+Configure automated phase cascade bots. When an activity moves to a trigger phase, the bot automatically moves linked activities to target phases.
+
+**Example:** Invoice → "Invoiced" automatically moves Invoice Rows → "Archived"
+
+**AWS Secret:** `activity-mover-{project}`
+
+---
+
+### Config Schema
+
+```typescript
+interface Config {
+  project: string;              // Hailer project identifier
+  email: string;                // Integration user email
+  password: string;             // Integration user password
+  logDiscussionId: string;      // Discussion ID (not activity ID)
+  triggers: Trigger[];
+}
+
+interface Trigger {
+  processId: string;            // Workflow that triggers automation
+  phaseId: string;              // Phase that fires the trigger
+  metaDataId: string;           // "Seen/Not seen" field ID
+  linkedProcesses: Process[];
+}
+
+interface Process {
+  processId: string;            // Target workflow ID
+  fromPhaseIds: string[];       // Only move activities in these phases
+  toPhaseId: string;            // Move to this phase
+}
+```
+
+One config supports multiple triggers and one trigger can cascade to multiple target workflows:
+
+```json
+{
+  "project": "project-name",
+  "email": "activity-mover+project@hailer.com",
+  "password": "USER_PROVIDES_PASSWORD",
+  "logDiscussionId": "discussion-id",
+  "triggers": [
+    {
+      "processId": "trigger-workflow-id",
+      "phaseId": "trigger-phase-id",
+      "metaDataId": "seen-field-id",
+      "linkedProcesses": [
+        {
+          "processId": "target-workflow-id",
+          "fromPhaseIds": ["phase-1", "phase-2"],
+          "toPhaseId": "destination-phase"
+        }
+      ]
+    }
+  ]
+}
+```
+
+---
+
+### Setup Steps
+
+**Prerequisites:**
+- Link field must exist connecting trigger → target workflows
+- Integration user exists with edit permissions on all workflows
+- Activity mover service running for the project
+
+**Step 1: Gather IDs**
+
+Get workflow, phase, and field IDs from `workspace/`.
+
+**Step 2: Create MetaData Field**
+
+Add a hidden "Activity Mover Status" field to the trigger workflow:
+
+```json
+{
+  "id": "activityMoverStatus",
+  "label": "Activity Mover Status",
+  "type": "text",
+  "hidden": true,
+  "defaultValue": "Not seen"
+}
+```
+
+Push the workspace config after adding the field.
+
+**Step 3: Create Logging Activity**
+
+Create an activity in a suitable workflow for bot logging. Note the **discussion ID** from the response (not the activity ID) — this is `logDiscussionId`.
+
+**Step 4: Generate Config JSON**
+
+Output the complete config (schema above) for the user to deploy.
+
+**Step 5: User Deploys**
+
+User manually:
+1. Fills in the integration user password
+2. Uploads to AWS Secrets Manager as `activity-mover-{project}`
+
+---
+
+### Agent Output Format
+
+```json
+{
+  "status": "success",
+  "result": {
+    "fields_created": ["activityMoverStatus"],
+    "logging_activity": "activity-id",
+    "logging_discussion": "discussion-id",
+    "config": { "...": "..." }
+  },
+  "summary": "Config ready - deploy to AWS",
+  "user_action": "Upload config to AWS Secrets Manager as activity-mover-{project}"
+}
+```
+
+---
+
+### Troubleshooting
+
+| Issue | Cause | Fix |
+|-------|-------|-----|
+| Activities not moving | Wrong phase IDs | Verify IDs from workspace/ |
+| "Not seen" not updating | Wrong metaDataId | Check field ID |
+| No log messages | Wrong discussionId | Use discussion ID, not activity ID |
+| Permission denied | Integration user lacks access | Add to workflow permissions |
+
+---
+
 ## Reference
 
 **Location:** `~/hailer-integration/packages/project-monolith/`

package/.claude/skills/hailer-permissions-system/SKILL.md

@@ -13,9 +13,9 @@ Managing access to Hailer **apps** for users and teams.
 **This skill covers APP permissions only.**
 
 For other permission types, see:
-- **Workflow permissions** (who can access a workflow) → SDK-ws-config-skill, main.ts `members[]`
-- **Phase permissions** (field visibility, transitions) → SDK-ws-config-skill, phases.ts
-- **Team management** (create/edit teams) → SDK-ws-config-skill, teams.ts
+- **Workflow permissions** (who can access a workflow) → sdk-ws-config-skill, main.ts `members[]`
+- **Phase permissions** (field visibility, transitions) → sdk-ws-config-skill, phases.ts
+- **Team management** (create/edit teams) → sdk-ws-config-skill, teams.ts
 
 App permissions = who can see/use an app in Hailer UI.
 Workflow permissions = who can see/edit activities in a workflow.
@@ -60,8 +60,7 @@ mcp__hailer__list_apps({})
 ```
 mcp__hailer__add_app_member({
   appId: "64a1b2c3d4e5f6a7b8c9d0e1",
-  memberId: "user_64a1b2c3d4e5f6a7b8c9d0e2",
-  memberType: "user"
+  member: "user_64a1b2c3d4e5f6a7b8c9d0e2"
 })
 ```
 
@@ -77,8 +76,7 @@ import { TeamIds } from './workspace/enums';
 ```
 mcp__hailer__add_app_member({
   appId: "64a1b2c3d4e5f6a7b8c9d0e1",
-  memberId: TeamIds.sales_team,
-  memberType: "team"
+  member: `team_${TeamIds.sales_team}`
 })
 ```
 
@@ -87,8 +85,7 @@ mcp__hailer__add_app_member({
 ```
 mcp__hailer__remove_app_member({
   appId: "64a1b2c3d4e5f6a7b8c9d0e1",
-  memberId: "user_64a1b2c3d4e5f6a7b8c9d0e2",
-  memberType: "user"
+  member: "user_64a1b2c3d4e5f6a7b8c9d0e2"
 })
 ```
 

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

@@ -1,7 +1,7 @@
 ---
 name: hailer-project-protocol
 description: Complete Hailer project management workflow schemas, field definitions, and protocols for SDK projects
-version: 1.0.1
+version: 1.1.0
 ---
 
 # Hailer Project Management Protocol
@@ -57,13 +57,9 @@ Every Hailer workspace uses project management workflows. Claude installs and ma
 | Technical Constraints | Long text | PRD: Performance, security, compatibility |
 | Out of Scope | Long text | PRD: What this feature does NOT include |
 
-### Field Explanations
 - **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
-- **Documentation**: How it works, usage instructions, user-facing docs
-- **Technical Notes**: Architecture decisions, implementation details
-- **User Stories/Acceptance Criteria/Technical Constraints/Out of Scope**: PRD fields for requirements
 
 ---
 
@@ -94,43 +90,10 @@ Every Hailer workspace uses project management workflows. Claude installs and ma
 | Files Modified | Text | - |
 | Commits | Text | - |
 
-### Field Explanations
 - **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)
-- **Related From**: Automatically shows items that link to this one
-
----
-
-## Link Relationship Summary
-
-```
-Project Planning                          Dev Tasks
-┌─────────────────────┐                  ┌─────────────────────┐
-│ Project             │                  │ Task/Bug/Tech Debt  │
-│                     │                  │                     │
-│ Child Features ◄────┼── Project ───────┼── (not used)        │
-│ (linked from)       │                  │                     │
-└─────────────────────┘                  │                     │
-         ▲                               │                     │
-         │                               │                     │
-┌────────┴────────────┐                  │                     │
-│ Feature / PRD       │                  │                     │
-│                     │                  │                     │
-│ Project ────────────┼─► Project        │                     │
-│ (activity link)     │                  │                     │
-│                     │                  │                     │
-│ Dev Tasks ◄─────────┼──────────────────┼── Feature           │
-│ (linked from)       │                  │   (activity link)   │
-└─────────────────────┘                  │                     │
-                                         │ Blocked By ─────────┼─► Dev Tasks
-                                         │ (activity link)     │
-                                         │                     │
-                                         │ Blocks ◄────────────┼── Blocked By
-                                         │ (linked from)       │   (from other)
-                                         └─────────────────────┘
-```
 
 ---
 
@@ -153,24 +116,22 @@ Notify user: "Setting up project management workflows for this workspace..."
 #### Create Project Planning Workflow
 
 ```typescript
-// Using Hailer MCP or SDK
 {
   name: "Project Planning",
   phases: ["Planning", "In Progress", "On Hold", "Completed"],
   fields: [
     { name: "Title", type: "text" },
-    { name: "Description", type: "longtext" },
-    { name: "Type", type: "predefined_single", options: ["Project", "Feature", "Session Handoff", "PRD"] },
-    { name: "Project", type: "activity_link", linkedWorkflow: "Project Planning" },
-    { name: "Goal", type: "longtext" },
-    { name: "Documentation", type: "longtext" },
-    { name: "Technical Notes", type: "longtext" },
-    { name: "Blockers", type: "longtext" },
-    // PRD fields
-    { name: "User Stories", type: "longtext" },
-    { name: "Acceptance Criteria", type: "longtext" },
-    { name: "Technical Constraints", type: "longtext" },
-    { name: "Out of Scope", type: "longtext" }
+    { 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" }
   ]
 }
 ```
@@ -183,12 +144,12 @@ Notify user: "Setting up project management workflows for this workspace..."
   phases: ["Backlog", "Todo", "In Progress", "Review", "Done"],
   fields: [
     { name: "Title", type: "text" },
-    { name: "Description", type: "longtext" },
-    { name: "Type", type: "predefined_single", options: ["Task", "Bug", "Tech Debt"] },
-    { name: "Priority", type: "predefined_single", options: ["HIGH", "MEDIUM", "LOW"] },
-    { name: "Feature", type: "activity_link", linkedWorkflow: "Project Planning" },
-    { name: "Blocked By", type: "activity_link", linkedWorkflow: "Dev Tasks" },
-    { name: "Related Items", type: "activity_link", linkedWorkflow: "Dev Tasks" },
+    { 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" }
   ]
@@ -330,7 +291,7 @@ Also create/update `SESSION-HANDOFF.md` in project root:
 ### New Feature
 | Field | Value |
 |-------|-------|
-| Title | Feature name (use prefixes: `Sales Orders → Automations`) |
+| Title | Feature name (use arrow prefix for related features: `Sales Orders → Automations`) |
 | Type | `Feature` |
 | Project | Link to parent Project |
 | Phase | `Planning` or `In Progress` |
@@ -339,7 +300,7 @@ Also create/update `SESSION-HANDOFF.md` in project root:
 | Documentation | How it works (fill when complete) |
 | Technical Notes | Architecture decisions |
 
-### New PRD (Product Requirements Document)
+### New PRD
 | Field | Value |
 |-------|-------|
 | Title | `PRD: [Feature Name]` |
@@ -435,54 +396,3 @@ When user requests sync (`/project-status`):
 ## Session Notes
 [Local notes not synced to Hailer]
 ```
-
----
-
-## Naming Conventions
-
-### Features
-Use arrow prefix for related features:
-- `Sales Orders` (main workflow)
-- `Sales Orders → Automations`
-- `Sales Orders → ERP Integration`
-
-### Tasks
-Specific and actionable:
-- `Add customer reference field to orders`
-- `Work on orders`
-
-### Bugs
-Include context:
-- `Order total wrong when discount applied`
-- `Calculation bug`
-
-### PRDs
-Always prefix with "PRD:":
-- `PRD: User Authentication`
-- `PRD: Sales Order Automations`
-
----
-
-## Hailer Project Structure
-
-```
-workspace/              # Local config (check FIRST)
-apps/                   # Frontend apps (if monorepo)
-integrations/           # Backend services (if monorepo)
-.claude/
-  agents/               # Agent definitions
-  hooks/                # Safety hooks
-  skills/               # On-demand documentation
-  commands/             # Slash commands
-  settings.json         # Permissions
-CLAUDE.md               # Project instructions
-DEVELOPMENT.md          # Project state (synced with Hailer)
-SESSION-HANDOFF.md      # Previous session context
-```
-
-### Key Principles
-- **Local-first**: Check `workspace/` before making API calls
-- **Skills before actions**: Load relevant skill before SDK/MCP commands
-- **Hooks protect you**: Push commands require confirmation via hooks
-- **Check scripts**: Run `npm run` to see available commands
-- **Session continuity**: Read SESSION-HANDOFF.md when resuming work

package/.claude/skills/integration-patterns/SKILL.md

@@ -49,8 +49,8 @@ interface Trigger {
 
 interface LinkedProcess {
   processId: string;            // Target workflow ID
-  sourcePhases: string[];       // Move FROM these phases
-  targetPhase: string;          // Move TO this phase
+  fromPhaseIds: string[];       // Move FROM these phases
+  toPhaseId: string;            // Move TO this phase
 }
 ```
 
@@ -70,8 +70,8 @@ interface LinkedProcess {
       "linkedProcesses": [
         {
           "processId": "67dc1b7d3d2c9f6cf9a54690",
-          "sourcePhases": ["67dc1b7d3d2c9f6cf9a54691", "67dc1b7d3d2c9f6cf9a54692"],
-          "targetPhase": "67dc1b7d3d2c9f6cf9a54695"
+          "fromPhaseIds": ["67dc1b7d3d2c9f6cf9a54691", "67dc1b7d3d2c9f6cf9a54692"],
+          "toPhaseId": "67dc1b7d3d2c9f6cf9a54695"
         }
       ]
     }
@@ -121,13 +121,13 @@ async function processTrigger(activityId: string, trigger: Trigger) {
   for (const process of trigger.linkedProcesses) {
     const toMove = linked.filter(a =>
       a.processId === process.processId &&
-      process.sourcePhases.includes(a.phaseId)
+      process.fromPhaseIds.includes(a.phaseId)
     );
 
     if (toMove.length > 0) {
       await client.request('v3.activity.updateMany', [
         toMove.map(a => a._id),
-        { phaseId: process.targetPhase }
+        { phaseId: process.toPhaseId }
       ]);
     }
   }

package/.claude/skills/lsp-setup/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: lsp-setup
-description: How to set up LSP (Language Server Protocol) for Claude Code - enables code intelligence for Lars and other agents
+description: How to set up LSP (Language Server Protocol) for Claude Code - enables code intelligence for sub-agents doing code inspection
 version: 1.0.0
 triggers:
   - LSP not available
@@ -15,7 +15,7 @@ LSP (Language Server Protocol) enables code intelligence features like go-to-def
 
 ## Why LSP?
 
-Without LSP, agents like Lars must guess about code usage via grep/file reads. With LSP:
+Without LSP, sub-agents must guess about code usage via grep/file reads. With LSP:
 - **Accurate dead code detection** - knows if exports are used elsewhere
 - **Type error detection** - without running compiler
 - **Find all references** - across entire codebase
@@ -78,7 +78,7 @@ claude -c
 
 ### Step 5: Test
 
-Ask Lars to find unused code in a TypeScript file:
+Ask a sub-agent to find unused code in a TypeScript file:
 ```
 Find unused code in src/App.tsx
 ```
@@ -109,13 +109,12 @@ The `typescript-lsp` plugin supports:
 | `outgoingCalls` | What this function calls |
 | `prepareCallHierarchy` | Get call hierarchy at position |
 
-## Agents That Use LSP
+## Sub-Agents That Use LSP
 
-| Agent | How They Use LSP |
-|-------|------------------|
-| **Lars** | Primary user - dead code, unused imports, type errors |
-| **Svetlana** | Type checking during code review (optional) |
-| **Giuseppe** | Verify code compiles before build (optional) |
+LSP is most useful for sub-agents doing code inspection:
+- Dead code detection, unused imports, type errors
+- Type checking during code review
+- Verifying code compiles before build
 
 ## Troubleshooting