gm-plugkit 2.0.1357 → 2.0.1359

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/SKILL.md CHANGED
@@ -52,6 +52,8 @@ The chain is not COMPLETE until your changes are on origin. Commit and push at t
52
52
 
53
53
  **Apply "every possible" to every noun.** PLAN is exhaustive, not minimal. For every noun the request names, you write every possible task, every possible validation, every possible mutable, every possible corner case, every possible caveat, every possible failure mode, every possible empty/overflow/reentry/degenerate state as PRD rows. Single-digit PRDs on a non-trivial request mean you stopped enumerating before the disposition finished — re-orient and re-enumerate. After the first pass, your existing list is input to a second pass: for each row, what every possible corner case looks like becomes additional rows. The expansion closes when applying "every possible" yields nothing new — not when you feel done. Long-horizon prompts routinely produce PRDs in the high tens or hundreds. Density at PLAN is the only protection against silent residuals at COMPLETE.
54
54
 
55
+ **Noticing is a planning event.** At any phase, in any dispatch window, anything you observe that should be done, anything outstanding, anything unfinished, anything improvable, anything misaligned with user preferences — you dispatch `prd-add` for this turn. Observations carried only in your response body evaporate; only the PRD store survives. The default response to noticing is to convert. "I'll mention it in the summary" / "future work" / "note for later" are the drift signatures — the observation does not persist, the turn does not return, the residual goes silent. Density grows along the walk, not just at PLAN-time. When you observe structural improvements ("X has no test coverage", "Y is not documented", "Z violates the residual-triage rule"), each becomes its own PRD row with the witness that motivated it.
56
+
55
57
  `git push` is admissible only when `git status --porcelain` reads empty, and the porcelain probe must be its own Bash **tool-use event** before the push — a separate `Bash(...)` invocation, not a `&&`-chained command within one Bash call. ccsniff `--git-discipline` scans the last 20 Bash tool-use events (not shell commands within those events) for an explicit `git status --porcelain` (or `-s`); putting `add && commit && push` into one Bash call counts as one event with no porcelain witness, even though `git push` is technically the third shell command. The witness lives in the tool-call stream, not the shell stream. The discipline is **three Bash tool-use events** visible in the transcript: `Bash(git status --porcelain)` → read empty → `Bash(git push)`. You dispatch the `git_push` verb (not raw Bash) when possible — it gates on the porcelain probe internally, refuses dirty, and emits `deviation.push-dirty`. A raw `git push` Bash event without a preceding porcelain-probe Bash event is itself a deviation, regardless of how clean the worktree is by construction. Witness clean via `git_status`; witness pushed-to-remote via `branch_status` (ahead==0). The residual-scan and COMPLETE gate both refuse a dirty tree or a missing residual-check marker.
56
58
 
57
59
  Response body is not a mutation surface. Memory writes route through `memorize-fire` only — another verb YOU dispatch. **Never** write persistent memory to platform-specific paths (`~/.claude/projects/*/memory/`, `~/.codex/memory/`, `~/.cursor/*`, etc.) — those don't transport between agent platforms and break the moment a session runs under a different harness. The only two portable surfaces are (a) dispatched `memorize-fire` (which writes through plugkit to the rs-learn store that travels with the project) and (b) `AGENTS.md` for project-tracked rules. If you reach for a `Write` tool on a memory directory under `~/`, stop — that's the lock-in anti-pattern.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "gm-plugkit",
3
- "version": "2.0.1357",
3
+ "version": "2.0.1359",
4
4
  "description": "Bootstrap and daemon-spawn tool for gm plugkit binary. Downloads the correct platform binary, verifies SHA256, and starts the spool watcher daemon. Includes plugkit-wasm-wrapper for WASM-based spool watching.",
5
5
  "main": "index.js",
6
6
  "bin": {
@@ -2639,12 +2639,26 @@ async function runSpoolWatcher(instance, spoolDir) {
2639
2639
  fs.renameSync(tmp, UPDATE_CHECK_SHARED_CACHE);
2640
2640
  } catch (_) {}
2641
2641
  }
2642
+ let _lastKnownUpdateError = null;
2643
+ function logUpdateCheckError(fields) {
2644
+ const key = `${fields.status || ''}:${fields.error || ''}`;
2645
+ if (_lastKnownUpdateError === key) return;
2646
+ _lastKnownUpdateError = key;
2647
+ logEvent('plugkit', 'update.check.error', fields);
2648
+ }
2649
+ function clearUpdateCheckError(installed) {
2650
+ if (_lastKnownUpdateError !== null) {
2651
+ logEvent('plugkit', 'update.check.recovered', { installed, was: _lastKnownUpdateError });
2652
+ _lastKnownUpdateError = null;
2653
+ }
2654
+ }
2642
2655
  function applyUpdateCheckResult(installed, latest, statusCode) {
2643
2656
  if (statusCode !== 200) {
2644
- logEvent('plugkit', 'update.check.error', { installed, status: statusCode });
2657
+ logUpdateCheckError({ installed, status: statusCode });
2645
2658
  return;
2646
2659
  }
2647
2660
  if (!latest) return;
2661
+ clearUpdateCheckError(installed);
2648
2662
  if (latest === installed) {
2649
2663
  try { fs.unlinkSync(UPDATE_AVAILABLE_PATH); } catch (_) {}
2650
2664
  if (_lastKnownDrift) {
@@ -2715,18 +2729,18 @@ async function runSpoolWatcher(instance, spoolDir) {
2715
2729
  _lastKnownDrift = latest;
2716
2730
  }
2717
2731
  } catch (e) {
2718
- logEvent('plugkit', 'update.check.error', { error: String(e && e.message || e) });
2732
+ logUpdateCheckError({ error: String(e && e.message || e) });
2719
2733
  }
2720
2734
  });
2721
2735
  });
2722
2736
  req.on('timeout', () => {
2723
2737
  req.destroy();
2724
2738
  writeSharedUpdateCache(null, -1);
2725
- logEvent('plugkit', 'update.check.error', { error: 'timeout' });
2739
+ logUpdateCheckError({ error: 'timeout' });
2726
2740
  });
2727
2741
  req.on('error', (e) => {
2728
2742
  writeSharedUpdateCache(null, -2);
2729
- logEvent('plugkit', 'update.check.error', { error: String(e && e.message || e) });
2743
+ logUpdateCheckError({ error: String(e && e.message || e) });
2730
2744
  });
2731
2745
  }
2732
2746
  setTimeout(checkForUpdate, 10_000);
package/plugkit.version CHANGED
@@ -1 +1 @@
1
- 0.1.511
1
+ 0.1.512