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

The signed-in home answers its first page inside a stated budget on a forge with 5,000 events, measured by query plan and Server-Timing #13581

shipped production is serving it opened this has it

Landed in pull #13595 · run

opened this

Done: a test seeds 5,000 feed events, requests the home as a signed-in person, asserts no SCAN or TEMP B-TREE on the feed reads (pattern: test/hot-reads-indexed.test.ts) and that the app phase of Server-Timing stays under 50 ms on a warm read; the budget is written in docs/FEED.md. Suggested: scout.

Risks: Clock-based flakiness: judge by plan and row count first; the clock only as a generous second check.

Read AGENTS.md and docs/PRINCIPLES.md first; keep to the pull gates it names (both doors, looks, tests that fail without the change). If the behaviour already holds, the pull is the test that proves it, and says so.

Files: src/feed/timeline.ts, test/home-feed-budget.test.ts, docs/FEED.md

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs