@hailer/mcp 1.1.15 → 1.1.17-beta.0

package/.claude/skills/{SDK-function-fields → sdk-function-fields}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: SDK-function-fields
+name: sdk-function-fields
 description: Complete guide to creating calculated function fields in Hailer - workflow, variable types, patterns
 version: 1.2.0
 triggers:
@@ -39,7 +39,7 @@ npm run pull
 // workspace/[Workflow]_[id]/fields.ts
 {
   label: "Total Cost",
-  type: "number",
+  type: "numeric",
   key: "total_cost",
   function: "@function:totalCost",
   functionEnabled: true,
@@ -105,16 +105,11 @@ Run: `npm test`
 npm run fields-push:force
 ```
 
----
+Use `fields-push:force` (not `fields-push`). The non-force variant uses `fast-deep-equal` comparison which may skip `functionVariables` changes — your dependency wiring won't update.
 
-## Variable Types Reference
+### 7. Verify Enum Imports After Pull
 
-| Type | Name | data Array | Returns |
-|------|------|------------|---------|
-| `=` | Current field | `[FieldId]` | Single value |
-| `>` | Forward link | `[LinkFieldId, TargetFieldId]` | Single value |
-| `<` | Backlink | `[WorkflowId, TargetFieldId]` | **Array** |
-| `?` | Static | `[WorkflowId, PhaseId]` | Phase ID string |
+After pull, check enum imports manually. Identical hex suffixes across workflows can resolve to the wrong enum (e.g., `Tasks_FieldIds` vs `Orders_FieldIds` both having a field ending in `_abc123`). Fix any wrong imports before proceeding.
 
 ---
 
@@ -326,20 +321,7 @@ if (item.phase === donePhase || item.phase === archivePhase) {
 
 ## Common Patterns
 
-### Sum from Backlinks
-
-```javascript
-function total(dep) {
-  const prices = dep.prices || [];
-  let sum = 0;
-  for (let i = 0; i < prices.length; i++) {
-    sum += Number(prices[i]) || 0;
-  }
-  return sum;
-}
-```
-
-### Filter by Phase (Complete Example)
+### Sum from Backlinks + Filter by Phase (Complete Example)
 
 **functionVariables config:**
 ```javascript
@@ -485,21 +467,7 @@ function nameWithEmoji(dep) {
 }
 ```
 
-**Key:** Compare against the activity's OWN phase (from `"data"` metadata), not the parent workflow's phase.
-
----
-
-## Code Style
-
-**Use `const` and `let`** - NOT `var`:
-```javascript
-// Correct
-const prices = dep.prices || [];
-let total = 0;
-
-// Wrong
-var prices = dep.prices || [];
-```
+**Key:** Compare against the activity's OWN phase (from `"meta"` metadata), not the parent workflow's phase.
 
 ---
 
@@ -514,7 +482,7 @@ var prices = dep.prices || [];
 7. **updateMany single-workflow rule** - `v3.activity.updateMany` targets one workflow per call. For cascading updates across multiple workflows, create separate function fields per target workflow. Don't mix activities from different workflows in one payload
 8. **Double-wrapped array for generic CRUD** - When outputting a payload for the monolith `POST /api/update-activities` handler, use `[[{_id, phaseId}, ...]]` (double-wrapped). The handler spreads parsed JSON as `updateMany(...args)`, so the first arg must be the array. Single-wrapped `[{_id, phaseId}]` causes "must be an array" validation error
 9. **Empty string validation** - Hailer rejects empty string `''` with "value is not allowed to be empty". Always return `'[]'` or a valid non-empty string as default from function fields
-10. **Data metadata shorthand** - `type: "="` with `data: ["data"]` returns this activity's metadata object (same as `data: ["meta"]`). Similarly, `type: "<"` with `data: [workflowId, "data"]` returns array of metadata objects for linked activities
+10. **Metadata aliases** - `"data"` and `"meta"` are interchangeable aliases. `type: "="` with `data: ["meta"]` (or `data: ["data"]`) returns this activity's metadata object. `type: "<"` with `data: [workflowId, "meta"]` (or `data: [workflowId, "data"]`) returns array of metadata objects for linked activities. Prefer `"meta"` for clarity.
 
 ---