@smart-cloud/publisher-exporter 1.1.57 → 1.1.59

package/README.md

@@ -56,7 +56,7 @@ npx @smart-cloud/publisher-exporter queue-runner --runtime-dir /srv/site/runtime
 ## Crawl Modes And Repair Workflows
 
 - `crawl` without extra flags performs a normal full crawl, asset download, and final text rewrite.
-- `crawl --crawl-mode incremental` reuses the existing crawl manifest when possible and rewrites only the files affected by re-crawled pages, text assets, or changed asset-map entries.
+- `crawl --crawl-mode incremental` reuses the existing crawl manifest when possible and rewrites only the files affected by re-crawled pages, text assets, or changed asset-map entries. After a successful unlimited discovery pass it also removes exporter-generated HTML that is no longer present in the current manifest and records exact deletion tombstones for the deploy step. Post-crawl copy-map destinations remain protected.
 - An incremental crawl now fails closed when the remote WP Suite subscription configuration cannot be loaded. It never silently falls back to a full crawl that clears the existing output tree.
 - `crawl --resume-rewrite` skips discovery, rendering, and asset download, then reruns the final text rewrite over the existing output tree using the current rewrite rules.
 - `crawl --retry-timeouts` retries timed-out URLs from the latest archived full crawl or publish log snapshot.
@@ -113,6 +113,8 @@ When the runtime config contains enabled scheduler rules and the active queue-ru
 - A 1-minute external runner tick is the recommended cadence.
 - Supported scheduled commands are `publish`, `crawl`, `deploy`, `invalidate`, `retry-timeouts`, `url`, and Professional/Agency-only `content-sync`.
 - Content sync requires a successful normal publish baseline and processes only its configured post types, multisite scope, listings, archives, and sitemap surfaces.
+- 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.
+- Targeted content sync can render or tombstone exact plugin-owned public resources declared through the versioned WordPress resource-change contract.
 - The scheduler timezone value is currently informational for operations context; interval matching is based on elapsed minute buckets checked at each queue-runner start.
 - 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.
 
@@ -176,7 +178,7 @@ Prune old archive directories with `publisher-exporter prune-logs --runtime-dir
 - If direct CLI execution seems to ignore the expected runtime state, verify that `PUBLISHER_CONFIG` and `STATIC_PUBLISHER_RUNTIME_DIR` both point at the same runtime tree. A mismatched config path and runtime dir can make the run look idle or incomplete.
 - Prefer incremental crawl when the existing manifest is trusted and you only need a fast recrawl of changed pages or assets. Prefer a full crawl when discovery rules changed, the manifest is missing or suspect, or you want a clean end-to-end rebuild.
 - JavaScript bundle discovery follows only explicit dynamic `import()` calls and fixed Webpack chunk-filename mappings such as `runtime.u = () => "custom-block-parser.js"`. It does not infer dependencies from arbitrary quoted paths or application-specific loader calls; add those manually as extra assets when needed.
-- In `sdk-upload-delete` mode, remote-only S3 objects are protected unless the crawl deploy plan contains an explicit manifest-backed deletion tombstone. Protected keys are listed in `deploy-diff.json` and the deploy log. This intentionally favors availability over automatically removing an unverified remote-only object.
+- In `sdk-upload-delete` mode, remote-only S3 objects are protected unless the crawl deploy plan contains an explicit manifest-backed deletion tombstone. Successful unlimited incremental discovery reconciles exporter-generated local HTML with the current crawl manifest and creates those exact tombstones for orphaned HTML. Protected keys are listed in `deploy-diff.json` and the deploy log. This intentionally favors availability over automatically removing an unverified remote-only object.
 - `queue-runner-heartbeat.json` reports both the exporter package version and the installed `@smart-cloud/wpsuite-core` version. Crawl logs also report the runtime `virtualAssetBaseUrl`, remote config loader status, and resolved subscription type without logging the runtime token. Legacy runtime input using `uploadUrl` is accepted during migration but normalized to `virtualAssetBaseUrl`.
 - For generated 404 capture, set `generated404RequestPath` to a path that really returns HTTP 404 from the origin. The exporter validates that response before reusing it as the generated 404 page.