release: bump version to 0.66.0

docs/technical/en/backend-collectors.md

@@ -73,6 +73,8 @@ async def run(self, db):
 
 **Core file**: `backend/app/services/collectors/base.py`
 
+Manual trigger, data clearing, and cache clearing now enter the PostgreSQL data job queue. `collection_tasks` remains the task ledger. Collectors only own `fetch -> transform -> save`; the `data_jobs.py` worker claims `collect` / `clear_data` / `clear_cache` / `earth_refresh` jobs and writes progress back. Earth layer refresh relationships live in `earth_layer_adapters.py`; do not hand-code cache invalidation or WebSocket broadcasts inside individual collectors or buttons.
+
 ## III. Collector List
 
 | Collector | Data type | Content | Frequency |
@@ -93,7 +95,7 @@ Earth boundaries are no longer data collectors. They are Earth static rendering
 
 TOP500 and Epoch AI compute sources do not always provide usable coordinates. The unified Earth compute-center endpoint uses only valid source-provided coordinates or `compute_center_locations` dimension-table coordinates during the main map startup path; records without coordinates are returned as `unresolved` instead of being rendered from a local registry, country centroid, or guessed city. When users manually collect candidates, the backend queries ROR and Nominatim/OpenStreetMap from source fields; accepted candidates are saved into `compute_center_locations` and rendered from that table on the next layer refresh.
 
-Admin Next collection management follows the business hierarchy instead of flattening every endpoint into one table:
+Admin collection management follows the business hierarchy instead of flattening every endpoint into one table:
 
 - `Collectors`: endpoint, authentication, headers, base parameters, enabled state, and credential guides.
 - `Collection Schedule`: scheduler state and task controls.