security: 7 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 (Track A covers PA001/PA007 separately via PR #11). Findings already suppressed in audits/assail-classifications.a2ml are also excluded.

Estate tracker: hyperpolymath/panic-attack#32.

DynamicCodeExecution (1 findings)

file:line list

### `HardcodedSecret` (5 findings)

file:line list

Critical  protocols/proven-kms/src/KMS/Types.idr:?  Possible hardcoded secret in protocols/proven-kms/src/KMS/Types.idr
Critical  protocols/proven-radius/src/RADIUS/Types.idr:?  Possible hardcoded secret in protocols/proven-radius/src/RADIUS/Types.idr
Critical  protocols/proven-authserver/src/Authserver/Types.idr:?  Possible hardcoded secret in protocols/proven-authserver/src/Authserver/Types.idr
Critical  not-proven/proven-ssh-bastion/src/SSH/Auth.idr:?  Possible hardcoded secret in not-proven/proven-ssh-bastion/src/SSH/Auth.idr

### `SupplyChain` (1 findings)

file:line list

---

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