Chris Sells
d2f87d50de
* docs(pipeline): pin the generated CLI docs to the released bd; repair main's CLI reference The #4874 squash-merge raced the docs-autofix bot: the bot had pushed a regeneration from main's source onto the PR branch, so the squash landed a contradictory mix — the release-aligned hand-written docs plus a CLI reference re-documenting unreleased commands and flags, with docs.json referencing four pages (heartbeat, migrate-personal, reclaim, unclaim) whose files do not exist. That broken nav fails the docsync guard on main and on every branch cut from it. This restores the intended end state of #4874 and lands the pin that prevents the race from recurring. - Regenerate the CLI reference from a bd built from the v1.1.0 tag (CI's canonical pure-Go build), removing the unreleased commands/flags and fixing the dangling nav entries. - docs/cli-docs.pin names the release tag; scripts/resolve-docs-bd.sh builds and caches a canonical pure-Go bd from that tag, fetching the tag first in shallow CI checkouts. - generate-cli-docs.sh, check-doc-flags.sh, and check-cli-docs-drift.sh resolve bd through the pin and ignore a supplied binary while pinned (BD_DOCS_IGNORE_PIN=1 bypasses), so the drift gates and the autofix bot now enforce docs-match-release instead of docs-match-main. - tools/docsmint detects the pre-overhaul Docusaurus staging layout that bd <= v1.1.0 emits and converts it to the generic form before its normal Mintlify transform (tested); removable once the pin reaches a release whose emitter writes build/cli-docs. - check-doc-flags.sh: run without timeout(1) on macOS instead of failing Check 4. - Decision record: engdocs/decisions/2026-07-17-docs-release-pin.md; the beads-docs skill §8 updated to match. * lint: annotate gosec G705 false positive in the docsmint legacy bridge Same class as the existing nav-splice annotation: a developer tool writing repo Markdown, not a web-output sink.
2.1 KiB
title, description
| title | description |
|---|---|
| bd human | Display a focused help menu showing only the most common commands. |
{/* AUTO-GENERATED: do not edit manually */}
Generated from bd help --doc human.
Display a focused help menu showing only the most common commands.
bd has 70+ commands - many for AI agents, integrations, and advanced workflows. This command shows the ~15 essential commands that human users need most often.
For the full command list, run: bd --help
SUBCOMMANDS: human list List all human-needed beads (issues with 'human' label) human respond <id> Respond to a human-needed bead (adds comment and closes) human dismiss <id> Dismiss a human-needed bead permanently human stats Show summary statistics for human-needed beads
bd human [flags]
bd human dismiss
Dismiss a human-needed bead permanently without responding.
The issue is closed with a "Dismissed" reason and optional note.
Examples: bd human dismiss bd-123 bd human dismiss bd-123 --reason "No longer applicable"
bd human dismiss <issue-id> [flags]
Flags:
--reason string Reason for dismissal (optional)
bd human list
List all issues labeled with 'human' tag.
These are issues that require human intervention or input.
Examples: bd human list bd human list --status=open bd human list --json
bd human list [flags]
Flags:
-s, --status string Filter by status (open, closed, etc.)
bd human respond
Respond to a human-needed bead by adding a comment and closing it.
The response is added as a comment and the issue is closed with reason "Responded".
Examples: bd human respond bd-123 --response "Use OAuth2 for authentication" bd human respond bd-123 -r "Approved, proceed with implementation"
bd human respond <issue-id> [flags]
Flags:
-r, --response string Response text (required)
bd human stats
Display summary statistics for human-needed beads.
Shows counts for total, pending (open), responded (closed without dismiss), and dismissed beads.
Example: bd human stats
bd human stats [flags]