Each file here is a complete, copy-paste stub workflow. Pick the one that matches your setup, copy it to .gitea/workflows/adversarial-review.yml in the repo you want reviewed, and set the secrets/vars it references. Gadfly is advisory only — it never blocks a merge.

File	Backend	Needs
`reusable.yml`	slimmest stub — calls Gadfly's reusable workflow and inherits its default swarm (3 cloud + Claude Code, 5-lens suite), forwarding only the secrets it needs (least privilege, not `secrets: inherit`); the stub keeps a cloud-only `models:` override so it runs with just the Ollama key (drop it + add the Claude token to get the full default)	secret `OLLAMA_CLOUD_API_KEY`
`adversarial-review.yml`	Ollama Cloud (default) + inline notes for every provider; full self-contained stub	secret `OLLAMA_CLOUD_API_KEY`
`local-ollama.yml`	a local/LAN Ollama daemon	nothing (or `GADFLY_BASE_URL` for a remote host)
`openai-compatible.yml`	any OpenAI-compatible endpoint (local Ollama `/v1`, gateway, vLLM, OpenRouter…)	`GADFLY_BASE_URL` (+ a key for most gateways)
`endpoint-aliases.yml`	several named backends at once (one comment each)	repo vars `GADFLY_ENDPOINT_<NAME>`
`claude-code.yml`	the bundled Claude Code CLI engine (`claude-code/<model>`)	secret `CLAUDE_CODE_OAUTH_TOKEN` (or `ANTHROPIC_API_KEY`)
`.gadfly.yml`	per-repo specialist config (not a workflow — goes at your repo root)	—

Common to all:

Triggers: new/reopened/ready non-draft PR (auto), @gadfly review comment (allowed users), or manual workflow_dispatch with a pr_number.
GITEA_TOKEN is provided automatically; comments post as gitea-actions.
Tested backends are the Ollama ones; OpenAI/Anthropic/Google are wired via majordomo but untested. See the repo README for the full config reference and the honest tested/untested status.

Gitea note: repo vars/secrets are not auto-exposed as env — anything you reference via ${{ vars.X }} / ${{ secrets.X }} must appear in the step's env: block (already wired in these examples).