[refactor] Introduce Typed Safety Audit Finding Types in Classification Engine #40

New issue

Closed

opened 2026-08-30 16:14:08 +03:00 by jalmari · 1 comment

jalmari commented

2026-08-30 16:14:08 +03:00

Owner

Parent

Part of #39

What to build

Add an explicit AuditFindingType string enum in the classification domain module. Update ClassificationEngine.audit_safety and SafetyAuditor to emit and evaluate AuditFindingType constants instead of plain string literals.

Acceptance criteria

AuditFindingType enum is defined with categories for transactional, shipping, and protected item findings
ClassificationEngine.audit_safety returns tuples of (AuditFindingType, AnalysisResult)
SafetyAuditor evaluates AuditFindingType constants during scan summary and plan audits
Unit tests for classification engine and safety auditor verify typed finding assertions

Blocked by

None (can start immediately)

## Parent Part of #39 ## What to build Add an explicit `AuditFindingType` string enum in the classification domain module. Update `ClassificationEngine.audit_safety` and `SafetyAuditor` to emit and evaluate `AuditFindingType` constants instead of plain string literals. ## Acceptance criteria - [ ] `AuditFindingType` enum is defined with categories for transactional, shipping, and protected item findings - [ ] `ClassificationEngine.audit_safety` returns tuples of `(AuditFindingType, AnalysisResult)` - [ ] `SafetyAuditor` evaluates `AuditFindingType` constants during scan summary and plan audits - [ ] Unit tests for classification engine and safety auditor verify typed finding assertions ## Blocked by - None (can start immediately)

jalmari added the

ready-for-agent

label

2026-08-30 16:14:08 +03:00

jalmari referenced this issue

2026-08-30 16:14:08 +03:00

[test] Verify End-to-End Safety Audit and Tooling Integration #42

jalmari added a new dependency

2026-08-30 16:14:08 +03:00

#42 [test] Verify End-to-End Safety Audit and Tooling Integration

jalmari commented

2026-08-30 16:33:13 +03:00