Public: anyone can read this; the crew can change it.
The README's "What is real, and what is not yet" names what the app does today, so a realtor reading it before the meeting is not surprised #208
The README's "What is real, and what is not yet" now lists everything issue #191 asks for, and a test keeps its links true. The branch now holds only that change on top of current main. I ran src/readme.test.ts (it passes) and pushed.
stopped parked by the crew deploy a9cf290
3 earlier comments
The README's "What is real, and what is not yet" now lists everything issue #191 asks for, and a test keeps its links true. The branch now holds only that change on top of current main. I ran src/readme.test.ts (it passes) and pushed. I did not run the full suite. bun x tsc --noEmit printed its help text instead of type-checking, so I can't call the type check clean.
Why #200 stayed red. The earlier branch also carried a code change to the clock's "This week" card (src/pages/clock.ts, src/pages/week.ts, src/week.ts). That change overlapped what main later landed as #199 and conflicted with it, and it isn't part of #191. I dropped it and merged main in. main has since gained a README line on clash flagging, so the diff against main is now only the README edit and the new test file.
What changed
- README real/not-yet list: it has a plain-words bullet for each of these, linking to the README section that shows how:
- downloading your deals and bringing them back - times and places for closings, inspections and walkthroughs - same-day clash flagging - home-anniversary notes that wait for your approval - Activity and its spreadsheet - commission and your year
- Clash bullet: I rewrote it to match what the code now does. It covers two closings, or an inspection or walkthrough and another timed appointment, less than two hours apart on the same day. The old wording only covered closings.
- Simulated and phase-two bullets: unchanged. They still say no email or text message leaves the app.
src/readme.test.ts: a new test checks that every](#anchor)link in the README resolves to a heading in it. There are two tests and both pass.
Not done: I did not run the full bun test, bun scripts/gate.ts or bun scripts/fast.ts. The forge's check runs the full suite on this push. The change touches only the README and one test file.
Branch history: the push is a normal fast-forward on top of the old branch tip. A force push is refused here, so history on the branch is not rewritten.
🤖 Generated with Claude Code
I couldn't find a cause for the preview's 503, so I pushed an empty commit to redeploy it. Nothing in this branch's code explains it.
- This branch against
main: it ismainplus only the README edit andsrc/readme.test.ts. No code or schema is changed. - Fresh boot: the app answers
/healthzwith 200 on an empty data directory. - Tests:
src/week.appointment.test.ts(the file the deploy log stopped at) passes locally.src/upgrade.test.ts, the health tests andsrc/readme.test.tspass together, 65 tests in all. - Production and preview: from my sandbox, production and the #208 preview both answered 502. I can't reach the logs behind those 502s.
- Likely cause: the preview's own database may be at a schema the boot didn't repair, but I could not check that, so it is a guess.
If the redeployed preview still returns 503, the 503 body names the failed check and the deploy log for that run is the next thing to read. I can't read either from here.
I did not run the full suite or the gate script. Beyond what I ran, the forge's check on this push covers that.
I found no cause for the 503 and changed nothing, so nothing new is pushed. The pull is still main plus the README edit and src/readme.test.ts.
What I checked
- The branch:
git diff origin/main --statshows onlyREADME.mdandsrc/readme.test.ts. No code, schema or migration is touched. - Fresh boot: on an empty data directory the app answers
/healthzwith 200. - The log: it ends partway through the suite at
src/clash.test.ts, which uses its own temporary directory. Those tests don't touch the preview's data, and no test failed. The failure is the readiness probe seeing 503 for 30 seconds. - Other preview: pull #207's preview answers
/healthz200 right now, on currentmaincode. Production answered 502 from my sandbox.
My best guess
- Guess: the 503 comes from the preview's own database, not from this code.
/healthzreturns 503 when a column the first paint reads is missing. - Mechanism:
migrate()insrc/db.tsapplies migrations by position and records the version. A database that earlier ran a different set of migrations in those positions would skip a migration and stay broken. - Not checked: I can't read the preview's database or its logs, so I couldn't confirm any of this.
What to do next
- Read the 503 body: it names the failed check, such as
datesordeals, and the deploy log for that run has the rest. - Pull #207: it logs the failing check and the database's own error at boot. With it landed, the next failed preview names the missing column.
- Resetting the preview's data directory for #208 would confirm or rule out the guess. I can't do that from here.
I didn't add a repair-on-boot for missing columns. It is a new behaviour that issue #191 doesn't ask for, and I'd be guessing at the cause. I didn't push another empty redeploy either, since the last one failed the same way.
Parked by the crew: the check stayed red through 2 automatic tries
The README's "What is real, and what is not yet" now lists everything issue #191 asks for, and a test keeps its links true. The branch now holds only that change on top of current
main. I ransrc/readme.test.ts(it passes) and pushed. I did not run the full suite.bun x tsc --noEmitprinted its help text instead of type-checking, so I can't call the type check clean.Why #200 stayed red. The earlier branch also carried a code change to the clock's "This week" card (
src/pages/clock.ts,src/pages/week.ts,src/week.ts). That change overlapped whatmainlater landed as #199 and conflicted with it, and it isn't part of #191. I dropped it and mergedmainin.mainhas since gained a README line on clash flagging, so the diff againstmainis now only the README edit and the new test file.What changed
- downloading your deals and bringing them back - times and places for closings, inspections and walkthroughs - same-day clash flagging - home-anniversary notes that wait for your approval - Activity and its spreadsheet - commission and your year
src/readme.test.ts: a new test checks that every](#anchor)link in the README resolves to a heading in it. There are two tests and both pass.Not done: I did not run the full
bun test,bun scripts/gate.tsorbun scripts/fast.ts. The forge's check runs the full suite on this push. The change touches only the README and one test file.Branch history: the push is a normal fast-forward on top of the old branch tip. A force push is refused here, so history on the branch is not rewritten.
🤖 Generated with Claude Code
Closes #191