Joshua King 540f59a353 PresenceEngine with is_present and the always-present default (Feature 05, task 3)
PresenceEngine is an immutable, database-free snapshot of the
children's schedules answering is_present(child_id, date): a child
with NO schedule entry is present every day (the household's
always-present sibling); a scheduled child is present exactly when
the date's weekday is in the pattern for that date's cycle week
(anchor-date arithmetic via cycle_week_index — never ISO parity).
Construction validates the snapshot shape (dict keyed by the
schedule's own child_id, values are PresenceSchedules) and exposes it
read-only (MappingProxyType + __setattr__ refusal). is_present
rejects non-int child ids and non-plain dates.

Tests: the three-child fixture (two complementary rotation children,
one schedule-free) asserted for every day of a four-week span plus
spot-checked swap days; weekend/weekday-set behaviour across weeks;
construction/input rejection matrix; engine immutability. Suite:
985 passed.
2026-09-15 17:57:02 -04:00
2026-09-14 21:31:55 -04:00

NestQuest - House Chaos Coordination

Home Assistant custom integration for managing chores, custody schedules, and house coordination.

Overview

NestQuest helps households coordinate daily life, chore tracking, custody schedules, and shared tasks directly within Home Assistant. Version 0.2.0 ships the integration foundation (a configuration scaffold providing the package and manifest, shared constants, a single-instance config flow, setup/unload lifecycle handling with an options-reload listener, an options flow for horizon days / day rollover time / panel idle timeout, and HACS metadata) plus its persistence layer: an integration-owned SQLite database (nestquest.db) with WAL mode and foreign keys, a versioned migration runner stamping schema version 1 across eight tables (children, admin_users, schedule_rules, task_definitions, presence_schedules, presence_overrides, task_instances, completion_events), typed DAO layers so no other feature writes raw SQL, an append-only completion-event log, and startup handling that creates a missing database, opens a valid one, and refuses — without touching a single byte — to start on a corrupt one. Sensors, calendar events, and service calls are forthcoming in later releases and are not yet part of the integration.

Installation

  1. Ensure HACS (Home Assistant Community Store) is installed.
  2. In Home Assistant, open HACS > Integrations.
  3. Select the three-dots menu in the top right and click Custom repositories.
  4. Enter the repository URL: https://github.com/talon2king/NestQuest
  5. Select category Integration and click Add.
  6. Search for NestQuest and click Download.
  7. Restart Home Assistant.

Note: Development happens in the private Gitea repository (https://code.cubecraftlabs.com/Maniacs_Mansion/NestQuest). The GitHub repository is a public mirror maintained for HACS distribution.

Manual Installation

  1. Download the latest release from the repository.
  2. Copy the custom_components/nestquest directory into your Home Assistant installation's config/custom_components/ folder:
    cp -R custom_components/nestquest <config_dir>/custom_components/
    
  3. Restart Home Assistant.

Configuration

After installation and restart:

  1. Navigate to Settings > Devices & Services in Home Assistant.
  2. Click Add Integration and search for NestQuest.
  3. Follow the on-screen configuration flow.

Developer Setup and Testing

This project uses uv for fast Python package and dependency management.

Prerequisites

  • Python 3.11 or newer
  • uv installed on your machine

Setup Environment

To set up the development environment and install dependencies:

uv sync

Running Tests

Run the test suite with pytest:

uv run pytest

License

This project is licensed under the MIT License - see the LICENSE file for details.

S
Description
No description provided
Readme MIT
6.7 MiB
Languages
TypeScript 41.2%
Python 39.7%
JavaScript 17.9%
CSS 1.1%