Inspect the implementation boundary
The reference category has an independently deployable package, a shared hosted wrapper, and a source manifest. The inspected category factory returns no specialized handler. That is a significant fact, not a detail to hide behind a feature list.
The repository therefore supports a narrower story than a full interactive reference application. It captures a category's packaging and provenance while leaving application-specific hosted behavior unimplemented in that factory.
Keep the migration reviewable
The shared runtime provides origin, revision, identity, and service-scoped storage. The package documentation describes disabled desktop dependencies and an endpoint that reports hosted readiness. Source hashes connect exported files to the original local toolkit.
This approach lets an extraction be reviewed independently: a reviewer can see the service boundary and then ask which adapters are present. The absence of a handler is visible rather than being disguised as a successful integration.
A separate source manifest and readiness response make the unfinished boundary discoverable, giving future work a clear place to begin instead of relying on assumptions.
Make unfinished boundaries discoverable
The factory's absence of specialized handlers is visible alongside the package and provenance information. Future application behavior has a clear place to enter the runtime and can arrive with corresponding checks. That is a more useful migration record than treating a category's successful packaging as proof that all of its tools already work in the cloud.