Grey out menu options the game would refuse, with the reason

[dmccoystephenson]

Summary

An option the player had earned but couldn't use right now looked exactly like one they could. The only way to find out you were too tired to fish was to pick Fish and be told so afterwards — the same for buying gear you can't afford, withdrawing from an empty account, or guessing a dice face before staking anything.

Every front-end now shows those options as unpickable and says why on the row itself.

• showOptions takes an optional {optionNumber: reason} mapping. Call sites key by 1-based option number because these menus are built by appending — len(optionList) right after an append is always the row just added, so the numbers can't drift as options appear and disappear with progression. BaseUserInterface.unavailableReasons() converts it once into a list parallel to the options.
• Web (web/client.js, shared by the server-backed and Pyodide front-ends): a greyed-out, disabled button carrying the reason in its own span, plus a tooltip; its number key is inert too.
• Console: the row is tagged (unavailable: ...), and picking it names the blocker instead of "Try again!".
• pygame: the row is drawn in grey, the arrow keys step over it, and ENTER/number keys can't confirm it.

Marked so far: fishing without the energy for an hour; selling with an empty hold; bait/rod that's unaffordable or already maxed out; drinking, buying a boat, a property or a home rung you can't pay for; repairing or upgrading a hull whose bill you can't cover; depositing with an empty purse; withdrawing from an empty account; guessing a dice face before placing a bet.

Safety: the game's own post-choice guards are left untouched, so nothing depends on a front-end honouring this. canAfford/hasEnergy are used as the predicates, so operator mode never sees a greyed-out button. Marking every option is treated as a call-site bug and dropped rather than leaving a menu that accepts nothing, and an out-of-range option number raises with a message naming the fix.

Two magic numbers picked up names along the way, since the new gate and the existing charge had to agree: docks.FISHING_ENERGY_COST and tavern.DRINK_COST.

Test plan

• python3 -m compileall -q src tests
• SDL_VIDEODRIVER=dummy SDL_AUDIODRIVER=dummy python3 -m pytest --verbose -vv --cov=src --cov-report=term-missing --cov-report=xml:cov.xml — 770 passed, 97% coverage (up from 731)
• black src tests + autoflake per format.sh
• All three front-ends touched and covered: new tests for the shared contract (tests/ui/test_baseUserInterface.py), the console rows and refusal message (tests/ui/test_userInterface.py), pygame row text/navigation/keyboard (tests/ui/test_pygameUserInterface.py), and the web screen contract (tests/ui/test_webUserInterface.py). tests/web/test_clientParity.py asserts the shared browser client actually consumes the contract, so it can't be sent server-side and ignored client-side.
• Verified in a real browser client: ran web/client.js against a DOM stub — an options screen with unavailable: ["needs 10 energy - sleep at home", null, null] renders [1] Fish — needs 10 energy - sleep at home as class="unavailable", disabled=true, no click handler, while options 2 and 3 stay live. Pressing 1 sends nothing; pressing 2 sends "2".
• Ran examples/web_app.py and confirmed GET /state publishes the new unavailable list alongside options.
• No Player/Stats/TimeService fields changed, so no schemas/*.json or *JsonReaderWriter updates are needed.
• README.md updated where the staged reveal is described.

🤖 Generated with Claude Code

---

drafted by Claude on behalf of Daniel Stephenson