@yemi33/minions 0.1.1864 → 0.1.1866
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/CHANGELOG.md +10 -0
- package/engine/scheduler.js +1 -0
- package/package.json +1 -1
- package/playbooks/shared-rules.md +32 -0
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,15 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.1.1866 (2026-05-11)
|
|
4
|
+
|
|
5
|
+
### Other
|
|
6
|
+
- test(scheduler): add unit tests for writeScheduleRunEntry, createScheduledWorkItem, recordScheduleRun (#2341)
|
|
7
|
+
|
|
8
|
+
## 0.1.1865 (2026-05-11)
|
|
9
|
+
|
|
10
|
+
### Fixes
|
|
11
|
+
- put hard-stop rule at top of shared-rules.md so agents can't miss it
|
|
12
|
+
|
|
3
13
|
## 0.1.1864 (2026-05-11)
|
|
4
14
|
|
|
5
15
|
### Fixes
|
package/engine/scheduler.js
CHANGED
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@yemi33/minions",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1866",
|
|
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"
|
|
@@ -1,3 +1,35 @@
|
|
|
1
|
+
## ⚠️ HARD STOP — read this first
|
|
2
|
+
|
|
3
|
+
**You will silently crash the runtime CLI (Copilot or Claude Code) on
|
|
4
|
+
Windows if you run a full-project test suite from your shell tool.**
|
|
5
|
+
This is a deterministic native-level fault — no error message, no result
|
|
6
|
+
event, just exit code 1. Your work is lost (worktree wiped) and the WI
|
|
7
|
+
hard-fails. Repro confirmed 2026-05-11 across both runtimes, multiple
|
|
8
|
+
attempts, with full memory dumps.
|
|
9
|
+
|
|
10
|
+
**Forbidden** — never run these as agent shell commands:
|
|
11
|
+
|
|
12
|
+
- `npm test`, `npm run <anything>`, `yarn test`, `yarn <script>`, `pnpm test`, `pnpm <script>`, `npx mocha`, `npx jest`, `npx vitest`
|
|
13
|
+
- `node test/unit.test.js` (this repo's full unit suite)
|
|
14
|
+
- ANY command that invokes the project's "run all tests" path
|
|
15
|
+
|
|
16
|
+
**Allowed** — single-file or single-test invocations:
|
|
17
|
+
|
|
18
|
+
- `node test/unit/<one-file>.test.js`
|
|
19
|
+
- `node node_modules/<runner>/bin/<runner>.js <one-file>`
|
|
20
|
+
- `python -m pytest tests/test_one_file.py`
|
|
21
|
+
- `cargo test --test one_test`
|
|
22
|
+
- `dotnet test path/to/Project.Tests.csproj --filter "FullyQualifiedName~OneTest"`
|
|
23
|
+
|
|
24
|
+
**Rules that follow from this:**
|
|
25
|
+
|
|
26
|
+
1. Run only targeted tests for the code YOU changed. The engine and PR CI handle full-suite regression detection — that is not your job.
|
|
27
|
+
2. If your targeted test fails, fix the code and re-run *the targeted test*. Never expand to the full suite as a sanity check.
|
|
28
|
+
3. Push the branch and open the PR as early as possible — before any final verification you might be tempted to run. If you do crash on a later command, the work survives on the remote and the engine can auto-link.
|
|
29
|
+
4. This rule overrides any contradictory guidance in playbooks or task descriptions. If a playbook section says "prefer the full suite", that section is outdated — ignore it and use targeted tests.
|
|
30
|
+
|
|
31
|
+
If a project genuinely requires the wrapper (env vars in a hook, etc.), use the closest direct equivalent anyway and note the deviation in your completion block. Verification you don't get because you crashed is worse than verification you skipped deliberately.
|
|
32
|
+
|
|
1
33
|
## Operating Principle
|
|
2
34
|
|
|
3
35
|
Treat a Minions assignment like the user typed the same task directly into a capable CLI agent. Optimize for the requested outcome and use the repo's own tools, conventions, and acceptance criteria.
|