chore(release): enforce self-coverage in CI + dogfooding badge - #24
Merged
Conversation
…sign [roadmap:autonomous-qa-enhancements] Implements lore-proofkeeper/requirements/req-dogfood-coverage-gate.md and lore-proofkeeper/designs/design-dogfood-coverage-gate.md. Records the capability that Proofkeeper's own corpus stays fully verified, enforced in CI via the coverage command and surfaced as a README badge. The requirement is itself verified by the dogfood workflow file. Signed-off-by: Tom Ballard <tom@armytage.co>
…dge [roadmap:autonomous-qa-enhancements] Adds .github/workflows/dogfood.yml: builds, installs the rac engine from rac-core, and runs 'proofkeeper coverage --corpus lore-proofkeeper/', which exits non-zero on any unverified capability. Adds a README dogfooding badge tied to the workflow's status on main. Proofkeeper now verifies itself the same way it verifies any consumer. Signed-off-by: Tom Ballard <tom@armytage.co>
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.
What & why
Turns Proofkeeper's dogfood signal into an enforced gate: a CI job runs Proofkeeper's own
coveragecommand against its own Lore corpus and fails on any unverified capability, so the corpus can never drift un-green. Plus a README dogfooding badge tied to the job.This was split out earlier because it depended on rac-core's
verified_bygraph contract (ADR-096), which is now merged to rac-coremain(#245). The gate installsracfrom rac-coremain, so it now finds theverified_byedges and passes.How
.github/workflows/dogfood.yml(job Dogfooding): build, install theracengine from rac-core (pip install "git+https://github.com/itsthelore/rac-core.git"— a contract dependency, not a package dep; distribution isrequirements-as-code, console scriptrac), then runnode dist/cli.js coverage --corpus lore-proofkeeper/, which exits non-zero on any unverified capability. Uses the real CLI and the realrac export --graphcontract path — Proofkeeper verifies itself the way any consumer would.dogfoodingbadge tied to the workflow's status onmain.req-dogfood-coverage-gate+design-dogfood-coverage-gate(the gate is itself a recorded capability,## Verified Bythe workflow file), plus a roadmap initiative.Verification
verified_by-capablerac:proofkeeper coverage --corpus lore-proofkeeper/→ 13/13 capabilities verified, exit 0. Gate teeth confirmed earlier: exit 1 on a mixed fixture, 0 on all-verified.rac validate27/27,rac relationships --validate0 issues,rac review100/100.main(after feat(agent): OpenAI-compatible model adapter — BYOK for any model #22/feat(agent): browser-extension verification (load, drive, compile, re-run) #23); the roadmap now lists all three new initiatives.Notes
main(works now that #245 is merged). Pinning to a tagged rac-core release is optional hardening — a follow-up, not required for green.