review-feedback-schema

# Review Feedback Schema ## Purpose Structured format for logging code review outcomes. This data enables: 1. Identifying rules that produce false positives 2. Tracking skill accuracy over time 3. Automated skill improvement via pattern analysis ## Schema ```csv date,file,line,rule_source,category,severity,issue,verdict,rationale ``` | Field | Type | Description | Example Values | |-------|------|-------------|----------------| | `date` | ISO date | When review occurred | `2025-12-23` | | `file` | path | Relative file path | `amelia/agents/developer.py` | | `line` | string | Line number(s) | `128`, `190-191` | | `rule_source` | string | Skill and rule that triggered issue | `python-code-review/common-mistakes:unused-variables`, `pydantic-ai-common-pitfalls:tool-decorator` | | `category` | enum | Issue taxonomy | `type-safety`, `async`, `error-handling`, `style`, `patterns`, `testing`, `security` | | `severity` | enum | As flagged by reviewer | `critical`, `major`, `minor` | | `issue` | string | Brief description | `Return type list[Any] loses type safety` | | `verdict` | enum | Human decision | `ACCEPT`, `REJECT`, `DEFER`, `ACKNOWLEDGE` | | `rationale` | string | Why verdict was chosen | `pydantic-ai docs explicitly support this pattern` | ## Gates (feedback log rows) Run **in order** before appending a row. Do not skip ahead while a gate fails. 1. **Evidence bound to code** - **Pass when:** `file` is a repo-relative path that exists (or existed at review time), an...