oh-my-opencode-beads 0.0.3 → 0.0.5

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/dist/cli/index.js CHANGED
@@ -8877,7 +8877,7 @@ var {
8877
8877
  // package.json
8878
8878
  var package_default = {
8879
8879
  name: "oh-my-opencode-beads",
8880
- version: "0.0.3",
8880
+ version: "0.0.5",
8881
8881
  description: "The Best AI Agent Harness - Batteries-Included OpenCode Plugin with Multi-Model Orchestration, Parallel Background Agents, and Crafted LSP/AST Tools",
8882
8882
  main: "dist/index.js",
8883
8883
  types: "dist/index.d.ts",
@@ -8951,13 +8951,13 @@ var package_default = {
8951
8951
  typescript: "^5.7.3"
8952
8952
  },
8953
8953
  optionalDependencies: {
8954
- "oh-my-opencode-beads-darwin-arm64": "0.0.3",
8955
- "oh-my-opencode-beads-darwin-x64": "0.0.3",
8956
- "oh-my-opencode-beads-linux-arm64": "0.0.3",
8957
- "oh-my-opencode-beads-linux-arm64-musl": "0.0.3",
8958
- "oh-my-opencode-beads-linux-x64": "0.0.3",
8959
- "oh-my-opencode-beads-linux-x64-musl": "0.0.3",
8960
- "oh-my-opencode-beads-windows-x64": "0.0.3"
8954
+ "oh-my-opencode-beads-darwin-arm64": "0.0.5",
8955
+ "oh-my-opencode-beads-darwin-x64": "0.0.5",
8956
+ "oh-my-opencode-beads-linux-arm64": "0.0.5",
8957
+ "oh-my-opencode-beads-linux-arm64-musl": "0.0.5",
8958
+ "oh-my-opencode-beads-linux-x64": "0.0.5",
8959
+ "oh-my-opencode-beads-linux-x64-musl": "0.0.5",
8960
+ "oh-my-opencode-beads-windows-x64": "0.0.5"
8961
8961
  },
8962
8962
  trustedDependencies: [
8963
8963
  "@ast-grep/cli",
@@ -1 +1 @@
1
- export declare const START_WORK_TEMPLATE = "You are starting a beads-driven work session.\n\n## WHAT TO DO\n\n1. **Check for in-progress issues**: Run `bd list --status=in_progress --json` to find work already claimed\n\n2. **Find available work**: Run `bd ready --json` to list issues with no blockers\n\n3. **Decision logic**:\n - If there are in-progress issues:\n - Resume work on the first in-progress issue\n - If no in-progress issues but ready issues exist:\n - If ONE ready issue: auto-select it\n - If MULTIPLE ready issues: show list with priorities, ask user to select\n - If no ready issues:\n - Check `bd blocked --json` for blocked work\n - Report status and ask user what to create or unblock\n\n4. **Claim work**: Run `bd update <id> --status=in_progress` to claim the selected issue\n\n5. **Read issue details** with `bd show <id> --json` and start executing the work\n\n## OUTPUT FORMAT\n\nWhen listing issues for selection:\n```\nAvailable Work (beads ready)\n\nCurrent Time: {ISO timestamp}\nSession ID: {current session id}\n\n1. [{issue-id}] P{priority} - {title}\n2. [{issue-id}] P{priority} - {title}\n\nWhich issue would you like to work on? (Enter number or issue ID)\n```\n\nWhen resuming in-progress work:\n```\nResuming Work Session\n\nActive Issue: [{issue-id}] {title}\nPriority: P{priority}\nStatus: in_progress\n\nReading issue details and continuing work...\n```\n\nWhen auto-selecting single issue:\n```\nStarting Work Session\n\nIssue: [{issue-id}] {title}\nSession ID: {session_id}\nStarted: {timestamp}\n\nClaiming issue and beginning execution...\n```\n\n## CRITICAL\n\n- The session_id is injected by the hook - use it directly\n- Always claim the issue with `bd update` BEFORE starting work\n- Read the FULL issue details with `bd show` before beginning\n- Close issues with `bd close <id>` when work is complete";
1
+ export declare const START_WORK_TEMPLATE = "You are starting a beads-driven work session.\n\n## WHAT TO DO\n\n1. **Check for in-progress issues**: Run `bd list --status=in_progress --json` to find work already claimed\n\n2. **Find available work**: Run `bd ready --json` to list issues with no blockers\n\n3. **Decision logic**:\n - If there are in-progress issues:\n - Resume work on the first in-progress issue\n - Otherwise, if ready issues exist:\n - Auto-select one ready issue (highest priority first, then oldest created)\n - If no ready issues:\n - Check `bd blocked --json` for blocked work\n - Report status and suggest the next unblock/create action\n\n4. **Claim work**: Run `bd update <id> --status=in_progress` to claim the selected issue\n\n5. **Read issue details** with `bd show <id> --json` and start executing the work\n\n## OUTPUT FORMAT\n\nWhen resuming in-progress work:\n```\nResuming Work Session\n\nActive Issue: [{issue-id}] {title}\nPriority: P{priority}\nStatus: in_progress\n\nReading issue details and continuing work...\n```\n\nWhen auto-selecting single issue:\n```\nStarting Work Session\n\nIssue: [{issue-id}] {title}\nSession ID: {session_id}\nStarted: {timestamp}\n\nClaiming issue and beginning execution...\n```\n\n## CRITICAL\n\n- The session_id is injected by the hook - use it directly\n- Always claim the issue with `bd update` BEFORE starting work\n- Read the FULL issue details with `bd show` before beginning\n- Close issues with `bd close <id>` when work is complete";
package/dist/index.js CHANGED
@@ -40188,13 +40188,12 @@ var START_WORK_TEMPLATE = `You are starting a beads-driven work session.
40188
40188
 
40189
40189
  3. **Decision logic**:
40190
40190
  - If there are in-progress issues:
40191
- - Resume work on the first in-progress issue
40192
- - If no in-progress issues but ready issues exist:
40193
- - If ONE ready issue: auto-select it
40194
- - If MULTIPLE ready issues: show list with priorities, ask user to select
40191
+ - Resume work on the first in-progress issue
40192
+ - Otherwise, if ready issues exist:
40193
+ - Auto-select one ready issue (highest priority first, then oldest created)
40195
40194
  - If no ready issues:
40196
- - Check \`bd blocked --json\` for blocked work
40197
- - Report status and ask user what to create or unblock
40195
+ - Check \`bd blocked --json\` for blocked work
40196
+ - Report status and suggest the next unblock/create action
40198
40197
 
40199
40198
  4. **Claim work**: Run \`bd update <id> --status=in_progress\` to claim the selected issue
40200
40199
 
@@ -40202,19 +40201,6 @@ var START_WORK_TEMPLATE = `You are starting a beads-driven work session.
40202
40201
 
40203
40202
  ## OUTPUT FORMAT
40204
40203
 
40205
- When listing issues for selection:
40206
- \`\`\`
40207
- Available Work (beads ready)
40208
-
40209
- Current Time: {ISO timestamp}
40210
- Session ID: {current session id}
40211
-
40212
- 1. [{issue-id}] P{priority} - {title}
40213
- 2. [{issue-id}] P{priority} - {title}
40214
-
40215
- Which issue would you like to work on? (Enter number or issue ID)
40216
- \`\`\`
40217
-
40218
40204
  When resuming in-progress work:
40219
40205
  \`\`\`
40220
40206
  Resuming Work Session
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "oh-my-opencode-beads",
3
- "version": "0.0.3",
3
+ "version": "0.0.5",
4
4
  "description": "The Best AI Agent Harness - Batteries-Included OpenCode Plugin with Multi-Model Orchestration, Parallel Background Agents, and Crafted LSP/AST Tools",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -74,13 +74,13 @@
74
74
  "typescript": "^5.7.3"
75
75
  },
76
76
  "optionalDependencies": {
77
- "oh-my-opencode-beads-darwin-arm64": "0.0.3",
78
- "oh-my-opencode-beads-darwin-x64": "0.0.3",
79
- "oh-my-opencode-beads-linux-arm64": "0.0.3",
80
- "oh-my-opencode-beads-linux-arm64-musl": "0.0.3",
81
- "oh-my-opencode-beads-linux-x64": "0.0.3",
82
- "oh-my-opencode-beads-linux-x64-musl": "0.0.3",
83
- "oh-my-opencode-beads-windows-x64": "0.0.3"
77
+ "oh-my-opencode-beads-darwin-arm64": "0.0.5",
78
+ "oh-my-opencode-beads-darwin-x64": "0.0.5",
79
+ "oh-my-opencode-beads-linux-arm64": "0.0.5",
80
+ "oh-my-opencode-beads-linux-arm64-musl": "0.0.5",
81
+ "oh-my-opencode-beads-linux-x64": "0.0.5",
82
+ "oh-my-opencode-beads-linux-x64-musl": "0.0.5",
83
+ "oh-my-opencode-beads-windows-x64": "0.0.5"
84
84
  },
85
85
  "trustedDependencies": [
86
86
  "@ast-grep/cli",