Skip to content

feat(evidence): publish multi-spec PR tapes - #3546

Open
benjaminshafii wants to merge 1 commit into
devfrom
feat/evidence-multi-tape
Open

feat(evidence): publish multi-spec PR tapes#3546
benjaminshafii wants to merge 1 commit into
devfrom
feat/evidence-multi-tape

Conversation

@benjaminshafii

Copy link
Copy Markdown
Member

What

  • Merge evidence into one sticky PR comment using deterministic per-spec sections.
  • Replace only a republished spec while retaining every other tape and a summary of all verdicts.
  • Add --all to publish every valid roll matching the PR head in chronological order, skipping malformed, unreadable, missing-SHA, and stale rolls with clear messages.

Why

A five-spec PR had its five tapes published sequentially, but the single sticky comment was replaced each time. Four tapes were silently overwritten, leaving only the last tape and making multi-spec human verification unreliable.

Tests

  • pnpm --dir evals test — PASS (151 passed, 0 failed).
  • pnpm exec tsc --noEmit --strict --module nodenext --moduleResolution nodenext --target es2023 --lib es2023,esnext.disposable --allowImportingTsExtensions --erasableSyntaxOnly --verbatimModuleSyntax --skipLibCheck --types node evals/packages/evidence/src/*.ts evals/packages/evidence/test/*.ts — PASS.
  • pnpm --dir evals typecheck — unavailable because the isolated evals workspace does not install tsc; root pnpm exec tsc -p evals reaches an unrelated pre-existing error in evals/specs/connectors-quick-add.slow.test.ts:253.

Evidence

This changes tooling for the evidence layer itself. The network-free comment composition is covered by pure unit tests, including merge, same-slug replacement, marker preservation, summary rendering, and stable ordering. No real PR was published during implementation; the orchestrator will exercise the publisher live.

@vercel

vercel Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
openwork-app Ready Ready Preview Aug 5, 2026 6:42am
openwork-den Ready Ready Preview Aug 5, 2026 6:42am
openwork-den-worker-proxy Ready Ready Preview Aug 5, 2026 6:42am
openwork-diagnostics Ready Ready Preview Aug 5, 2026 6:42am
openwork-landing Ready Ready Preview, v0 Aug 5, 2026 6:42am

@diff-warden diff-warden Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Warden security clearance: clear. No new security issues found in this diff (e24ac3d76ceab8bb1a0f3888ba1596a93855982d). Automated clearance satisfies the required-review gate only — a human still reviews and merges. Analysis run


function parseSections(body: string): PrEvidenceSection[] {
const sections: PrEvidenceSection[] = [];
for (const match of body.matchAll(SECTION_PATTERN)) {
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants