W105.3 — Fold in the vehicle transport waiver from games/03-game-design.md sec16.4

The user supplied the companion game design doc directly, revealing "Transport ...
waived if the player owns a vehicle" -- an asymmetry the original W105.3 amendment
missed (transportCents was unconditional, same as utilitiesCents). Added a reserved
"vehicle" tag on ItemDefinition.tags that housing checks against player.inventory;
utilitiesCents keeps no such waiver, matching sec16.4's own asymmetry. Revised the
90-decisions.md entry in place rather than superseding it, since the PR hasn't merged.

Author: The-Running-Dev

design/20-contract.md

@@ -5087,7 +5087,7 @@ value this kind computes rather than stores.
 **`utilitiesCents`/`transportCents` (W105.3; [issue #109](https://github.com/The-Running-Dev/SubZeroDev.GameOfLife/issues/109)).**
 Charged separately from rent means itemized as distinct cost lines a player can see, not a
 separate consequence track: the `housing` end-of-week system (§3) charges
-`weeklyCostCents + utilitiesCents + transportCents` as one combined levy against
+`weeklyCostCents + utilitiesCents + effectiveTransportCents` as one combined levy against
 `cashCents`, unconditionally, in the same pass and by the same rule §3's own W53/W55 decision
 already gives rent alone (`90-decisions.md`, 2026-08-08 entry) — `cashCents` may go negative,
 proving the same "wages before costs" ordering claim. `missedCents` is computed from that
@@ -5099,6 +5099,20 @@ content that declares neither is unaffected. `HousingState` (§6.9) gains matchi
 `weeklyCostCents` already is — a `kindVersion` bump and `Kind.migrateState` default both to `0`
 for a save with no such fields (§10.2).
 
+**`transportCents` is waived when the player owns a vehicle; `utilitiesCents` is not.** The
+companion game design (`games/03-game-design.md` §16.4, mirrored from GameOfLife) states this
+asymmetry directly for its own baseline scenario: "Transport ... waived if the player owns a
+vehicle," with no equivalent stated for utilities. `effectiveTransportCents` (above) is
+`0` for a week in which `player.inventory` (§6.10) contains at least one `InventoryItem` with
+`condition > 0` whose `ItemDefinition.tags` (§7.5) includes the reserved literal `"vehicle"`,
+and `HousingState.transportCents` otherwise. **`"vehicle"` is this kind's first
+engine-recognized tag value** — every other `tags: string[]` field in this kind (§7.2, §7.5,
+§7.6, §7.9) is free-text content-author metadata nothing in `src/engine` branches on; this is
+the first tag the `housing` system itself reads, the same kind of reserved-namespace
+precedent `core.reason.*` (04 §12) already sets for reason codes. `housing` (§3) is threaded
+`items: readonly ItemDefinition[]` to evaluate this, the same parameter shape `jobs`/`goalDefs`
+already use for their own end-of-week systems.
+
 ### 7.5 Items
 
 ```typescript

design/90-decisions.md

@@ -1498,7 +1498,11 @@ Chosen (user-selected over the alternative below): two new optional `Cents` fiel
 
 Rejected: **Separate arrears tracking** (independent `overdueUtilitiesCents`-style state, no eviction consequence for utilities/transport specifically) — presented to the user as the alternative and declined; more faithful to "separate from rent" as a full consequence split, but adds new runtime state and a second reconciliation rule with no player action (a `pay_bills`-equivalent) specified to clear it, for a distinction (eviction only ever follows unpaid rent, never unpaid utilities) the issue never asked for.
 
-Reversibility: cheap as a contract statement; a `kindVersion` bump and `Kind.migrateState` are real once implemented, and the combined-levy choice becomes a compatibility surface for any Stable Life save that predates it.
+**Revised the same day, against new evidence.** The user supplied `games/03-game-design.md` §16.4 directly after this entry was first written from the issue text alone. It states the recurring-cost baseline as a table — Rent $95, Utilities $18 ("scales with housing tier"), Transport $15 ("**waived if the player owns a vehicle**") — and §10.2 independently confirms both W105.1 and W105.2's examples verbatim ("Clothing improves employability or prestige"; "A vehicle reduces travel time but creates fuel, insurance, and repair expenses"). The combined-levy/one-arrears-mechanism call above is unchanged — nothing in §16.4 contradicts it — but the unconditional charge was wrong for `transportCents` specifically: §16.4 states a waiver this entry's original text did not capture, because the source document wasn't available to read. Amended: `effectiveTransportCents` is `0` for a week in which `player.inventory` (§6.10) holds an unbroken `InventoryItem` whose `ItemDefinition.tags` (§7.5) includes the reserved literal `"vehicle"`, and `HousingState.transportCents` otherwise; `utilitiesCents` keeps no such waiver, matching §16.4's own asymmetry (only the Transport row states one). This is this kind's first engine-reserved tag value — every other `tags: string[]` field is free-text content metadata nothing in `src/engine` reads — the same kind of reserved-namespace move `core.reason.*` already made for reason codes (04 §12). `housing` (§3) is threaded `items: readonly ItemDefinition[]`, the same shape `employment`/`goals` already thread `jobs`/`goalDefs`.
+
+Rejected (for the amendment): **Record the waiver as a known-and-retained gap instead of amending** — offered to the user as the lower-scope alternative and declined; §16.4 states the behavior plainly enough, and the tag mechanism needed to express it is small and additive rather than speculative. **A `Requirement`-shaped check instead of a reserved tag** — considered and dropped without asking; `Requirement` (§8.1) gates an action or eligibility, not a per-week automatic waiver with no failure code or message to attach, so reusing it would be forcing an ill-fitting shape onto a simpler rule.
+
+Reversibility: cheap as a contract statement; a `kindVersion` bump and `Kind.migrateState` are real once implemented, and the combined-levy choice becomes a compatibility surface for any Stable Life save that predates it. The reserved `"vehicle"` tag is a soft convention, not a type — reversible by simply not checking for it, though any campaign that has already tagged an item `"vehicle"` for the waiver would then need a replacement mechanism.
 
 ### 2026-09-07 — W105.4: `NPCDefinition` gains `startingMemories`
 

docs/docs/engine/10-simulation-kind.md

@@ -1694,7 +1694,7 @@ value this kind computes rather than stores.
 **`utilitiesCents`/`transportCents` (W105.3; [issue #109](https://github.com/The-Running-Dev/SubZeroDev.GameOfLife/issues/109)).**
 Charged separately from rent means itemized as distinct cost lines a player can see, not a
 separate consequence track: the `housing` end-of-week system (§3) charges
-`weeklyCostCents + utilitiesCents + transportCents` as one combined levy against
+`weeklyCostCents + utilitiesCents + effectiveTransportCents` as one combined levy against
 `cashCents`, unconditionally, in the same pass and by the same rule §3's own W53/W55 decision
 already gives rent alone (`90-decisions.md`, 2026-08-08 entry) — `cashCents` may go negative,
 proving the same "wages before costs" ordering claim. `missedCents` is computed from that
@@ -1706,6 +1706,20 @@ content that declares neither is unaffected. `HousingState` (§6.9) gains matchi
 `weeklyCostCents` already is — a `kindVersion` bump and `Kind.migrateState` default both to `0`
 for a save with no such fields (§10.2).
 
+**`transportCents` is waived when the player owns a vehicle; `utilitiesCents` is not.** The
+companion game design (`games/03-game-design.md` §16.4, mirrored from GameOfLife) states this
+asymmetry directly for its own baseline scenario: "Transport ... waived if the player owns a
+vehicle," with no equivalent stated for utilities. `effectiveTransportCents` (above) is
+`0` for a week in which `player.inventory` (§6.10) contains at least one `InventoryItem` with
+`condition > 0` whose `ItemDefinition.tags` (§7.5) includes the reserved literal `"vehicle"`,
+and `HousingState.transportCents` otherwise. **`"vehicle"` is this kind's first
+engine-recognized tag value** — every other `tags: string[]` field in this kind (§7.2, §7.5,
+§7.6, §7.9) is free-text content-author metadata nothing in `src/engine` branches on; this is
+the first tag the `housing` system itself reads, the same kind of reserved-namespace
+precedent `core.reason.*` (04 §12) already sets for reason codes. `housing` (§3) is threaded
+`items: readonly ItemDefinition[]` to evaluate this, the same parameter shape `jobs`/`goalDefs`
+already use for their own end-of-week systems.
+
 ### 7.5 Items
 
 ```typescript