Skip to main content

Repository directories and build boundaries

Find the UI, history core, plugin contracts and validation tools, and understand their build boundaries.

FolderRewind/
  Views/ ViewModels/ Models/ Services/
  History/
    Domain/ Storage/ Index/ LocalState/
    Application/ Representation/ Retention/ Cloud/ Migration/ Merge/
  Assets/ Strings/ Styles/ Controls/ Converters/
FolderRewind.Plugin.Abstractions/
FolderRewind.Plugin.Runtime/
FolderRewind.Tests/
FolderRewind.Plugin.Abstractions.Tests/
FolderRewind.Plugin.Runtime.Tests/
Installer/ .github/ docs/

UI and Host​

Views bind interactions; ViewModels own state/async commands. Models are split by configuration/scopes/filters/automation/cloud/plugins/discovery, rather than the old1300-line BackupModels.cs listing. Services includes Host adapters/discovery/Plugins/V3 orchestration.

Core and external repos​

Abstractions has Manifest/Lifecycle/Capabilities/Snapshots/Identifiers/Artifacts/KnotLinkCoreCommands. Runtime owns Activation/Loading/Settings/Packaging/Operations/artifact transactions, not the public plugin reference boundary.

MineRewind, Catalog and website are independent repos. Nearby checkouts do not become Host solution inputs; acceptance pins artifacts. Verify actual project files rather than copying legacy trees.