{"content":"Development journal for commit 9633e920 (fix(trust): owner pin gmid-to-address via metafile-indexer + bind-device cache invalidation).\n\nTwo smoke-test findings fixed. BUG-1 (P1 read-side): resolveMetaIdOwnerAddress queried manapi /api/info/metaid/:gmid, which answers a globalMetaId with an empty record (no address) - so the default OwnerPinReader returned null for every subject and the whole trust chain walk never walked a link: deviceBinding stuck unbound, team add always team_not_same_owner, grant reads always empty, remote peers always stranger. Step 1 now uses the metafile-indexer globalmetaid route (the omni-read convention, manapi has no gmid endpoint); steps 2-3 stay on manapi (verified healthy). Live-verified against real indexers: the device-to-owner binding pin published 11-20 (373132bd...80c9ai0) now resolves to a BOUND verdict with the exact daemon deviceBindingStatus logic. BUG-2: bindDevice published the pin but left the pre-bind self-root trust-cache entry in place for up to its 5-minute TTL; it now drops the device entry best-effort after a successful publish. New tests: ownerPinRead (two-base convention, walk, revoke filtering, path lister) + ownerHandlers (cache invalidation, fail-closed bind, who deviceBinding). Scoped suite 136/136. Follow-up noted, out of scope: no OAC code path publishes the Bot-to-Device binding pin, so local bots resolve to self-root by design-of-absence; peer tiers need bot binding publishes to climb.\n\nVerification:\nnode --test --test-concurrency=1 tests/owner/*.test.mjs tests/trust/*.test.mjs\n\nFiles:\nsrc/core/trust/ownerPinRead.ts\nsrc/daemon/ownerHandlers.ts\ntests/owner/ownerHandlers.test.mjs\ntests/trust/ownerPinRead.test.mjs","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}