adopt-pipelinelisted

# Adopt Pipeline Skill Change the `adopt` module — a pipeline of small, ordered steps that clones a GitHub repository, wires Claude Code into it, and opens a pull request. The module's rules are unusually strict because it shells out to `git`, `gh` and `claude` against real repositories. ## The pipeline, in order `GitHubRepoAdopter.defaultSteps(options)` assembles: 1. `ToolchainStep` — the pipeline's own tools: `git`, `claude`, `gh` (and `gh` is logged in). Fails before any expensive work. A dry run is checked with `ToolchainStep.forDryRun()` — `git` and `claude` only, since `gh` is used by the pull request the run leaves out. 2. `CloneStep` — clones into the workspace, then rewrites the checkout's `origin` to `checkoutUrl()`, the same URL without its credentials, so the token git wrote into `.git/config` does not outlive the run. 3. `BuildToolchainStep` — the *cloned project's* build tool, checked as soon as the clone reveals which one it is. 4. `BranchStep` — feature branch (`claude/adopt-claude-code` by default). The default branch is never written to. 5. `TrustStep` — marks the checkout trusted for Claude Code. 6. `ClaudeInitStep` → `ClaudeMdConformanceStep` → `CommitStep` — generate `CLAUDE.md`, conform it (plus a companion `AGENTS.md`) as far as the guard about to be wired in demands — `BuildSystem.requiredClaudeMdSections()`, so only the Maven path adds the format rule's Java/Maven headings — commit. 7. `EnforcerStep` → `CommitStep` — w