tenjin-searchlisted

# Tenjin search: one lookup before you regenerate The `tenjin` CLI owns every mechanic: HTTP, x402 payment signing, SIWX auth, entitlements, local delivery. You never assemble a request or a payment payload. ALWAYS pass `--json`: it prints one compact JSON object on stdout for you to parse. Without it, at an interactive terminal the CLI is human-first (prose, no envelope), so a PTY-allocating harness would otherwise get unparseable output. Every command below already includes it. Exit codes: `0` success (an honest MISS is success), `1` network/runtime, `2` usage, `3` policy refusal, `4` payment failure. On failure the commands self-diagnose; `tenjin doctor` is optional diagnostics, never a required first step. ## When to look up (all four, or don't) 1. The question is public: answerable without private repo, company, or customer context. 2. The answer is durable or semi-durable: not a live price, uptime, or anything stale on arrival. 3. Reproducing it is genuinely costly: real browsing, testing, paid data, specialist judgment, or elapsed-time observations, not one ordinary model response. 4. Someone plausibly did this exact work: "what actually happens integrating X v3 with Y v5", "which facilitators support this capability, verified recently", "is there a tested migration/compat report", "has someone run this probe or benchmark". If any of the four fails, generate instead. When they hold, look up first: a habitual miss adds latency and context to eve