Tody?

Build a focused replacement for Tody for one clearly defined user, based on this public product description: “Tody — Your cleaning schedule, on autopilot — Tody is a cleaning-schedule app for iPhone, iPad, and Android that keeps track of what needs cleaning and when, so the plan for a clean home doesn't have to live in one person's head.” Do not copy the original brand, proprietary assets, name, logo, UI, or copy; create an original visual system.

Core workflow
- Recreate only the narrow primary workflow described above, with model the product's primary input → workflow → output in an editable interface; make state, errors, and external dependencies visible; provide portable data, export, and deletion controls; include fixture data and a deterministic happy-path test.
- Keep the product name and source description in a research note in the README, and turn every uncertain behavior into an explicit assumption or user setting rather than inventing a feature.
- Use a small React/TypeScript app with a portable JSON or SQLite data model, clear loading/empty/error states, and adapters around external services. Seed realistic demo data so the complete workflow works without paid credentials.

Scope boundaries
- Out of scope for v1: feature-for-feature parity; broad integrations; unverified enterprise or scale claims. Do not promise feature parity, proprietary data, or enterprise reliability.

Include a README with setup, environment variables, data model, implementation decisions, privacy behavior, testing instructions, and important limitations.