undo-bootstrap

Wraps bin/undo-bootstrap.sh. Read this end-to-end before invoking; the refusal modes carry real meaning.

1. Locate the BootRecord

Boot records live under <repo>/memory/.nyann/bootstraps/<ISO-ts>/. Each contains a manifest.json (the BootRecord) and a pre-state/ directory with original file bytes.

By default the script picks the newest manifest. When the repo has multiple records (typical: one bootstrap + one or more retrofits), list them and ask which to undo:

ls -1t memory/.nyann/bootstraps/*/manifest.json | head -10

Show the list with created_at, source, and a one-line summary (extract via jq -r '.created_at + " " + .source + " (" + (.actions | length | tostring) + " actions)"'). Pass the chosen one via --manifest <path>.

2. Always preview first

Run with --dry-run and surface the JSON to the user:

bin/undo-bootstrap.sh --target "$PWD" --dry-run

Walk the four arrays in the result: restored, deleted, branches_dropped, defaults_renamed_back. Read skipped[] carefully and explain each entry — they're the load-bearing communication.

For ambiguous cases (skipped entries with overrides available), use `AskUserQuestion`:

{
  "questions": [
    {
      "question": "Some files were modified after bootstrap finished. Override and overwrite local edits?",
      "header": "Force",
      "multiSelect": false,
      "options": [
        { "label": "No (Recommended)", "description": "Skip those files — your edits are safe; you can manually restore later." },
        { "label": "Yes, --force", "description": "Overwrite local edits with the pre-bootstrap state. Edits are LOST." }
      ]
    }
  ]
}

3. Refusal semantics

Skipped entries (in the result JSON, not refusals):

4. Decide scope

Default --scope all reverses every category. Use narrower scopes when the operator wants surgical undo:

{
  "questions": [
    {
      "question": "Which parts of the bootstrap should be reversed?",
      "header": "Scope",
      "multiSelect": true,
      "options": [
        { "label": "All (Recommended)", "description": "Restore everything bootstrap touched." },
        { "label": "docs", "description": "docs/ and memory/ scaffolds, CLAUDE.md." },
        { "label": "hooks", "description": ".git/hooks/, .husky/, pre-commit, package.json mutations." },
        { "label": "gitignore", "description": ".gitignore merge." },
        { "label": "editorconfig", "description": ".editorconfig." },
        { "label": "github", "description": ".github/ workflows, templates, CODEOWNERS." },
        { "label": "branching", "description": "Branches created, default-branch renames." }
      ]
    }
  ]
}

5. Invoke

bin/undo-bootstrap.sh --target <cwd> \
  [--manifest <path>] \
  [--scope <csv>] \
  [--force] [--allow-rebase] [--allow-non-empty-branches] \
  [--dry-run] \
  --yes

Without --yes, the script returns status: "preview" and exits 0 without mutating — same idiom as bin/undo.sh.

6. Post-undo report

On success, walk the result JSON and tell the user:

• How many files were restored / deleted / branches dropped.
• Anything in skipped[] (with override hints).
• Whether the boot record was cleaned up (it is, when no

reversible-but-deferred skips remain) or kept (run again with --force / --allow-non-empty-branches to finish the job).

For seed-commit skips, suggest the manual command:

git update-ref -d refs/heads/<branch>   # only if you really want a fresh start

Don't run that automatically — it strands the working tree.

7. Hand-off

• "Now run bootstrap again with a different profile" → /nyann:bootstrap.
• "Undo just the docs part" → re-run with --scope docs (works even

after a previous full undo if the manifest was kept).

• "I want to keep the manifest as a record" → re-run with --keep-record.