wdi-method 0.4.5 → 0.5.0

package/kit/assets/bmad-custom/bmad-correct-course.toml

@@ -1,27 +1,28 @@
-# Kelas B — tidak ada knob path sama sekali.
+# Class B — no path knob at all.
 #
-# customize.toml bawaan bmad-correct-course hanya membuka activation_steps, persistent_facts, dan
-# on_complete. Tidak ada *_output_path, jadi proposalnya tetap mendarat di
-# _bmad-output/planning-artifacts/sprint-change-proposal-{date}.md dan MUST didaratkan ulang oleh
-# wdi-decision sebagai `DEC-` bertipe course-correction. Kode `SCP-` dan folder
-# .control/supplements/ SUDAH DICABUT — koreksi arah adalah keputusan, dan tidak ada kode kedua yang
-# menamai hal yang sama.
+# bmad-correct-course's own default customize.toml only opens activation_steps, persistent_facts,
+# and on_complete. There is no *_output_path, so its proposal still lands at
+# _bmad-output/planning-artifacts/sprint-change-proposal-{date}.md and MUST be landed again by
+# wdi-decision as a `DEC-` of type course-correction. The `SCP-` code and the
+# .control/supplements/ folder have ALREADY BEEN RETIRED — a course correction is a decision, and
+# there is no second code naming the same thing.
 #
-# Bahaya utamanya bukan path, melainkan kebiasaan skill ini menyunting langsung: default-nya
-# "direct updates to epics, stories, or PRD sections". Di repo ini itu MUST NOT terjadi — perubahan
-# dokumen lewat wdi-decision intent `apply`, isi wave lewat wdi-build. Karena itu larangannya
-# dipasang sebagai persistent_facts, yang dipegang sejak aktivasi, bukan sebagai poles di akhir.
+# The main danger is not the path but this skill's habit of editing directly: its default is
+# "direct updates to epics, stories, or PRD sections". In this repo that MUST NOT happen —
+# document changes go through wdi-decision intent `apply`, and wave content through wdi-build.
+# That is why the prohibition is installed as a persistent fact, held from activation, rather than
+# as end-of-run polish.
 
 [workflow]
 
 persistent_facts = [
-  "file:{project-root}/.constitution/document/delivery-flow-guide.md",
-  "file:{project-root}/.constitution/document/corpus-guide.md",
-  "Skill ini MUST NOT menulis atau menyunting apa pun di {project-root}/.what/ maupun {project-root}/.how/. Keluarannya adalah proposal; perubahan dokumen dikerjakan wdi-decision intent `apply` setelah `DEC-`-nya accepted, dan isi wave oleh wdi-build.",
-  "epics.md dan sprint-status.yaml TIDAK dipakai di repo ini — kita menjalankan stories route. Keduanya MUST NOT dibaca sebagai sumber, dan MUST NOT dibuat.",
-  "Pemindaian impak MUST mencakup .what/_prd/, .what/<pc>/, .how/_platform/, .how/<pc>/, SPEC.md, .control/registry/waves.yaml, dan berkas story. .what/<pc>/ tidak dikenal skill ini sama sekali dan tanpa ini akan basi diam-diam.",
-  "Setiap perubahan rencana yang mahal dibalik MUST menjadi `DEC-` lewat wdi-decision, bukan paragraf di dalam proposal. Koreksi arah sendiri adalah satu `DEC-` bertipe course-correction.",
-  "Sebuah koreksi yang membatalkan lebih dari 30% story sebuah wave MUST NOT ditangani sebagai tambalan. Katakan begitu, dan biarkan wave-nya dipotong ulang lewat wdi-build.",
+  "file:{project-root}/.constitution/method/document/delivery-flow-guide.md",
+  "file:{project-root}/.constitution/method/document/corpus-guide.md",
+  "This skill MUST NOT write or edit anything in {project-root}/.what/ or {project-root}/.how/. Its output is a proposal; document changes are made by wdi-decision intent `apply` once the `DEC-` is accepted, and wave content by wdi-build.",
+  "epics.md and sprint-status.yaml are NOT used in this repo — we run the stories route. Neither MUST be read as a source, and neither MUST be created.",
+  "The impact scan MUST cover .what/_prd/, .what/<pc>/, .how/_platform/, .how/<pc>/, SPEC.md, .control/registry/waves.yaml, and the story files. .what/<pc>/ is unknown to this skill entirely, and without this it goes stale silently.",
+  "Every plan change that is expensive to reverse MUST become a `DEC-` through wdi-decision, not a paragraph inside the proposal. A course correction is itself one `DEC-` of type course-correction.",
+  "A correction that voids more than 30% of a wave's stories MUST NOT be handled as a patch. Say so, and let the wave be re-cut through wdi-build.",
 ]
 
-on_complete = "Serahkan pendaratan ke wdi-decision: seluruh proposal jadi satu `DEC-` bertipe course-correction, dan folder run-nya MUST NOT dihapus. MUST NOT menempatkan sendiri, MUST NOT menyunting .what/ atau .how/."
+on_complete = "Hand the landing to wdi-decision: the whole proposal becomes one `DEC-` of type course-correction, and its run folder MUST NOT be deleted. MUST NOT land itself, MUST NOT edit .what/ or .how/."

package/kit/assets/bmad-custom/bmad-deep-recon.toml

@@ -1,11 +1,12 @@
-# Skill ini dikirim dengan `persistent_facts = []`, jadi tidak seperti 41 skill lain ia tidak
-# memungut konteks proyek sendiri. Berkas ini menutup celah itu; tanpanya riset menjelang G1 berjalan
-# tanpa kosakata dan aturan repo, dan hasilnya memakai istilah yang tidak ada di Glossary.
-
-[workflow]
-
-persistent_facts = [
-  "file:{project-root}/.control/product-glossary.md",
-  "Laporan riset mendarat di _bmad-output/ dan tinggal di sana selamanya. Ia MUST NOT dipromosikan ke .what/ dan MUST NOT dilebur ke brief maupun PRD; `DEC-` dan PRD merujuknya lewat path. Folder run-nya MUST NOT dihapus — intent Update membacanya kembali sebagai original inputs.",
-  "Istilah domain MUST memakai entri Glossary apa adanya. Istilah baru yang muncul dari riset MUST diusulkan sebagai entri Glossary, bukan dipakai diam-diam.",
-]
+# This skill ships with `persistent_facts = []`, so unlike the other 41 skills it picks up no
+# project context of its own. This file closes that gap; without it, research ahead of G1 runs
+# with no vocabulary and no repo rules, and its output uses terms that don't exist in the
+# Glossary.
+
+[workflow]
+
+persistent_facts = [
+  "file:{project-root}/.control/product-glossary.md",
+  "A research report lands in _bmad-output/ and stays there permanently. It MUST NOT be promoted into .what/ and MUST NOT be folded into the brief or a PRD; a `DEC-` or PRD references it by path instead. Its run folder MUST NOT be deleted — intent Update reads it back as original inputs.",
+  "A domain term MUST use the Glossary entry as written. A new term surfacing from research MUST be proposed as a Glossary entry, not used silently.",
+]

package/kit/assets/bmad-custom/bmad-prd.toml

@@ -1,42 +1,42 @@
-# Kelas A — menulis langsung ke korpus.
-#
-# Satu PRD per **inisiatif / area fungsi**, bukan per rilis. Ia living document:
-# perubahan perilaku masuk lewat intent Update ke PRD yang sama, bukan PRD baru.
-# Rilis dibawa registry lewat target_release, bukan oleh nama folder.
-#
-# run_folder_pattern MUST diisi slug inisiatif dan MUST NOT memakai {date}.
-# Saat inisiatif baru dibuka, DUA baris MUST diubah bersamaan:
-#   1. run_folder_pattern             -> slug inisiatif berikutnya
-#   2. --path .../prd-<slug>.md       -> memlog inisiatif berikutnya
-# Mengubah salah satu saja menghasilkan PRD baru yang menempel pada memlog lama.
-#
-# Nilai bawaan di bawah sengaja tidak bisa dipakai apa adanya — ia MUST diganti
-# di langkah 4 runbook. PRD yang mendarat di folder bernama ISI-slug-inisiatif
-# adalah tanda langkah itu terlewat.
-
-[workflow]
-
-prd_template       = "{project-root}/.constitution/document/templates/prd.md"
-prd_output_path    = "{project-root}/.what/_prd"
-run_folder_pattern = "ISI-slug-inisiatif"
-
-doc_standards = ["file:{project-root}/.constitution/document/prd-guide.md"]
-
-# Fakta di bawah sengaja mengulang sebagian prd-guide.md. Sebabnya waktu: doc_standards baru
-# menyala di langkah Polish, sedangkan deteksi intent Create-versus-Update terjadi di aktivasi.
-# Yang otoritatif tetap prd-guide.md; kalau keduanya berselisih, guide yang menang dan baris di
-# sini MUST diperbaiki.
-persistent_facts = [
-  "file:{project-root}/.control/registry/requirements.yaml",
-  "file:{project-root}/.constitution/document/prd-guide.md",
-
-  "FR-N, NFR-N, UJ-N, dan CAP-N MUST dialokasikan dari requirements.yaml dan MUST NOT dimulai ulang dari 1. PRD inisiatif berikutnya melanjutkan deret PRD sebelumnya — deretnya global, satu produk satu deret.",
-
-  "PRD ini living document. Perubahan perilaku, penambahan fitur yang erat kaitannya, maupun koreksi janji MUST masuk lewat intent Update ke PRD yang sama. PRD baru MUST NOT dibuat hanya karena rilisnya berganti; ia dibuat hanya saat area fungsinya benar-benar berbeda dan tidak enak dibaca kalau digabung.",
-
-  "Tiap run intent Update MUST menambah tepat satu baris di tabel Revision History PRD: tanggal, apa yang berubah dalam bahasa pembaca luar, dan sebabnya. Tabel itu untuk pembaca; memlog untuk audit. Keduanya MUST NOT saling menggantikan.",
-
-  "Rilis MUST NOT dinyatakan lewat nama folder PRD maupun judulnya. Ia dibawa field target_release di requirements.yaml dan waves.yaml. Menyebut nomor rilis di dalam prosa PRD MAY dilakukan sebagai konteks, tetapi yang mengikat tetap registry.",
-
-  "Seluruh panggilan memlog.py — init, append, set, dan pembacaan saat resume atau intent Update — MUST memakai --path {project-root}/.control/memlog/prd-ISI-slug-inisiatif.md. Slug-nya MUST sama dengan run_folder_pattern di atas, dan kedua baris MUST diubah bersamaan saat inisiatif berganti. --workspace MUST NOT dipakai.",
-]
+# Class A — writes straight into the corpus.
+#
+# One PRD per **initiative / functional area**, not per release. It is a living document:
+# a behaviour change goes through intent Update on the same PRD, never a new one.
+# A release is carried by the registry through target_release, not by the folder name.
+#
+# run_folder_pattern MUST be filled with the initiative slug and MUST NOT use {date}.
+# When a new initiative opens, TWO lines MUST change together:
+#   1. run_folder_pattern             -> the next initiative's slug
+#   2. --path .../prd-<slug>.md       -> the next initiative's memlog
+# Changing only one produces a new PRD stuck to the old memlog.
+#
+# The default value below is deliberately unusable as-is — it MUST be replaced at runbook
+# step 4. A PRD landing in a folder literally named FILL-initiative-slug is the sign that step
+# was skipped.
+
+[workflow]
+
+prd_template       = "{project-root}/.constitution/method/document/templates/prd.md"
+prd_output_path    = "{project-root}/.what/_prd"
+run_folder_pattern = "FILL-initiative-slug"
+
+doc_standards = ["file:{project-root}/.constitution/method/document/prd-guide.md"]
+
+# The facts below deliberately repeat part of prd-guide.md. The reason is timing: doc_standards
+# only activates at the Polish step, while Create-versus-Update intent detection happens at
+# activation. prd-guide.md remains authoritative; where the two disagree, the guide wins and the
+# line here MUST be fixed.
+persistent_facts = [
+  "file:{project-root}/.control/registry/requirements.yaml",
+  "file:{project-root}/.constitution/method/document/prd-guide.md",
+
+  "FR-N, NFR-N, UJ-N, and CAP-N MUST be allocated from requirements.yaml and MUST NOT restart from 1. The next initiative's PRD continues the previous PRD's sequence — the sequence is global, one product, one sequence.",
+
+  "This PRD is a living document. A behaviour change, a closely related feature addition, or a promise correction MUST go through intent Update on the same PRD. A new PRD MUST NOT be created just because the release changed; it is created only when the functional area is genuinely different and reads badly if merged.",
+
+  "Every intent Update run MUST add exactly one row to the PRD's Revision History table: the date, what changed in language an outside reader understands, and why. That table is for the reader; the memlog is for the audit. Neither MUST substitute for the other.",
+
+  "A release MUST NOT be stated through the PRD's folder name or its title. It is carried by the target_release field in requirements.yaml and waves.yaml. Naming a release number inside the PRD's prose MAY be done as context, but the registry remains what binds.",
+
+  "Every memlog.py call — init, append, set, and the read on resume or intent Update — MUST use --path {project-root}/.control/memlog/prd-FILL-initiative-slug.md. The slug MUST match run_folder_pattern above, and both lines MUST change together when the initiative changes. --workspace MUST NOT be used.",
+]

package/kit/assets/bmad-custom/bmad-product-brief.toml

@@ -1,34 +1,34 @@
-# Kelas A — menulis langsung ke korpus.
-# Singleton: satu produk, satu brief, lintas rilis. Produk kedua MUST dapat repo sendiri.
+# Class A — writes straight into the corpus.
+# Singleton: one product, one brief, across releases. A second product MUST get its own repo.
 #
-# Dipanggil lewat `wdi-problem`, bukan langsung. Override di sini yang menentukan
-# ke mana artefaknya mendarat; skill wrapper yang memeriksa isinya.
+# Called through `wdi-problem`, never directly. The override here decides where the artifact
+# lands; the wrapper skill checks its content.
 
 [workflow]
 
-brief_template     = "{project-root}/.constitution/document/templates/brief.md"
+brief_template     = "{project-root}/.constitution/method/document/templates/brief.md"
 
-# run_folder_pattern MUST konstan — tanpa {project_name} dan tanpa {date}.
-# Itu yang memaksa singleton: tiap run jatuh ke folder yang sama, jadi run kedua
-# terdeteksi sebagai resume/update, bukan folder sebelah.
-# Hasilnya .what/_product-brief/brief.md dan .what/_product-brief/addendum.md;
-# kedua nama berkas itu di-hardcode di SKILL.md dan tidak bisa diatur.
+# run_folder_pattern MUST be constant — no {project_name}, no {date}.
+# That is what forces the singleton: every run lands in the same folder, so a second run is
+# detected as a resume/update, not a sibling folder.
+# The result is .what/_product-brief/brief.md and .what/_product-brief/addendum.md; both
+# filenames are hardcoded in SKILL.md and cannot be configured.
 brief_output_path  = "{project-root}/.what"
 run_folder_pattern = "_product-brief"
 
-# Append-only terhadap default `skill:bmad-review lenses=structure,prose`.
-doc_standards = ["file:{project-root}/.constitution/document/brief-guide.md"]
+# Append-only against the default `skill:bmad-review lenses=structure,prose`.
+doc_standards = ["file:{project-root}/.constitution/method/document/brief-guide.md"]
 
 persistent_facts = [
-  "Seluruh panggilan memlog.py — init, append, set, dan pembacaan saat resume atau intent Update — MUST memakai --path {project-root}/.control/memlog/brief.md. --workspace MUST NOT dipakai; ia akan menaruh .memlog.md di dalam .what/, dan tidak ada memlog yang boleh tinggal di korpus.",
+  "Every memlog.py call — init, append, set, and the read on resume or intent Update — MUST use --path {project-root}/.control/memlog/brief.md. --workspace MUST NOT be used; it would place a .memlog.md inside .what/, and no memlog is allowed to live in the corpus.",
 
-  "Template brief membuka dengan izin membuang section yang tidak layak. Izin itu MUST NOT diterapkan pada delapan section wajib: The Problem, Who This Serves, Goals, Success Criteria, Scope In, Scope Out, Constraints, Assumptions — beserta Prerequisites. Section template lain MAY dibuang.",
+  "The brief template opens with permission to drop a section that does not fit. That permission MUST NOT apply to the eight mandatory sections: The Problem, Who This Serves, Goals, Success Criteria, Scope In, Scope Out, Constraints, Assumptions — plus Prerequisites. Other template sections MAY be dropped.",
 
-  "Goals MUST bernomor BG-1, BG-2, dan seterusnya. MUST NOT bernomor G1, G2 — G1 sampai G5 adalah nama lima gate di metode ini, dan BG adalah mata rantai pertama rantai traceability BG -> CAP -> FR/NFR -> UC -> Story -> Test.",
+  "Goals MUST be numbered BG-1, BG-2, and so on. They MUST NOT be numbered G1, G2 — G1 through G5 are the names of this method's five gates, and BG is the first link in the BG -> CAP -> FR/NFR -> UC -> Story -> Test traceability chain.",
 
-  "Tabel Who This Serves MUST memuat tepat satu baris bertanda primary, dan MUST memuat seluruh stakeholder termasuk yang tidak pernah membuka produknya.",
+  "The Who This Serves table MUST carry exactly one row marked primary, and MUST cover every stakeholder including one who never opens the product.",
 
-  "Brief MUST NOT memuat daftar Product Component dan MUST NOT mengisi product_components maupun logical_components. Slicing lahir di EKOR G2 lewat wdi-init intent `component`, dibaca dari brief plus seluruh PRD.",
+  "The brief MUST NOT carry a Product Component list, and MUST NOT fill product_components or logical_components. The slicing is born at the TAIL of G2 through wdi-init intent `component`, read from the brief plus every PRD.",
 
-  "Keluaran riset, brainstorming, forge, dan PRFAQ MUST tetap di _bmad-output/. Ia MUST NOT dilebur ke dalam brief dan MUST NOT dipromosikan ke .what/; `DEC-` atau PRD merujuknya lewat path. Folder run itu MUST NOT dihapus — intent Update membacanya kembali sebagai original inputs.",
+  "Output from research, brainstorming, forge, and PRFAQ MUST stay in _bmad-output/. It MUST NOT be folded into the brief and MUST NOT be promoted into .what/; a `DEC-` or PRD references it by path. That run folder MUST NOT be deleted — intent Update reads it back as original inputs.",
 ]

package/kit/assets/bmad-custom/bmad-retrospective.toml

@@ -1,9 +1,9 @@
-# Berjalan di stories mode: membaca SPEC.md + stories.yaml + stories/<id>-*.md, bukan
-# sprint-status.yaml. Keluarannya RETROSPECTIVE.md di dalam folder spec — yang fana.
+# Runs in stories mode: reads SPEC.md + stories.yaml + stories/<id>-*.md, not
+# sprint-status.yaml. Its output is RETROSPECTIVE.md inside the spec folder — which is ephemeral.
 
 [workflow]
 
 persistent_facts = [
-  "Repo ini berjalan di stories mode. RETROSPECTIVE.md MUST diarsipkan jadi RTR-<wave> di .control/reports/ oleh wdi-build sebelum wave ditutup. Ia WAJIB pada wave `L` dan advisory pada `S` dan `M` — V19 diikatkan ke ukuran wave, bukan ke `mode`, dan melewatinya MUST dinyatakan alih-alih didiamkan.",
-  "Seluruh baris tabel distilasi di .constitution/document/bmad-guide.md MUST tuntas sebelum wave dinyatakan tertutup.",
+  "This repo runs in stories mode. RETROSPECTIVE.md MUST be archived as RTR-<wave> in .control/reports/ by wdi-build before the wave closes. It is REQUIRED on a wave `L` and advisory on `S` and `M` — V19 is tied to wave size, not to `mode`, and skipping it MUST be stated rather than left silent.",
+  "Every row of the distillation table in .constitution/method/document/bmad-guide.md MUST be complete before a wave is declared closed.",
 ]

package/kit/assets/bmad-custom/bmad-spec.toml

@@ -1,15 +1,16 @@
-# Kelas C — satu run per (wave x Product Component), habis setelah G5.
-#
-# Slug menentukan apakah spec fana atau hidup: slug yang sama mendarat di folder yang sama dan
-# mempertahankan capability ID. Slug per-PC saja akan membuat SPEC.md jadi dokumen hidup per PC —
-# saingan langsung SRS. Slug w<N>-<pc> menjaga spec tetap fana, dan CAP-N tetap terjaga karena
-# dialokasikan dari registry, bukan dari mekanisme internal BMad.
-
-[workflow]
-
-persistent_facts = [
-  "Slug spec MUST berbentuk w<N>-<pc>, satu run per pasangan wave x Product Component.",
-  "SPEC.md MUST NOT memuat apa pun yang tidak berasal dari SRS, SDD, atau PRD. Temuan baru MUST didaratkan ke korpus oleh skill pemilik lapisannya — tabel kepemilikan di .constitution/document/corpus-guide.md — sebelum wave ditutup, bukan dibiarkan tinggal di spec.",
-  "CAP-N MUST dialokasikan dari {project-root}/.control/registry/requirements.yaml.",
-  "file:{project-root}/.control/product-glossary.md",
-]
+# Class C — one run per (wave x Product Component), spent once G5 closes.
+#
+# The slug decides whether a spec is ephemeral or lives on: the same slug lands in the same
+# folder and keeps its capability ID. A slug per-PC alone would turn SPEC.md into a living
+# document per PC — a direct rival to the SRS. The slug w<N>-<pc> keeps the spec ephemeral, and
+# CAP-N stays sound because it is allocated from the registry, not from BMad's own internal
+# mechanism.
+
+[workflow]
+
+persistent_facts = [
+  "A spec slug MUST take the shape w<N>-<pc>, one run per (wave x Product Component) pair.",
+  "SPEC.md MUST NOT carry anything that did not come from the SRS, SDD, or PRD. A new finding MUST be landed in the corpus by the skill that owns that layer — the ownership table in .constitution/method/document/corpus-guide.md — before the wave closes, never left sitting in the spec.",
+  "CAP-N MUST be allocated from {project-root}/.control/registry/requirements.yaml.",
+  "file:{project-root}/.control/product-glossary.md",
+]

package/kit/assets/bmad-custom/bmad-ux.toml

@@ -1,19 +1,19 @@
-# Kelas B — path bisa dikonfigurasi, granularitas per-PC tidak.
-#
-# bmad-ux hanya mengenal {project_name} dan {date}, tidak ada {slug}, jadi ia tidak bisa mendarat
-# sendiri ke .how/<pc>/. Landing zone-nya dibuat NETRAL di _bmad-output/ karena keluarannya
-# membelah dua lapisan: DESIGN.md milik .how/, EXPERIENCE.md milik .what/. Mendarat lebih dulu di
-# salah satunya adalah pelanggaran lapisan yang hidup selama satu run.
-
-[workflow]
-
-ux_output_path     = "{project-root}/_bmad-output/ux"
-run_folder_pattern = "ux"
-
-doc_standards = ["file:{project-root}/.constitution/document/ux-guide.md"]
-
-persistent_facts = [
-  "Seluruh panggilan memlog.py MUST memakai --path {project-root}/.control/memlog/ux.md. --workspace MUST NOT dipakai.",
-]
-
-on_complete = "Serahkan pendaratan ke wdi-ux: DESIGN.md ke .how/<pc>/01-ux/, token dan komponen dasar ke .how/_platform/design-system.md, EXPERIENCE.md ke .what/<pc>/04-usecases/, tiap layar didaftarkan sebagai LC ui-screen di components.yaml. MUST NOT menempatkan sendiri."
+# Class B — the path is configurable, per-PC granularity is not.
+#
+# bmad-ux only knows {project_name} and {date}, no {slug}, so it cannot land directly into
+# .how/<pc>/. Its landing zone is made NEUTRAL in _bmad-output/ because its output splits across
+# two layers: DESIGN.md belongs to .how/, EXPERIENCE.md belongs to .what/. Landing in either one
+# first would be a layer violation that lives for the length of one run.
+
+[workflow]
+
+ux_output_path     = "{project-root}/_bmad-output/ux"
+run_folder_pattern = "ux"
+
+doc_standards = ["file:{project-root}/.constitution/method/document/ux-guide.md"]
+
+persistent_facts = [
+  "Every memlog.py call MUST use --path {project-root}/.control/memlog/ux.md. --workspace MUST NOT be used.",
+]
+
+on_complete = "Hand the landing to wdi-ux: DESIGN.md to .how/<pc>/01-ux/, tokens and base components to .how/_platform/design-system.md, EXPERIENCE.md to .what/<pc>/04-usecases/, every screen registered as an LC ui-screen in components.yaml. MUST NOT land itself."

package/kit/assets/bmad-custom/config.toml

@@ -1,6 +1,6 @@
-# Dipasang di langkah 1 runbook — MUST lebih dulu dari yang lain.
+# Installed at runbook step 1 — MUST come before anything else.
 #
-# bmad-help dan bmad-correct-course membaca {project_knowledge}. Selama ia menunjuk docs/,
-# keduanya membaca folder yang sudah dibubarkan.
+# bmad-help and bmad-correct-course read {project_knowledge}. As long as it points at docs/,
+# both read a folder that has already been dissolved.
 
 project_knowledge = "{project-root}/.control"

package/kit/skills/wdi-blueprint/SKILL.md

@@ -32,7 +32,7 @@ of that is `wdi-component` at G4. You MUST NOT write a promise; when the bluepri
 | `.control/product-glossary.md` | Terms already fixed |
 | `.control/decisions/` | `accepted` and `applied` decisions an `AD-N` usually sits behind |
 | `src/` · `web/` | What actually runs, when this is not a new project |
-| `.constitution/document/srs-guide.md` · `architecture-guide.md` | The rules the result is checked against |
+| `.constitution/method/document/srs-guide.md` · `architecture-guide.md` | The rules the result is checked against |
 
 ## Step 1 — Position
 
@@ -65,7 +65,7 @@ whose nouns nobody defined.
 the count passes a third of a component's use cases, derive it again — `delivery-flow-guide.md` owns the rule
 and it MUST NOT be negotiated.
 
-**A method term MUST NOT be written into `.constitution/method-glossary.md`.** A product term binds one
+**A method term MUST NOT be written into `.constitution/method/method-glossary.md`.** A product term binds one
 project; a method term binds every project the method is installed in. Raise it as a proposal, state where it
 appeared and why the existing vocabulary does not cover it, and hand it to the owner.
 
@@ -152,7 +152,7 @@ copy inside any SDD.
 | State | How each is born |
 |---|---|
 | No code yet | Written as a **plan** — the tables, endpoints, and screens intended. Nothing can be derived, because there is no source |
-| Code exists | **Derived first** by `.constitution/scripts/inventory.py` — migrations for tables, route registration for endpoints, pages for screens — then compared with the plan. The difference is a **finding**, not hand work |
+| Code exists | **Derived first** by `.constitution/method/scripts/inventory.py` — migrations for tables, route registration for endpoints, pages for screens — then compared with the plan. The difference is a **finding**, not hand work |
 
 An inventory MUST NOT be assembled from a README or from route names that look plausible. Numbers are stable:
 a new row takes the next number, never a renumber.