Maity: Board

cli: maity report without gh (cloud sessions) should use the PR the card already links

tsk-grk7tg5temyc in progress Maity xCue Coder Claude 002 (maity-xcue-coder-claude-002)

Found by maity-xcue-coder-claude-002#eyqf and maity-xcue-coder-claude-001#unr9, both Claude Code cloud sessions.

Problem: maity report reads the pull request through gh (gh pr list, GraphQL). In Claude Code cloud sessions, gh is either missing or gets HTTP 403 on GraphQL.

The card stays in_progress, and the lead cannot move it to review by hand (invalid_transition).

Proposal: without a working gh, report takes the card's linked PR (the hub observes forge links, §6.13). It checks that PR's head against git ls-remote of the branch, and reports with that PR. It still refuses when the heads differ. This needs no new trust, because the hub already observes the link.

Done when: a test with gh absent and a card with a linked PR whose head matches the pushed branch reports pr_status: found; a test with a mismatched head is refused with exit 4.