| name | paperhub-sync |
| description | Sync a PaperHub workspace, inspect conflicts, retry failures, and repair stuck events |
PaperHub Sync
Use this skill when the user wants to synchronize PaperHub metadata and hydrated PDFs, or recover from sync failures.
What this skill does
- Shows sync queue state
- Pushes pending metadata and blobs to configured backends
- Shows remote backend state
- Lists conflicts
- Retries failed events
- Repairs a failed event by skipping or clearing it
Workflow
Inspect state
paperhub sync-status --workspace <workspace-path>
paperhub sync-remote-status --workspace <workspace-path>
paperhub sync-conflicts --workspace <workspace-path>
Push changes
paperhub sync-push --workspace <workspace-path>
Retry failures
paperhub sync-retry --workspace <workspace-path> [--seq <seq>] [--limit <n>] [--max-retries <n>]
Repair a stuck event
paperhub sync-repair --workspace <workspace-path> --seq <seq> --strategy skip
Operational rules
- Describe sync as application-managed, not as GitHub push/pull.
- Explain failures in terms of queue events and conflict records.
- Only use
sync-repair --strategy skip when the user accepts skipping that failed event.