feat(ui): route chat deploy intent through the template catalog

[zjy365]

Asked to "部署 glpi", the Assistant invented a Docker image instead of using the curated GLPI template that already exists in the Sealos catalog.

Three causes, all engineering:

1. No catalog discovery. createDeployTask accepts a template source but nothing let the model learn a valid templateName, so it fell back to the one source it could fully specify from its own knowledge.
2. No routing guidance. CHAT_BASE_SYSTEM_PROMPT covered AP/DB/Project/bash and said nothing about choosing a Deployment Source.
3. GitHub was hard-blocked in chat, and the error text pointed at a UI pane the model cannot operate — so it fell back to Docker.

Changes

Catalog discovery — new searchDeployCatalog, shaped like loadSkill (ranked index query, detail on demand), backed by the already-cached listTemplateCatalog. Returns the exact templateName plus required args. Returns a tool-level error instead of throwing when the provider is unreachable, so the turn degrades to a prompt source rather than dying.

Routing prompt — explicit source preference: template → github → prompt → docker, with docker only when the user names an image. Requires asking the user for a template's required args instead of inventing secrets (GLPI needs admin_password).

Unbound GitHub tasks (ADR-0062) — chat can now create GitHub tasks, and a task no longer requires a Deployment Credential Binding. The runner already treated the token as optional at every use site; a single throw required it. An unbound task clones a public repo anonymously and deploys an already-published image.

Two guards keep that honest:

• Creation fast-fails a repository GitHub positively refuses (404, or 403 with budget left). It fails open on rate limits — anonymous GitHub reads are 60/hr per egress IP, so inability to ask must not block a deploy.
• The managed gateway prompt tells the agent it has no registry credential and must fail with github-credential-required rather than attempt a push — turning a failure that used to land after a full image build into one at detection time.

Verification

bun typecheck and bun check clean.

Suite	Result
chat-deploy-catalog-tool.test.ts	9 pass
chat-deploy-task-tool.test.ts	6 pass
repo-public-access.test.ts	6 pass
runner-credential-binding.test.ts	4 pass
gateway-prompt.test.ts	4 pass
deploy-tasks/route.test.ts	14 pass
engine/engine.test.ts	42 pass

Ranking also validated against the live 215-template catalog: glpi, GLPI helpdesk, and the repo URL all rank the glpi template first and surface admin_password. wiki correctly returns nothing (no wiki template exists), falling through to the github/prompt path.

Two route tests changed meaning rather than breaking: they encoded the old "connection required" rule and now assert unbound creation plus private-repo rejection.

Notes for review

• Load-bearing assumption: unbound value depends on "public repo + already-published image" covering most requests. No data behind that yet — the share of tasks ending in github-credential-required is the signal. If most need a source build, the answer is lowering GitHub-connect friction, not more unbound work.
• The create path now makes a live GitHub API call for unbound tasks. Cached 1h, fails open.
• Deliberately not included: the 64k-row repo crawler DB. It has no deployability signal and would push the agent toward deploying libraries and awesome-lists.

🤖 Generated with Claude Code