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).
543 B
543 B
| title | description |
|---|---|
| bd ping | Check database connectivity |
{/* AUTO-GENERATED: do not edit manually */}
Generated from bd help --doc ping.
Lightweight health check that confirms bd can reach its database.
Steps:
- Resolve the .beads workspace
- Open the store (embedded or server)
- Run a trivial query (issue count)
- Report timing
Exit 0 on success, exit 1 on failure.
Examples: bd ping # Quick connectivity check bd ping --json # Structured output for automation
bd ping [flags]