Related #70862

What?

Adds routes support to the @wordpress/boot package with surface-based rendering (stage and inspector areas).

Why?

Enables the boot package to support dynamic route registration with lifecycle hooks and code splitting. Routes can define content for different UI surfaces (main stage area and optional inspector sidebar).

How?

• Updated init() to accept routes and menus
• Converted Home to a static route.

Testing Instructions

You can access the demo route http://localhost:8888/wp-admin/admin.php?page=gutenberg-boot&p=%2F

Or you can add a small testing route

• Create a test route:

  import { init } from '@wordpress/boot';

  init({
    menuItems: [],
    routes: [{
      path: '/test',
      content: {
        stage: () => <div>Main content</div>,
        inspector: () => <div>Sidebar</div>
      }
    }]
  });

• Navigate to ?p=/test and verify both surfaces render correctly

What's next

As a next step, I would like to update the build too to support a "routes" folder with some conventions, that way folks don't have to hook anything, there routes will get automatically registered.