Give the module a predictable home
The inspected factory enables the PDF autosave service. Before constructing it, the adapter creates runtime document and trash directories through the hosted file abstraction. The application module can retain its file-oriented model while the host supplies a controlled storage implementation.
The category name covers a broader local toolkit, but the factory is the evidence for the specific hosted behavior. The PDF autosave adapter is the concrete hosted capability in this factory.
Separate source from personal material
The repository's release source excludes mutable data and desktop credentials. Hosted files and binary chunks are stored through a service-scoped API, with one compare-and-set manifest used to publish updates. Stale writes are reported as conflicts.
The service has no direct Redis listener and no subprocess permission. Its account identity comes from the shared controller rather than a client-submitted user field.
Creating a dedicated trash location gives the adapted document service a place for recoverable removals, keeping that behavior distinct from permanently deleting the source package.
Preserve the document boundary
The adapter lets the document module work with predictable runtime locations while the shared host controls persistence. Sample documents can exercise saving, revisions, and recoverable removal without coupling those operations to the source checkout. Native desktop dependencies still need their own hosted adapters; packaging alone does not recreate the local environment.