opencode-beads
Advanced tools
+1
-1
| { | ||
| "name": "opencode-beads", | ||
| "version": "0.7.0", | ||
| "version": "0.8.0", | ||
| "type": "module", | ||
@@ -5,0 +5,0 @@ "description": "A plugin for OpenCode that provides integration with the beads issue tracker.", |
+1
-1
@@ -36,3 +36,3 @@ # opencode-beads | ||
| { | ||
| "plugin": ["opencode-beads@0.7.0"] | ||
| "plugin": ["opencode-beads@0.8.0"] | ||
| } | ||
@@ -39,0 +39,0 @@ ``` |
@@ -11,3 +11,3 @@ --- | ||
| - **Tier 1**: Semantic compression (30+ days closed, ~70% size reduction) | ||
| - **Tier 2**: Ultra compression (90+ days closed, ~95% size reduction) | ||
| - **Tier 2**: Ultra compression (90+ days closed) — planned, not yet implemented | ||
@@ -14,0 +14,0 @@ ## Usage |
@@ -19,4 +19,8 @@ --- | ||
| Dolt is the primary storage backend, so manual export is rarely needed. Use `bd export` when you need: | ||
| - A JSONL snapshot for backup | ||
| - A JSONL snapshot of issue records | ||
| - Data migration to another system | ||
| - Sharing issues outside the Dolt workflow | ||
| `bd export` is not a full database backup. It does not capture Dolt branches, | ||
| commit history, working-set state, or non-issue tables. Use `bd backup` for a | ||
| restorable Dolt-native database backup. |
@@ -7,2 +7,5 @@ Load AI-optimized workflow context for beads issue tracking. | ||
| bd prime | ||
| bd prime --memories-only | ||
| ``` | ||
| Use `--memories-only` when a hook should inject durable project memories without the full workflow guide. |
56015
0.62%