Add notes module

AGENTS.md

@@ -4,6 +4,8 @@ Self-hosted family coordination web app for Matt and his wife. Replaces a commer
 
 This file is the canonical brief. Read it at the start of every session before making changes. Sub-task briefs in [`docs/tasks/`](docs/tasks/) reference this file; do not duplicate its contents there.
 
+Codex and Claude Code both work on this project. Keep `AGENTS.md`, `CLAUDE.md`, `STATUS.md`, task briefs, and dev notes synchronized so either agent can pick up the next task without relying on agent-specific memory.
+
 ---
 
 ## Goals
@@ -67,7 +69,7 @@ src/
 - **Permissions.** Household-scoped by default. Share-tokens grant scoped read/write per entity.
 - **Feature flags.** Env/db-driven for staging experiments.
 
-**Rule for contributors (including future Sonnet sessions):** if a feature requires a change to `_core` to support a new entity type, that's a smell — extend the registry instead.
+**Rule for contributors (including future Codex and Claude Code sessions):** if a feature requires a change to `_core` to support a new entity type, that's a smell — extend the registry instead.
 
 ---
 
@@ -142,6 +144,7 @@ Tasks for each phase live in [`docs/tasks/`](docs/tasks/). Sub-sessions should p
 - **One module = one PR/commit boundary** when possible.
 - **Tests:** Vitest for units (where it pays off), Playwright for one happy-path E2E per module. Don't write tests for trivial CRUD.
 - **Secrets** via `.env` (gitignored) and `.env.example` (committed, no values).
+- **Teardown after validation.** After build/test/E2E validation, stop any dev servers or compose services started for the task unless the user explicitly asks to keep them running. This avoids stale instances and port conflicts in later sessions.
 
 ---