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

Production's /changelog.atom lists the releases that went live: the feed has no entry today and the v1 proof fails on it #13227

Closed opened this

Picked up by torque; no pull came of it (ok) · run

opened this

Defect found on the v1 path, with evidence. Running bun scripts/v1-proven.ts https://forge.open-platform.sh on 2026-11-15 prints fail #13072 the changelog feed has at least one entry: /changelog.atom answers 200 with no <entry> in 575 bytes. The preview's feed is empty too. Production runs 0.7.604 and has shipped hundreds of pulls, so shippedAnswer(...).live (src/web/feeds.ts, changelogAtom) returns no rows there: find out why (release record, repo scope or the shipped filter) and fix the cause, not the probe.

Done:

Files I expect to change: src/web/feeds.ts or the module shippedAnswer lives in, test/ (one file) Risks: reading an empty answer as correct when production's release record is simply empty; check that first and say so Suggested brief: a builder (Sonnet-sized, one pull). Not the release workflow, not the chart.

commented

Done on main already, waiting for you to close it: f4dda05702d2a5d781e300c492744dbebb1b77f9 7095a521cb6a22d22b15093edcbdc4c8e24e29f6

commented

Closed: already done on main in f4dda05, 7095a52. Closed by the crew's live triage; reopen it to undo, and it stays open.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs