fridge: fold the three Auto Door Open variant hrefs into one pattern cap (issue #328)

AUTO_DOOR_SINGLE/KIMCHI/WINECELLAR were identical one-line no-entity
Capability declarations differing only by href. Replaced with
AUTO_DOOR_VARIANT, a pattern cap keyed on href_prefix='/autodoor/' and
gated by match_fn (presence of ado.openOptions) rather than the prefix
alone, so it only claims the variant-declaration hrefs and not
/autodoor/timer/vs/0 -- which doesn't matter in practice anyway, since
that href's own exact-href AUTO_DOOR_TIMER cap always wins first.

Registry-scoped (refrigerator.py's own pattern_capabilities list), not
global ignored.py -- the unknown-device-type fallback that motivates
ignored.py's 'exact hrefs only' rule never reaches this registry, so the
same constraint doesn't apply. A fourth fridge sub-type reporting this
feature at a new href now needs no code change to stay covered.

custom_components/localthings/registry/by_type/refrigerator.py

@@ -16,9 +16,6 @@ REGISTRY = DeviceRegistry(
             fridge.AIR_FILTER,
             fridge.DEODOR_FILTER,
             fridge.AUTO_DOOR_TIMER,
-            fridge.AUTO_DOOR_SINGLE,
-            fridge.AUTO_DOOR_KIMCHI,
-            fridge.AUTO_DOOR_WINECELLAR,
             fridge.WINECELLAR_PANTRY_ZONE,
             fridge.WINECELLAR_INFO,
             dishwasher.DIAGNOSIS,
@@ -51,5 +48,6 @@ REGISTRY = DeviceRegistry(
         fridge.DOOR_GENERIC,
         fridge.KIMCHI_ZONE,
         fridge.KIMCHI_DOOR_GENERIC,
+        fridge.AUTO_DOOR_VARIANT,
     ],
 )

custom_components/localthings/registry/capabilities/fridge.py

@@ -383,16 +383,27 @@ AUTO_DOOR_TIMER = Capability(
 )
 
 # /autodoor/<variant>/vs/0 -- one per fridge sub-type sharing the Auto Door
-# Open feature (single-door, kimchi, winecellar; issue #328). Each reports
-# only x.com.samsung.da.ado.openOptions, declaring which open styles that
-# variant supports -- every dump seen so far carries exactly one option
-# ('Single') with no paired desired/current field to make a choice against,
-# the same "no real choice to expose yet" shape as ignored.py's /mode/0.
-# Bound with no entities to record the three hrefs as coverage; revisit if
-# a device ever reports more than one option.
-AUTO_DOOR_SINGLE = Capability(href="/autodoor/single/vs/0")
-AUTO_DOOR_KIMCHI = Capability(href="/autodoor/kimchi/vs/0")
-AUTO_DOOR_WINECELLAR = Capability(href="/autodoor/winecellar/vs/0")
+# Open feature (single-door, kimchi, winecellar seen so far; issue #328).
+# Each reports only x.com.samsung.da.ado.openOptions, declaring which open
+# styles that variant supports -- every dump seen so far carries exactly
+# one option ('Single') with no paired desired/current field to make a
+# choice against, the same "no real choice to expose yet" shape as
+# ignored.py's /mode/0. Bound with no entities to record coverage; revisit
+# if a device ever reports more than one option.
+#
+# A pattern cap rather than one entry per variant: match_fn (not just the
+# prefix) is what actually gates this, so a future variant href needs no
+# code change to stay covered, and /autodoor/timer/vs/0's own exact-href
+# AUTO_DOOR_TIMER above always wins for that href regardless (discover()
+# only falls through to pattern caps when no exact cap matched). This is
+# registry-scoped, not global -- unlike ignored.IGNORED, the unknown-
+# device-type fallback never reaches it, so the prefix caveat in
+# ignored.py's own docstring doesn't apply here.
+AUTO_DOOR_VARIANT = Capability(
+    href=None,
+    href_prefix="/autodoor/",
+    match_fn=lambda rep, resources: "x.com.samsung.da.ado.openOptions" in rep,
+)
 
 # Wine-cellar variant (x.com.st.d.winecellar, issue #328) of the same
 # deodorizing filter AIR_FILTER models -- filterUsage/filterStatus at a