feat: implement issue #444 built-in review integrity + merge guard#446
feat: implement issue #444 built-in review integrity + merge guard#446harsh-batheja wants to merge 16 commits intomainfrom
Conversation
|
Progress update: implemented issue #444 feature delivery (core review-integrity domain, API propose/verify/apply flow, merge guard enforcement, GitHub SCM thread/check integrations), pushed commit 95b96d2, and updated PR description with validation details.\n\nCurrent blockers/follow-ups tracked in PR body:\n- full review-activity drift semantics (comment/version drift),\n- always-on background check-run refresh loop,\n- review thread pagination beyond first 100 threads. |
|
Follow-up: fixed the Bugbot-reported duplicate blocker issue in |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Summary
@composio/ao-core./api/prs/[id]/review-threads,/review-resolutions,/review-resolutions/verify,/review-resolutions/apply).POST /api/prs/[id]/mergeto hard-block with structured guard blockers and publishesreview-integrity+ao/merge-guardcheck runs (with commit-status fallback).Validation
corepack pnpm --filter @composio/ao-core test -- review-integrity.test.tscorepack pnpm --filter @composio/ao-core typecheckcorepack pnpm --filter @composio/ao-plugin-scm-github test -- index.test.tscorepack pnpm --filter @composio/ao-plugin-scm-github typecheckcorepack pnpm --filter @composio/ao-web test -- api-routes.test.tscorepack pnpm --filter @composio/ao-web typecheckProgress vs Issue #444
422blockers, and review resolution API lifecycle.review-integrity,ao/merge-guard) and check publication support in SCM GitHub plugin.Known Blockers / Follow-ups
Notes