v0.2.22

Doca 0.2.22 — Automatically reclaim idle capture slots

简体中文

Every new capture checks the existing ten-task limit. If full, the server retires the oldest pending captures with no upload or retry activity for at least 30 minutes, only until the new request fits. Connections with queued, running or approval-waiting browser AI jobs are protected. Retry and upload activity refreshes the task; long object uploads send a server heartbeat. Ten active tasks remain the limit.

Reclaimed tasks use the existing expired status. Their frozen input, uploaded objects and original 24-hour deadline remain unchanged until normal cleanup. Completed documents and images are retained. Cleanup also removes the retained source of expired tasks with no images when their deadline arrives. Reclamation and insertion share the account lock and transaction; invalid requests do not retire tasks.

Extension 0.2.10 automatically rebuilds an expired capture once from its frozen material, keeping its account, destination, selection and images. It does not reread another page or loop on quota/authorization errors. Unknown current error codes remain visible. No manual task-management workflow is required.

The user explicitly approved this automatic policy on 2026-10-26. Capture protocol v1, authorization v2, database tables/columns and stored JSON shapes are unchanged. Existing pending rows use their recorded activity/deadline; no historical defaults or data conversion are introduced. Older extensions keep their current interfaces and can recapture when an old task reports expiration. During rollback, preserve all records/objects and retain the expired-source cleanup fix, or wait for reclaimed tasks to reach their original deadlines and finish cleanup before reverting that fix.

Update the server to 0.2.22, then download/reload extension 0.2.10. The production failure after 0.2.21 was the full pending-task limit; its generic notice had hidden that cause. Existing content-conversion degradation and image placeholders remain in effect.

See the verification record for the production diagnosis, approved retention policy and regression scope.

Web assets are attached as doca-web-assets-v0.2.22.tar.gz.
Extract it and publish the assets directory unchanged.
Set DOCA_ASSET_BASE to the HTTPS prefix that contains that assets directory, with no trailing slash.

Image-only deployment files and initialization instructions are attached as doca-deploy-v0.2.22.tar.gz with a SHA-256 checksum.
Transfer this bundle to servers without GitHub access; no source checkout is needed.
The container image is separate. Pull the matching smartdoca/doca image or transfer it with docker save/load.

GitHub attachments and Docker Hub amd64/arm64 publication have been independently verified. See the release verification receipt. Production Annual Reviews acceptance has also passed after the site upgrade and extension reload: the real Chrome capture, document open and reload preserve the article ending, references and all nine stored images; the unsupported site SVG remains a placeholder with a current warning.