Honcho Backlog Cleanup

The open Honcho backlog has a lot of duplicate/overlapping PRs. Before merging more one-off fixes, maintainers should decide whether Honcho stays in-tree or is removed.

Decision Needed

PR #32753 removes the Honcho memory plugin. If that is the direction, most open Honcho PRs should be closed. If Honcho stays, the cleanup should focus on picking one canonical PR per bug and closing duplicates.

Current main already has Honcho under plugins/memory/honcho/, so #12743 should be treated as migration/activation cleanup rather than the initial plugin-system move.

Recommended Next Steps

1. Decide keep vs remove: #32753.
2. If keeping Honcho, merge/rebase narrow high-value fixes first:
   • #32244: apply 0600 permissions to memory-plugin config files containing API keys.
   • #30077: runtime peer mapping correctness; supersedes #27371.
   • #31240: fallback for direct target peer cards; closes #31219.
   • #15380: cap Honcho session names; closes #13868.
3. Close superseded duplicate PRs by cluster:
   • Multimodal sync_turn crash (#30252): prefer #32030; close #22768, #26484, #30264, #30294.
   • Peer-card "No profile facts" (#31219/#4751): prefer #27979 + #31240; close write-only subsets #20729/#23022 and fold/close #23485.
   • Multi-user identity (#27314/#28283): keep #30077, reconcile #28572, close #27371.
   • Session override normalization (#13284): prefer #23256 after rebase/status check; close #7629/#13322/#13333.
   • base_url/self-hosted handling (#2613/#4269/#20688): keep focused candidates #13439/#14489/#20720 after rebase/status check.
4. Track remaining real work separately:
   • #4074: cloud disclosure/security; #24458 exists but needs a clean rebase.
   • #13631: cache invalidation/perf from auto-injected context.
   • #4523, #8920, #17968, #5434: no clean fix identified.

Status note: PR mergeability was spot-checked on 2026-05-26. Re-check before merging or closing anything.