cc-devflow

Review and land one authenticated provider-native review item. Use when current-head review, landing, closeout, and remote-main parity are in scope.

Submit a named verified source for remote review. Use when explicit authority covers push and one review item, but not approval or landing.

Simplify verified changes before remote submission. Use for deletion-first, YAGNI, native-library, structural, and test-seam review.

Create narrow auditable local commits. Use when verified Dverity work must be staged and committed without absorbing unrelated changes.

Resolve an in-progress merge or rebase conflict from proven product intent. Use only when Git reports an actual conflict.

Find and reuse the nearest correct mechanism before adding another. Use when a Dverity change would add reusable code, policy, or workflow meaning.

Diagnose and repair confirmed defects to Verified Local. Use for evidence-first bug repair; remote submission requires separate explicit authority.

Gather evidence for Dverity repair decisions. Use when a repair hypothesis or boundary needs primary-source proof before mutation.

Recall or record confirmed reusable failure lessons. Use after a verified recurrence, review escape, failed gate, or explicit user request.