GJC SDK session discovery

Use this skill when an external agent needs to find or inspect local GJC sessions without terminal scraping, MCP, or coordinator delegation.

Required behavior

1. Resolve the repository root explicitly.
2. Run gjc sdk session list --json with that repository as the working directory and consume only its credential-free Broker DTO.
3. Select an exact session ID from that DTO, then use gjc sdk session inspect <sessionId> --json or the fixed raw-query commands below.
4. Fail closed for missing, unavailable, stale, dead, unknown, or ambiguous Broker results.
5. Never scan .gjc/state/sdk, parse endpoint records, read credentials, or open a raw per-session WebSocket.
6. Add --json explicitly to every machine CLI call: successful session JSON is unchanged, but default ordinary failures are text on stderr. Consume the single gjc.command-error version 1 stdout envelope on nonzero exit; never treat missing JSON as success or publish raw stderr. Usage exits 2; operation failures exit 1.

Core inspection recipe

Compose this task-required pull-based view in order with gjc sdk session raw query <sessionId> --query <query> --json: