diff --git a/docs/mining-cut-refresh.md b/docs/mining-cut-refresh.md index 54d3d9d81..49eae7c68 100644 --- a/docs/mining-cut-refresh.md +++ b/docs/mining-cut-refresh.md @@ -1,5 +1,7 @@ # Mining: refreshed cut map (v2, operator rulings of 2026-09-30) +> **Superseded in part (master `df7c44f2`).** Chunk reach and picking no longer go through `Zone.ChunksNear` or an `ActionGameManager` candidate list. `Zone.Targets` (`ServerShared/Targeting/`) answers range and best-first queries, `Entity` owns the reticle, next, previous and nearest rules, and belt tasks, `SettleBelts`, `BeltUpdates` and `MineAsteroid` are gone. Read the as-built section "Mining index: as built" in `docs/aetheria-release-map.md` (branch `eureka/aetheria-release-target`) before any anchor below that names `ChunksNear`, `VisibleChunksInReach`'s old body, `ActionGameManager` target code or belt threading. + v1 dated 2026-09-29; this is v2, 2026-09-30. Imagination output for Self. It re-anchors the Codex mining lane to the Body as it will stand after `codex/fire-control-12` merges to `master`, and it incorporates the operator's rulings of 2026-09-30: diff --git a/docs/mining-cut.md b/docs/mining-cut.md index d9f601a28..7c5be8297 100644 --- a/docs/mining-cut.md +++ b/docs/mining-cut.md @@ -1,5 +1,7 @@ # Mining: Target and Cut Map +> **Superseded in part (master `df7c44f2`).** Chunk reach and picking no longer go through `Zone.ChunksNear` or an `ActionGameManager` candidate list. `Zone.Targets` (`ServerShared/Targeting/`) answers range and best-first queries, `Entity` owns the reticle, next, previous and nearest rules, and belt tasks, `SettleBelts`, `BeltUpdates` and `MineAsteroid` are gone. Read the as-built section "Mining index: as built" in `docs/aetheria-release-map.md` (branch `eureka/aetheria-release-target`) before any anchor below that names `ChunksNear`, `VisibleChunksInReach`'s old body, `ActionGameManager` target code or belt threading. + Date: 2026-09-25 (corrected for M0, 2026-09-30) Status: target and cut map, from an Imagination pass. Cuts 1 and 2 have landed on `codex/mining` (see the status diff --git a/docs/scenarios-cut.md b/docs/scenarios-cut.md index 25102e378..82b5c1c10 100644 --- a/docs/scenarios-cut.md +++ b/docs/scenarios-cut.md @@ -834,7 +834,7 @@ Defaults Self took, which you may overrule: No correctness bug was found. The suite passes 516/516 with the catalog `b698e224` and the settings `b2e346f5` that the commit pins. The shared `pins/data/Settings.asset` (`347752dd`) is scenarios' file, so any runner that mounts that path by default has been testing mining with the wrong settings. Findings: -- **F1 (medium, operator):** picking a rock in a big belt costs one scan of every rock the search circle reaches. `Zone.ChunksNear` (`Zone.cs:333`) and `VisibleChunksInReach` (`Entity.cs:378-385`) run on every reticle, next or previous key press. Measured cost: 63 ms at 30k rocks, 449 ms at 300k and 4.3 s at 3M. The per-tick cost is fine. +- **F1 (medium, operator; fixed on master `df7c44f2` by the targeting index, no longer a scan; still O(rocks) per press, deferred to `mining-index-tree` and `mining-belt-cells`):** picking a rock in a big belt costs one scan of every rock the search circle reaches. `Zone.ChunksNear` (`Zone.cs:333`) and `VisibleChunksInReach` (`Entity.cs:378-385`) run on every reticle, next or previous key press. Measured cost: 63 ms at 30k rocks, 449 ms at 300k and 4.3 s at 3M. The per-tick cost is fine. - **F2 (medium):** nothing tests that the shipped catalog has a rock kind. Taking either side of the catalog conflict unchanged ships dark belts silently. Add a test for "at least one rock kind with weight above 0". - **F3:** the merge rule is corrected above. - **F4 (medium):** nothing tests the ping half of `Sensor.Gain`, because the golden fixture saturates at the cap. Two mutants survive (`Sensor.cs:168`, `:189`). Soul's sweep fixture kills both and gives the same hash (`35DE0E26…`) before extraction, at extraction and at the tip.