waldo.WTF

Deploy waldo.WTF to the Mac mini (waldomacmini1) native LaunchDaemon — no Docker. Runs tests + local-smoke, refreshes deps, restarts the launchd service, re-asserts Tailscale Serve, and smoke-checks HTTPS health + the MCP tool surface. Use whenever shipping code changes to the running Mac mini server, OR when running a data migration from docs/migrations/. Flags; `--migrate <name>` to run a registered migration, `--dry-run` to print the plan without executing.

Fast pre-deploy sanity check against a throwaway SQLite DB and a non-default port. Exercises the CLI (add/list/toggle/remove + validation errors) and boots the MCP HTTP server long enough to confirm it listens and `tools/list` returns the full tool surface. Use before `/deploy-local` to catch boot-time regressions that `npm test` doesn't. Never touches real lake data.

Update the /docs folder at the end of a coding task. Use immediately after a `/tdd-cycle` completes (or any meaningful workspace change) to refresh the changelog, setup, getting-started, or user guide as needed. Invoke proactively — documentation staleness is a bug.

Run the waldo.WTF TDD cycle for a coding task. Use at the start of ANY code change (feature, bug fix, refactor) to produce the RED test list, confirm failing tests, scaffold testable seams, implement to GREEN, refactor, and verify ≥90% coverage + requirement traceability. Invoke proactively — never write production code without running this first.

Scan the workspace for secrets, credentials, PII, and common security leaks. Runs as a mandatory step in every /tdd-cycle (after COVER, before UPDATE DOCS) and also on-demand when the user asks for a security check. Blocks the cycle if anything is found — never "note and continue".