Read the factory, not just the name
The repository is named for the deployment category, but its inspected factory mounts the navigation service. It supplies a runtime JSON path and the matching static asset directory. The source does not justify describing this hosted category as an unrestricted deployment engine.
A category label is an organizational choice; the factory and routes establish the capabilities actually wired into the hosted process.
Extract without expanding authority
The service is independently deployable and uses the shared controller for verified identity, public origin, revision, and scoped storage. Mutable application files are published through a compare-and-set manifest, keeping them separate from immutable source.
Native desktop tools, background workers, direct data-store access, and provider publishing remain disabled where suitable adapters are absent. A hosted-status endpoint reports those dependencies explicitly.
The navigation data path is supplied by the adapter rather than discovered from the checkout, allowing the same module to work over controlled hosted runtime storage.
Give each component a clear role
The hosted category maintains a navigation model over controlled runtime storage. Production release control belongs to the separate V39 broker. Keeping those roles explicit makes both components easier to reason about: navigation organizes destinations, while the broker verifies and executes release transitions.