@smart-cloud/publisher-exporter 1.1.58 → 1.1.60

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (7) hide show
  1. package/README.md +2 -0
  2. package/dist/content-sync.js +10 -10
  3. package/dist/crawl.js +8 -8
  4. package/dist/deploy.js +4 -4
  5. package/dist/invalidate.js +3 -3
  6. package/dist/queue-runner.js +3 -3
  7. package/package.json +1 -1
package/README.md CHANGED
@@ -113,6 +113,8 @@ When the runtime config contains enabled scheduler rules and the active queue-ru
113
113
  - A 1-minute external runner tick is the recommended cadence.
114
114
  - Supported scheduled commands are `publish`, `crawl`, `deploy`, `invalidate`, `retry-timeouts`, `url`, and Professional/Agency-only `content-sync`.
115
115
  - Content sync requires a successful normal publish baseline and processes only its configured post types, multisite scope, listings, archives, and sitemap surfaces.
116
+ - Crawl-producing jobs submit the privacy-minimal `privacy/cookie-observations.json` artifact to the authenticated WordPress bridge when a runtime token is configured; installed consent providers keep candidates pending manual classification.
117
+ - Targeted content sync can render or tombstone exact plugin-owned public resources declared through the versioned WordPress resource-change contract.
116
118
  - The scheduler timezone value is currently informational for operations context; interval matching is based on elapsed minute buckets checked at each queue-runner start.
117
119
  - If an equivalent queued or running job already exists for the same command, crawl mode, deployment profile, and URL, that rule is skipped for the current interval bucket.
118
120