@snarkipus/opencode-beads 0.9.3 → 0.9.4

package/README.md

@@ -30,12 +30,16 @@ Add the version-pinned plugin to `~/.config/opencode/opencode.json`:
 
 ```json
 {
-  "plugin": ["@snarkipus/opencode-beads@0.9.3"]
+  "plugin": ["@snarkipus/opencode-beads@0.9.4"]
 }
 ```
 
 Restart OpenCode. Update the pin explicitly when upgrading; an unpinned package entry is less reproducible.
 
+### 0.9.3 recovery notice
+
+Version 0.9.3 contained command guidance from the withdrawn upstream Beads v1.2.1 release. This plugin did not bundle the `bd` binary or implement database migrations, but it could invoke a consumer-installed v1.2.1 binary through `bd prime`. Even one v1.2.1 execution could migrate the database. Upgrade the plugin package to 0.9.4; if v1.2.1 was installed and may have run, also follow the [upstream database recovery guidance](https://github.com/gastownhall/beads/blob/v1.2.2/docs/RECOVERY-1.2.1.md).
+
 ## Context injection
 
 The plugin runs full `bd prime` when a primary-agent session first receives a message and after compaction. Prime supplies the canonical current workflow, command guidance, and persistent memories; the plugin adds only compact OpenCode-specific safety and delegation guidance.
@@ -67,10 +71,10 @@ Do not edit vendored files directly. Sync and package validation reject provenan
 | Component | Expected range | Validated baseline |
 | --- | --- | --- |
 | OpenCode | 1.18.3 through 1.x | 1.18.15 |
-| `bd` CLI | 1.0.5 through 1.x | 1.1.2 |
+| `bd` CLI | 1.0.5 through 1.x | 1.2.2 |
 | Bun | >=1.3.14 | 1.3.14 |
 
-The adapter builds against paired `@opencode-ai/plugin` and `@opencode-ai/sdk` 1.18.15 releases and declares compatible optional peers from 1.18.3 through stable 1.x. Command and agent provenance is synced from Beads v1.2.1.
+The adapter builds against paired `@opencode-ai/plugin` and `@opencode-ai/sdk` 1.18.15 releases and declares compatible optional peers from 1.18.3 through stable 1.x. Command and agent provenance is synced from Beads v1.2.2 at commit `6c124203e771433a3550c348771a5b5e27fd3c21`.
 
 ## Troubleshooting
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@snarkipus/opencode-beads",
-  "version": "0.9.3",
+  "version": "0.9.4",
   "type": "module",
   "description": "A maintained OpenCode integration for the Beads issue tracker, including context injection, vendored workflows, and a task agent.",
   "author": "Matt Jackson",

package/vendor/commands/audit.md

@@ -1,6 +1,6 @@
 ---
 description: Log and label agent interactions (append-only JSONL)
-argument-hint: "record|label"
+argument-hint: record|label
 ---
 
 Append-only audit logging for agent interactions (prompts, responses, tool calls) in `.beads/interactions.jsonl`.
@@ -25,3 +25,4 @@ Each line is one event. Labeling is done by appending a new `"label"` event refe
 - Audit entries are **append-only** (no in-place edits).
 - `bd dolt push` includes `.beads/interactions.jsonl` in the commit allowlist.
 
+

package/vendor/commands/blocked.md

@@ -1,6 +1,6 @@
 ---
 description: Show blocked issues
-argument-hint: ""
+argument-hint: []
 ---
 
 Show all issues that are blocked by dependencies.

package/vendor/commands/close.md

@@ -1,6 +1,6 @@
 ---
 description: Close a completed issue
-argument-hint: "[issue-id] [reason]"
+argument-hint: [issue-id] [reason]
 ---
 
 Close a beads issue that's been completed.

package/vendor/commands/comments.md

@@ -1,6 +1,6 @@
 ---
 description: View or manage comments on an issue
-argument-hint: "[issue-id]"
+argument-hint: [issue-id]
 ---
 
 View or add comments to a beads issue.

package/vendor/commands/compact.md

@@ -1,6 +1,6 @@
 ---
 description: Compact old closed issues using semantic summarization
-argument-hint: "[--all] [--id issue-id] [--dry-run]"
+argument-hint: [--all] [--id issue-id] [--dry-run]
 ---
 
 Reduce database size by summarizing closed issues no longer actively referenced.

package/vendor/commands/create.md

@@ -1,6 +1,6 @@
 ---
 description: Create a new issue interactively
-argument-hint: "[title] [type] [priority]"
+argument-hint: [title] [type] [priority]
 ---
 
 Create a new beads issue. If arguments are provided:

package/vendor/commands/decision.md

@@ -1,6 +1,6 @@
 ---
 description: Record, list, and manage project decisions with rationale tracking
-argument-hint: "record|list|show|supersede"
+argument-hint: record|list|show|supersede
 ---
 
 Record and track project decisions as beads issues with structured rationale, alternatives considered, and links to affected work.
@@ -9,7 +9,7 @@ Decisions use `--type decision`. The description field holds the structured deci
 
 ## Record a Decision
 
-When the user wants to record a decision (i.e. the `record` action of this command):
+When the user wants to record a decision (or you invoke `bd decision record`):
 
 1. Gather the following (ask if not provided):
    - **Title**: Short summary of what was decided (required)

package/vendor/commands/delete.md

@@ -1,6 +1,6 @@
 ---
 description: Delete issues and clean up references
-argument-hint: "[issue-ids...] [--force]"
+argument-hint: [issue-ids...] [--force]
 ---
 
 Delete one or more issues and clean up all references.

package/vendor/commands/dep.md

@@ -1,6 +1,6 @@
 ---
 description: Manage dependencies between issues
-argument-hint: "[command] [from-id] [to-id]"
+argument-hint: [command] [from-id] [to-id]
 ---
 
 Manage dependencies between beads issues.

package/vendor/commands/epic.md

@@ -1,6 +1,6 @@
 ---
 description: Epic management commands
-argument-hint: "[command]"
+argument-hint: [command]
 ---
 
 Manage epics (large features composed of multiple issues).
@@ -21,9 +21,6 @@ Manage epics (large features composed of multiple issues).
 1. Create epic: `bd create "Large Feature" -t epic -p 1`
 2. Link subtasks: `bd dep add bd-20 bd-10 --type parent-child` (task bd-20 is child of epic bd-10)
    - Or at creation: `bd create "Subtask title" -t task --parent bd-10`
-   - Children inherit parent labels by default. If the epic uses size/effort
-     labels and children should have their own, add `--no-inherit-labels`
-     (GH#4562).
 3. Track progress: `bd epic status`
 4. Auto-close when done: `bd epic close-eligible`
 

package/vendor/commands/export.md

@@ -1,6 +1,6 @@
 ---
 description: Export issues to JSONL format
-argument-hint: "[-o output-file]"
+argument-hint: [-o output-file]
 ---
 
 Export all issues to JSON Lines format (one JSON object per line).
@@ -9,7 +9,7 @@ Export all issues to JSON Lines format (one JSON object per line).
 
 - **To stdout**: `bd export`
 - **To file**: `bd export -o issues.jsonl`
-- **Include all records**: `bd export --all -o full.jsonl`
+- **Filter by status**: `bd export --status open`
 
 Issues are sorted by ID for consistent diffs, making git diffs readable.
 

package/vendor/commands/import.md

@@ -1,84 +1,18 @@
 ---
-description: Import issues and memories from JSONL
-argument-hint: "[file|-] [--input file] [--dry-run] [--dedup] [--allow-stale]"
+description: Import issues from JSONL format (removed)
+argument-hint: (removed)
 ---
 
-`bd import` imports newline-delimited JSON into an existing Beads database.
-Issues with new IDs are created and existing IDs use guarded upsert semantics.
-The command is not supported in proxied-server mode.
+`bd import` has been **removed**.
 
-## Usage
+## Migration
+
+If you need to import issues from a JSONL file, use `bd init` with the `--from-jsonl` flag:
 
 ```bash
-bd import                         # Read .beads/<import.path>
-bd import backup.jsonl            # Read a specific file
-bd import --input backup.jsonl    # Same as -i backup.jsonl
-bd import -                       # Read JSONL from stdin
-bd export --include-memories | bd import - # Round-trip issues and memories
-bd import --dry-run backup.jsonl  # Parse and report without writing
-bd import --json backup.jsonl     # Return a structured result
+bd init <prefix> --from-jsonl issues.jsonl
 ```
 
-With no file argument, the source is the `import.path` file under `.beads/`;
-`import.path` defaults to `issues.jsonl`. Use either a positional file or
-`--input`/`-i`, not both. The special path `-` reads stdin. With `--global` and
-no file, the source is `global-issues.jsonl` in the active Beads directory.
-
-Each non-empty line must be a JSON object. Issue records accept the schema
-emitted by `bd export`; `title` is the only required issue field. Records with
-`"_type":"memory"` and non-empty `key` and `value` fields are imported as
-persistent memories. Optional export header records are ignored, and tombstone
-rows are skipped. `bd export` omits memories by default; add
-`--include-memories` or `--all` when they should be carried into an import.
-
-## Merge and Safety Semantics
-
-For records that supply `updated_at`, an incoming row rewrites an existing
-issue only when its timestamp is strictly newer. Older records are skipped
-wholesale, including their labels, comments, and dependencies. When timestamps
-are equal, the local issue row wins, while those auxiliary records still merge.
-The stale check is repeated inside the upsert so a concurrent newer local update
-is not overwritten.
-
-If `updated_at` is omitted, the importer fills it with the current time during
-the write. A record naming an existing ID can therefore overwrite local state;
-include the exported timestamp when stale protection matters.
-
-Use `--allow-stale` only when deliberately restoring an older snapshot: it
-disables that guard and can overwrite newer local issue state. Imports are
-upserts, and labels, comments, and dependencies are deduplicated. Re-running
-canonical export data or other input with stable issue IDs and preserved
-`updated_at` values is safe and converges. Without a preserved timestamp, each
-run can appear newer and rewrite the row. An issue record without an ID is
-assigned one; re-importing it can create another issue instead of targeting the
-first.
-
-Large issue imports use bounded SQL transaction chunks. If one fails, the
-command exits nonzero and keeps the already committed prefix in the Dolt working
-set; no final import-summary Dolt commit is created. Re-run stable-ID input to
-resume only when its `updated_at` values are also preserved.
-
-After a successful non-dry import with accepted issue or memory records, the
-command calls `store.Commit` with an import summary regardless of the
-`dolt.auto-commit` policy. That commit can include unrelated pending working-set
-changes; in direct server mode, config (including memories) is excluded from
-this commit. When commit isolation matters, run `bd doctor` before importing and
-proceed only when its Dolt Status check reports a clean working set.
-
-The database must already exist; initialize or bootstrap it before importing.
-Use `--dry-run` to parse the input, apply optional title deduplication, and
-report issue and memory counts without writing. It does not run write-time field
-validation or predict stale skips and updates.
-
-## Flags
+## Note
 
-- `--input`, `-i <file>`: read a specific file instead of a positional path.
-- `--dry-run`: report parsed record counts without writing.
-- `--dedup`: skip an input issue whose title exactly matches, ignoring case, an
-  existing non-closed issue. Input rows are not compared with one another; if
-  the existing-issue search fails, title filtering is skipped.
-- `--allow-stale`: import older rows too, allowing newer local state to be
-  overwritten.
-- `--json`: use global JSON-output mode for structured counts and IDs. The
-  `created` count is accepted issue rows, including existing rows, not only new
-  inserts.
+Dolt is the primary storage backend. Manual JSONL import is no longer supported as a standalone command.

package/vendor/commands/init.md

@@ -1,6 +1,6 @@
 ---
 description: Initialize beads in the current project
-argument-hint: "[prefix]"
+argument-hint: [prefix]
 ---
 
 Initialize beads issue tracking in the current directory.

package/vendor/commands/label.md

@@ -1,6 +1,6 @@
 ---
 description: Manage issue labels
-argument-hint: "[command] [issue-id] [label]"
+argument-hint: [command] [issue-id] [label]
 ---
 
 Manage labels on beads issues. Labels provide flexible cross-cutting metadata beyond structured fields (status, priority, type).

package/vendor/commands/list.md

@@ -1,6 +1,6 @@
 ---
 description: List issues with optional filters
-argument-hint: "[--status] [--priority] [--type] [--assignee] [--label]"
+argument-hint: [--status] [--priority] [--type] [--assignee] [--label]
 ---
 
 List beads issues with optional filtering.

package/vendor/commands/quickstart.md

@@ -1,9 +1,9 @@
 ---
 description: Quick start guide for bd workflows (deprecated)
-argument-hint: ""
+argument-hint: []
 ---
 
-**Note:** The `bd quickstart` command is deprecated. See the [Quick Start](https://beads.gascity.com/getting-started/quickstart) on the documentation site, or the in-repo source [docs/getting-started/quickstart.md](https://github.com/gastownhall/beads/blob/main/docs/getting-started/quickstart.md).
+**Note:** The `bd quickstart` command is deprecated. See the [Quick Start](https://gastownhall.github.io/beads/getting-started/quickstart) on the documentation site, or the repo pointer [docs/QUICKSTART.md](../docs/QUICKSTART.md).
 
 The quickstart documentation covers:
 - Getting started with bd

package/vendor/commands/rename-prefix.md

@@ -1,6 +1,6 @@
 ---
 description: Rename the issue prefix for all issues
-argument-hint: "<new-prefix> [--dry-run]"
+argument-hint: <new-prefix> [--dry-run]
 ---
 
 Rename the issue prefix for all issues in the database.
@@ -9,6 +9,7 @@ Updates all issue IDs and all text references across all fields.
 
 ## Prefix Rules
 
+- Max length: 8 characters
 - Allowed: lowercase letters, numbers, hyphens
 - Must start with a letter
 - Must end with a hyphen (e.g., 'kw-', 'work-')

package/vendor/commands/reopen.md

@@ -1,6 +1,6 @@
 ---
 description: Reopen closed issues
-argument-hint: "[issue-ids...] [--reason]"
+argument-hint: [issue-ids...] [--reason]
 ---
 
 Reopen one or more closed issues.

package/vendor/commands/restore.md

@@ -1,6 +1,6 @@
 ---
 description: Restore full history of compacted issue from git
-argument-hint: "<issue-id>"
+argument-hint: <issue-id>
 ---
 
 Restore full history of a compacted issue from git version control.

package/vendor/commands/search.md

@@ -1,6 +1,6 @@
 ---
 description: Search issues by text query
-argument-hint: "<query> [--status] [--label] [--assignee]"
+argument-hint: <query> [--status] [--label] [--assignee]
 ---
 
 Search issues across title, description, and ID with a simple text query.

package/vendor/commands/show.md

@@ -1,6 +1,6 @@
 ---
 description: Show detailed information about an issue
-argument-hint: "[issue-id]"
+argument-hint: [issue-id]
 ---
 
 Display detailed information about a beads issue.

package/vendor/commands/sync.md

@@ -1,109 +1,17 @@
 ---
-description: Synchronize issues with a configured Dolt remote
-argument-hint: ""
+description: Synchronize issues (deprecated — use bd dolt push/pull)
+argument-hint: (deprecated)
 ---
 
-`bd sync` runs one full synchronization cycle against the configured Dolt
-remote: pull, check for merge conflicts, recompute the denormalized
-`is_blocked` flag, then push — retrying a bounded number of times when another
-replica wins the push race. It is the loop a multi-machine deployment otherwise
-hand-rolls in shell, and it is the verb to reach for on a sync timer.
+`bd sync` is **deprecated** and is now a no-op.
 
-(This is not the old JSONL-era `bd sync`, which was removed in v0.51. Nested
-commands such as `bd backup sync` and the tracker-specific sync commands are
-separate commands and are unaffected.)
+## Use Dolt commands instead
 
-```bash
-bd sync                  # sync with the default remote
-bd sync --remote mini    # sync with a specific named remote
-bd sync --attempts 5     # allow more push-race retries (default 3)
-bd sync --json           # machine-parseable outcome
-```
-
-Exit codes are the machine contract, so a timer can branch on them without
-parsing output:
-
-| Code | Meaning |
-|------|---------|
-| `0` | Synced, or nothing to do |
-| `1` | Error (transport, auth, storage) |
-| `2` | Merge conflict — halted, nothing pushed; resolve it by hand |
-| `3` | Push-race retries exhausted — transient, retry on the next tick |
-
-Two properties are the point of the verb. Conflicts are detected **positively**,
-from the merge's own conflict rows and from Dolt's conflict tables — never
-inferred from the pull's exit status, which is untrustworthy in both directions.
-And a conflict sync cannot settle is **never** resolved by picking a side: it
-halts before recomputing or pushing, and keeps halting the same way until an
-operator resolves the divergence. (The pull underneath still auto-settles the
-convergent conflict classes it always has — machine-local metadata rows,
-audit-only dependency rows, last-write-wins on issue cells. Anything past those
-halts here.)
-
-The halt message says which state the halt left behind, because it depends on
-the pull route and both are real: the SQL route aborts the conflicted merge and
-restores the working set, while the CLI/git-protocol route leaves the conflict
-rows **live** for you. A conflict that was already live when sync started — from
-an earlier halted sync or a hand-run merge — halts before the pull instead, and
-says that too.
-
-The recompute between pull and push is not bookkeeping either — `is_blocked` is
-denormalized, so a dependency edge merged in from another replica leaves
-`bd ready` stale until it runs. It runs on every attempt, unconditionally:
-`bd recompute-blocked`'s full pass is specifically the repair that does *not*
-depend on a merge advancing HEAD, so it is what recovers a column left stale by
-a conflicted pull you resolved by hand — a state sync itself creates by exiting
-2. Gating it on "did this tick merge anything" would mean that repair never runs
-again while every tick reports success.
-
-This is not `bd federation sync`, which syncs with named peer towns and takes a
-`--strategy ours|theirs` to resolve whatever conflicts it meets. `bd sync`
-targets the configured remote and has no such switch.
-
-`--json` reports `{"status", "attempts", "conflicts", "conflicts_live",
-"rows_corrected", "pushed"}` on every non-error exit; exit 1 emits bd's standard
-`{"error": ...}` envelope instead, so a timer reading `.status` must treat
-`null` as the error case (or just branch on the exit code, which is the point).
-A rig with no remote configured exits 0 with setup guidance; `dolt.local-only`
-and the `no-push` config flag are honored.
-
-## The equivalent by hand
-
-```bash
-# Before starting work or consuming changes from another clone
-bd dolt pull
-
-# After local issue updates and before handoff: commit, integrate, then publish
-bd dolt commit
-bd dolt pull
-bd dolt push
-```
-
-`bd dolt commit` creates an explicit commit boundary when auto-commit is off or
-in batch mode; it is a safe no-op when there is nothing pending. The following
-pull integrates remote changes before the final push. The pull steps require a
-configured remote; use the one-time setup below first when needed.
-
-Inspect the configured Dolt remotes with:
-
-```bash
-bd dolt remote list
-```
-
-If no Dolt remote exists, the project has a Git origin, and remote sync is
-enabled, `bd dolt push` automatically adopts that origin; do not add the
-matching URL manually. To use a distinct custom Dolt remote, first confirm that
-the chosen name is absent, then add it explicitly:
-
-```bash
-bd dolt remote add origin <distinct-dolt-remote-url>
-```
+- **Push to remote**: `bd dolt push`
+- **Pull from remote**: `bd dolt pull`
+- **Commit pending changes**: `bd dolt commit`
+- **Check connection**: `bd dolt show`
 
 ## Note
 
-When enabled, `dolt.auto-commit` records successful writes in local Dolt
-history; it does not push them to a remote. Remote auto-push is a separate,
-opt-in setting and is disabled by default. Auto-push publishes committed HEAD
-only; it does not commit pending working-set writes when auto-commit is off or
-in batch mode. Keep an explicit commit boundary before handoff unless the
-project has a coordinated policy that provides one.
+Most users should rely on the Dolt server's automatic sync (with `dolt.auto-commit` enabled) instead of running manual sync commands.

package/vendor/commands/update.md

@@ -1,6 +1,6 @@
 ---
 description: Update an issue's status, priority, or other fields
-argument-hint: "[issue-id] [status]"
+argument-hint: [issue-id] [status]
 ---
 
 Update a beads issue.

package/vendor/manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 1,
   "repository": "https://github.com/gastownhall/beads.git",
-  "tag": "v1.2.1",
-  "commit": "634cbbc4bc580fa5124f63fdf65d137a46d5b4ff",
+  "tag": "v1.2.2",
+  "commit": "6c124203e771433a3550c348771a5b5e27fd3c21",
   "sources": [
     {
       "source": "plugins/beads/agents/task-agent.md",
@@ -21,78 +21,78 @@
     },
     {
       "path": "commands/audit.md",
-      "bytes": 956,
-      "sha256": "bf941ae72f3dfad0e5a0997c8afa1647d6ce17934692efa30e9fe4da98e39de8"
+      "bytes": 955,
+      "sha256": "8a7f942b3b94576f8503cba282c9144953991ab2a76926323ab6ee895d33b9c5"
     },
     {
       "path": "commands/blocked.md",
       "bytes": 561,
-      "sha256": "30181c3645b5e233005facde694a3bb001c5935258745ae976abfe7b93eec346"
+      "sha256": "14822b644bb93d9f038107aaccf1eb5112e3e0b1cb0b9c013cb6dffbfe570335"
     },
     {
       "path": "commands/close.md",
-      "bytes": 585,
-      "sha256": "ef43e31c9f86082a6192ca131c175c55ee37dc115f4781413be11f1e85274b58"
+      "bytes": 583,
+      "sha256": "413946f6210b743398e1510a9806ac1c51c6d6e994d020e7e122062cc69ffd97"
     },
     {
       "path": "commands/comments.md",
-      "bytes": 967,
-      "sha256": "cad54141ee590be3b8d07878bb3ea34c252466bbb00a9b95d7d521303a8e3b83"
+      "bytes": 965,
+      "sha256": "9680911b297bdf24cb943c5dd7f71812cd60e0f9ef52a57bf1832110e02d5efc"
     },
     {
       "path": "commands/compact.md",
-      "bytes": 1083,
-      "sha256": "5204417505320501e2c5a529da6c670826ef5b62feab708a33b7452dfd6a80c4"
+      "bytes": 1081,
+      "sha256": "0fc6810f4e4da2d521d747c50c73e3a388bf16a94dc47ddf241a52826071d766"
     },
     {
       "path": "commands/create.md",
-      "bytes": 651,
-      "sha256": "1e27f3ff4f3ae041f6896b5181f0b0399ff80d52cd415dfd8cf6584a218736d3"
+      "bytes": 649,
+      "sha256": "f70104bd3792e5f005d0d7f2901c2b56da7f0136bf279f6d36e36d89b553bb93"
     },
     {
       "path": "commands/decision.md",
-      "bytes": 2670,
-      "sha256": "78c0de4a0979502cb553c2ad49df32cc1e6a7cb3eec25dc41f60290ad4fbbe36"
+      "bytes": 2662,
+      "sha256": "d62efc7e0d0bcd3a080e825b315acbf42c024d937382d8b8cf83b47016d4f908"
     },
     {
       "path": "commands/delete.md",
-      "bytes": 961,
-      "sha256": "a6a5e943cccc75c27820548ec4a810894be646604b98821822968c7cb55552eb"
+      "bytes": 959,
+      "sha256": "90424c81aac3d2b12379820aa0b6f5e37a60a0da33474d28c66e0422b8361532"
     },
     {
       "path": "commands/dep.md",
-      "bytes": 3410,
-      "sha256": "2d50ea5c65e0ce27bc076e77de5ea32de7086b34c6f49736e71517548cfe4b76"
+      "bytes": 3408,
+      "sha256": "2679ab80bfade1f6d4769ecef2575b196592c919cc36912e9fa8f29ab2a7d9f5"
     },
     {
       "path": "commands/epic.md",
-      "bytes": 1027,
-      "sha256": "174f54e3092e5a4b2f4c010e95418b13f1d910e185349ba0e131b04cf5783b8b"
+      "bytes": 858,
+      "sha256": "b31ffcfc2a423684f153042a0cb67b2d0472b63da594691b3c2656ed00cf2d6c"
     },
     {
       "path": "commands/export.md",
-      "bytes": 800,
-      "sha256": "5c8e9c9b4df71c804f489fa5785d607be971b7f62c836ad531f11e8b105ee47a"
+      "bytes": 789,
+      "sha256": "dc021e36c11c3ad2724f3097c6f461221d77e5bd26296e6db65b8bd5f5190be0"
     },
     {
       "path": "commands/import.md",
-      "bytes": 4433,
-      "sha256": "604e48e6d093d9a93f28a3a5ed7dd7946b10e7a4897bec8a88eefc5b6c9c776e"
+      "bytes": 401,
+      "sha256": "4f2b270a3f55d5b48f615864c07408bec3b339cd9ccab581e1e3c7c6ecd27e0e"
     },
     {
       "path": "commands/init.md",
-      "bytes": 753,
-      "sha256": "975759ee3d7ac6611fa54ae27c277a2995288a8fd089e6b46b791f73f3322177"
+      "bytes": 751,
+      "sha256": "68413502bcb73f25cbf7505e3951967bffb8e125f6647e98018588558171abae"
     },
     {
       "path": "commands/label.md",
-      "bytes": 898,
-      "sha256": "45f0422cce8764a19158a98e95b6b3c790e7a01b3438d9b5471ddb5f8c544129"
+      "bytes": 896,
+      "sha256": "82b702f10b31caf1c538119a5ae70603c88a7534de33bec2662b67a039a45572"
     },
     {
       "path": "commands/list.md",
-      "bytes": 2628,
-      "sha256": "990a0e6ef5af6a6ec596df32590750efd27fd231a44a0882d3f900dc71a4380f"
+      "bytes": 2626,
+      "sha256": "a986fdc0400c5e637f9e2103775f6b0c0297e48f96b0d2d1f8ecd15f14b7c524"
     },
     {
       "path": "commands/prime.md",
@@ -101,8 +101,8 @@
     },
     {
       "path": "commands/quickstart.md",
-      "bytes": 537,
-      "sha256": "de372b2dac3b1786ee383e8295bca781d6ce890db0daa09efa4d044325b80bbc"
+      "bytes": 469,
+      "sha256": "ee1d55aad65e7f5d293a394517964719b1bff1e4d7c92ccf55e2125608473bee"
     },
     {
       "path": "commands/ready.md",
@@ -111,28 +111,28 @@
     },
     {
       "path": "commands/rename-prefix.md",
-      "bytes": 574,
-      "sha256": "2e6a457dfe58a855daecc0581433584073d7b52565a9bdb85131d1b4a3d920e8"
+      "bytes": 599,
+      "sha256": "0315a4e4c8ddfd3ec6006f30f80de69c25d1cf3cab43d6bfa3d657b551437b60"
     },
     {
       "path": "commands/reopen.md",
-      "bytes": 595,
-      "sha256": "ea5535f0004d3137f05b6fc81cff1ecc670d918465b7d878eb6cb01d2427578c"
+      "bytes": 593,
+      "sha256": "db2927072ffbc3dbde644a123f877e4cb9a46df87c1252ab1256f8fa1f75a41e"
     },
     {
       "path": "commands/restore.md",
-      "bytes": 714,
-      "sha256": "94928e7b5d8ca1da80571e56685020f31eba6ce8fd38100cba09f00a051e164e"
+      "bytes": 712,
+      "sha256": "8cda7ebcaa572572cf55e4f1a2b15e028a01f7c373842c941c7f6fabbcecb4d2"
     },
     {
       "path": "commands/search.md",
-      "bytes": 3190,
-      "sha256": "2295d2cf34f0d7c3a74fab86f73aa312435870c97aa71d8c965486a450310085"
+      "bytes": 3188,
+      "sha256": "5d07fd4bd26bd90a31f2d0c58b8e1245234f3a897c2d2fe326b5f372ea2a9ecd"
     },
     {
       "path": "commands/show.md",
-      "bytes": 563,
-      "sha256": "51aa4b5a5bebeb9f1027f5a31a3de307dd8116052471f40272f0b2c980c720af"
+      "bytes": 561,
+      "sha256": "e170d3d532954aeea5c20eb2b1ea96625f17069d2cd6f9ff81317c05c13dda80"
     },
     {
       "path": "commands/stats.md",
@@ -141,8 +141,8 @@
     },
     {
       "path": "commands/sync.md",
-      "bytes": 4964,
-      "sha256": "09d999165b93ea183e5828c94d45498503ed179211db5f68b3c32f372ade9ac7"
+      "bytes": 493,
+      "sha256": "7ac9938d0e5ec0514edefc240971b4a0aade61cffca75efefac4011117d53ebb"
     },
     {
       "path": "commands/template.md",
@@ -151,8 +151,8 @@
     },
     {
       "path": "commands/update.md",
-      "bytes": 870,
-      "sha256": "34896bde7871805fb1941afd81a25ebc2ce1030090b8ce96afc63763bd2bd108"
+      "bytes": 868,
+      "sha256": "ff12a4ac6a686a11e2a029aac7070829051662027a868794717b1d3fee255d66"
     },
     {
       "path": "commands/version.md",