| name | deploy-and-recover |
| description | Handle persistent install, flash, and recovery flows through forge. |
Intent
Use this skill only when the user explicitly wants a persistent install image, a hard, permanent, or persistent flash path, or JTAG recovery.
Inputs
- Operation:
install, flash, or recover, with explicit permanent or repair intent.
- Target and any needed
--jtag-url override.
Execution
- Do not enter this skill for a generic request like "run firmware", "deploy firmware", "flash firmware", plain "run ", plain "deploy ", or plain "flash " unless the user clearly means hard, permanent, or persistent flash.
- If the user explicitly wants persistent deployment on
u64, prefer ./forge install u64 because that is the persistent u64 path exposed by the current root command surface.
- If the user explicitly wants hard, permanent, or persistent flash on
c64u, or if u64 is unavailable and the user explicitly wants the permanent path, use ./forge flash c64u.ue2.
- Use
./forge recover <target> for repair, with --jtag-url when needed.
Validation
- Confirm the target, transfer path, and whether the action was transient, persistent, or recovery.
- For
u64, make it explicit when persistent intent mapped to install rather than a direct flash verb.
- For
recover, report that the flow delegates to the upstream 1541ultimate recovery tooling.
Safety
- Treat
flash as the highest-risk path and keep that explicit.
- Do not substitute
flash for run or install.
- Do not infer hard-flash intent from ambiguous words like "run", "deploy", "flash firmware", plain "run ", plain "deploy ", or plain "flash ".