feat: verified share card — attested card.svg/card.png artifact (#50) - #63
Merged
Conversation
Implementation of the verified share card feature: a static 1200x627 SVG card with four headline metrics, QR verify link, and Sigstore attestation mark, plus CI pipeline for PNG conversion and dual attestation. Files changed: - render/render.go: added CardSVG function with helpers (orgContextLabel, coverageWindowStr, prsMergedStr, reviewsGivenStr, medianTTMStr, activeDaysStr, qrSVGForURL, htmlEscape) - render/card_test.go: all 9 acceptance criteria tested via golden-file and structural tests (full/sparse/unverified golden SVGs, multi-owner, QR payload, self-containment, prohibited strings, dimensions, action.yml wire check, four-metrics-only gate, attested-mark gates) - render/testdata/: three golden SVG references - cmd/coderepute/main.go: writeReport now also writes card.svg - action.yml: added card.png screenshot step (headless Chromium), card-png output, attestation includes card.png - .github/workflows/coderepute-report.yml: card-png output - README.md: report output table includes card.svg/card.png rows; verification instructions include card.png Design decisions: - QR code reuses existing go-qrcode library (same pattern as verifyQRSVG template func) with a refactored standalone helper - Four headline metrics: PRs merged, reviews given, median TTM, active days -- exactly the fixed four, no invented values - Missing metrics render as em dash; attestation mark only when verified; single-owner shows org name, multi-owner shows 'N orgs' - SVG uses system font stack only, no external references - The verification badge is the sole indicator of attested vs unverified (QA red flag: no Sigstore mark on unverified reports) Co-Authored-By: Claude <noreply@anthropic.com>
…- issue 50 slice F The previous commit left card_test.go with misaligned comments and no trailing newline. gofmt -w fixes both; no semantic changes. Co-Authored-By: Claude <noreply@anthropic.com>
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
1 participant
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.
Closes #50
Implemented by the autonomous loop. Ran out of rounds (2 rejections) because QAA's own prompt hardcodes
npx tsc --noEmit/npx tsx --testas "the deterministic gate results" - commands that always fail with "npx not found" in this Go-only sandbox, triggering QAA's own automatic-CHANGES_REQUESTED-on-gate-failure rule regardless of the actual (Go) gates, which were genuinely green. I've filed this as a real bug incollaudo-orchestrator-core'sbuildQaaPrompt(not vehicle-configurable gate commands) rather than working around it silently.Verified directly, independent of the confused QAA rounds:
go build ./...,go vet ./...,go test ./...,gofmt -l .all pass cleanly on the final commit.verifyFallbackURL,fixturePath) are both properly defined (the former in this diff's ownrender.go, the latter a pre-existing test constant inrender_test.goreused as-is) - proven by the build itself succeeding, not just by inspection.render/, CI/action wiring, README table update, CLI wiring inmain.go.