release: bump version to 0.59.0

docs/technical/en/datasource-collector-settings-connectivity.md

@@ -8,12 +8,12 @@ The console now separates the "data source catalog" from "collector configuratio
   - Lists all data sources, including built-in and custom sources.
   - Clicking a name only opens an information drawer.
   - Focuses on status, manual collection, and running collection tasks.
-- `/settings?tab=collector_credentials`
-  - Displays as "Collector Settings".
+- `/collection-management?tab=collector_credentials`
+  - Displays as "Collectors".
   - Owns endpoint, headers, base parameters, and credentials.
   - Every collector exposes a connection button for health checks.
 
-This reduces first-use confusion: API endpoints, headers, credentials, and custom source configuration all belong to collector settings instead of being scattered across the data source list and system settings.
+This reduces first-use confusion: API endpoints, headers, credentials, and custom source configuration all belong to Collectors instead of being scattered across the data source list and system settings.
 
 ## User-Facing Rules
 
@@ -53,7 +53,7 @@ Current behavior:
 
 `data-source-bulk-toolbar__running-pill` is the styling entry point for the "Collecting" pill. It is aligned with other status tags, while hover treatment, arrow affordance, and blue outline indicate interactivity.
 
-### Collector Settings
+### Collectors
 
 File:
 
@@ -61,7 +61,7 @@ File:
 
 Current behavior:
 
-- The `collector_credentials` tab is displayed as "Collector Settings".
+- The `collector_credentials` tab is displayed as "Collectors" under `/collection-management`.
 - A select lists built-in collectors and supports maintaining custom supplemental sources that merge into built-in data.
 - The only button beside the select is a plug icon for health checks.
 - Status tags below the select show:
@@ -307,7 +307,7 @@ Files:
 
 Custom sources are supplemental inputs for existing target schemas, not isolated data islands. The most complete target today is `vessel_ais`: a custom REST or WebSocket source is mapped deterministically, written into AIS raw observations, and then pushed to Earth through the `vessels` WebSocket channel.
 
-Earth high-precision boundaries use the same target-schema mechanism. `earth_boundary_source` receives mapped records for `earth_admin0_boundaries`, `earth_coastline`, and `earth_claim_lines`; full GeoJSON / JSON payloads are stored as artifacts, while the database only keeps source kind, sha256, feature count, license, artifact path, and sample properties so large geometries do not land in a single row.
+Earth high-precision boundaries no longer use custom-source target schemas. Boundaries are Earth static assets: the Earth Assets settings panel saves local source configuration and triggers PMTiles builds without writing records to `CollectedData`.
 
 ### Configuration Semantics
 
@@ -318,7 +318,7 @@ Important fields:
 - `auth_type`: `none`, `bearer`, `api_key`, or `basic`.
 - `headers`: static request headers.
 - `auth_config`: token, API key, or basic username/password; API keys can be sent by header or query.
-- `config.target_schema`: for example `vessel_ais` or `earth_boundary_source`.
+- `config.target_schema`: for example `vessel_ais`, `geo_points`, or `generic_records`.
 - `config.delivery_mode`: REST defaults to `polling`; WebSocket defaults to `realtime_stream`.
 - `config.merge_target_source`: records which built-in source this custom source supplements, such as `barentswatch_vessels`.