/assurance – 全仓库质量与检查体系统一规范（RADNA 体系）

Automating pull request classification involves analyzing PR diffs to categorize changes into Gate (security/infrastructure) or Business (functional features) buckets. This system automatically determines the change type and updates the relevant contract to prevent cross-contamination.

Generating QA-DECISION and AUDIT-REPORT artifacts is achieved by analyzing PR diffs against predefined rules. The system automatically produces these markdown artifacts based on the classified changes and contract updates, summarizing QA decisions and audit findings.

Updating Gate Contract (GCI) and Regression Contract (RCI) files requires classifying PR changes first. The system automatically updates gate-contract.yaml for Gate changes and regression-contract.yaml for Business changes, ensuring strict adherence to predefined boundaries.

Yes, a unified quality system coordinates both infrastructure and functional regression testing. It acts as a sole coordinator for the inspection system and business system, ensuring code quality and preventing regressions by classifying changes and managing contracts.

No, you do not need to manually define boundaries for code quality checks. The system ensures adherence to predefined rules and boundaries automatically, preventing cross-contamination between security infrastructure and functional business features.

Regression contract failures occur when changes are not properly classified. The system prevents this by automatically separating Gate changes into the Gate Contract and Business changes into the Regression Contract, ensuring no cross-contamination between the two categories.