What happened today
Sunday was the busiest day of the week: 54 commits across 19 repos.
- Play pipeline: most of the work went into the reusable app-publishing pipeline.
- Control panel: folding sections and setting groups.
- Admin app: a new Play tab grading each store listing before and after its rewrite.
- Widgets: a calorie widget that no longer shows yesterday at breakfast, and a new workout widget with a streak.
- Checkouts: terms clickwraps on two paid products.
From the waking world
A new global freshwater threat map brushes against our farm-water bloom checks, but that's context, not a build. The real signal came from the trend feed: AI coding tools' “don't ask again” approvals have put passwords into more than a thousand public GitHub files. That one points straight at us.
Dream connections
Approved commands are a secret store
Every command you tell your AI tool to stop asking about is saved verbatim in a project config file. If one included a password, the password is now on disk in plain text. A nightly job that pushes dozens of repos to GitHub can carry it off without anyone noticing.
The midnight bug is a family
Android's Doze mode lets home-screen widgets sleep through midnight and show yesterday's numbers at 7 AM. One app just fixed it with an alarm at 00:01. The new workout widget has the same problem, and so do two others. The fix is about 30 lines, already written once.
Clickwraps should meet the payment feed
Two checkouts now log which terms version each buyer accepted, and the sale watcher already sees every payment within two minutes. Matching the two turns “every buyer agreed” from a hope into a checked fact.
The receipts know the real fuel burn
The trip cost calculator assumes a fuel rate. The expense app holds a dozen real trips of gas receipts, and the field logger holds the real kilometres. Joining them gives a measured rate instead of a guessed one.
No password ever reaches GitHub through AI approval memory.
What already exists:
- A nightly backup that pushes about 53 repos to GitHub.
- A secret gate that checks for known password literals.
- A long habit of approving one-liners with credentials inline.
The missing piece: nobody has checked whether any .claude/ settings file was ever committed, including in history.
Smallest step:
- Loop every backed-up repo and run
git log --all -- '*.claude/*'. - Grep the hits against the known literals.
- Add the settings file to the default
.gitignore. - Rotate anything found.
It takes twenty minutes and either proves a clean bill or catches a real leak.
Reopen the paused checkouts, with receipts
The higher-risk products are paused until liability insurance is in place. The evidence an insurer wants is already scattered around:
- clickwrap logs by terms version;
- a sale watcher that confirms every buyer;
- stated refund windows;
- a public self-audit.
Stitch them into one record per purchase: what was bought, which terms were accepted and when, the confirmation sent, and the refund window. Then the broker conversation starts with a file instead of a promise, and the quote becomes the only thing standing between pause and open.
Tomorrow's suggestion
First, run the approval-file sweep: it's cheap, it's security, and a public repo makes it urgent. Then port the midnight widget alarm into the workout app before its next store upload, so the streak is right the first morning anyone installs it.