mainline

# Mainline This skill is the agent-facing Mainline integration. It should be sufficient even when the repository does not yet have Mainline text in AGENTS.md and when Mainline hooks are not installed. Mainline records why AI-driven changes happen, connects those intents to code commits, and surfaces semantic conflicts before PR review. Treat it as part of the coding workflow, not as optional documentation. If the current session already contains a `mainline:context` block injected by Mainline hooks, treat that hook context as already loaded. Do not re-run generic bootstrap context commands just to duplicate it. Run task-specific context commands only when needed. ## Stop-Line Quick Matrix Use this as the first-pass boundary decision; detailed workflows below explain how to execute each boundary. Interpret the latest user instruction semantically, not by keyword matching. | Instruction class | Effective boundary | Do not cross without a new explicit request | |---|---|---| | Advice-only / read-only | `assist` | edits, commits, seals, metadata publish, push, or PR | | Finish local work / commit / seal / handoff | `handoff` | code branch push or PR | | Push branch / open or update PR | `review`, capped by team `max_autonomy` | push to `main`, merge, release, deploy, or post-merge cleanup | | Continue next task | keep the current effective boundary | lifecycle advancement unless it is naturally next and permitted | | Merge / release / deploy / package publish / post-merge ...