Navigation: crest tap to child log and idle return #177

1 Commits
Author SHA1 Message Date
overseer 5af0fde2fd Assert the crest-tap navigation the strategy wires
The strategy already computes quest_log_path and board_path and the cards
already navigate by them, so no card source needed fixing — what was
missing was proof: nothing asserted where a crest tap or the quest log's
idle return actually lands. The render harnesses now report the navigation
target of a present-plate tap, that an away plate is not tappable and does
not navigate, and that the idle return goes back to the strategy-computed
board path, so the navigation contract is asserted against the bundle HACS
ships instead of read out of the sources.
2026-09-23 11:02:53 -04:00