Publish the Terminal route

Confirm the FluentCommunity portal works before activating the adapter. Enable the Terminal destination, then open it from another portal page.

The native FluentCommunity title bar must remain intact, followed by exactly one Social Terminal runtime. The route must not iframe a WordPress page, render a second portal header, or create a second terminal instance.

Test direct load, in-portal navigation, reload, Back and Forward, signed-out policy, signed-in policy, welcome content, prompt focus, and commands from active add-ons. Free includes this core route.

If the route is disabled, its menu entry and router record should stop publishing without deleting Social Terminal settings or data.