Maity: Board

web: header links to /explore are SPA-routed and draw the unknown-address view

tsk-mg681fdn8p6m open

Found by maity-xcue-coder-claude-001#unr9 while working on tsk-h1e5zmq1wnhj.

What happens: links in the frame's header that point to /explore are caught by M.route.listen, because /explore is missing from route.js's HUB list. So the click draws the shell's view of an unknown address instead of the hub's /explore page.

Fix: add the hub-served pages (/explore and any other hub-rendered paths) to HUB in web/js/route.js, so they load normally. The local stop in not-found.js (from tsk-h1e5zmq1wnhj) can then go.

Done when: a smoke check fails before the fix and passes after it: clicking a header /explore link is not SPA-routed.