beads/docs/cli-reference/recompute-blocked.md
Chris Sells 4ea6fa3ac0 docs(emitter): emit Mintlify CLI reference and generated docs.json nav
bd help --docs-root now additionally writes docs/cli-reference/ in Mintlify
form (frontmatter title as H1, extensionless root-relative links, JSX
auto-generated markers since Mintlify parses .md through MDX) and rewrites
the CLI Reference pages array inside docs/docs.json via a textual splice
that leaves the rest of the file byte-identical — the ~113 nav entries are
never hand-maintained. The Docusaurus outputs (docs/CLI_REFERENCE.md,
website/docs/cli-reference/, versioned snapshots) are unchanged.

generate-cli-docs.sh --check seeds docs/docs.json and docs/cli-reference/
into its scratch root and diffs both; check-cli-docs-drift.sh adds them to
GEN_PATHSPECS and the regeneration fingerprint; docs-autofix-push.sh
allowlists the new generated paths; check-doc-flags.sh scans the new
docs/ subdirectories and requires command coverage in docs/cli-reference/.

Includes the initial docs/docs.json scaffold (nav mirrors the Docusaurus
sidebar IA) and the generated docs/cli-reference/ pages.

TDD: new emitter behavior covered in cmd/bd/help_all_test.go
(Mintlify page format, nav splice correctness + idempotence, bare-root
generation without docs.json).
2026-07-12 10:37:07 -07:00

1.2 KiB

title description
bd recompute-blocked Recompute is_blocked for all issues (repairs stale flags after a pull)

{/* AUTO-GENERATED: do not edit manually */}

Generated from bd help --doc recompute-blocked.

Recompute the denormalized is_blocked flag for every issue and wisp.

is_blocked is derived from the dependency graph and maintained automatically by local writes and by a post-pull recompute scoped to what the merge changed. If that scoped recompute is skipped — a recompute that failed after its merge committed, or a conflicted pull resolved by hand — the flag can go stale, and a later pull that merges nothing will not refresh it (bd-6dnrw.37). 'bd ready' trusts the flag, so stale values silently hide ready work or surface blocked work.

This command runs the full recompute unconditionally and commits the result. It is idempotent: on a consistent database it changes nothing. Works in both embedded and server mode (unlike 'bd doctor', which is server-mode only).

Examples: bd recompute-blocked # Repair stale is_blocked flags bd recompute-blocked --json # Machine-parseable {"rows_corrected": N}

bd recompute-blocked [flags]