gm-kilo 2.0.900 → 2.0.902

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.
@@ -1,6 +1,6 @@
1
- 9273a89cc377ba2280dbf3cdd5e4981f952cde735afa0cd873385bcdc04bfdb5 plugkit-win32-x64.exe
2
- 54836274e93a759706963ca3fd12d7e28a3e6a6b64fcfcd0cc07ac0e857722f5 plugkit-win32-arm64.exe
3
- 4521af911ebd26005b167a4b60d4f17789f8b696694bc6e4a8f106ba86fc3386 plugkit-darwin-x64
4
- 7cdb818ba897983fc031bd06f6995e68520d40e02c01af8c76713a3d61fe6023 plugkit-darwin-arm64
5
- 8c6478e7f2ae34a284c665fb80d169830d713a60e42b966d50107888b0b7fa20 plugkit-linux-x64
6
- 81b2fff11fda9f4e7ccc8b55aba951f2708f81200438c5b3a7678fa49ebcdc53 plugkit-linux-arm64
1
+ 3830b5e61e70afa16607df943117568ec1a48139e79d41ed287cb7cb27decb63 plugkit-win32-x64.exe
2
+ 016107e7e474fb3b908258b177772041a0c1a55acd51127aac4a97b48d03d48b plugkit-win32-arm64.exe
3
+ dcf527927f474e988f3d11c376844ee5008a010e5fdc36209f11aad2a00f8695 plugkit-darwin-x64
4
+ 694468e65e7d3fdb7156be078657fcb9158f4b513eb7f4077e6cafd69c8111aa plugkit-darwin-arm64
5
+ bdfab97a2f6d9546883625b45203931ba7479f977d5b574963aa0fe87cc8157a plugkit-linux-x64
6
+ a649a1650c756258489d58db338c863995b4b7728458ea9e3a196abbea965de5 plugkit-linux-arm64
@@ -1 +1 @@
1
- 0.1.298
1
+ 0.1.299
package/bin/rtk.sha256 CHANGED
@@ -1,5 +1,5 @@
1
- eee29adeb0001f4388b781ad72d8f47f2961c4a731cefd53470d5f73d1e2e0d2 rtk-win32-x64.exe
2
- 4ed505b9a2c35194b66b362e7b2fef8322c71f16c41462f8ef7ac3b0e23509b5 rtk-win32-arm64.exe
1
+ e85126aee9bb1de54eeb80eea1fff9bc7cbc11cbbe72441b83e6f50c96103591 rtk-win32-x64.exe
2
+ 115f29549c19996ef538829f61a44444f2e37821a1282ad82aded792833e2d5b rtk-win32-arm64.exe
3
3
  1b1e792767ed0e1e6ca0e2f0a8de02e77b06dea2f5ae667278b94baf239fcdc3 rtk-darwin-x64
4
4
  9717978d9d6216ea50c94444e00e359479b6315a17bd48c16064b267c8b0b60d rtk-darwin-arm64
5
5
  a100d3defac54194144e5723aec57e6f286b42298c67145c8428815246c9ee56 rtk-linux-x64
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "gm-kilo",
3
- "version": "2.0.900",
3
+ "version": "2.0.902",
4
4
  "description": "State machine agent with hooks, skills, and automated git enforcement",
5
5
  "author": "AnEntrypoint",
6
6
  "license": "MIT",
@@ -13,7 +13,7 @@ Phases: PLAN → EXECUTE → EMIT → VERIFY → UPDATE-DOCS. Each loaded by Ski
13
13
 
14
14
  The user's request is the authorization. The PRD records it. Doubts during execution resolve by witnessed probe, by recall, or by re-reading the PRD. Questions back to the user only when the next action is destructive-irreversible AND uncovered by the PRD, or when intent is genuinely irrecoverable from PRD, memory, code, and the public web. `exec:pause` is the channel; in-conversation asking is beneath that. Web-search before pausing on anything the public web could plausibly answer.
15
15
 
16
- The obvious read of "deeply integrate", "all of them", "every X", "across the whole Y" is wider, not narrower. Pick the maximum reachable shape, declare the read in one line so the user can interrupt, execute. Multi-repo scope, build cost, CI duration, binary-size impact are never grounds to re-confirm. When scope exceeds reach, write every witnessable subset into the PRD as separate items and finish them all. Residuals within the spirit of the ask and reachable from this session expand the PRD silently-but-declared; only out-of-spirit-or-unreachable residuals are name-and-stop.
16
+ The obvious read of "deeply integrate", "all of them", "every X", "across the whole Y" is wider, not narrower. Pick the maximum reachable shape, declare the read in one line so the user can interrupt, execute. Multi-repo scope, build cost, CI duration, binary-size impact are never grounds to re-confirm. When scope exceeds reach, write every witnessable subset into the PRD as separate items and finish them all. Residuals within the spirit of the ask and reachable from this session re-enter `planning`, append PRD items, and execute — silently-but-declared, never name-and-stop, never asked back. The only name-and-stop residual is one that is genuinely outside the spirit of the ask OR genuinely unreachable from this session; everything else is this turn's work. Before declaring done, scan once more: any reachable in-spirit residual found means re-enter PLAN, not stop.
17
17
 
18
18
  When a PRD holds remaining items, do every reachable one — never offer the user a numbered choice between strategies, never serialize "approach A then approach B then approach C" through the user's inbox. Independent items run as parallel `gm:gm` subagents in one message; sequential items execute back-to-back without re-asking permission between them. The user's authorization for the PRD is authorization for every item in it. A response that asks "1, 2, 3, or 4?" when the PRD is non-empty is the failure this rule guards against — pick the obvious reading, declare it in one line, execute all of them.
19
19
 
@@ -26,7 +26,7 @@ Failure triage: broken output to EMIT, wrong logic to EXECUTE, new unknown to PL
26
26
  - `git_clean` — `git status --porcelain` returns empty
27
27
  - `git_pushed` — `git log origin/main..HEAD --oneline` returns empty
28
28
  - `ci_passed` — every GitHub Actions run reaches `conclusion: success`
29
- - `prd_empty` — `.gm/prd.yml` deleted
29
+ - `prd_empty` — `.gm/prd.yml` deleted AFTER residual scan: enumerate every in-spirit reachable residual surfaced this session; any hit re-enters `planning`, appends PRD items, executes. Empty PRD is necessary, not sufficient — done = empty PRD AND zero reachable in-spirit residuals. Out-of-spirit-or-unreachable residuals are named in the response and skipped; everything else is this turn's work.
30
30
  - `stress_suite_clear` — change walked through M1–D1 (governance), none flunked
31
31
  - `hidden_decision_posture` — open → down_weighted → closed only when CI is green AND stress suite is clear
32
32