azhou-setuplisted

# Azhou Setup **🦊 阿舟 · Azhou Setup** > 🧰 先看计划，再按同一计划执行。 Use the repository Foundation CLI as the mutation authority. Always inspect first. Never reimplement copy, link, receipt, lock, rollback, or deletion logic in the prompt. ## Brand protocol Emit this exact display event once, at the start of every run, with the selected mode and resolved checkout scope: ```text 🦊 阿舟 · Azhou Setup 启动｜mode=<setup|repair|migrate|uninstall>｜scope=<checkout> ``` Use `✅ 验证通过` only after the exact reviewed plan is applied when mutation was requested, or after a declared dry-run is read back. Use `❌ 验证失败` for a plan, apply, rollback, or evidence failure and `🔒 阿舟暂停这一项` for missing target or authorization. Emoji is display-only; keep JSON keys, schema values, digests, paths, commands, test names, managed receipts, and raw evidence emoji-free. A host without Unicode may remove the leading emoji while preserving the fixed text, `｜` separators, fields, and values. ## Workflow 1. Resolve the checkout from a user-supplied path, or from the current Git root only when both `scripts/azhou_hub.py` and `docs/skill-standard.md` exist. Do not scan unrelated directories or infer a harness home. 2. Require an explicit absolute `--target`. For setup, require the intended canonical skill and choose `link` or `copy`; do not choose a harness root for the user. 3. Run the selected command without `--apply` and present its JSON plan: - `python scripts/azhou_hub.py setup --skill <name> --target </absol