fix: second pass over the 2023-client wire defects, plus a coverage harness

Fourteen agents worked one server file each over the audit's open findings,
re-verifying every claim against the client binary before changing anything.
Route+verb coverage against the recovered client inventory is now 474/522
(90.8%), up from 86.2% when the harness was first wired up.

Adds ClientRouteCoverageTests, which turns "are we compliant?" into a number
instead of an opinion. It reads data/client-routes-2023.tsv — every request the
2023-03-21 client can issue, recovered from the binary — and asserts each one
has a handler under the verb the client actually uses, separating "no handler"
from "handler exists, wrong verb" since those have different fixes. Remaining
gaps live in KnownGaps, which is expected to shrink and never grow.

Also fixes a real blind spot in EndpointContractDiscovery: it only collected
HttpMethodAttribute, so an action carrying a bare [Route] with no verb attribute
was invisible to it. The CDN's unity_assets handler is exactly that shape, which
had been showing up as a phantom gap.

Notable findings from this pass:

- The club permissions envelope key is literally "Type", not "MembershipType"
  as the audit's suggested fix guessed. Read off the generated reader, then
  cross-checked against the 2020 decompile — the int bitmask we were emitting
  was wrong for BOTH client generations, not just 2023.
- Room-consumable purchase responses carry OperationResult as an OBJECT
  { Status, InventoryItem }; the scalar operation enum belongs in
  BalanceUpdateResult. The base type OKHNOPLBOFP holds a single BGHBAILNNJJ,
  which exposes exactly those two properties. A test asserting the old scalar
  shape was corrected rather than the code.
- buyProgressionEventXpBoost blind-inserted an ObjectiveProgress row whose
  (PlayerId, Key) is unique, so a second purchase of the same boost threw
  "UNIQUE constraint failed" and 500'd AFTER taking the player's currency.
  Now an upsert.

Agents were forbidden from faking fixes they could not complete in their own
file, and several correctly refused: club role permissions, club additional
image slots, announcement meta, MinLevel/ClubChatEnabled, currency purchase
offer ordering, and room-key image/currency columns all need new entities or
columns. Those are deliberately left for a single coherent schema change rather
than stubbed out here.

DorkNet.Server/Controllers/API/RoomConsumables/RoomConsumablesController.cs

@@ -18,10 +18,16 @@ namespace DorkNet.Server.Controllers.API.RoomConsumables;
 /// LPFAFIGAIOE / HJOKFJKKEJM / IDBFKCFEAHM / PECGEJAAMHB / DPNLANKOHON):
 ///
 ///   desc      = { RoomConsumableId, RoomId, Name, Description, ImageName,
-///                 PriceAndCurrency: { Price, CurrencyId } }
+///                 Price, PurchaseCurrencyId, ModifiedAt }
 ///   inventory = { RoomConsumableId, AccountId, Count, ConcurrencyCode,
 ///                 ModifiedAt, Consumable: desc }
 ///
+/// The desc price is FLAT on the way OUT even though it is NESTED on the way
+/// IN. The response formatter FCIBLPCOODP's key map is exactly the eight keys
+/// above — Price at index 5, PurchaseCurrencyId at 6, ModifiedAt at 7, and no
+/// PriceAndCurrency key at all (FCIBLPCOODP.txt:670/686/710). See ToDescWire.
+/// The inventory key map is likewise exact (CICEHLNDLDE.txt:447-562).
+///
 /// <c>Consumable</c> must never be null on an inventory row — the
 /// client's RoomConsumablesManager dereferences it unconditionally while
 /// processing the room-join inventory fetch and NREs otherwise (that NRE