fix(rhodibot): automated RSR compliance fixes

[hyperpolymath]

• Fixed SPDX header in (AGPL → PMPL)
• Fixed SPDX header in (AGPL → PMPL)

Summary

Changes

RSR Quality Checklist

Required

• Tests pass (just test or equivalent)
• Code is formatted (just fmt or equivalent)
• Linter is clean (no new warnings or errors)
• No banned language patterns (no TypeScript, no npm/bun, no Go/Python)
• No unsafe blocks without // SAFETY: comments
• No banned functions (believe_me, unsafeCoerce, Obj.magic, Admitted, sorry)
• SPDX license headers present on all new/modified source files
• No secrets, credentials, or .env files included

As Applicable

• .machine_readable/STATE.a2ml updated (if project state changed)
• .machine_readable/ECOSYSTEM.a2ml updated (if integrations changed)
• .machine_readable/META.a2ml updated (if architectural decisions changed)
• Documentation updated for user-facing changes
• TOPOLOGY.md updated (if architecture changed)
• CHANGELOG or release notes updated
• New dependencies reviewed for license compatibility (AGPL-3.0-or-later / MPL-2.0)
• ABI/FFI changes validated (src/interface/abi/ and src/interface/ffi/ consistent)

Testing

Screenshots

[hyperpolymath]

Closed during 2026-05-27 estate sweep: this PR is a regression, not a fix. The diff rewrites a correct AGPL-3.0-or-later SPDX header to an invalid AGPL-3.0-or-later-or-later (double suffix is not a valid SPDX identifier). rhodibot's auto-fix logic appears to apply s/AGPL-3.0/AGPL-3.0-or-later/ without checking whether -or-later is already present. Filing a rhodibot bug separately. No file change is needed in this repo — the existing headers are correct.