docs: complete the page-by-page read — card options, sensor fields, service fields
Final pass over the reference pages.
- Dashboard Cards documented the Child Card without show_roulette, pre_reader
or pre_reader_labels, all of which the card accepts. Added, with a note that
roulette currently only renders on the classic design.
- Sensor Reference repeated pending_points and committed_points in the
children table, and omitted the v5 per-child fields is_guest,
guest_expires_on and roulette that sensor.py exposes.
- Services documented every service but was missing three accepted fields:
expires_in_minutes and speed_bonus_points on add_chore (reactive chores),
and combinator on add_badge/update_badge. Its 'not exposed on add_chore'
note predated the reactive-chore fields.
All 71 pages have now been read end to end. Cross-checks pass: no broken page
links, no broken anchors, no missing images.
docs: fix contradicting ranges, stale nav lists and remaining wizard steps
- Settings repeated the wrong perfect-week range (10-500; it is 0-1000) and
gave the family-goal target default as 0 when the panel defaults it to 500,
contradicting the Family Goals page.
- Sensor Attributes documented the per-child sensors as sensor.<child>_points
and _stats. They are sensor.taskmate_<child>_points/_stats.
- card_design was still listed without accessible on Sensor Attributes and in
two places on Sensor Reference.
- Admin Panel's navigation description omitted Insights and Audit from the
sidebar groups.
- Dynamic Chore Visibility repeated the same wrong 'unavailable defaults to
visible' claim twice, and still had a config-flow 'Complete Step 2' step.
- Chore Scheduling said 'two scheduling modes' while documenting three, and
still referenced Step 1/Step 2 of the removed wizard plus a 'Re-enable
Chore' action that is now Activate chore in the row menu.
- Five more 'Continue to Step 1 visibility fields' leftovers in the visibility
scenarios.
- Card Design Styles had the Accessible section below Related; moved it up.
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.
docs: illustrate the wiki — 44 new screenshots across 59 pages
Image coverage goes from 6/71 pages to 65/71, and from 8 images to 52.
Captured from the live dev instance: every admin panel tab (including the
Audit tab, which only became reachable in the panel fix that accompanies
this), all four Insights reports, all 21 Lovelace cards, the five card design
styles side by side, and the Home Assistant surfaces the reference pages
describe — the integration entry, Developer Tools states, and the to-do lists.
Two things worth recording about how these were produced:
- Scaffolding data in the dev instance (I558 Step A, E2E Test Quest, E2E687
Cousin) would have looked unprofessional in a public wiki, so the capture
relabels it to realistic household chores. That relabelling happens on an
in-page copy of the state only — nothing is written back, and the dev
instance keeps its issue-reproduction data intact.
- Child-scoped cards pick the child who actually has chores outstanding,
otherwise half of them would have documented their own empty state.
The design-styles image was replaced rather than added: the previous one
showed four styles and predated Accessible, so its caption was wrong too.
Six pages are still text-only — Automations, FAQ, Services, Troubleshooting,
Visibility-Operators-Reference and Voice-Assistants. All six are reference
tables or prose where a screenshot would decorate rather than explain.
Created Visibility Configuration Guide (markdown)