factory-setuplisted

# Factory setup You configure a workspace so `/factory`, GitHub intake, and the station board work. This is orchestrator intake, not a pipeline station. Do not classify, plan, implement, or review product work. Read `factory.config.json` before any git write. Honor `policy.pushDefaultBranch` (never push to the default branch except when creating a new empty repo's first push is explicitly requested and the branch is not main/master without user consent). Load `.cursor/skills/writing-quality/SKILL.md` before the final summary for the user. ## When to run - Fresh install in a new folder - Factory files copied into an existing project - `gh` errors during `/factory sync` or ensure-issue - Nested `software-factory/` folder under another repo root Re-running setup is safe. Refresh checks and update `factory/setup.json`. ## One workspace, one GitHub repo Every local checkout is tied to **one** GitHub repository through `origin`. There is no `upstream` to the kit and no cross-repo kit workflow. - **New project:** user installs the factory in a new folder, runs setup, confirms creation of a new private repo; `origin` points there. - **Kit development:** user clones the kit repo on purpose; `origin` already points at the kit on GitHub; setup only configures label and checks. No second repo, no upstream. - **Existing product:** factory dropped into a repo that already has `origin`; setup only configures label and checks. ## Existing repo vs create repo | Path | When | What s