@mutmutco/kilo-plugin 3.98.0 → 3.100.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 +1 -1
- package/skills/bootstrap/SKILL.md +21 -0
package/package.json
CHANGED
|
@@ -36,6 +36,27 @@ Priority is a **board field**, never a label (#1454 retired the four `priority:*
|
|
|
36
36
|
checks they are gone). The per-step instructions below
|
|
37
37
|
are the manual path; `bootstrap apply <repo> [--execute]` automates them from this manifest.
|
|
38
38
|
|
|
39
|
+
**`bootstrap apply` is a single-repo tool** — fresh bootstrap/onboarding, or refreshing one repo's own
|
|
40
|
+
drifted seed. It is **never** the fleet-wide fan-out for an `org`-owned seed edit: that write path is
|
|
41
|
+
propagation from a Hub merge (#4233), and the seeded `agent-pr.yml` itself now fails the merge gate on
|
|
42
|
+
any repo that receives a hand-edit to an org-owned target path outside a propagation/bootstrap-delivery
|
|
43
|
+
branch (#4241). Running `apply --execute` against every registry repo by hand to fan out a Hub edit is
|
|
44
|
+
exactly the copy-per-repo pattern this rule exists to end — see Hub#4234.
|
|
45
|
+
|
|
46
|
+
**Rollback is per-repo, never a second fleet overwrite (#4240).** When a propagated `org`-owned seed
|
|
47
|
+
breaks a repo, the recovery is `mmi-cli bootstrap rollback <repo> --target <t> [--execute]` — it resolves
|
|
48
|
+
the ONE merge commit that repo's `bootstrap propagate` (#4238) run actually landed (live from the repo's
|
|
49
|
+
`seed-propagate-<slug>` merged-PR history, or replayed from a persisted propagate `--json` report via
|
|
50
|
+
`--record`) and opens an ordinary revert PR of it, through that repo's own gate, on a `seed-rollback-<slug>`
|
|
51
|
+
branch. It refuses — never guesses a commit — when no clean, single-file propagation record resolves for
|
|
52
|
+
that repo+target. **Explicitly forbidden as a rollback path: a fleet-wide `bootstrap apply --execute` of
|
|
53
|
+
"the old bytes"** — that is the second blind fleet overwrite #4233 rules out, and it races the propagation
|
|
54
|
+
lane. **MMI-Hub stays the source of truth during a rollback**: a per-repo revert is the emergency stop, not
|
|
55
|
+
the fix — closure is the Hub reverting (or fixing forward) the bad seed commit on `development`, after
|
|
56
|
+
which reverted repos match the Hub again and the drift alarm closes itself. A per-repo revert with no
|
|
57
|
+
Hub-side follow-up re-alarms as drift within a week, deliberately, so an emergency divergence can never
|
|
58
|
+
silently become permanent.
|
|
59
|
+
|
|
39
60
|
**Release gap — a new topology value must reach TWO surfaces, and a local dev build only fixes one (#2928).**
|
|
40
61
|
A new `--project-type`, `--deploy-model`, or `--release-track` lands on `development` but is not live until a
|
|
41
62
|
release train ships it — in **both** of these places:
|