See the coming week across every listing on one page: what goes out each day, which open houses, and what still needs approval #94

/week now shows the next seven days across every listing the viewer may list, /week.ics gives the same days as one calendar file, and the home list links to it as "This week". The new src/week.test.ts and the schedule, speed, a11y, hostile, openapi, contract, design and deps tests all pass. bun run lint:design printed nothing. The type check could not run, because the repo has no tsconfig.json and bun x tsc printed only its usage text. I did not run scripts/gate.ts or scripts/fast.ts; they aren't in the clone.

What changed

• src/clock.ts (new): the single clock for "today", with now() and setNow() so tests can pin the date. /week and /week.ics read it.
• src/schedule.ts: added weekDays (seven days with empty ones kept, each row carrying its listing), awaitingApproval (on-market listings with unapproved assets and "N of M approved") and weekIcs. I split scheduleIcs into shared event and calendar builders, so the per-listing file is byte-for-byte the same.
• src/pages/week.ts (new): the page, in the order the issue asks for.

- The "Still needs approval" section comes first. - Each day follows, using the same day names and row styling as /listings/:id/schedule. - An empty day says "Nothing scheduled."

• src/routes.ts: GET /week and GET /week.ics.

- Listing access goes through listListings and getListing, which ask permit. - contract.json is unchanged.

• Tests and docs: /week and /week.ics are added to speed.test.ts, /week to a11y.test.ts and hostile.test.ts. week.test.ts pins the clock and checks the window, an open house's day and times, Draft rows, the approval count and the ICS output. The README's agent section describes the page and how to add it to a calendar.

Not done

• /week.ics is not in the OpenAPI listing. /listings/:id/schedule.ics is, but the issue didn't ask for it here.
• Listings that are sold, withdrawn or expired contribute no rows and are left out of the approval section, because scheduleRows returns nothing for them.

To try it Open /, click "This week", then "Add to calendar".

🤖 Generated with Claude Code

Closes #92

/week now shows the next seven days across every listing the viewer may list, /week.ics gives the same days as one calendar file, and the home list links to it as "This week". The new src/week.test.ts and the schedule, speed, a11y, hostile, openapi, contract, design and deps tests all pass. bun run lint:design printed nothing. The type check could not run, because the repo has no tsconfig.json and bun x tsc printed only its usage text. I did not run scripts/gate.ts or scripts/fast.ts; they aren't in the clone.

What changed

• src/clock.ts (new): the single clock for "today", with now() and setNow() so tests can pin the date. /week and /week.ics read it.
• src/schedule.ts: added weekDays (seven days with empty ones kept, each row carrying its listing), awaitingApproval (on-market listings with unapproved assets and "N of M approved") and weekIcs. I split scheduleIcs into shared event and calendar builders, so the per-listing file is byte-for-byte the same.
• src/pages/week.ts (new): the page, in the order the issue asks for.

- The "Still needs approval" section comes first. - Each day follows, using the same day names and row styling as /listings/:id/schedule. - An empty day says "Nothing scheduled."

• src/routes.ts: GET /week and GET /week.ics.

- Listing access goes through listListings and getListing, which ask permit. - contract.json is unchanged.

• Tests and docs: /week and /week.ics are added to speed.test.ts, /week to a11y.test.ts and hostile.test.ts. week.test.ts pins the clock and checks the window, an open house's day and times, Draft rows, the approval count and the ICS output. The README's agent section describes the page and how to add it to a calendar.

Not done

• /week.ics is not in the OpenAPI listing. /listings/:id/schedule.ics is, but the issue didn't ask for it here.
• Listings that are sold, withdrawn or expired contribute no rows and are left out of the approval section, because scheduleRows returns nothing for them.

To try it Open /, click "This week", then "Add to calendar".

🤖 Generated with Claude Code

The week across every listing now has a terminal view, and it's pushed to the same branch. I ran the tty, week, schedule, speed, a11y, hostile, openapi, contract, design and deps tests; they pass. The type check still can't run because the repo has no tsconfig.json.

Terminal view

• Press w on the terminal's listings view to see the week; esc goes back. The help line now says "w this week".
• weekText in src/schedule.ts sits beside scheduleText and is built from weekDays and awaitingApproval. It lists the listings still needing approval first, then the seven days, with a Draft row never shown as going out.
• The listing gathering moved out of routes.ts into listWeek in src/actions.ts, so the page, /week.ics and the terminal all use it. It asks permit per listing through listListings and getListing, so a guest sees only what a guest may list.
• Both the page and the terminal read today from src/clock.ts.
• The README's agent section now says how to reach it from the terminal.

Tests

• src/tty.test.ts has two new tests. One covers w, the Draft mark, the help line and esc. The other covers a guest, who sees only the samples.
• src/week.test.ts now pins the clock with setNow and derives today from that same value, so it can't flake across midnight UTC.

Disagreement: none. I did not add a terminal view of /week.ics, since the calendar file is a web download.

🤖 Generated with Claude Code