verify-bb

# Verify BB Run from the repository root. Start with [the feature map](features/README.md) and select the affected journeys. Read `docs/debugging-and-qa.md` for the source development workflow. The launch below targets the source web app and local host daemon. Desktop, native mobile, and hosted services have additional setup in their feature files. A pass on one platform does not verify another. ## Coverage and selection The feature map aims to inventory every feature discoverable in this checkout, including disabled plugins, compatibility paths, and developer surfaces. Group files contain individual capability recipes. Read only the relevant files for a focused verification request; for an exhaustive audit, track every recipe. Mark each selected recipe `passed`, `failed`, `not run`, or `blocked` with its specific prerequisite and evidence. Group-level source coverage never upgrades an unexecuted recipe to a pass. Run the read-only inventory check before selecting coverage: ```bash .bb/skills/verify-bb/scripts/inventory.py ``` Python 3 and Git are required. The check compares source declarations and fingerprints with [INVENTORY.md](INVENTORY.md) and `inventory.json`, and requires all recipe owners to exist. On drift, inspect the changed source, add/update recipes and their prerequisites, then run `scripts/inventory.py --write` via its full path above and review the diff. Never accept a new baseline merely to silence the check. It watches CLI families, app routes/actions...