security: 10 Critical/High panic-attack findings need human triage (Track C)

[hyperpolymath]

panic-attack estate sweep — Track C tracking issue

panic-attack assail flagged the findings below in this repo on 2026-05-26. They are aggregated here for human triage rather than as individual PRs because each requires judgement (supply-chain pin choice, schema-design call, mutation-test gap, etc.).

PA001/PA007 UnsafeCode/UnsafeFFI findings are NOT in this list. Findings already suppressed in audits/assail-classifications.a2ml are also excluded.

Estate tracker: hyperpolymath/panic-attack#32.

SupplyChain (1 findings)

file:line list

### `UnboundedAllocation` (9 findings)

file:line list

Critical  src/rsr/compliance.rs:?  Potential unbounded allocation pattern detected in src/rsr/compliance.rs
Critical  src/rsr/schemas.rs:?  Potential unbounded allocation pattern detected in src/rsr/schemas.rs
Critical  src/rsr/templates.rs:?  Potential unbounded allocation pattern detected in src/rsr/templates.rs
Critical  src/rsr/remediation.rs:?  Potential unbounded allocation pattern detected in src/rsr/remediation.rs
Critical  src/rsr/requirements.rs:?  Potential unbounded allocation pattern detected in src/rsr/requirements.rs
Critical  src/rsr/config.rs:?  Potential unbounded allocation pattern detected in src/rsr/config.rs
Critical  src/cache/filesystem.rs:?  Potential unbounded allocation pattern detected in src/cache/filesystem.rs
Critical  src/pipeline/definition.rs:?  Potential unbounded allocation pattern detected in src/pipeline/definition.rs

---

🤖 Discovered during the panic-attack estate sweep (2026-05-26). See hyperpolymath/panic-attack#32 for campaign tracker.