An unidentified unique on a base with two of one name is still a question

[JIRPOS]

Release notes

CHANGED: an unidentified unique on a base that rolls into two uniques of the same name now asks
which one it is, instead of naming and pricing the other unique that drops on that base. An
unidentified Topaz Flask was read as a Vessel of Vinktar, a Crystal Wand as a Corona Solaris and a
Primal Arrow Quiver as a Poised Prism; four more bases said no unique dropped on them at all. The
fix is in the game data, so it arrives with the next data release and needs no update.

Review notes

ADDED: a capture of a Stormblood on the Topaz Flask, and a test that the base rolls into two
candidates rather than one, that each identified copy resolves to the record for the base it is
on, and that the search is sent for that base.
CHANGED: the bundle slicer refuses a key naming more than one record instead of quietly taking the
last, so a unique that drops on two bases is asked for as "UNIQUE::Stormblood::Topaz Flask" and
the two game classes that both print "Maps" are told apart by id.
CHANGED: the test bundle carries both flask bases, both Stormblood records and Vessel of Vinktar;
strip_magic_affixes' "not in this bundle" case moved to a base the slice still lacks.

• Nothing in the app changed. The defect was in the data build, which deduplicated item records on
  (namespace, name, tradeDisc) and so threw away 20 of trade's 1,546 unique entries across 13
  names — fixed in PathOfPriceCheck-Data b2364e1, which also documents the identity. What that
  cost was en-items-base.index.bin: a base left with one candidate is not a question the app
  asks, it is the name.

Still outstanding

• en-unique-mods.ndjson keys on the name alone too, so the two variants of a two-base unique
  are merged into one record — Stormblood's says its fixed mods include both the Lightning and the
  Cold ailment line, and five of the affected names show it (Combat Focus, Doryani's Delusion,
  Eclipse Solaris and Precursor's Emblem, the last with 12 duplicated entries). Mostly inert: the
  join is per printed modifier, and the "only trust a range that contains the roll" guard discards
  a range belonging to the other variant. Fixing it means one record per (name, base) and
  find_unique_mods taking the base, which is a coordinated data + app change — released apps
  would get the wrong variant where today they get a superset.
• Artwork is joined per name, so both records of a two-base unique carry one picture — the
  Topaz Stormblood gets StormbloodSapphire.png. That is the game's own answer:
  UniqueStashLayout has one row per name.

🤖 Generated with Claude Code