Tend Onboard — the installer

Detect this repo's stack, determine which capability modules apply, and write .claude/tend/config.yaml so the other tend-* skills stop running at conservative core-tier defaults. Runs once per install (or after a stack change) — not a scanning skill itself.

Phase 1 — Investigate

Spawn a single Explore-subagent investigation of the repo (the same shape as do-security-audit's Phase 1 stack triage, but broader): read package.json, lockfile, config files (svelte.config.js, vite.config.ts, biome.json, .env.example), and grep for code signatures. The subagent should report back, not act — it makes no edits.

MANDATORY READ references/module-signals.md before spawning — the exact dependency and code-signature signals for each of the 5 capability modules.

Ask the subagent to report:

1. Core stack confirmation (SvelteKit + Svelte 5 + TS strict + Biome + Vitest + pnpm) — flag anything missing or different; a missing core piece means core-tier tend skills will need to fall back further than usual.
2. Which of the 5 modules apply, with evidence (dependency name + version, or file:line for pattern-only signatures).
3. Repo-knowledge seeds: existing off-limits conventions (generated files, vendored code, lockfiles), any naming pattern for "superseded" or "@deprecated" helpers, any existing feature-flag or auth-token module names worth recording.

Phase 2 — Resolve ambiguity

Dependency-detectable modules (data, validation, realtime) auto-activate on a confirmed dependency — no confirmation needed.