@smart-cloud/publisher-exporter 1.1.66 → 1.1.68

package/README.md

@@ -213,11 +213,31 @@ DynamoDB heartbeats while a synchronous Lambda invocation is running and
 forwards them to the existing runtime progress snapshot. Workers write those
 rows directly with conditionally increasing sequence numbers.
 
-Rewrite requests carry the original object MIME type, and workers preserve it
-when writing transformed HTML, CSS, JavaScript, or other text back to S3. After
+Workers prefer the origin response `Content-Type`, fall back to the resource
+extension only when the header is absent or invalid, and preserve that value
+when writing transformed HTML, CSS, JavaScript, or other text back to S3. The
+deploy worker includes `Content-Type` in its unchanged-object decision. After
 upgrading from an earlier delegated rewrite implementation, republish affected
 targets to replace already incorrect object metadata.
 
+Render workers terminate orphaned Playwright Chromium processes and remove
+stale `playwright_chromiumdev_profile-*` directories before launching Chromium
+and after closing it. If Chromium disconnects during
+a page render, the worker starts a clean browser and retries that URL once.
+Structured `Remote worker checkpoint.` records include the request, job, task,
+page, attempt, remaining Lambda time, process memory, `/tmp` and `/dev/shm`
+space, and the visible Playwright profile count. Lambda `Runtime.ExitError`
+events are emitted by the platform after the runtime has already stopped, so
+the last checkpoint before the matching `REPORT` line identifies where the
+runtime disappeared. This CloudWatch Logs Insights query keeps both records in
+one timeline:
+
+```text
+fields @timestamp, @requestId, @message
+| filter @message like /Remote worker checkpoint|Remote worker runtime diagnostic|Runtime.ExitError/
+| sort @timestamp asc
+```
+
 The saved runtime configuration remains compatible with older exporters:
 
 ```json