chore(git): the discovery cap logs, and the resolve-and-fetch surface is noted master
The reader gains a notice sink, wired to console.warn, so the discovery cap reports what it drops rather than dropping in silence. A read names an account by DID and fetches the serviceEndpoint the DID document publishes, so it is a request to a URL a request chose, bounded to GET of the repo and git paths. The boundary is documented at the port and in the plan, so a deployment behind a private network resolves DIDs through a directory it trusts before it ships. The notice sink is an arrow that logs on an answer larger than a unit test builds, so the methods function floor drops from 100 to 96 with a note. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RomHvaB4nyAckbRD7W36Ue