fix: publish native GitHub reviews#10
Merged
CompleteDotTech merged 3 commits intoJul 14, 2026
Merged
Conversation
CompleteDotTech
marked this pull request as ready for review
July 14, 2026 11:43
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
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.
Summary
APPROVEorREQUEST_CHANGES; downgrade stale, partial, contradictory, dirty-worktree, incomplete-diff, or unverified-test output toCOMMENTpull_request/pushApp subscriptions are explicitly verifiedRoot cause
The hosted adapter published agent text as issue comments and trusted runtime claims without fully reconciling them against the PR revision, checkout, diff coverage, validation receipts, or existing GitHub review state. It also performed long work in the webhook request path and lacked reliable recovery for several crash, race, and transient-API cases. Together, those gaps caused inconsistent pseudo-reviews, duplicate or stale review state, and ambiguous test claims.
This remains deployment-specific transport and evidence enforcement. Canonical familiar/authority rules and result contracts continue to live in
OpenCoven/coven-github.Validation
npm test— 93 passingnpm run buildnpm run smoke:appnode --check scripts/doctor-app-config.mjsjq empty config/example-policy.jsongit diff --checkTypeScript test + buildonb96014caf095243dc8226b7e393d8d900960bca1Coverage includes delivery-claim and publication races, orphan recovery, worker crashes, stale head/base revisions, base-branch pushes, masked dismissal failures, Retry-After handling, signed-marker forgery/key rotation, inline diff locations, incomplete evidence, secret redaction, state-path hardening, and isolation gates.
Deployment gates
publication.mode=record_onlyuntil the installed App is verified to receive bothpull_requestandpush, and protected-branch dismissal authority is proven with a real test PRcoven-codestill receives a reusable model credential; untrusted/public PR execution needs a separately constrained worker and quota-limited credential broker