hatch3r-board-shared

# Board Shared Reference Shared context for `hatch3r-board-fill`, `hatch3r-board-groom`, `hatch3r-board-pickup`, `hatch3r-board-refresh`, and related board commands. Read once per run and cache. ## §0 Detect Ambiguity + Prerequisite Check (P8 B1) — run at the start of every board command Before reading configuration, validate that prerequisites are met. If any check fails, stop immediately with an actionable error message. For interactive sessions where credentials are missing, use the `agents/shared/user-question-protocol.md` plain-text fallback shape to offer the user a numbered choice (interactive login / paste-token / abort) instead of a bare stop message. 1. **hatch.json exists:** If `.hatch3r/hatch.json` is missing or unreadable, stop with: > "Board commands require a hatch3r project. Run `npx hatch3r init` to set up your project first." 2. **owner/repo configured:** If both top-level `owner`/`repo` and `board.owner`/`board.repo` are empty, stop with: > "Board commands require owner and repo. Run `npx hatch3r config` to set your repository identity, or provide them in `.hatch3r/hatch.json` under the top-level `owner` and `repo` fields." 3. **Platform authentication:** Verify CLI authentication for the configured platform. On failure, ASK via user-question-protocol with three numbered options (interactive login / paste-token / abort) and default to option 1 if no response. - **GitHub:** Run `gh auth status`. If it fails or the `project` scope is missing, ...