List Installed On

The connections THIS identity holds (TOS-6647).

Historically this endpoint returned the full live set, whose first leg is every account in any folder the subject REACHES - so a person who never connected anything saw the whole folder catalog rendered as "Attached" on their profile. That conflated two questions: what is reachable (the Marketplace/Discover read, served by /instances with its reach parameters) and what the subject HOLDS (this read).

Held means one of exactly three things, resolved as a case() over the instance rows in the SAME statement that fetches them (zero extra round trips past the route's sql-trace baseline):

• the subject's own credential row exists on the account (per_caller connected by them, or the shared account's connection is theirs) -> "connected",
• an active, unexpired ConnectionAccessGrant names them (TOS-3500) -> "granted", or
• the account was explicitly attached for them -> "approved". The attaching decision may be the subject's own (decided_by == subject, what POST /instances/{id}/install records in a normal folder) or their controller-owner's (TOS-3444: the owner attaching their own home folder integration to their agent is the ONLY attach path a home folder allows, and the route deliberately records decided_by = the owner, "the owner authorized it, not the agent itself").

Plain folder reach, wrapper projection and approvals decided by someone who is neither the subject nor their controller-owner are NOT holds and are dropped from the response; the raw live set remains available to callers that genuinely answer the reach question (turn-pipeline liveness). hold_state tells the three cases apart so the shelf can render "Connected" (your credential) vs "Granted" (shared to you) vs "Approved" (attached by or for you).