mqqt_washingMachine/.ai/TASKS.md

TASKS

Use this board to coordinate handoff between planner, implementer, and reviewer.

Status values:

• in_planning
• ready_for_implement
• in_implementation
• ready_for_review
• in_review
• ready_to_commit
• changes_requested
• done

Command expectations:

• planner moves tasks into in_planning and ready_for_implement
• implementer moves tasks into in_implementation, ready_for_review, and done, and resumes work from changes_requested and ready_to_commit
• reviewer moves tasks into in_review, ready_to_commit, or changes_requested
• status_cycle should report deterministic task status, current owner role, and next recommended action based on this board

Task ID	Scope	Status	Acceptance Criteria	Evidence	Next Role
T-001	Status evaluation logic (3-sample window, 3.00 W threshold, waiting/incomplete/running/done) and Tasmota payload parsing, with tests first	done	All state/boundary tests pass (2.99 idle, 3.00 active, gap -> incomplete, <3 samples -> waiting); payload parser handles valid, missing ENERGY/Power, and invalid JSON; fmt/vet/test pass	2026-10-12T11:03:20Z: tests first, fmt/vet/test PASS; review PASS	none
T-002	Per-minute sampler, MQTT subscription, HTTP /api/status and phone-first page, main.go env config	ready_for_implement	Sampler records valid/missing samples per tick; /api/status matches JSON contract; page has white background, large status, 47.70W readings, viewport meta, 60 s refresh; fmt/vet/test pass	n/a	implement
T-003	Dockerfile, docker-compose example, .dockerignore, README documentation	ready_for_implement	Image builds (or noted if Docker unavailable); README documents rules, env vars, deployment, limitations; existing AI Workflow section untouched	n/a	implement