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 #200
The README's "What is real, and what is not yet" section now names each feature a realtor would ask about, and a new test keeps its links true. I ran bun test src/readme.test.ts (both tests pass). I did not run the full suite, and bun x tsc --noEmit printed only its usage text, so I can't call the type check clean.
stopped parked by the crew deploy 81f61da
3 earlier comments
The README's "What is real, and what is not yet" section now names each feature a realtor would ask about, and a new test keeps its links true. I ran bun test src/readme.test.ts (both tests pass). I did not run the full suite, and bun x tsc --noEmit printed only its usage text, so I can't call the type check clean. There is no scripts/gate.ts or scripts/fast.ts in this clone, and I did not run the design lint because src/web/ is untouched.
What changed
- New Real bullets: download and bring back your deals, times and places on inspections, walkthroughs and closings, two closings too close together being flagged, home-anniversary notes drafted for approval, the Activity record and its spreadsheet, and commission with your year. Each links to the README section that shows how.
- Activity section: it never mentioned the spreadsheet, so I added a sentence about it.
/activity.csvand the "Download spreadsheet" button on that page exist insrc/routes.tsandsrc/pages/activity.ts. - Test:
src/readme.test.tschecks that every](#anchor)link inREADME.mdmatches a heading in it. It also checks that the section still says "no email or text message leaves the app" and still names each feature.
What I left alone
- The Simulated and phase-two bullets are unchanged. They already say no email or text leaves the app, and that matches the code.
- I did not check each claim against
src/routes.tsline by line. I wrote them from the README's own existing sections. I did confirm the Activity spreadsheet route. - "Bring deals back" is a bold paragraph under "Make it yours", not a heading, so its link points to that section.
No running-app code changed and no permission cell was loosened.
I found no fault in this pull, so I fixed nothing. I pushed an empty commit (478b1ba) to trigger a fresh preview deploy. I haven't seen the result.
- What this pull changes: only
README.mdandsrc/readme.test.ts, so the app's code andforge.jsonare as they were onmain. - Fresh boot is healthy: I started the app on an empty
FORGE_APP_DATAand/healthzanswered 200. - Production is down too: it answers 502 from outside, and the preview of this pull gave me a 502 as well. That points to the host or to existing data, not to a README edit.
- The log doesn't name the cause: the excerpt stops mid-test-run. A 503 from
/healthzalso names the failed check, and the excerpt doesn't show which one. I can't see the preview's data or logs from the sandbox.
If the redeploy fails the same way, send me the full log, and the failed check named in the 503 body if you have it. A person will need to look at the preview's data directory, because a schema left behind by an older build could produce this.
I did not run the full suite or bun x tsc --noEmit this round, since nothing in the code changed.
This fixes the failing preview deploy: the clock page's "This week" card now shows an inspection or walkthrough's time and place, the same as the printed /week sheet. Tests pass except the suites that need unix sockets, which this sandbox skips. bun scripts/gate.ts doesn't exist in this clone, and tsc has no tsconfig.json here, so neither ran.
The cause. The test week.page.test.ts › lists overdue and coming dates… compares the rows on /week with the rows on the clock card. #193 added the time and place to /week rows only. #194's sample deals have those times, so the two pages started to differ. The sample dates sit relative to today, which is why this surfaced on a README-only pull.
The fix.
src/week.tshas a newrowNote(deal, d). It gives a closing's time and place, or an appointment's, or an empty string.src/pages/clock.tsandsrc/pages/week.tsboth use it, so the two pages can't drift apart again.
What I left alone. No test changed, because the existing one was right. I ran the week, clock and appointment suites, and in a full bun test run that one test was the only failure.
To try it. Open / and look at the "This week" card. A row like "Inspection period ends · 10:30 am · 77 Harbor View Dr, Unit 4B" matches the same row on /week.
Parked by the crew: the check stayed red through 2 automatic tries
The README's "What is real, and what is not yet" section now names each feature a realtor would ask about, and a new test keeps its links true. I ran
bun test src/readme.test.ts(both tests pass). I did not run the full suite, andbun x tsc --noEmitprinted only its usage text, so I can't call the type check clean. There is noscripts/gate.tsorscripts/fast.tsin this clone, and I did not run the design lint becausesrc/web/is untouched.What changed
/activity.csvand the "Download spreadsheet" button on that page exist insrc/routes.tsandsrc/pages/activity.ts.src/readme.test.tschecks that every](#anchor)link inREADME.mdmatches a heading in it. It also checks that the section still says "no email or text message leaves the app" and still names each feature.What I left alone
src/routes.tsline by line. I wrote them from the README's own existing sections. I did confirm the Activity spreadsheet route.No running-app code changed and no permission cell was loosened.
Closes #191