ha-closet

Infer accessory sizing for jewelry and watches categories and are now recognized category roots: in maps them to the existing , the same way and already work. Purchases in these categories no longer need a manually declared in , and no longer fail with a confusing item-level when the author forgets to declare one. Behavior change worth noting now fires for / categories that declare a non-accessory (for example on a ring). Before this change the check was skipped for these roots (inference returned nothing to compare against), so such catalogs compiled. The one-line fix is . Catalogs with no declared are unaffected — inference covers them now. What's in the box Inference arms (): / roots and dot-prefixed children infer accessory sizing. No new // variants; ring sizes (numeric with halves, e.g. ) and watch inventory () fit the existing accessory forms and bounds. Compiler tests (): one test proves both roots infer accessory sizing with no declared (ring renders , watch renders ); one proves a wrongly declared kind now fails (asserted as the single recorded error). These are also the first tests anywhere covering accessory-kind numeric sizing. Fictional examples (): a "Band ring" (, metal composition, size on a bounded accessory profile) and a "Field watch" (, ), following the existing tee entry's shape, with URLs. The example categories omit , so the existing example-catalog CI tests exercise the inference end to end. Docs (): one sentence documenting that recognized roots infer their sizing kind while unrecognized roots declare explicitly, plus a stale example-description fix. One over-broad assertion in the numeric-pair roundtrip test was scoped to the tee purchases it actually tests (the new heterogeneous example purchases made the blanket assertion untestable). Out of scope, deliberately Today outfit generation () is untouched — jewelry and watches stay out of outfit suggestions, consistent with the existing belts/hats exclusion and the project's "Today is an optional experiment" stance. No web UI, HA integration, OpenAPI, or migration changes were needed: category and size travel through those layers as opaque strings.