release: bump version to 0.71.0

docs/technical/en/earth-news-sources.md

@@ -86,6 +86,55 @@ Importance levels are fixed: `low` 0–34, `medium` 35–59, `high` 60–79, and
 
 `GET /api/v1/earth/news-sources` returns the default or saved configuration. `PUT /api/v1/earth/news-sources` saves it, increments `cache_version`, and clears the process region cache. `POST /api/v1/earth/news-sources/reset` restores defaults. `POST /api/v1/earth/news-sources/test` tests one RSS/Atom/Aggregated source without writing news items.
 
+## Manual News Content
+
+Manual news is a content-management path, not an RSS source configuration. The Admin entry is `Earth Content -> News Content`; the left rail groups items by RSS source and manual news group. After opening a manual group, administrators can add one item or upload a JSON array. Manual items are written to `earth_news_items` with `feed_type/source_type = manual`; the display label is “手动添加” / “Manual”. They do not participate in RSS connectivity tests and are not routed through RSS fetching.
+
+Manual news uses a publish-first, enrich-later flow:
+
+1. Saving immediately writes the item to `earth_news_items`.
+2. If no manual coordinates are provided, the selected region anchor is used and `verified=false`.
+3. If manual coordinates are provided, the item uses `location_source=manual_location` and `verified=true`; later AI enrichment does not overwrite that location.
+4. Create and reprocess actions enqueue the item for cleanup, translation, classification, importance, Breaking, and target-location inference.
+5. When enrichment finishes, the same row is updated and Earth receives a news reload / patch so the frontend replaces the item without a manual refresh.
+
+The Admin API is under `/api/v1/earth/news-items`:
+
+- `GET /earth/news-groups`: return RSS virtual source groups and manual news groups.
+- `POST /earth/news-groups`: create a manual news group.
+- `PUT /earth/news-groups/{group_id}`: rename a manual news group and synchronize metadata for items in that group.
+- `GET /earth/news-items`: paginated RSS and manual news list, with filters for source type, region, category, and status.
+- `POST /earth/news-items`: create one manual news item.
+- `POST /earth/news-items/import`: upload a JSON array; `group_id` selects the current manual news group.
+- `PUT /earth/news-items/{id}`: edit a manual news item; RSS items are read-only.
+- `DELETE /earth/news-items/{id}`: delete a manual news item and trigger an Earth news reload.
+- `POST /earth/news-items/{id}/reprocess`: requeue cleanup, translation, and geolocation.
+
+The first JSON import format supports arrays only:
+
+```json
+[
+  {
+    "title": "Required title",
+    "summary": "Optional summary",
+    "content": "Optional body",
+    "url": "https://example.com/story",
+    "source": "Manual",
+    "region": "global",
+    "published_at": "2026-05-15T03:00:00Z",
+    "category": "business",
+    "tags": ["manual", "analysis"],
+    "location": {
+      "label": "Beijing, China",
+      "latitude": 39.9057,
+      "longitude": 116.3913
+    }
+  }
+]
+```
+
+Imports deduplicate through a stable `manual:{hash}` ID derived from title, published time, URL, and source. Importing the same manual item again updates the existing row instead of creating a duplicate EarthFeed entry.
+
 ## Feed Query and Category Filtering
 
 The Web Earth client and UE client both consume `GET /api/v1/news/earth-feed`. The endpoint supports server-side filtering, so clients do not need to fetch the full list and apply the primary category filter locally.
@@ -107,6 +156,8 @@ Unknown category or locale values return `422` with the allowed values. The resp
 
 The Web Earth category chips only store the current browser preference; changing them triggers a new API request. UE should pass its selected categories through the `categories` query parameter and does not need to perform the primary filtering itself.
 
+When `sources` is omitted, the service layer prefers stories that already have displayable title and summary content for the requested `locale`, supplements candidates from enabled sources, and rotates sources so one source's newest pending items cannot occupy all 12 default slots. An explicit `sources` filter remains precise and does not supplement other sources. The database query layer owns region, category, source, and ordering constraints only; it does not own locale presentation policy.
+
 Source testing only proves that a specific RSS/Atom/XML feed can be parsed. It does not mean those items have already been written to the news table or are visible in the current region/category view. Saving or resetting news sources increments the configuration version and clears cache; if an enabled feed has no recent stored items, the next `earth-feed` request supplements from RSS so newly enabled sources such as 36Kr and Ebrun are not masked by fresh Google News rows.
 
 ## Breaking News Insertion
@@ -163,9 +214,11 @@ Reference links show that they only record a homepage, report page, or future co
 ```mermaid
 flowchart LR
   Admin["Admin: Earth Content / News Sources"] --> Source["Source config"]
+  ManualAdmin["Admin: Earth Content / News Content"] --> ManualAPI["/api/v1/earth/news-items"]
   Source --> Feed["Feed children"]
   Feed --> ConfigAPI["/api/v1/earth/news-sources"]
   ConfigAPI --> Config["SystemSetting: earth_news_sources"]
+  ManualAPI --> Store
 
   Earth["Earth News Panel"] --> NewsAPI["/api/v1/news/earth-feed"]
   NewsAPI --> Resolver["Source Resolver"]