overlord-cli 4.3.0 → 4.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "overlord-cli",
3
- "version": "4.3.0",
3
+ "version": "4.6.0",
4
4
  "description": "Overlord CLI — launch AI agents on tickets from anywhere",
5
5
  "type": "module",
6
6
  "bin": {
@@ -4,7 +4,7 @@ Claude Code plugin that exposes the Overlord local ticket workflow to any Claude
4
4
 
5
5
  ## What ships
6
6
 
7
- - `skills/overlord-ticket-workflow/SKILL.md` — durable attach → update → ask → deliver workflow.
7
+ - `skills/overlord-ticket/SKILL.md` — durable attach → update → ask → deliver workflow.
8
8
  - `commands/{connect,load,spawn}.md` — slash commands for session routing and ticket creation.
9
9
  - `hooks/hooks.json` + `scripts/permission-hook.sh` — PermissionRequest notifier that posts to `/api/protocol/permission-request` on the Overlord platform.
10
10
  - `userConfig` for `overlord_url` (non-sensitive) and `agent_token` (sensitive → OS keychain) so the hook and CLI know where to talk.
@@ -35,7 +35,7 @@ The plugin prompts for `overlord_url` and `agent_token` at install time. The tok
35
35
 
36
36
  Inside Claude Code the components are surfaced with the plugin prefix:
37
37
 
38
- - skill → `overlord:overlord-ticket-workflow`
38
+ - skill → `overlord:overlord-ticket`
39
39
  - commands → `/overlord:connect`, `/overlord:load`, `/overlord:spawn`
40
40
 
41
41
  Prompts generated by Overlord (see `lib/overlord/ticket-prompt.ts`) already reference these names in `bundle` instruction mode.
@@ -1,9 +1,9 @@
1
1
  ---
2
- name: overlord-ticket-workflow
2
+ name: overlord-ticket
3
3
  description: Overlord local workflow protocol — attach, update, deliver lifecycle for ticket-driven work from Claude Code.
4
4
  ---
5
5
 
6
- # Overlord Local Workflow
6
+ # Overlord Ticket
7
7
 
8
8
  If you receive a prompt with a specified ticket ID, adhere to the following. If the prompt does not have a ticket ID, the user may choose to add one later, but otherwise, proceed without it.
9
9
 
@@ -1,8 +1,8 @@
1
1
  ---
2
- name: overlord-ticket-workflow
2
+ name: overlord-ticket
3
3
  description: Durable local workflow for Overlord tickets from Cursor.
4
4
  ---
5
5
 
6
- # Overlord Ticket Workflow
6
+ # Overlord Ticket
7
7
 
8
8
  Attach first with `ovld protocol attach --ticket-id <ticket-id>`, keep the `sessionKey`, post updates during implementation, and deliver last with change rationales.
@@ -30,7 +30,7 @@ The MCP server shells into the installed `ovld` binary so the plugin stays align
30
30
 
31
31
  ## Skill coverage
32
32
 
33
- - `skills/overlord-ticket-workflow/SKILL.md` teaches Codex the durable local workflow:
33
+ - `skills/overlord-ticket/SKILL.md` teaches Codex the durable local workflow:
34
34
  attach first, update during work, ask when blocked, and deliver last.
35
35
 
36
36
  ## App surface status
@@ -1,4 +1,4 @@
1
- # Overlord Ticket Workflow
1
+ # Overlord Ticket
2
2
 
3
3
  Use this skill when the user wants to work on an Overlord ticket from Codex through the local
4
4
  Overlord plugin.