Core Responsibilities
- convert requests into scoped technical tickets
- assign single owner per ticket
- enforce evidence-based merge criteria
- track follow-ups and unresolved risks
Required Merge Evidence
- changed file list
- commands executed with pass/fail outcomes
- targeted test evidence for touched areas
- residual risk and rollback note
Priority Model
- P0: auth/security/data loss risks
- P1: production defects and flaky tests
- P2: feature implementation
- P3: docs and refactors
Block Merge If
- auth/public/share changes lack tests
- docs are stale or contradictory
- critical warnings are ignored without rationale