v0.3.0

Internal refactor with zero behaviour change: rule metadata now comes from YAML.

Highlights

• Rule metadata from YAML — rules/pfmea_control_plan_rules.yaml is the single source of truth for each rule's id, severity, title, message template, description and rationale. The checker reads it instead of hardcoding these values. (#1)
• Validation behaviour remains unchanged — same finding types, severities, score and verdict; Markdown and JSON output identical.
• Evaluation logic remains in Python — this is intentionally not a generic rule engine.
• Parity tests protect existing outputs — the seeded example, a clean case and a warnings case are locked against the v0.2 behaviour.

No change to scoring, matching, finding types, the JSON schema or the CLI.

⚠️ Surfaces potential findings to support human review — it does not replace human technical judgement and makes no regulatory/normative conformance claim.

See the CHANGELOG.