factory-line

# Factory line Execute **one station** of a declared program end-to-end: sync → wave plan → parallel slots → cumulative gate → human handoff. The program lives in an **installed line bundle**, not in this skill. Find it with `har line status`: installed lines live at `.har/lines/<id>/line.json` and are recorded in `.har/lines.json`. This skill is the orchestrator; station-specific how-to lives in other skills the program lists. `*.line.json` files under `examples/` are **authoring templates**, not the installed program. Read one to learn the shape or to seed a new bundle (`har line create <id>`); do not run a station off a loose file when a line is installed. **HAR already has the primitives.** Work units, isolated slots, stages with quick/full tiers, validation records, the commit gate, plugins, Mission Control. A line is composition plus a manifest. Do not invent a second runner, a stack-specific MCP tool, or GitHub-shaped stations. Contract: [LINE.schema.md](./LINE.schema.md). Instances: [examples/](./examples/). ## Inputs Resolve these before doing anything (ask only if not inferable): 1. **Line** — run `har line status` (or MCP `har_line_status`). One installed line: use it. Several: ask which. **None installed**: stop and offer `har line create <id>` (scaffold) or `har line add <spec>` (install a published bundle, e.g. `github:os-factory/har-line`). Authoring templates live in `examples/`: `v1-milestone.line.json`, `new-plugin.line.json`, `docs-m...