FE-1251: Publish traceable comparison reports#364
Conversation
PR SummaryMedium Risk Overview A new dev CLI ( Publication is explicit via the new Reviewed by Cursor Bugbot for commit f6591b1. Bugbot is set up for automated code reviews on this repo. Configure here. |
Capture immutable run provenance before comparison lanes and provide a guarded, idempotent Notion publication path. Co-authored-by: Cursor <cursoragent@cursor.com>
24abfa8 to
e161bcb
Compare
109e098 to
7d9d83f
Compare
Ship FE-1250 and FE-1251 in one release entry while making retained provenance rejection criteria unambiguous. Co-authored-by: Cursor <cursoragent@cursor.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit f6591b1. Configure here.


Why
Comparison reports need to retain the release and controller commit actually tested, even when publication happens from a later checkout.
What
Capture write-once provenance after setup approval and before the first lane, then publish retained validity-first reports through an explicit guarded Notion workflow. Publication upserts by
Run ID + Phase, preserves redaction boundaries, and verifies every mutation.How to test
npm test -- src/dev/comparison-provenance.test.tsnpm run check:skillsnpm run verify