@yemi33/minions 0.1.2163 → 0.1.2164
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/docs/deprecated.json +4 -4
- package/engine/timeout.js +14 -2
- package/package.json +1 -1
package/docs/deprecated.json
CHANGED
|
@@ -27,14 +27,14 @@
|
|
|
27
27
|
"id": "completion-fallback-parsers",
|
|
28
28
|
"description": "parseStructuredCompletion and parseCompletionFieldSummary in engine/lifecycle.js",
|
|
29
29
|
"file": "engine/lifecycle.js",
|
|
30
|
-
"lines": "
|
|
30
|
+
"lines": "3410, 3608",
|
|
31
31
|
"telemetryGate": "_engine.completionFallbacks must read 0 (both fenced and summary counters) across sweepWindowDays starting from sweepStartDate",
|
|
32
32
|
"sweepWindowDays": 14,
|
|
33
|
-
"sweepStartDate": "2026-
|
|
34
|
-
"sweepRationale": "14 days matches the dead-code audit cadence (one full weekly audit cycle plus a buffer week). Policy decision pending confirmation in open-question #1 of the 2026-05-27 Bug Audit Review meeting conclusion — if the human teammate prefers a different cadence, repin this field and the matching enforcingSweepWindowTest fixture.",
|
|
33
|
+
"sweepStartDate": "2026-06-11",
|
|
34
|
+
"sweepRationale": "14 days matches the dead-code audit cadence (one full weekly audit cycle plus a buffer week). Window restarted on 2026-06-11 (= merge_date(P-a7b2c1d9) + 1 day, anchor commit eb544aa80dbd64c87b78ad08a17ca3560e627094 merged 2026-06-10T18:04:12Z) because the original 2026-05-27 window was invalidated: the engine/timeout.js caller of parseStructuredCompletion (commit 0f4b9787, 2026-04-30) predated the telemetry counter (commit cea61119, 2026-05-13), so the hidden caller was never instrumented and a zero reading proved nothing. P-a7b2c1d9 removed that hidden caller; the new window measures only callers that the counter actually instruments. Policy decision pending confirmation in open-question #1 of the 2026-05-27 Bug Audit Review meeting conclusion — if the human teammate prefers a different cadence, repin this field and the matching enforcingSweepWindowTest fixture.",
|
|
35
35
|
"enforcingTest": "test/unit/completion-fallback-telemetry.test.js:217-234",
|
|
36
36
|
"enforcingSweepWindowTest": "test/unit/completion-fallback-sweep-window.test.js",
|
|
37
|
-
"notes": "Do NOT set removedAt until telemetry confirms zero usage across the sweepWindowDays from sweepStartDate. The follow-up code-removal PR (dropping parseStructuredCompletion at engine/lifecycle.js:
|
|
37
|
+
"notes": "Do NOT set removedAt until telemetry confirms zero usage across the sweepWindowDays from sweepStartDate. The follow-up code-removal PR (dropping parseStructuredCompletion at engine/lifecycle.js:3410, parseCompletionFieldSummary at :3608, and the gated fallback at :4675-4700) is dispatched separately once the window is observed clean."
|
|
38
38
|
},
|
|
39
39
|
{
|
|
40
40
|
"id": "config-claude-binary-override",
|
package/engine/timeout.js
CHANGED
|
@@ -594,7 +594,15 @@ function checkTimeouts(config) {
|
|
|
594
594
|
const engineRestartGraceUntil = engine().engineRestartGraceUntil;
|
|
595
595
|
const engineRestartGraceExempt = engine().engineRestartGraceExempt;
|
|
596
596
|
const { completeDispatch } = dispatch();
|
|
597
|
-
|
|
597
|
+
// P-a7b2c1d9: fenced ```completion stdout parser (formerly destructured here)
|
|
598
|
+
// deliberately dropped from this destructure. The recovery path uses the
|
|
599
|
+
// sidecar (parseCompletionReportFile) as the sole structured-completion
|
|
600
|
+
// source. The stdout parser added no new signal on the timeout/exit-recovery
|
|
601
|
+
// path — only a disagreement risk between the sidecar and the stdout block.
|
|
602
|
+
// Removing this caller unblocks the completion-fallback-parsers deprecation
|
|
603
|
+
// sweep window in docs/deprecated.json (its `counter==0 ⇒ parser unused`
|
|
604
|
+
// claim is now logically sound).
|
|
605
|
+
const { runPostCompletionHooks, parseAgentOutput, parseCompletionReportFile, detectNonTerminalResultSummary } = require('./lifecycle');
|
|
598
606
|
|
|
599
607
|
const timeout = config.engine?.agentTimeout || ENGINE_DEFAULTS.agentTimeout;
|
|
600
608
|
const defaultStaleOrphanTimeout = config.engine?.heartbeatTimeout || ENGINE_DEFAULTS.heartbeatTimeout;
|
|
@@ -642,8 +650,12 @@ function checkTimeouts(config) {
|
|
|
642
650
|
const runtimeName = item.meta?.runtimeName || item.runtimeName || 'claude';
|
|
643
651
|
outputResultSummary = parseAgentOutput(fullLogForHooks, runtimeName).resultSummary || '';
|
|
644
652
|
const gateSummary = outputResultSummary || (!fullLogForHooks.includes('"type":') ? fullLogForHooks : '');
|
|
653
|
+
// P-a7b2c1d9: pass `null` for structuredCompletion. By the time
|
|
654
|
+
// checkTimeouts runs, the sidecar `completion.json` (parseCompletionReportFile)
|
|
655
|
+
// is the documented source of truth; the fenced ```completion stdout
|
|
656
|
+
// parser is intentionally bypassed here.
|
|
645
657
|
completionDetection = isSuccess
|
|
646
|
-
? detectNonTerminalResultSummary(gateSummary,
|
|
658
|
+
? detectNonTerminalResultSummary(gateSummary, null, parseCompletionReportFile(item), { detectPhantom: true })
|
|
647
659
|
: null;
|
|
648
660
|
} catch (e) { log('warn', 'completion summary gate: ' + e.message); }
|
|
649
661
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@yemi33/minions",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.2164",
|
|
4
4
|
"description": "Multi-agent AI dev team that runs from ~/.minions/ — five autonomous agents share a single engine, dashboard, and knowledge base",
|
|
5
5
|
"bin": {
|
|
6
6
|
"minions": "bin/minions.js"
|