Public: anyone can read this; the crew can change it.

Thirty days after a deal closes, the agent gets a drafted "How is the new home?" check-in to their clients, approved like any reminder, so past clients turn into referrals #156

Merged opened this

Check · Review · Land · Live done — Landed and live in production.

Merged

Thirty days after a deal's closing is marked done, each past client now gets a drafted "How is the new home?" check-in, approved like any reminder. The full bun test suite passes and scripts/lint-design.ts is clean. bun x tsc --noEmit didn't run, because the clone has no tsconfig.json.

Notes

shipped production is serving it deploy d2eada7

opened this

Thirty days after a deal's closing is marked done, each past client now gets a drafted "How is the new home?" check-in, approved like any reminder. The full bun test suite passes and scripts/lint-design.ts is clean. bun x tsc --noEmit didn't run, because the clone has no tsconfig.json. scripts/gate.ts and scripts/fast.ts don't exist here either. I didn't boot the app or try the new screens in a browser.

What changed

  • Who and when: the check-in goes to the buyers on a buyer-side deal, the sellers on a listing, and both on a both-sides deal, for parties with a contact. It is due the morning 30 days after the day the closing was marked done. It is one draft per client, so a both-sides deal gives two.
  • Words: they are in their own function in the new src/checkin.ts, so #135's sign-off edit in src/reminders.ts should rebase cleanly. The draft names the address, asks how the move went, offers help, and asks for a referral with "No pressure". It ends with the usual sign-off and never quotes the price.
  • Moment: this is a new moment, checkin, on the closing's deadline, with the done-day as its due. drafts() returns check-ins for a closed deal, so the review page, the header's waiting count and /tick pick them up without other changes.
  • Doors: send, hold, decline, release and undo go through the same doors as other reminders. The sent record keeps the approved words on the deal's Messages record. A reopened or fell-through deal gets none. A deal reopened and closed again is a new check-in.
  • Migration: CHECK constraints on the reminder tables needed it. It is appended as the last migration, with the pin updated. It rebuilds reminder, reminder_declined and reminder_hold with checkin allowed.
  • Closed deals: they stay off the clock lanes, This week and People. A closed deal's page gets a "Check-in" card. The clock's "Reminders for today" lists the check-in as a row that links to that card, so its count matches the header.
  • API and docs: the OpenAPI moment enums and descriptions, the /tick summary and the MCP tool descriptions mention checkin, and contract/openapi.json is regenerated. The README gets its one sentence and docs/TECHNICAL.md a short paragraph.
  • Tests: src/checkin.test.ts covers the day-30 and day-29 split, the side picking recipients, the wording, no check-in for reopened or fell-through deals, send recording the words, decline stopping it, and hold moving it to tomorrow.

What I chose

  • Stays until acted on: an unsent check-in stays on the review list on later days until it is sent or declined, rather than disappearing after its morning. Other reminders drop off once their date passes. Say if you want a cutoff.
  • Contacts: a party without a contact gets no check-in, as with the status update.

The permission table is untouched.

🤖 Generated with Claude Code

Closes #139

1 earlier comment · 2 events
commented

Thirty days after a deal's closing is marked done, each past client now gets a drafted "How is the new home?" check-in, approved like any reminder. The full bun test suite passes and scripts/lint-design.ts is clean. bun x tsc --noEmit didn't run, because the clone has no tsconfig.json. scripts/gate.ts and scripts/fast.ts don't exist here either. I didn't boot the app or try the new screens in a browser.

What changed

  • Who and when: the check-in goes to the buyers on a buyer-side deal, the sellers on a listing, and both on a both-sides deal, for parties with a contact. It is due the morning 30 days after the day the closing was marked done. It is one draft per client, so a both-sides deal gives two.
  • Words: they are in their own function in the new src/checkin.ts, so #135's sign-off edit in src/reminders.ts should rebase cleanly. The draft names the address, asks how the move went, offers help, and asks for a referral with "No pressure". It ends with the usual sign-off and never quotes the price.
  • Moment: this is a new moment, checkin, on the closing's deadline, with the done-day as its due. drafts() returns check-ins for a closed deal, so the review page, the header's waiting count and /tick pick them up without other changes.
  • Doors: send, hold, decline, release and undo go through the same doors as other reminders. The sent record keeps the approved words on the deal's Messages record. A reopened or fell-through deal gets none. A deal reopened and closed again is a new check-in.
  • Migration: CHECK constraints on the reminder tables needed it. It is appended as the last migration, with the pin updated. It rebuilds reminder, reminder_declined and reminder_hold with checkin allowed.
  • Closed deals: they stay off the clock lanes, This week and People. A closed deal's page gets a "Check-in" card. The clock's "Reminders for today" lists the check-in as a row that links to that card, so its count matches the header.
  • API and docs: the OpenAPI moment enums and descriptions, the /tick summary and the MCP tool descriptions mention checkin, and contract/openapi.json is regenerated. The README gets its one sentence and docs/TECHNICAL.md a short paragraph.
  • Tests: src/checkin.test.ts covers the day-30 and day-29 split, the side picking recipients, the wording, no check-in for reopened or fell-through deals, send recording the words, decline stopping it, and hold moving it to tomorrow.

What I chose

  • Stays until acted on: an unsent check-in stays on the review list on later days until it is sent or declined, rather than disappearing after its morning. Other reminders drop off once their date passes. Say if you want a cutoff.
  • Contacts: a party without a contact gets no check-in, as with the status update.

The permission table is untouched.

🤖 Generated with Claude Code

the crew's run was interrupted: restart, resumes on the next pass — cancelled
Changes requested — before the latest push

Mostly sound: the moment is wired through send/hold/decline/release/undo, the migration is appended and pinned, no contract cell is loosened, the preview answers 200, and the tests are real. One thing to fix: the check-in is offered before its day.

checkinCard on the deal page (src/pages/deal.ts) renders checkinDrafts(...) unconditionally. The moment a closing is marked done, the deal page therefore shows a "Check-in" card with Send, Edit and Decline controls, 30 days early. Box 3 says the draft appears that morning, and the card's own copy says "A month after closing". Fix: show the card only for drafts that are due (d.on <= on) or that have a sent, declined or held record. Add a test that dealPage at 2026-10-30 does not contain "Check-in" and at 2026-10-31 does. The current test only checks the day-31 page.

Smaller, no change needed: an unsent check-in stays on the list indefinitely, because pending includes checkin regardless of due. That is a defensible choice and the builder flagged it.

commented

The check-in card on the deal page now shows only once its day has come, or once the check-in has a record (sent, declined or held). That fixes the card appearing 30 days early. src/checkin.test.ts passes (6 tests). I did not run the rest of the suite, since the forge runs it on push.

  • The fix: in src/pages/deal.ts, checkinCard filters checkinDrafts to drafts where d.on <= on or sent_at, declined or held is set. If none remain, no card renders, so there are no Send, Edit or Decline controls before the day.
  • The test: a new test in src/checkin.test.ts checks that dealPage at 2026-10-30 does not contain "Check-in" and at 2026-10-31 does.
  • Left alone, as you said: an unsent check-in stays on the list indefinitely.
  • Not run: this clone has no tsconfig.json and no scripts/gate.ts. bun x tsc --noEmit only printed tsc's help text, so the type check and the gate did not run.

🤖 Generated with Claude Code

Approved

Earlier ask (check-in card showing 30 days early) is met: checkinCard now shows only on/after the day or once a record exists, and a test covers day 29 vs 30. No new findings: no contract cell loosened, writes go through the existing reminder doors, migration is appended with pin updated, openapi/MCP/README updated. Non-blocking: an unsent check-in lingers on the review list indefinitely; consider a cutoff later.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs