fix: unblock the bounty sync, plus board, disciplines and docs corrections

[sl33ty]

Why the board has always been empty

sync-bounties.yml declared permissions: contents: write, pull-requests: write. A permissions: block is a replacement, not an addition, so every scope left out is set to none — including issues. The gh issue list call in scripts/sync-bounties.mjs therefore returned an empty array without erroring, and the job regenerated an empty board, found no diff, and exited green having published nothing.

The evidence is in the last run (30635127205, 31 Jul): it printed zero ::warning:: lines. Had it fetched the two labelled issues and failed to parse them, there would be one warning per issue. Silence means it read nothing at all. Running the same gh issue list locally returns them fine.

Adding issues: read is the whole fix.

Also in here

Bounty table row keys. Rows were keyed on row.title, and hover state tracked by title too. Titles are author-supplied and do collide, which threw a React duplicate-key error and made hovering one row highlight every row sharing its title. Now keyed on the issue URL, hover tracked by index.

Disciplines page on mobile. The page runs to roughly eight phone screens across 9 categories and 43 disciplines, and the category headings live inside DisciplineGrid where Docusaurus never sees them for the "On this page" sidebar — so there was no way to reach Operations except scrolling past everything. Adds a jump bar and card ids. Also swaps the grid track to minmax(min(310px, 100%), 1fr): the fixed 310px minimum forced a column wider than its container below about a 342px viewport and gave the whole page a sideways scroll.

Contributor map notice. It rendered whenever any demo row existed, so the first real registration did not change it — the map went on telling visitors all 26 dots were placeholders while one was a real contributor. Now counts the real rows, and says nothing once the placeholders are gone.

Placeholder award records removed. Previous Bounties and Previous Grants both shipped tables of specific payouts, recipients and completion dates. Neither was a record: both were born fully populated in the initial docs scaffold, the recipient handles appear nowhere in the repo except the cspell dictionary added to make them pass spellcheck, and no bounty has ever reached the board. Replaced with honest empty states. Also deleted docs-bounty/previous-bounties.md, an unreferenced duplicate that kept the invented table reachable by URL.

Video Guide embedded a placeholder YouTube ID that would have served an unrelated video to anyone who found the page. Embed removed until the real one exists.

Docs corrections. What are Bounties claimed every bounty pays in both USDC and ARROW; the form marks both optional and the sync requires only one, so ARROW-only bounties are normal and the page was setting a payment expectation we cannot meet. Its discipline list was also stale, merging Design, Content and Growth into one bullet against the board's nine sections and dropping five disciplines. Creating Bounties had the required-field count wrong (the form enforces five) and now documents the green-but-empty failure mode above.

Bounty table headers move from Departure Mono to Neue Haas Grotesk, to match the project category tabs. Scoped to .theme-doc-markdown .bt-table th so every other table in the docs is untouched.

Verifying the sync fix

This one cannot be proven until it is merged and the workflow is dispatched. After merge: Actions → Sync bounty board data → Run workflow. With at least one bounty-labelled issue present it should open a PR against this branch's base rather than reporting "No bounty data changes".

Note there are currently no bounty-labelled issues: #201 and #167 were test artifacts and have been unlabelled, so a run today would still correctly produce nothing. File a real bounty first, then dispatch.