overlord-cli 0.2609270909.0 → 0.2609280950.0

package/dist/connectors/VERSION

@@ -1 +1 @@
-0.3.48
+0.3.49

package/dist/connectors/adapters/antigravity/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://antigravity.google/schemas/v1/plugin.json",
   "name": "overlord",
-  "version": "0.3.48",
+  "version": "0.3.49",
   "description": "Chat-driven access to Overlord mission protocol workflows through skills and MCP.",
   "author": {
     "name": "Cooperativ",

package/dist/connectors/adapters/claude/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.48",
+  "version": "0.3.49",
   "description": "Overlord mission protocol workflow for Claude Code — attach/update/ask/deliver, slash commands, and hook-driven activity capture.",
   "author": {
     "name": "Cooperativ",

package/dist/connectors/adapters/claude/README.md

@@ -52,15 +52,6 @@ The plugin prompts for `overlord_url` and, when needed for non-interactive use,
 claude --plugin-dir /absolute/path/to/Overlord/connectors/adapters/claude
 ```
 
-### Install (published marketplace)
-
-Once published:
-
-```bash
-claude plugin marketplace add cooperativ/overlord-marketplace
-claude plugin install overlord@cooperativ
-```
-
 ### Namespaced components
 
 Inside Claude Code the components are surfaced with the plugin prefix:

package/dist/connectors/adapters/codex/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.48",
+  "version": "0.3.49",
   "description": "Chat-driven access to Overlord mission protocol workflows with hook-driven activity capture.",
   "author": {
     "name": "Cooperativ",

package/dist/connectors/adapters/cursor/.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "overlord",
-  "version": "0.3.48",
+  "version": "0.3.49",
   "description": "Overlord mission protocol workflow for Cursor — attach/update/ask/deliver, slash commands, MCP bridge, and follow-up capture.",
   "author": {
     "name": "Cooperativ",

package/dist/connectors/core/overlord-mission/SKILL.md

@@ -222,8 +222,8 @@ nothing qualifies. Omit the report when none of these facts apply.
 
 #### Writing a human action the operator can complete
 
-Human actions are collected across every mission into the Feed page's **Human actions** rail,
-where the operator reads them without the delivery context. Each item must stand alone:
+Human actions are shown on the delivery card, where the operator reads them without your
+session transcript. Each item must stand alone:
 
 | Field      | Expected   | What to write                                                                                     |
 | ---------- | ---------- | ------------------------------------------------------------------------------------------------- |
@@ -241,7 +241,7 @@ Vague (the operator has to rediscover everything):
 { "action": "Set up the env var for Gemini." }
 ```
 
-Good (the operator can finish it from the rail alone):
+Good (the operator can finish it from the card alone):
 
 ```json
 {

package/dist/connectors/core/scripts/overlord-mcp.mjs

@@ -1228,7 +1228,7 @@ process.stdin.on('data', async chunk => {
         result: {
           protocolVersion: PROTOCOL_VERSION,
           capabilities: { tools: { listChanged: false } },
-          serverInfo: { name: 'overlord-__OVERLORD_ADAPTER_KEY__', version: '0.3.48' }
+          serverInfo: { name: 'overlord-__OVERLORD_ADAPTER_KEY__', version: '0.3.49' }
         }
       });
       continue;

package/dist/index.js

@@ -38714,8 +38714,8 @@ deliver:
       "link":     ".env.example"  // when known. HTTP(S) URL or repo-relative path only.
     }
     Vague: { "action": "Set up the env var for Gemini." } forces the operator to rediscover
-    the name, the place, and the check. Actions are read from the Feed rail without the
-    delivery, so each must stand alone. Overlord adds deterministic_rule actions for new
+    the name, the place, and the check. Actions are read from the delivery card without
+    your transcript, so each must stand alone. Overlord adds deterministic_rule actions for new
     migrations, .env.example edits, dependency manifests, and CI workflow files on its own;
     report those yourself when you can supply the real command and verify step.
   Optional: