poi-plugin-item-improvement2-beta 1.0.22 → 1.0.23

package/REFACTOR_NOTES.md

@@ -1,30 +1,33 @@
-# Data projection refactor
+# Data projection and route refactor
 
 ## Runtime files
 
-The plugin now consumes exactly two backend projections:
+The plugin consumes:
 
 - `assets/db/improvement-list.json`: compact all + seven-day list data.
-- `assets/db/improvement-detail.nedb`: full equipment detail records.
-
-The old `arsenal_all.nedb`, `arsenal_weekday.nedb`, and `items.nedb` runtime split has
-been removed.
+- `assets/db/improvement-detail.nedb`: full equipment detail and recipe routes.
 
 ## Responsibility boundary
 
-- Spider parses Wiki rules and owns list aggregation.
-- The list page reads backend-provided `[itemId, assistantTexts]` rows directly.
-- The detail page reads the detail NeDB records.
-- Spider already emits `shipIdList` and `assistantShipIdsByDay`, but this plugin version
-  deliberately does not consume them yet.
-- Detail presentation continues to use the legacy anchor `id` and source `text`, so an
-  irregular description such as `夕張改二/特/丁` is not reduced to one anchor ship.
+- Spider parses Wiki rules, normalizes assistant IDs and splits concrete recipes.
+- The list page reads backend-provided `[itemId, assistantTexts]` rows.
+- The detail page displays every `improvementList[]` entry as one independent route.
+- Wiki source text remains the default assistant display, so compact expressions are
+  not unexpectedly expanded in the UI.
+
+## Multiple route support
+
+`DetailRow` renders one table per improvement route. Each table uses its own:
 
-## Data source
+- base resources;
+- stage costs;
+- consumables;
+- MAX target;
+- assistant schedule.
 
-`views/improvement-data-source.es` loads, validates, downloads, and replaces the two
-files as one dataset. `selectors.es` only joins the detail records with Poi master data
-and attaches the backend list summary.
+This supports assistant-specific recipes such as the `玉波改二` route for
+`12.7cm連装砲D型改二`, and also prevents future routes with different base resources
+or update targets from sharing the first route's table header.
 
 ## Verification
 
@@ -33,3 +36,12 @@ npm ci --include=dev
 npm test
 npm pack --dry-run
 ```
+
+## Route-aware detail UI (1.0.21)
+
+- Each backend `improvementList` route renders as a separate detail table.
+- Every table uses its own base resources, stage costs, consumables and update
+  target; it no longer borrows the first route's header or recipe.
+- Assistant-specific routes such as 玉波改二 are shown independently from the
+  default route.
+- The bundled schema-v3 detail fixture is covered by tests for item 267.