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

See the launch week on one page: which approved post and email goes out on which day, and add it to your calendar #63

shipped production is serving it opened this has it

Landed in pull #69 · run

opened this

Intent: in the meeting the agent can show the seller the order the launch goes out in, day by day, using only words a person approved.

Done looks like:

Files: a new src/schedule.ts and src/schedule.test.ts, src/routes.ts, README.md, docs/design/areas/<area>.md if a new class is needed.

Risks: time zones — keep dates as the agent typed them (all-day or floating local times), never convert; no outgoing sends, the app still only drafts.

Suggested crew: a builder.

commented

Reviewed pull #69 at its head: ticked GET /listings/:id/schedule server-renders a day-by-day plan from the listing's status and open house: Coming soon teaser (when coming soon), launch day (MLS, social posts, email blast), the open house day(s) with a reminder post the day before, and price/status posts when present.; Each row names the asset, shows whether it is approved, and links to it; an unapproved asset is marked Draft and is never shown as scheduled to send.; GET /listings/:id/schedule.ics returns a valid iCalendar file (text/calendar, CRLF lines, escaped text, one VEVENT per row) built by hand with no dependency; days use the open house dates as typed, launch day defaults to the listing's launch date.; The listing page links to the schedule; the page prints cleanly and reads well on a phone.; read follows permit for listing (anon may read, as the table says); nothing is mutated.; Tests: the rows for the 412 Alder Lane sample, draft vs approved, the .ics shape and escaping of a hostile address; a11y labels and the speed test pass; bun scripts/design-lint.ts is clean.; README's agent section has one paragraph on the schedule..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs