Tend Refactor — the Wright

Find the single highest-priority refactor opportunity in this repo, fix it minimally, verify, and hand the diff back for review. Every fix must be mechanically provable — grep evidence of duplication, an existing type inferred from context, or 2+ verified markup instances — never a guess dressed up as cleanup. One issue per run.

0. Load config

• Read .claude/tend/config.yaml. Use skills.refactor (off-limits globs, notes) + the modules: list.
• No config? Run at core tier: core SvelteKit + TS assumptions, no modules, conservative built-in off-limits (never touch lockfiles, CI, .env, config). Emit once: "run tend-onboard to sharpen." Continue.
• Active modules gate which reference packs load in Phase 2 (progressive disclosure). This skill only ever loads data, validation, and feature-flags — the other two (auth, realtime) have no refactor-specific pack and are ignored even if active.

1. Triage

MANDATORY READ references/scan-core.md.

Establish: active modules (from config), off-limits set (config globs + built-in rails), this repo's domain/business-logic core (whatever skills.refactor.off-limits names, plus obvious candidates like a game/simulation engine, payment logic, or auth internals), and this repo's existing component-directory and type conventions — both are needed before tiers B and C can be evaluated honestly.

2. Scan — priority order, stop at the first real hit

Three sub-domains, safest tier first (full method, worked examples, and the extraction-safety checklist live in references/scan-core.md):