feat(classic-ui): add classic menu resources and cursor intents

[jrepp]

Summary

• Rebased this PR onto origin/main so the Classic menu work is isolated from the script-debugger and MCP stack.
• Adds Classic menu resource parsing plus the app-side Classic command menu hookup.
• Keeps the script-debugger changes in feat(debugger): add statement stepping and polish script editor #292 and the MCP bridge changes in refactor(mcp): simplify tool bridge and remove AIContextToolPolicy #286; this PR now owns the Classic menu code that had leaked into the old feat(debugger): add statement stepping and polish script editor #292 base.

Context

Classic menu resources imported from HyperCard need both a core representation and a visible menu projection in the app. The menu source test already expected ClassicMenuCommandMapper output to be exposed through app commands, so this branch now contains that UI/runtime hookup instead of leaving the parser detached.

Changes Made

• Added ClassicMenuResources.swift for decoding imported Classic menu resources into menu/item models.
• Added a Classic command menu in GoMenuCommands that projects imported menus from the focused stack.
• Added a Classic menu runner that dispatches selected items through the existing HypeTalk doMenu path and applies document mutations/navigation through the normal coordinator.
• Added/kept MenuCommandSourceTests coverage asserting imported menu resources surface as Classic menu commands.

Testing & Verification

• scripts/test.sh --filter MenuCommandSourceTests (5 tests passed)

Review Notes

• Review the Classic menu runner path in GoMenuCommands.swift for whether doMenu is the right compatibility boundary for all imported menu items.
• Review whether disabled Classic menu items should remain visible but disabled, as implemented here, or be hidden to better match HyperCard behavior.
• No .hype document format changes are introduced.