Repo Setup — adopt the agentloop plugin in a repo

Run once per repo to go from "plugin installed" to "loop skills can actually run here". The supporting environment the sweep/review skills assume (a repo-profile, the coordination labels, a verify gate, a working toolchain + gh auth) is otherwise implicit — this makes it explicit and reproducible. All scripts live in <plugin_root>/bootstrap/ and are idempotent (the directory keeps its name: there it means "the scripts that bootstrap a repo", which is unambiguous — the skill was renamed because /agentloop:bootstrap alone did not say what it bootstrapped, and now pairs with /agentloop:fleet-setup).

This is hybrid by design. The split, and why it matters:

• Deterministic scripts lay down structure and auto-detect what can be mechanically probed (repo_slug, plugin_root, default_branch, package_manager, the fixed label set, the env assertions). They never guess values they can't ground in a file, and never mutate your system.
• You, the agent, do what needs judgement or side-effects: install missing tools, fill the profile fields that require reading the repo, write the real verification checks. Scripts hand you a stable skeleton; you supply the parts a script can't reliably infer.