adventure: show the item, not just its name and price

Renders what gogobee now sends: descriptions, the engine's own effect
summary, slot and skill tags, and a Worn panel with the bond count. One row
template for all three panels — worn, backpack, vault show the same facts and
only the frame differs.

The one distinction worth the wrapper struct: "inert" is a real problem state
— the item is on you doing nothing because all three bonds are spoken for.
The same item in a backpack isn't inert, it's just not worn yet. Rendering
both the same would invent a problem the player doesn't have, on the exact
panel they'd go to to fix it. An ItemView can't tell you which panel it's in,
so itemRow carries it, and TestWhoInertOnlyWhenWorn pins it.

Effect arrives resolved and Pete renders it as given. If it ever disagrees
with what an item does in a fight, that's a gogobee bug — deriving it here
from tier and slot would just be a second opinion that drifts.

No migration: detail rides as a JSON blob.

internal/storage/detail.go

@@ -15,17 +15,34 @@ type PlayerDetail struct {
 	Token     string     `json:"token"`
 	Inventory []ItemView `json:"inventory,omitempty"`
 	Vault     []ItemView `json:"vault,omitempty"`
+	Equipped  []ItemView `json:"equipped,omitempty"`
 	House     HouseView  `json:"house"`
 	Pets      []PetView  `json:"pets,omitempty"`
 }
 
-// ItemView is one backpack or vault item.
+// ItemView is one item in a private panel — backpack, vault, or worn.
+//
+// Desc and Effect arrive already resolved: gogobee's inventory rows carry no
+// description, and the combat delta is computed from the item rather than
+// stored. Effect is the game engine's own summary, not Pete's guess at one — if
+// it ever disagrees with what the item does in a fight, that is a gogobee bug
+// and not something Pete can paper over here.
+//
+// Attunement means the item wants a bond; Attuned means it has one. Only worn
+// items can be Attuned — equipping moves the row out of gogobee's inventory
+// table entirely, so a backpack item's bond state isn't false, it's undefined.
 type ItemView struct {
-	Name   string `json:"name"`
-	Type   string `json:"type"`
-	Tier   int    `json:"tier"`
-	Value  int64  `json:"value"`
-	Temper int    `json:"temper,omitempty"`
+	Name        string `json:"name"`
+	Type        string `json:"type"`
+	Tier        int    `json:"tier"`
+	Value       int64  `json:"value"`
+	Temper      int    `json:"temper,omitempty"`
+	Slot        string `json:"slot,omitempty"`
+	SkillSource string `json:"skill_source,omitempty"`
+	Desc        string `json:"desc,omitempty"`
+	Effect      string `json:"effect,omitempty"`
+	Attunement  bool   `json:"attunement,omitempty"`
+	Attuned     bool   `json:"attuned,omitempty"`
 }
 
 // HouseView is the owner's housing summary.