Installing a SEED

Reference implementation of SEED installation. The install procedure lives in SEED.md; this skill is the call site.

Two contracts govern every install run. Read both before starting:

1. Display gate — every repo-supplied shell block is shown in full before it runs (agent-run blocks also announced in one line). No per-block confirmation. See §Display gate.
2. Output: install-report.json — on completion the skill writes a minimal, flat seven-field JSON at <repo-root>/install-report.json — {success, duration_seconds, platform, os_version, hardware, agent, model} and nothing else. On user consent the feedback dispatch uploads it verbatim — plus a separate sanitized clone_url field alongside it, for attribution (the report file itself stays seven fields). See §Install report.

Do not start the install procedure without committing to both. The display gate without the report is a black-box install; the report without the gate violates trust. They run together.

Display gate

Every shell block under ## Dependencies and every shell prompted by ## Verification MUST be displayed in full before execution. After displaying, the agent prints a one-line summary (10–20 words: what runs and why) and executes immediately. No yes/no prompt, no "approve all", no batching question. The user gave consent once at the install entry point; per-block prompts are redundant friction. The one exception: blocks routed to the prepare-script (§Preflight step 5) get the same full display inside the bundle but run as the operator, and are never re-executed in the dependency walk.

The skill's own pre-SEED commands (clone, cd) follow the same pattern: display, announce in one line, run.

Before §Preflight, the skill asks no questions — clone mode included. In clone mode it resolves the default install location — ${SEED_HOME:-$HOME/seeds}/<repo-name> — then announces the target and proceeds (tier-1: display + announce, no confirmation), exactly as it treats every other pre-SEED command; the operator overrides the parent dir via $SEED_HOME or interrupts (Ctrl-C) to stop (local-path and CWD installs likewise proceed without a prompt). Preflight then collects non-secret inputs through the question interface up front and hands the secret ones (plus interactive logins / sudo) to the user-run prepare-script (see §Preflight); those two are the operator interactions, and after them the ## Dependencies walk and ## Verification run without further questions.