Instructions for an AI
to install or upgrade safely.

The AI must confirm the current folder first

1. Show the absolute path of the current working folder.
2. Ask: “Is this the folder where you want Agent Handoff Kit installed or upgraded?”
3. If the user cannot confirm, stop with zero writes. Do not run init, upgrade, or doctor.
4. Only after confirmation, inspect whether the folder already has AGENTS.md, CLAUDE.md, GEMINI.md, START_NEXT_SESSION_PROMPT.txt, or dev/.

Decide how to install

Verify after completion

This version also strengthens everyday rule-writing boundaries. When the user later asks to add a durable rule, follow Governance Write Boundary in the installed dev/rules/agent-governance.md to find an existing writable home, protect official prose, and verify the reading route. This does not automatically reconcile older local rules already mixed into official prose; handle those conflicts through the authorized merge flow above.

Report the migration result separately from whole-project health. A changed version number alone is not completion evidence. Existing handoff content is preserved. At the next real closeout, the AI should use the updated rules to reconcile the overall outcome, subtask, resume point, and source-reading gaps, rather than inventing project state during the upgrade.

1. Read back the same operation's root, CLI version, complete terminal outcome, and health result. Reuse that operation's doctor result without another run only when the process exits successfully, installation is complete or the upgrade is committed (or confirmed unnecessary), no transaction remains unresolved, health explicitly passes, and no relevant files have changed or become uncertain afterwards. Preserve all warnings. A version number, a success message somewhere in the output, or an old conversation record is insufficient.
2. Do not reuse an earlier pass after failure, interruption, incomplete output, or later relevant file changes. If an upgrade transaction is unresolved, first follow the CLI recovery guidance using upgrade --yes --root ., then verify the complete terminal outcome; do not delete the lock or substitute a standalone doctor for recovery. Run the command below when no transaction is unresolved but valid health evidence is still missing, or when the user separately requests a check.

The same-operation result proves that local health check, not a fresh lookup of npm's latest version. A latest-version claim still requires npm registry readback and comparison with the actual CLI and installed versions; a successful preview does not replace completed installation or upgrade. This rule does not remove checks separately required by formal closeout or independent acceptance.

3. If doctor passes, read AGENTS.md, then follow the Start Agent Handoff startup flow to connect this folder.
4. If doctor fails, stop and explain the failed items. Do not reinstall over the project.
5. If doctor only reports that the convenience copy START_NEXT_SESSION_PROMPT.txt is behind, explain that it will be regenerated at formal closeout; do not reinstall because of this.

AI response format

This section is the checklist for the completion-report contract at the top of the page. After acting, the AI must not say only “completed” or paste only terminal output. It must explain the result and next step to the user in short, plain language.

• ✅ Result: installation completed, upgrade completed, or stopped because of a conflict.
• 📁 Current folder: show the confirmed absolute path.
• 🩺 Health check: say whether doctor passed, failed, or only noted that the convenience copy is behind.
• ⚠️ The next step is not a terminal command: Start Agent Handoff / “開工” must be entered in an AI conversation that can read and write this folder.
• 🚀 Next step: if the AI is already in this folder, ask the user to enter Start Agent Handoff or “開工”; only if the AI has not yet been pointed at the folder, give the path-bearing startup sentence.