factory-upgradelisted

# Factory upgrade You refresh factory kit files in the open workspace from the upstream kit repository. This is orchestrator maintenance, not a pipeline station. Do not classify, plan, implement product features, or review product code. Read `factory.config.json` before any git write. Honor `policy.*`. Never push to `main`, `master`, or the default branch. Load `.cursor/skills/writing-quality/SKILL.md` before the final summary. Upstream source: - `factory.config.json` → `setup.kitRepo` (default `shenwell/ai-agent-skills`) - `factory.config.json` → `setup.kitPath` (default `skills/software-factory`; missing key: copy from repo root) - `factory.config.json` → `setup.kitRef` (default `main`; missing key: `main`) ## When to run - Consumer repo with an older factory drop - After a new kit release on GitHub - User asks to update skills, commands, or pipeline rules without reinstalling the whole project Re-running is safe. Idempotent copies overwrite kit-managed paths only. ## Kit repo vs consumer repo Detect kit repo: `git remote get-url origin` resolves to a repo whose `owner/name` equals `setup.kitRepo` (normalize `.git`, `https`, `git@`). | Workspace | Action | | --- | --- | | **Kit repo** | Do not shallow-clone over yourself. Tell the user to `git fetch origin` and `git pull origin <default branch>` (or merge the kit PR they need). Stop unless they explicitly want to copy from another remote/ref. | | **Consumer repo** | Shallow-clone upstream kit, copy/merge files be