agents-synclisted

**OPTIONAL — requires a Quarktex API key in config.yml; refuse with a one-line setup pointer if disabled.** > Inherits `references/kernel.md` (the provenance contract). Reads `references/wiki-spec.md` for schema. > Wire contract: `integrations/quarktex/relay-contract.md`. Cache format: `integrations/quarktex/agents/_agents.md` (SPEC §10). ## Gate (check first, every run) 1. Require `quarktex.enabled: true` in `config.yml` **and** a key in `.env` (`bash integrations/quarktex/relay.sh check`). 2. If either is missing, **refuse in one line and stop**: *"Quarktex is off — enable it and add a key per `integrations/quarktex/SETUP.md`."* ## What this does Refreshes the **cache of callable agents** so `/call-agent` has cards to work from. It only touches the discovery cache and the trust column — it does **not** call any agent and writes **nothing** to `wiki/`. (Discovery is metadata, not knowledge: agent cards are not facts about your business, so they never enter canon. A fact only enters the brain when `/call-agent` actually invokes an agent and `/capture` sources it.) ## Execution ### Step 1 — Query the directory 1. Run discovery via the relay (public view; webhooks are hidden): ```bash bash integrations/quarktex/relay.sh search "<text>" --capability <cap> # GET /agents?q=&capability= bash integrations/quarktex/relay.sh get qt_yyyyyyyy # GET /agents/:id (one card) ``` With no arguments, do a broad pull to seed the cache. Each ca