[User Story] Fix tester-reported module CLI command contracts

[djm81]

User Story

As a first real-use adopter using SpecFact modules through the installed CLI, I want project, codebase, sync, and backlog module commands to match their docs and show actionable help when usage is incomplete so I can recover without reading source code.

Parent Features

• Context Adapters For Validation Evidence #161 Project Bundle Runtime
• Sync Safety For Validation Context Adapters #147 Sync Engine
• [Feature] Code Import Runtime Hardening #234 Codebase Import Runtime Hardening
• Backlog CLI Contract Reliability feature created by this wave

Source Tracking

• Moves ownership for specfact project regenerate crashes with NoneType during bundle processing specfact-cli#586.
• Owns modules side of sync bridge reports specfact-project module missing immediately after successful install check specfact-cli#587 and #588.
• Owns modules side of Semgrep diagnostic reports disabled even when semgrep is installed via uv specfact-cli#590.
• Fixes Backlog auth command group errors with "Missing command" when invoked directly specfact-cli#591 and #592.
• Paired core story: [User Story] Harden CLI command guidance, command inventory, and package-manager runtime checks specfact-cli#594.

Acceptance Criteria

• project regenerate handles missing/null bundle data with a typed diagnostic.
• project sync bridge help/docs/prompts use canonical specfact project sync bridge syntax.
• code import help/docs either support or clearly reject legacy option ordering with migration guidance.
• semgrep/tool diagnostics use active uv/hatch/pip/pipx context.
• backlog auth and delta status comply with the shared CLI error contract.
• Modules publish deterministic generated command overview artifacts and validate docs/prompts/templates against them.

OpenSpec

• Change: tester-module-cli-reliability