@agentled/cli 0.7.4 → 0.7.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agentled/cli",
-  "version": "0.7.4",
+  "version": "0.7.5",
   "description": "CLI for Agentled — manage workflows, apps, and knowledge from the command line. Zero context-window cost for AI agents.",
   "type": "module",
   "main": "dist/index.js",
@@ -16,7 +16,7 @@
     "prepublishOnly": "npm run build"
   },
   "dependencies": {
-    "@agentled/core": "^0.2.2",
+    "@agentled/core": "^0.2.3",
     "commander": "^12.0.0"
   },
   "devDependencies": {

package/patterns/v1/08-composed-email-approval.md

@@ -124,6 +124,7 @@ Before wiring a composed-email step into a workflow:
 - [ ] `onApproval.action: "schedule-email"` is set
 - [ ] `next.conditions.approvalRequired: true` on the outgoing edge
 - [ ] Recipient and subject are derived from prior step output, not hardcoded
+- [ ] The output page has `displayConfig.executionNameTemplate` with the entity and outreach state. For single-entity outreach, use `{{entityName}} - Email Drafted` before approval and `{{entityName}} - Email Sent` or `{{entityName}} - Contacted` after the post-send status step, e.g. `Joe Dan - VC Firm Name - Email Drafted`; add `{{today}}` only when a short date helps. For batch runs, summarize counts instead, e.g. `26 May - 4 sourced - 3 contacted`.
 
 ## When to use a generic approval gate instead
 

package/skills/agentled/SKILL.md

@@ -686,6 +686,7 @@ When a workflow sends emails, add an outreach profile input page to `context.inp
 - `next.conditions.approvalRequired: true` — blocks the pipeline until human approval
 - Email body must be email-safe HTML (`<p>`, `<br>`, `<a>`, `<strong>` — no CSS, no scripts)
 - **Never** use separate "draft" + "gmail send" appAction steps for outreach
+- Set an output page `displayConfig.executionNameTemplate` that names the entity and the outreach state. For single-entity outreach, use `{{entityName}} - Email Drafted` before approval and `{{entityName}} - Email Sent` or `{{entityName}} - Contacted` after the post-send status step, e.g. `Joe Dan - VC Firm Name - Email Drafted`; add `{{today}}` only when a short date helps. For batch runs, summarize counts instead, e.g. `26 May - 4 sourced - 3 contacted`.
 
 ## Entity Pipeline Pattern (Source → KG → Process)