Repository navigation
Dashboard pages see every week of a series: agents, command center, conflicts, memories, moments, outcomes, planning, profile - #928
Closed
NewWorldVenture wants to merge 5 commits into
Conversation
…onflicts, memories, moments, outcomes, planning, profile Eight server pages read `calendar_events` by `starts_at` — a series' FIRST start — over their window: the agents' week, the command center's week and its "events remaining today", the conflicts resolver's fortnight, the memories page's next three things, the moments page's next holiday, the outcomes page's count of today, the planning hub's next four and their count, and the profile's "events this week". A weekly lesson created in August was on none of them from September — including the page whose whole job is finding the clash booked over it. All eight read through `readCalendarOccurrences` now: - agents, command center, conflicts, moments (holiday via `refine`), profile (this member via `assigneeId`): the same instant windows in the family's zone, series included. - outcomes: today on the family's wall (`briefingCalendarBounds`); `count` is every occurrence, as the head count was every row. - memories and planning read ahead with no end: one-offs stay open-ended (`calendarOpenWindowFilter`), a series is expanded over the year ahead, and the planning hub's count is the occurrences in that year rather than the rows for ever — a weekly lesson counts once a week, not once. Tests: tests/dashboard-pages-see-every-week-of-a-series.test.ts (12): the conflicts resolver shows the photo booked over this week's lesson four weeks into the series (control: nothing to resolve without it), the command center counts the lesson among today's remaining events, the profile counts it in the week, and the eight pages are pinned to the shared read. The pages' existing seventeen suites are source-level and pass unchanged. Controls (mutate, run the new test, restore; md5 verified): A the calendar read drops every series → 3 fail; B the conflicts page reads by first start → 2 fail; C the command center reads by first start → 2 fail; D the profile reads by first start → 2 fail. tsc clean; eslint clean on the changed files; the pages' 17 suites (84 tests) green. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KP9rt5rVQ9jDMpZp2xBy3K
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
This was referenced Oct 3, 2026
…claude/dashboard-pages-see-series-20261003
…claude/dashboard-pages-see-series-20261003 Carries main (933236e, #922 squashed) down the series stack. No conflicts. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KP9rt5rVQ9jDMpZp2xBy3K
…dashboard-pages-see-series-20261003 Carries the refreshed parent (main merged) down the series stack. Two pages took both sides: memories and planning keep the family-zone formatters the parent gained and the year-ahead bounds this branch added. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KP9rt5rVQ9jDMpZp2xBy3K
The merge that carried the family-zone formatters down this stack left the page with two `tz` declarations: the one #942 added on main and the one this branch added for the series bounds. One is enough. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KP9rt5rVQ9jDMpZp2xBy3K
NewWorldVenture
marked this pull request as ready for review
October 4, 2026 14:59
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #926 → #924 → #923 → #922 → #921 → main. Sixth unit of the "a series is on the calendar every week" class: the dashboard pages. No migration.
Summary
Eight server pages read
calendar_eventsbystarts_at, a series' first start, over their window: the agents' week, the command center's week and its "events remaining today", the conflicts resolver's fortnight, the memories page's next three things, the moments page's next holiday, the outcomes page's count of today, the planning hub's next four and their count, and the profile's "events this week". A weekly lesson created in August was on none of them from September, including the page whose whole job is finding the clash booked over it.All eight read through
readCalendarOccurrencesnow.Changes
refine), profile (this member viaassigneeId) — the same instant windows in the family's zone, series included.briefingCalendarBounds);countis every occurrence, as the head count was every row.calendarOpenWindowFilter), a series is expanded over the year ahead. The planning hub's count is the occurrences in that year rather than the rows for ever, so a weekly lesson counts once a week, not once.Tests
tests/dashboard-pages-see-every-week-of-a-series.test.ts(12), rendering three pages over the in-memory Supabase and reading the props they hand their client components: the conflicts resolver shows the photo booked over this week's lesson four weeks into the series (control: nothing to resolve without it); the command center counts the lesson among today's remaining events; the profile counts it in the week; all eight pages are pinned to the shared read.Controls (mutate, run the new test, restore; md5 verified): A the calendar read drops every series → 3 fail; B the conflicts page reads by first start → 2 fail; C the command center reads by first start → 2 fail; D the profile reads by first start → 2 fail.
tsc clean; eslint clean on the changed files; the pages' 17 suites (84 tests) plus the new one green locally.
🤖 Generated with Claude Code
https://claude.ai/code/session_01KP9rt5rVQ9jDMpZp2xBy3K
Generated by Claude Code