docs: document 15 missing bus events, fix badge sensor id and stale counts
- Automations is the canonical event reference and was missing 15 of the 36
events TaskMate fires: the whole mandatory-miss set, allowance, family goal,
season champion, undo, and every v5.0.0 event (chore expired, roulette spun,
unlock started/ended, scheduled change applied, guest archived, read aloud).
Payload fields taken from each async_fire call.
- Achievement Badges and Sensor Reference gave the per-child badge sensor as
sensor.taskmate_badges_<child>. It is sensor.taskmate_<child>_badges.
- Notifications said the routing matrix has 6 built-in types; there are 15, and
its bus-event table listed only 11 of them.
- Notifications' migration section still pointed at the removed config flow.
- Chores had a note saying due days are set via the config flow, described
'Add Multiple Chores' rather than Bulk add, and its field table predated the
weather, scheduled-change and visibility sections.
- Visibility Operators Reference omitted the default None operator and the
attribute-matching fallback.
docs: stop sending readers to a configuration UI that was removed in v4.0.0
Fourteen pages still documented the old options/configure flow — "Settings →
Devices & Services → TaskMate → Configure → Manage Chores", a Step 1/Step 2
wizard, a four-item menu. None of that exists. config_flow.py has exactly one
step (async_step_user) and does nothing but initial setup. Admin-Panel.md has
said the flow "was retired in v4.0.0" the whole time, while the rest of the
wiki kept pointing at it — including line 1 of Settings.md and the first
walkthrough a new user reads in Getting Started.
Visibility Configuration Guide was the worst of them and is substantially
rewritten. Beyond the dead setup flow it also had:
- No mention of the "None" operator, which is what every chore starts with.
- A wrong claim that an unavailable entity defaults to visible. Only a MISSING
entity short-circuits to visible; "unavailable" is an ordinary state string
that fails the comparison, so the chore hides. That is the opposite of what
a reader was told to expect.
- Two "common mistakes" that contradicted each other and the code — one said
matching is case-insensitive, the next implied case matters. It is
case-insensitive.
- No mention that a value beginning >=, <=, >, < or != overrides the operator
dropdown, or that attribute values are matched when the state doesn't match.
Both are real behaviours in _is_visibility_entity_active.
Also corrected: card counts of 17 and 18 in Getting Started, Installation and
Card Design Styles (21), and [[Configuration Guide]] links on two pages, which
pointed at a page that has never existed.
Add Settings, Localization pages; card selection guide; calendar event format; clarify assignment/visibility/claim_allowance
Created Visibility Operators Reference (markdown)