Document moving a TaskNotes task-folder collection to hosted storage without losing custom definitions

[callumalpass]

Documentation gap

The task-folder-only hosted workflow is unclear when the source Obsidian vault stores TaskNotes contracts, schemas, custom types, and collection configuration at its root. Users can end up copying or deleting definition directories while troubleshooting, then interpreting seeded defaults as an overwrite by pairing.

Code-established distinctions to explain

• hosted create creates a generic mdbase collection; crates/connect-agent/src/server/control.rs does not upload a local vault or its TaskNotes contract.
• Definition resources are part of the hosted authority, not ordinary folders to exclude or independently arbitrate through record mirroring.
• The current TaskNotes application manifest declares _types/task.md as a seed resource. Current mdbase type-pack handling preserves an existing seed target and creates defaults when absent. An actual pairing overwrite has not been established.
• The TaskNotes app supports hosted update_type through task-model settings. Custom status schema and contract binding must remain consistent; changing just the enum is insufficient.
• Mirror exclusions are intended to reconcile an existing mirror. Remove/re-add loses the baseline and is not the normal way to change exclusions.

Desired guide

Provide one supported, end-to-end workflow for a collection containing only a task folder, including:

1. Backing up and identifying the collection boundary and required definitions.
2. Explaining whether to use authority transfer or a new hosted collection, and how to preserve the intended grammar in the chosen workflow.
3. Preserving custom statuses and their TaskNotes binding.
4. Handling generated Obsidian view files without conflating them with managed definition resources.
5. Explaining app authorization versus explicit collection setup, and when default types are seeded.
6. Diagnosing collisions and recovering without deleting definitions or repeatedly recreating mirrors.

Validate the documented workflow before publishing it. Coordinate with TaskNotes documentation where appropriate. This is not a confirmed report that pairing overwrites an intact custom type.