haiku-method 2.3.0 → 3.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "haiku-method",
3
- "version": "2.3.0",
3
+ "version": "3.0.0",
4
4
  "description": "H·AI·K·U methodology — universal lifecycle orchestration with hat-based workflows, completion criteria, and automatic context preservation.",
5
5
  "homepage": "https://haikumethod.ai",
6
6
  "repository": {
@@ -7,6 +7,23 @@ description: Migrate legacy AI-DLC intents to H·AI·K·U format
7
7
 
8
8
  Convert legacy `.ai-dlc/` intents to `.haiku/` format.
9
9
 
10
- 1. Scan `.ai-dlc/` for intents. If a specific slug is given, migrate that one. Otherwise list and ask.
11
- 2. Run `haiku migrate <slug>` to perform the migration.
12
- 3. After migration, suggest `/haiku:pickup <slug>` to continue execution.
10
+ **Never apply a migration without showing a dry-run first.** Bare `haiku migrate` is rejected by the binary, but the rule still holds when you pass `--all` or a specific slug: dry-run, get the user's OK, then apply.
11
+
12
+ ## Steps
13
+
14
+ 1. List candidates: `ls .ai-dlc/`. If the user named a slug, use that. Otherwise show the list and ask which one(s).
15
+ 2. **Dry-run**: `haiku migrate <slug>` (dry-run is the default). Show the user the output — what would be written, where, how many files.
16
+ 3. **Get explicit approval** from the user before applying. Don't infer consent from prior context.
17
+ 4. **Apply**: `haiku migrate <slug> --apply`. One slug at a time unless the user explicitly approved `--all`.
18
+ 5. After migration, suggest `/haiku:pickup <slug>` to continue execution.
19
+
20
+ ## Flags
21
+
22
+ - `--apply` — actually write. Default is dry-run.
23
+ - `--all` — migrate every intent in `.ai-dlc/`. Pair with `--apply` to commit.
24
+ - `--force` — re-migrate intents that already exist under `.haiku/`. Use sparingly.
25
+ - `--allow-dirty` — skip the git-clean precheck. Don't pass this without user approval; a dirty tree means the migration output gets tangled with unrelated in-progress work.
26
+
27
+ ## Why these rules exist
28
+
29
+ Bare `haiku migrate --apply` rewrites every intent in `.ai-dlc/` at once. In a monorepo, one such commit shows up in every open MR. The dry-run-then-confirm flow exists so this can't happen by accident.