docs: document decay + upkeep in item-data READMEs (6b)

Author: HandyS11

README.md

@@ -10,7 +10,7 @@ The bot is live: it pairs with Rust+ over FCM, holds a socket per server, and
 auto-provisions its own Discord channels. Pairing/connection, the chat bridge,
 in-game `!commands` and slash surfaces, live map events, map rendering, smart
 devices (switches, alarms, storage monitors), and an offline item database with
-recycle/craft/research calculators are all shipped. Cameras are next.
+recycle/craft/research/decay/upkeep calculators are all shipped. Cameras are next.
 
 ## Features
 
@@ -48,14 +48,14 @@ configurable per-server prefix (default `!`) and per-command cooldowns:
 - **Server** — `!pop`, `!time`, `!wipe`
 - **Team** — `!online`, `!offline`, `!team`, `!alive`, `!steamid [name]`, `!prox [name]`
 - **Live events** — `!cargo`, `!heli`, `!chinook`, `!small`, `!large`, `!events`
-- **Items** — `!item`, `!recycle`, `!craft`, `!research` (name or id)
+- **Items** — `!item`, `!recycle`, `!craft`, `!research`, `!decay`, `!upkeep` (name or id)
 - **Control** — `!mute` / `!unmute` (gate all bot→game output)
 
 ### Slash commands
 
 - **Server data** (ephemeral, with a `server` selector when several are paired) —
   `/pop`, `/time`, `/wipe`, `/online`, `/offline`, `/team`, `/alive`, `/small`, `/large`
-- **Items** (ephemeral) — `/item`, `/recycle`, `/craft`, `/research` (name or id)
+- **Items** (ephemeral) — `/item`, `/recycle`, `/craft`, `/research`, `/decay`, `/upkeep` (name or id)
 - **Utility** — `/help`, `/uptime`, `/leader` (Manage Server — transfer in-game team leadership)
 - **Admin** — `/setup`, `/workspace reset`, `/workspace simulate-server`
 
@@ -75,8 +75,9 @@ configurable per-server prefix (default `!`) and per-command cooldowns:
 ### Item database & calculators
 
 - An **offline, versioned item dataset** (bundled, ~1200 items) behind one
-  lookup seam, exposing four calculators both in-game and as ephemeral slash
-  commands: item info, recycler yields, craft recipes, and research scrap cost.
+  lookup seam, exposing six calculators both in-game and as ephemeral slash
+  commands: item info, recycler yields, craft recipes, research scrap cost,
+  decay time, and building-block upkeep cost.
 - **Name-or-id lookup** — type a name (case-insensitive, partial), an exact name,
   or a numeric id; multiple matches return a short "did you mean" list.
 - **Provenance-aware** — each result footers the date its data was sourced, and a
@@ -127,7 +128,7 @@ See [docs/development/running-locally.md](docs/development/running-locally.md).
 | `RustPlusBot.Features.Commands` | In-game `!commands`, slash surfaces, `/help`/`/leader` |
 | `RustPlusBot.Features.Events` | Live map-event classification + `#events` feed |
 | `RustPlusBot.Features.Map` | Map image rendering with toggleable layers |
-| `RustPlusBot.Features.ItemData` | Bundled item dataset, lookup seam, recycle/craft/research data |
+| `RustPlusBot.Features.ItemData` | Bundled item dataset, lookup seam, recycle/craft/research/decay/upkeep data |
 | `RustPlusBot.Host` | Generic Host entry point, DI wiring, startup validation |
 
 The `tools/` folder holds maintainer utilities that are not part of the running
@@ -147,7 +148,7 @@ Subsystems are built in order; each has its own spec → plan → build cycle.
 | 3 | Chat bridge + `!commands` + slash surfaces | Done |
 | 4 | Smart devices (switches, alarms, storage monitors) | Done |
 | 5 | Cameras | Planned |
-| 6 | Item database & calculators (recycle/craft/research) | In progress |
+| 6 | Item database & calculators (recycle/craft/research/decay/upkeep) | In progress |
 
 ## License
 

tools/RustPlusBot.ItemData.Generator/README.md

@@ -2,7 +2,7 @@
 
 A maintainer CLI that regenerates the embedded Rust item dataset
 (`src/RustPlusBot.Features.ItemData/Data/item-data.json`) consumed by the bot's
-`/item`, `/recycle`, `/craft`, and `/research` calculators.
+`/item`, `/recycle`, `/craft`, `/research`, `/decay`, and `/upkeep` calculators.
 
 This tool is **not** part of the running bot — it is referenced by nothing in
 the application graph. It exists so the bundled item data can be refreshed when
@@ -13,11 +13,11 @@ Rust updates, rather than shipping a frozen copy that silently rots.
 The reference data has two very different freshness profiles:
 
 - **Item names / ids** are well maintained and current.
-- **Calculator data** (recycle yields, craft recipes, research costs) is sourced
-  from rustlabs and tends to lag game updates.
+- **Calculator data** (recycle yields, craft recipes, research costs, decay
+  times, upkeep costs) is sourced from rustlabs and tends to lag game updates.
 
 So the dataset carries per-section provenance dates (`Sources.NamesAsOf`,
-`RecycleAsOf`, `CraftAsOf`, `ResearchAsOf`), surfaced to users as a
+`RecycleAsOf`, `CraftAsOf`, `ResearchAsOf`, `DecayAsOf`, `UpkeepAsOf`), surfaced to users as a
 "data as of `<date>`" footer, and this tool can re-emit a fresh snapshot on
 demand. It **validates loudly and refuses to overwrite a good bundle with
 garbage** if the upstream shape drifts.
@@ -35,12 +35,16 @@ garbage** if the upstream shape drifts.
    | `rustlabsRecycleData.json` | recycler yields |
    | `rustlabsCraftData.json` | craft ingredients + time |
    | `rustlabsResearchData.json` | research scrap cost |
+   | `rustlabsDecayData.json` | decay time + HP |
+   | `rustlabsUpkeepData.json` | upkeep cost (resource + quantity range) |
 
 2. Projects them into our own typed schema (`ItemDataset` /
    `ItemRecord` / …, defined in `RustPlusBot.Features.ItemData`), keyed by item id,
    with calculator data inlined per item (null where an item has none).
-3. **Validates** the result (`DatasetValidator`): a minimum item-count floor and
-   that every recycle-yield / craft-ingredient id resolves to a known item.
+3. **Validates** the result (`DatasetValidator`): a minimum item-count floor,
+   that every recycle-yield / craft-ingredient / upkeep-cost id resolves to a
+   known item, that upkeep quantity ranges are well-formed (`min <= max`), and
+   that decay values are non-negative.
 4. On any validation error, prints the errors to stderr and exits non-zero
    **without writing** — the existing good bundle is never clobbered.
 5. On success, writes the dataset as indented JSON and exits 0.