@lead: externalize agent.yml inline scripts into .gitea/workflows/scripts/*.sh

Rebased onto the per-agent skill-scoping change so PR #25 carries both:
- route.sh keeps the registry 'skills' allow-list and emits skills as a step output
- install-opencode.sh writes the permission.skill block (deny-all + allow listed)

Pure refactor otherwise: each step's shell moves to its own file, called via
bash "$SCRIPTS/<name>.sh". The two extracted SKILL.md bodies are byte-identical to
main; routing/config/publish behavior is unchanged. Because this is a reusable
workflow (workflow_call) the runtime checkout is the caller's repo, so agent.yml now
checks THIS repo out into .agents-workflow/ (pinned @main) and points $SCRIPTS there.

.gitea/workflows/scripts/install-opencode.sh

@@ -0,0 +1,39 @@
+#!/usr/bin/env bash
+# Install opencode + provider config (+ Playwright MCP for browser agents).
+#
+# Required env (provided by the workflow step): OLLAMA_URL OLLAMA_CLOUD_API_KEY NAME SKILLS
+#   GITHUB_PATH HOME
+set -eu
+
+curl -fsSL https://opencode.ai/install | bash
+echo "$HOME/.opencode/bin" >> "$GITHUB_PATH"
+mkdir -p ~/.config/opencode
+# Playwright browser MCP only for agents that need to drive a web app
+MCP='{}'
+case "$NAME" in
+  senior|lead|qa)
+    echo "Enabling Playwright MCP for @$NAME"
+    MCP='{"playwright":{"type":"local","command":["npx","-y","@playwright/mcp@latest","--headless"],"enabled":true}}'
+    npx -y playwright install --with-deps chromium || npx -y playwright install chromium || true
+    ;;
+esac
+# Per-agent skill scoping. Skills are loaded on-demand by opencode: only a skill's one-line
+# `description` ever appears in an agent's <available_skills> list, and the full SKILL.md body
+# (curl/API how-to) is loaded ONLY when the agent calls the `skill` tool — it is never in any
+# system prompt. To also hide the summary from agents that shouldn't use a skill, we deny all
+# skills by default and allow only the ones in this agent's registry list (passed via $SKILLS).
+# A denied skill is hidden entirely (name + description omitted), so e.g. @junior never sees
+# gitea-api at all; it just knows from the roster that @senior/@lead can, and asks them.
+SKILLS="${SKILLS:-[]}"
+PERM=$(jq -nc --argjson s "$SKILLS" '
+  {skill: ( {"*":"deny"} + (reduce $s[] as $k ({}; . + {($k):"allow"})) )}')
+# Two ollama providers: local self-hosted (ornith) + Ollama Cloud (gemma4/kimi-k2.7-code/glm-5.2/minimax-m3).
+jq -n --argjson mcp "$MCP" --argjson perm "$PERM" --arg url "$OLLAMA_URL" --arg ckey "$OLLAMA_CLOUD_API_KEY" '{
+  provider: {
+    ollama: {npm:"@ai-sdk/openai-compatible", options:{baseURL:($url+"/v1")}, models:{"ornith:35b":{}}},
+    "ollama-cloud": {npm:"@ai-sdk/openai-compatible", options:{baseURL:"https://ollama.com/v1", apiKey:$ckey}, models:{"glm-5.2:cloud":{},"gemma4:cloud":{},"kimi-k2.7-code:cloud":{},"minimax-m3:cloud":{}}}
+  },
+  permission: $perm,
+  mcp: $mcp
+}' > ~/.config/opencode/opencode.json
+echo "opencode config (secrets masked):"; cat ~/.config/opencode/opencode.json