Background jobs learned to tell me when they had finishedBackground jobs learned to tell me when they had finished

July 30, 2026 · Less building than bookkeeping: the paper trail was made to match reality, the repo went to GitHub, and background jobs learned to push a notification.Mostly tidying up: making the notes match what was actually built, putting the code online, and getting a message when a background job finishes.
last updated

Auditing PLAN.md against reality

Today was less about new features and more about making the project's paper trail match reality. PLAN.md had drifted from the live system. Several Phase 0 and Phase 1 items (Xcode Command Line Tools, ask-cli, Docker, Tailscale, Cloudflare's nameserver validation) were all actually done but still sitting there unchecked. Rather than trust old checkbox marks, the whole plan got re-audited against the running system itself: launchctl, docker ps, tailscale status, ask smapi, npm test, and live curls against every hostname. The one item that couldn't be fully confirmed either way was the Alexa simulator's original "unable to reach the skill" blocker. The skill is registered and built successfully now, and a voice test from a real device is noted as having worked on 2026-07-29, but the access log had rotated when skill-backend became a LaunchDaemon, so there's no fresh log evidence backing it up. Flagged for a live retest rather than assumed fixed.

Going from local-only to GitHub

The repo also went from local-only to a private GitHub repo (gkbii/BigBrain), pushed with gh now that Homebrew is actually installed on the Mac mini. Before pushing, the real secrets in skill-backend/.env and infra/cloudflared/.env were double-checked to make sure they'd stayed gitignored the whole time, and four stale worktrees left over from the original async multi-agent build got pruned so they wouldn't tag along as nested git-links.

Push notifications for background jobs

The one genuinely new piece of work: task-runner's freeform jobs (the ones that spawn a real backgrounded claude -p session off a voice command) now push a notification through ntfy when they finish, fail, or time out. It's a plain fetch() POST to ntfy.sh, no new dependency and no paid account, matching the project's habit of avoiding anything that needs a compiler toolchain the Mac mini doesn't have. It's a no-op unless NTFY_TOPIC is set, the real topic only lives in the gitignored task-runner/.env, and the test suite force-clears that variable so npm test can never accidentally fire a real push.

Today was mostly bookkeeping rather than new features. The project's running notes had drifted out of sync with reality. Several finished tasks were still marked as not done. Rather than trust the old notes, everything got re-checked against what was actually running on the computer, one item at a time. The only thing that couldn't be fully confirmed either way was whether Alexa's testing tool could reach the skill. Real voice tests from an actual device had worked a day earlier, but the evidence for that had since rotated out of the logs, so it got flagged for a fresh check rather than assumed fine.

The project also moved from living only on this one computer to having a real backup on GitHub, a private online code-storage service. Before pushing it up, the real passwords and secret keys were double-checked to make sure they'd never actually be included, and some leftover experimental copies of the project got cleaned up first.

The one genuinely new feature: background coding jobs triggered by voice now send a phone notification when they finish, fail, or take too long, so there's no need to keep checking back manually. It uses a free, no-signup notification service, and it stays silent unless it's specifically turned on.