# Vendored assets — provenance & sync

`sql-tools-config.schema.json` is a **snapshot** copied out of the Ixora platform repo. It's a hand-authoring aid: it documents the exact shape of a custom SQL tool (field names, types, bounds) so you can write valid `ibmiTools` / `--ibmi-tools` YAML. It is **not executed by this skill** — the platform validates each tool server-side when you run `ixora agents create`. Because it duplicates a contract the Ixora app owns, it can drift; re-sync on release.

| File | Upstream source | Last synced |
|------|-----------------|-------------|
| `sql-tools-config.schema.json` | `ixora/tools/sql-tools-config.schema.json` | ixora @ `1b9a350` |

The agent-config contract (the IBM i toolkit, the `/agents:apply` payload shape, the protected keys `tools`/`dependencies`/`db`) now lives **entirely server-side** — owned by the `ixora agents create/apply/update` CLI and the platform's agent-create endpoint (in `ixora`, the `AgentBuilderTools` / `builder.py` area; this is part of the in-flight agents-create feature and may not be on the platform's released branch yet). This skill no longer duplicates it, so there's nothing here to keep byte-for-byte in sync; the only shared snapshot is the schema above.

## Sync check

To confirm the schema snapshot is current:

```bash
diff sql-tools-config.schema.json /path/to/ixora/tools/sql-tools-config.schema.json
```

If a custom-tool agent is rejected at `ixora agents create` with a shape error this snapshot doesn't explain, the snapshot has drifted from the platform — re-sync it.