Same upgrade as favela-peer 0.0.59, for the same reason: autobee 2.1.1's `_bumpPendingWriters` reselects a pending writer it can neither apply nor drop (fixed upstream in 2.5.1, ed166f4). That loop pinned a core in ap-bridge on 2026-10-12. This registry opens its base `optimistic: true`, so it was not exposed to that exact path, but it was the last 2.1.1 left in favela-peer's tree, and one autobee across the stack is the point. Now resolves autobee 2.12.1, hyperbee2 2.18.0, hypercore 11.38.0: the same as favela-peer. 10/10 tests, 37 asserts, under brittle-bare AND brittle-node. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>