strapi-content-sync-pro 1.0.2 → 1.0.4

package/admin/src/components/ConfigTab.jsx

@@ -30,6 +30,7 @@ const ConfigTab = () => {
         apiToken: '',
         instanceId: '',
         sharedSecret: '',
+        syncMode: 'paired',
     });
 
     // Login modal state
@@ -131,6 +132,7 @@ const ConfigTab = () => {
             if (config.apiToken && config.apiToken !== '••••••••') payload.apiToken = config.apiToken;
             if (config.instanceId) payload.instanceId = config.instanceId;
             if (config.sharedSecret && config.sharedSecret !== '••••••••') payload.sharedSecret = config.sharedSecret;
+            if (config.syncMode) payload.syncMode = config.syncMode;
 
             await post(`/${PLUGIN_ID}/config`, payload);
             setMessage({ type: 'success', text: 'Connection configuration saved' });
@@ -349,6 +351,11 @@ const ConfigTab = () => {
                     {/* Connection Tab */}
                     <Tabs.Content value="connection">
                         <Box>
+                            <Box paddingBottom={4}>
+                                <Alert variant="info" title="Deployment mode">
+                                    In <strong>Paired</strong> mode, install Content Sync Pro on both local and remote servers. In <strong>Single-side</strong> mode, install on local only; remote plugin routes are not required. Connection test behavior and allowed sync/execution options follow the selected mode.
+                                </Alert>
+                            </Box>
                             <Flex gap={6}>
                                 {/* LEFT COLUMN: Remote Server */}
                                 <Box flex="1">
@@ -362,7 +369,7 @@ const ConfigTab = () => {
                                                 value={config.baseUrl}
                                                 onChange={(e) => setConfig((p) => ({ ...p, baseUrl: e.target.value }))}
                                             />
-                                            <Field.Hint>URL of the Strapi server to sync with</Field.Hint>
+                                            <Field.Hint>URL of the remote Strapi server where this plugin is also installed</Field.Hint>
                                         </Field.Root>
 
                                         <Field.Root>
@@ -378,7 +385,7 @@ const ConfigTab = () => {
                                                 </Box>
 
                                             </Flex>
-                                            <Field.Hint>Full Access token from the remote server</Field.Hint>
+                                            <Field.Hint>Remote API token with permissions for this plugin routes and synced content types</Field.Hint>
                                         </Field.Root>
                                         <Field.Root>
                                             <Button
@@ -404,7 +411,7 @@ const ConfigTab = () => {
                                                 value={config.instanceId}
                                                 onChange={(e) => setConfig((p) => ({ ...p, instanceId: e.target.value }))}
                                             />
-                                            <Field.Hint>Name to identify this server in logs</Field.Hint>
+                                            <Field.Hint>Unique local instance name used in logs and sync traceability</Field.Hint>
                                         </Field.Root>
 
                                         <Field.Root>
@@ -415,7 +422,21 @@ const ConfigTab = () => {
                                                 value={config.sharedSecret}
                                                 onChange={(e) => setConfig((p) => ({ ...p, sharedSecret: e.target.value }))}
                                             />
-                                            <Field.Hint>Must match on both servers</Field.Hint>
+                                            <Field.Hint>Must match exactly on both local and remote plugin configurations</Field.Hint>
+                                        </Field.Root>
+
+                                        <Field.Root>
+                                            <Field.Label>Sync Mode</Field.Label>
+                                            <SingleSelect
+                                                value={config.syncMode || 'paired'}
+                                                onChange={(value) => setConfig((p) => ({ ...p, syncMode: value }))}
+                                            >
+                                                <SingleSelectOption value="paired">Paired (plugin on both servers)</SingleSelectOption>
+                                                <SingleSelectOption value="single_side">Single-side (plugin only on local)</SingleSelectOption>
+                                            </SingleSelect>
+                                            <Field.Hint>
+                                                Paired mode supports push/pull/bidirectional and remote plugin validation. Single-side mode is pull-focused and does not require plugin routes on remote.
+                                            </Field.Hint>
                                         </Field.Root>
                                     </Flex>
                                 </Box>

package/admin/src/components/HelpTab.jsx

@@ -38,7 +38,7 @@ export const HelpTab = () => {
       <Box paddingBottom={4}>
         <Typography variant="beta" tag="h2">Plugin Documentation</Typography>
         <Typography variant="omega" textColor="neutral600">
-          Complete guide for configuring and using the Content Sync Pro plugin.
+          End-to-end guide for configuring, securing, and operating Content Sync Pro across Strapi environments.
         </Typography>
       </Box>
 
@@ -49,7 +49,9 @@ export const HelpTab = () => {
           <Tabs.Trigger value="content-types">Content Types</Tabs.Trigger>
           <Tabs.Trigger value="sync-profiles">Sync Profiles</Tabs.Trigger>
           <Tabs.Trigger value="execution">Sync Execution</Tabs.Trigger>
+          <Tabs.Trigger value="bulk-transfer">Bulk Transfer</Tabs.Trigger>
           <Tabs.Trigger value="media">Media</Tabs.Trigger>
+          <Tabs.Trigger value="stats">Stats</Tabs.Trigger>
           <Tabs.Trigger value="enforcement">Enforcement</Tabs.Trigger>
           <Tabs.Trigger value="alerts">Alerts</Tabs.Trigger>
           <Tabs.Trigger value="troubleshooting">Troubleshooting</Tabs.Trigger>
@@ -124,10 +126,13 @@ export const HelpTab = () => {
               <ul style={{ paddingLeft: '20px', marginTop: '8px', lineHeight: '1.8' }}>
                 <li><Typography variant="omega">Bi-directional sync (push, pull, or both)</Typography></li>
                 <li><Typography variant="omega">Sync Profiles for defining WHAT to sync</Typography></li>
-                <li><Typography variant="omega">Execution modes: On-demand, Scheduled, or Live (real-time)</Typography></li>
+                <li><Typography variant="omega">Execution modes: On-demand, Scheduled, Live, or External scheduler</Typography></li>
                 <li><Typography variant="omega">Field-level sync policies (Advanced mode)</Typography></li>
                 <li><Typography variant="omega">Conflict resolution strategies (Latest, Local, Remote wins)</Typography></li>
+                <li><Typography variant="omega">Pagination support for large datasets with bounded memory usage</Typography></li>
                 <li><Typography variant="omega">Dependency resolution - sync related entities automatically</Typography></li>
+                <li><Typography variant="omega"><strong>Bulk Transfer</strong> - top-level tab for one-click full push / full pull with selectable chunks, page-level progress, pause / resume / cancel, and persisted run history (restart or resume any previous run)</Typography></li>
+                <li><Typography variant="omega">Media sync (URL or rsync) with MIME filters and morph-link remapping</Typography></li>
                 <li><Typography variant="omega">Enforcement checks - schema, version, and time validation</Typography></li>
                 <li><Typography variant="omega">Configurable alerts via email, webhook, or Strapi logs</Typography></li>
                 <li><Typography variant="omega">Secure communication via API tokens and HMAC signatures</Typography></li>
@@ -141,6 +146,7 @@ export const HelpTab = () => {
               <ul style={{ paddingLeft: '20px', marginTop: '8px', lineHeight: '1.8' }}>
                 <li><Typography variant="omega"><strong>Sync Profiles</strong> - Define WHAT to sync (direction, conflict strategy, field policies)</Typography></li>
                 <li><Typography variant="omega"><strong>Sync Execution</strong> - Define WHEN to sync (on-demand, scheduled, live) and dependency handling</Typography></li>
+                <li><Typography variant="omega"><strong>Bulk Transfer</strong> - One-click full pull / push across selectable chunks with pause / resume and persisted history (separate top-level tab)</Typography></li>
                 <li><Typography variant="omega"><strong>Enforcement</strong> - Pre-sync validation (schema match, version check, time sync)</Typography></li>
                 <li><Typography variant="omega"><strong>Alerts</strong> - Notifications for sync success/failure</Typography></li>
               </ul>
@@ -148,10 +154,11 @@ export const HelpTab = () => {
 
             <HelpSection title="Quick Start">
               <ol style={{ paddingLeft: '20px', lineHeight: '2' }}>
-                <li><Typography variant="omega"><strong>Configuration Tab</strong> - Set up remote server URL, API token, and shared secret</Typography></li>
+                <li><Typography variant="omega"><strong>Configuration Tab</strong> - Set up remote server URL, API token, instance ID, and shared secret</Typography></li>
                 <li><Typography variant="omega"><strong>Content Types Tab</strong> - Enable content types for sync (auto-generates default profiles)</Typography></li>
                 <li><Typography variant="omega"><strong>Sync Profiles Tab</strong> - Customize sync behavior or use defaults</Typography></li>
-                <li><Typography variant="omega"><strong>Sync Tab</strong> - Configure execution settings and run sync operations</Typography></li>
+                <li><Typography variant="omega"><strong>Sync Tab</strong> - Configure execution settings, page size, and run sync operations</Typography></li>
+                <li><Typography variant="omega"><strong>Bulk Transfer Tab</strong> - For a first-time migration or full refresh, run a one-click Full Pull or Full Push with selectable chunks, pause / resume, and persisted run history</Typography></li>
               </ol>
             </HelpSection>
 
@@ -170,6 +177,14 @@ export const HelpTab = () => {
               <Typography variant="omega" paddingBottom={2}>
                 Configure the connection to the remote Strapi instance in the <strong>Connection</strong> sub-tab.
               </Typography>
+              <Typography variant="omega" paddingBottom={2}>
+                <strong>Deployment modes:</strong> Use <strong>Paired</strong> mode when the plugin is installed on both servers,
+                or <strong>Single-side</strong> mode when the plugin is installed only on local server.
+              </Typography>
+              <Typography variant="omega" paddingBottom={2}>
+                In paired mode, connection test validates remote plugin reachability and token access. In single-side mode,
+                test validates remote reachability and content API token access without requiring remote plugin endpoints.
+              </Typography>
 
               <Box background="neutral100" padding={4} hasRadius marginBottom={4}>
                 <Typography variant="sigma" textColor="neutral800">Base URL</Typography>
@@ -295,6 +310,9 @@ http://localhost:1337</CodeBlock>
                 Sync Profiles define <strong>WHAT</strong> to sync and <strong>HOW</strong> conflicts are resolved.
                 They do NOT control when sync runs - that's configured in the Sync tab (Execution).
               </Typography>
+              <Typography variant="omega" paddingTop={2}>
+                In <strong>Single-side</strong> mode, profiles are automatically restricted to <strong>Pull Only</strong>.
+              </Typography>
               <Typography variant="omega" paddingTop={2}>
                 Each profile specifies:
               </Typography>
@@ -525,7 +543,7 @@ http://localhost:1337</CodeBlock>
                   Uses lifecycle hooks to detect changes.
                 </Typography>
                 <Typography variant="pi" textColor="warning600" paddingTop={2}>
-                  Note: Increases server load. Use for critical content only.
+                  Note: Increases server load. Use for critical content only. Live mode is available in paired mode and disabled in single-side mode.
                 </Typography>
               </Box>
             </HelpSection>
@@ -555,6 +573,18 @@ http://localhost:1337</CodeBlock>
               </ul>
             </HelpSection>
 
+            <HelpSection title="Bulk Transfer (Full Pull / Full Push)">
+              <Typography variant="omega">
+                Bulk Transfer is now its own <strong>top-level tab</strong> (separate from Sync). It is a
+                one-click helper for moving everything between local and remote, with selectable chunks,
+                page-level progress, pause / resume / cancel, and a persisted run history you can restart
+                or resume from.
+              </Typography>
+              <Typography variant="omega" paddingTop={2}>
+                See the <strong>Bulk Transfer</strong> help tab for the full guide.
+              </Typography>
+            </HelpSection>
+
             <HelpSection title="Execution Status">
               <Typography variant="omega">
                 The Status tab in Sync shows the current state of all profiles:
@@ -566,11 +596,103 @@ http://localhost:1337</CodeBlock>
                 <li><Typography variant="omega"><strong>Next Run</strong> - When scheduled sync will run next</Typography></li>
                 <li><Typography variant="omega"><strong>Status</strong> - Running or Idle</Typography></li>
               </ul>
-            </HelpSection>
-          </Box>
-        </Tabs.Content>
+                 </HelpSection>
+              </Box>
+            </Tabs.Content>
+
+            {/* Bulk Transfer Tab */}
+            <Tabs.Content value="bulk-transfer">
+              <Box paddingTop={4}>
+                <HelpSection title="What is Bulk Transfer?">
+                  <Typography variant="omega">
+                    <strong>Bulk Transfer</strong> is a dedicated top-level tab for one-click, full-scope data
+                    movement between the local and remote Strapi instances. It is the fastest way to perform an
+                    initial migration, a full refresh, or a disaster-recovery style mirror, without having to
+                    orchestrate individual Sync Profiles.
+                  </Typography>
+                  <Typography variant="omega" paddingTop={2}>
+                    Unlike the Sync tab — which is profile-driven and can be scheduled or live — Bulk Transfer is
+                    an explicit, user-driven run: pick a direction, pick the scopes, pick (or deselect) the chunks,
+                    and start. It is designed to be safely pausable, resumable, and inspectable.
+                  </Typography>
+                </HelpSection>
+
+                <HelpSection title="Direction & Scopes">
+                  <ul style={{ paddingLeft: '20px', marginTop: '8px', lineHeight: '1.8' }}>
+                    <li><Typography variant="omega"><strong>Direction</strong> — <em>Full Pull</em> (remote → local) or <em>Full Push</em> (local → remote). In <strong>Single-side</strong> mode only Full Pull is available.</Typography></li>
+                    <li><Typography variant="omega"><strong>Content</strong> — All user-defined <code>api::*</code> content types.</Typography></li>
+                    <li><Typography variant="omega"><strong>Media</strong> — Files and morph links via the active media profiles.</Typography></li>
+                    <li><Typography variant="omega"><strong>Strapi Users</strong> — <code>plugin::users-permissions.user</code>.</Typography></li>
+                    <li><Typography variant="omega"><strong>Admin Users</strong> — <code>admin::user</code> (experimental; use with care).</Typography></li>
+                    <li><Typography variant="omega"><strong>Apply deletions</strong> — Destination removes items missing on source. Use with care, especially with user scopes.</Typography></li>
+                    <li><Typography variant="omega"><strong>Conflict strategy</strong> — Latest updated wins (default), Local wins, or Remote wins.</Typography></li>
+                    <li><Typography variant="omega"><strong>Auto-continue</strong> — Run all selected chunks back-to-back, or pause between chunks to review.</Typography></li>
+                  </ul>
+                </HelpSection>
+
+                <HelpSection title="Selectable Chunks & Page-level Progress">
+                  <Typography variant="omega">
+                    A bulk job expands into one <strong>chunk</strong> per content type and one chunk per active
+                    media profile (plus any selected user scopes). In the Run Transfer view you can:
+                  </Typography>
+                  <ul style={{ paddingLeft: '20px', marginTop: '8px', lineHeight: '1.8' }}>
+                    <li><Typography variant="omega">Toggle individual chunks, or use <strong>Select / Deselect All</strong> to run only a subset.</Typography></li>
+                    <li><Typography variant="omega">Watch per-chunk <strong>page progress</strong> (<code>page X of Y</code>, records pushed / pulled, errors) updated in near real-time.</Typography></li>
+                    <li><Typography variant="omega">See consolidated run stats (total pushed, pulled, errors, pages done) and a spinner while the job is actively processing.</Typography></li>
+                    <li><Typography variant="omega">Use <strong>Pause</strong> to stop after the current page, <strong>Resume</strong> to continue from the exact saved cursor, <strong>Run Next Chunk</strong> in manual mode, or <strong>Cancel</strong> to stop the run without losing the progress already made.</Typography></li>
+                  </ul>
+                  <Typography variant="pi" textColor="neutral600" paddingTop={2}>
+                    Because transfer is paginated end-to-end using the global <code>syncPageSize</code>, memory
+                    stays bounded even on very large datasets.
+                  </Typography>
+                </HelpSection>
+
+                <HelpSection title="Pause, Resume & Cancel">
+                  <Typography variant="omega">
+                    Bulk Transfer treats <strong>pause</strong>, <strong>cancel</strong>, and <strong>resume</strong> as
+                    first-class operations:
+                  </Typography>
+                  <ul style={{ paddingLeft: '20px', marginTop: '8px', lineHeight: '1.8' }}>
+                    <li><Typography variant="omega"><strong>Pause</strong> — Stops after the current page finishes. The chunk cursor, page number, and counters are persisted, so resume continues from the same place.</Typography></li>
+                    <li><Typography variant="omega"><strong>Cancel</strong> — Distinct from pause: the run is marked cancelled and the in-flight chunk is preserved as <em>paused</em> with accumulated progress, not falsely reported as successful.</Typography></li>
+                    <li><Typography variant="omega"><strong>Resume</strong> — Re-opens the run exactly where it stopped: same direction, scopes, deletion flag, auto-continue, conflict strategy, and the same chunk selection, with cursor/page restored.</Typography></li>
+                  </ul>
+                </HelpSection>
+
+                <HelpSection title="Previous Runs & History">
+                  <Typography variant="omega">
+                    Every bulk run — completed, paused, cancelled, or failed — is recorded in the
+                    <strong> Previous Runs</strong> sub-tab. History is persisted in the plugin store (not just
+                    in memory), with serialized writes so concurrent updates from the polling loop and control
+                    actions never clobber each other.
+                  </Typography>
+                  <ul style={{ paddingLeft: '20px', marginTop: '8px', lineHeight: '1.8' }}>
+                    <li><Typography variant="omega"><strong>Expand</strong> a row to inspect per-chunk status, page progress, record counts, and error messages for that run.</Typography></li>
+                    <li><Typography variant="omega"><strong>Restart</strong> — Re-runs the same configuration from scratch (fresh cursor) while keeping the original entry in history.</Typography></li>
+                    <li><Typography variant="omega"><strong>Resume</strong> — For paused / cancelled / incomplete runs, rehydrates the Run Transfer tab with the exact prior state (direction, scopes, options, chunk selection) and continues from the saved cursor and page.</Typography></li>
+                    <li><Typography variant="omega"><strong>Clear history</strong> — Removes the stored history entries.</Typography></li>
+                  </ul>
+                  <Typography variant="omega" paddingTop={2}>
+                    Each run is also recorded as a Stats report with <code>runType = bulk_transfer</code>, so the
+                    before/after snapshots are available in the Stats tab.
+                  </Typography>
+                </HelpSection>
+
+                <HelpSection title="Bulk Transfer vs Sync">
+                  <ul style={{ paddingLeft: '20px', marginTop: '8px', lineHeight: '1.8' }}>
+                    <li><Typography variant="omega"><strong>Sync</strong> is <em>profile-driven</em>: on-demand, scheduled, or live; intended for ongoing incremental synchronization with field-level policies.</Typography></li>
+                    <li><Typography variant="omega"><strong>Bulk Transfer</strong> is <em>operation-driven</em>: an explicit full pull/push, chunked and resumable, intended for migrations, backfills, and full refreshes.</Typography></li>
+                  </ul>
+                  <Typography variant="pi" textColor="warning600" paddingTop={2}>
+                    Note: The active in-memory job registry is cleared on Strapi restart, but the run history
+                    (and its saved cursor/page/selection) is persisted — so after a restart you can open Previous
+                    Runs and <strong>Resume</strong> the interrupted job.
+                  </Typography>
+                </HelpSection>
+              </Box>
+            </Tabs.Content>
 
-        {/* Media Tab */}
+            {/* Media Tab */}
         <Tabs.Content value="media">
           <Box paddingTop={4}>
             <HelpSection title="Pagination for Large Datasets">
@@ -632,6 +754,10 @@ http://localhost:1337</CodeBlock>
               <Typography variant="omega">
                 Each profile can sync two distinct aspects of media:
               </Typography>
+              <Typography variant="omega" paddingTop={2}>
+                For entity-linked media consistency, this plugin also syncs media morph links using <strong>documentId-based remapping</strong>
+                (file documentId and related entity documentId are resolved to local numeric ids before insert).
+              </Typography>
               <Box background="neutral100" padding={4} hasRadius marginTop={2} marginBottom={2}>
                 <Typography variant="sigma" textColor="neutral800">DB Rows (Metadata)</Typography>
                 <Typography variant="omega" paddingTop={1}>
@@ -652,6 +778,11 @@ http://localhost:1337</CodeBlock>
                 If you only need metadata references (e.g., both sides use the same S3 bucket), you can
                 sync DB rows only.
               </Typography>
+              <Typography variant="pi" textColor="neutral600" paddingTop={2}>
+                Note: Strapi components, repeatable components, and dynamic zones are already tracked by
+                document service sync using stable documentIds, so they do not require id-to-documentId remapping
+                like upload morph tables do.
+              </Typography>
             </HelpSection>
 
             <HelpSection title="URL strategy (HTTP)">
@@ -720,6 +851,61 @@ http://localhost:1337</CodeBlock>
           </Box>
         </Tabs.Content>
 
+        {/* Stats Tab */}
+        <Tabs.Content value="stats">
+          <Box paddingTop={4}>
+            <HelpSection title="Database Stats Overview">
+              <Typography variant="omega">
+                The Stats tab compares local and remote data state per content type, including content
+                entries, media files, and media morph (relation) links. The view is split into two
+                sub-tabs: <strong>Current Snapshot</strong> and <strong>Run Reports</strong>.
+              </Typography>
+            </HelpSection>
+
+            <HelpSection title="Current Snapshot Tab">
+              <Typography variant="omega">
+                Shows the latest live counts and newest timestamps per content type, with the newest
+                side (local / remote / equal) highlighted. Use the controls above the table to drill in:
+              </Typography>
+              <ul style={{ paddingLeft: '20px', marginTop: '8px', lineHeight: '1.8' }}>
+                <li><Typography variant="omega"><strong>Search</strong> - Filter rows by UID substring.</Typography></li>
+                <li><Typography variant="omega"><strong>Type</strong> - Filter by Content, Media, or Media Morph.</Typography></li>
+                <li><Typography variant="omega"><strong>Newest side</strong> - Show only rows where local, remote, or both are newest.</Typography></li>
+                <li><Typography variant="omega"><strong>Page size / pagination</strong> - Browse large snapshots without scrolling.</Typography></li>
+              </ul>
+            </HelpSection>
+
+            <HelpSection title="Run Reports Tab (Before vs After)">
+              <Typography variant="omega">
+                Before every sync run, the plugin captures a pre-run snapshot. After the run completes,
+                it captures a post-run snapshot and stores both in a report so you can review sync impact
+                and trends over time.
+              </Typography>
+              <ul style={{ paddingLeft: '20px', marginTop: '8px', lineHeight: '1.8' }}>
+                <li><Typography variant="omega"><strong>Status filter</strong> - Show all runs, or only success / failed.</Typography></li>
+                <li><Typography variant="omega"><strong>Page size / pagination</strong> - Reports are paginated server-side.</Typography></li>
+                <li><Typography variant="omega"><strong>Show details</strong> - Expand a report card to see the before/after row tables (first {25} rows per side).</Typography></li>
+              </ul>
+            </HelpSection>
+
+            <HelpSection title="Top Action Row: Refresh, Clear & Retention">
+              <Typography variant="omega">
+                The top of the Stats tab exposes the controls that apply to both sub-tabs:
+              </Typography>
+              <ul style={{ paddingLeft: '20px', marginTop: '8px', lineHeight: '1.8' }}>
+                <li><Typography variant="omega"><strong>Refresh Stats</strong> - Reload the snapshot and reports.</Typography></li>
+                <li><Typography variant="omega"><strong>Clear Logs</strong> - Remove stored sync logs.</Typography></li>
+                <li><Typography variant="omega"><strong>Clear Stats Reports</strong> - Remove all before/after run reports.</Typography></li>
+                <li><Typography variant="omega"><strong>Max Logs / Max Reports</strong> - Retention limits; older entries are pruned when exceeded.</Typography></li>
+                <li><Typography variant="omega"><strong>Save &amp; Apply Retention</strong> - Persists the limits and immediately prunes old data.</Typography></li>
+              </ul>
+              <Typography variant="pi" textColor="neutral600" paddingTop={2}>
+                Retention is also enforced automatically after each sync run.
+              </Typography>
+            </HelpSection>
+          </Box>
+        </Tabs.Content>
+
         {/* Enforcement Tab */}
         <Tabs.Content value="enforcement">
           <Box paddingTop={4}>
@@ -897,10 +1083,10 @@ http://localhost:1337</CodeBlock>
               </Box>
 
               <Box background="danger100" padding={4} hasRadius marginBottom={4}>
-                <Typography variant="sigma" textColor="danger700">401 Unauthorized</Typography>
+                <Typography variant="sigma" textColor="danger700">401 Unauthorized / 403 Forbidden</Typography>
                 <Typography variant="omega" paddingTop={1}>
-                  The API token is invalid or expired. Generate a new token on the remote server and update
-                  Configuration → Connection → API Token.
+                  The API token is invalid, expired, or missing required permissions. Generate a new token on the remote
+                  server and ensure it can access the synced content types (and Upload permissions for media sync).
                 </Typography>
               </Box>
 
@@ -913,10 +1099,10 @@ http://localhost:1337</CodeBlock>
               </Box>
 
               <Box background="danger100" padding={4} hasRadius marginBottom={4}>
-                <Typography variant="sigma" textColor="danger700">Content type not found on remote</Typography>
+                <Typography variant="sigma" textColor="danger700">Content type endpoint not found on remote</Typography>
                 <Typography variant="omega" paddingTop={1}>
-                  The content type exists locally but not on the remote server. Ensure both instances
-                  have matching content type definitions.
+                  The content type exists locally but the remote REST endpoint is missing or named differently.
+                  Ensure both instances have matching content type definitions and API routes are enabled.
                 </Typography>
               </Box>
 

package/admin/src/components/MediaTab.jsx

@@ -400,6 +400,13 @@ const MediaTab = () => {
             {status?.lastResult && (
               <Box paddingTop={3} background="neutral0" padding={4} hasRadius shadow="tableShadow">
                 <Typography variant="sigma">Last Run Result</Typography>
+                {(status.lastResult.morphLinksApplied !== undefined || status.lastResult.morphLinksSkipped !== undefined) && (
+                  <Box paddingTop={2} paddingBottom={2}>
+                    <Typography variant="omega" textColor="neutral700">
+                      Morph links synced: applied {status.lastResult.morphLinksApplied || 0}, skipped {status.lastResult.morphLinksSkipped || 0}
+                    </Typography>
+                  </Box>
+                )}
                 <Typography variant="pi" style={{ fontFamily: 'monospace', whiteSpace: 'pre-wrap' }}>
                   {JSON.stringify(status.lastResult, null, 2)}
                 </Typography>