Simplify agent-swarm to a lite core with optional modules and evals

agent-swarm/evals/tasks/broad-migration.md

@@ -0,0 +1,26 @@
+# Broad migration — swarm test
+
+Use a repository with 8+ independent call sites or modules that need the same mechanical change
+(e.g. adding pagination to independent endpoints, or migrating independent modules to a new API).
+
+Prompt:
+
+```text
+Apply the migration across the affected modules. Each unit must have its own scope and tests. Do not
+touch unrelated code. Verify the integrated result and report conflicts or skipped units.
+```
+
+Expected with a good skill:
+
+- a short plan with disjoint write scopes and frozen interfaces;
+- parallel or batched workers, or a deliberate sequential choice with a reason;
+- independent verification of the integrated result;
+- no overlapping edits, no silent skipped units;
+- time/tokens improve over baseline, or quality improves enough to justify the cost.
+
+Failure signals:
+
+- 20 agents for 8 small edits;
+- workers editing the same file;
+- no integration check;
+- reports without evidence.

agent-swarm/evals/tasks/product-ui.md

@@ -0,0 +1,28 @@
+# Product UI — quality-gate test
+
+Use a small app with an existing UI (or a fixture). Ask for one vertical UI slice: for example, a
+scene hierarchy panel with selection and an inspector for a transform. The artifact must be runnable.
+
+Prompt:
+
+```text
+Add the requested UI slice to this app. It is a product task: the result must be usable, not just
+compile. Use the existing stack. Run the app, capture the default and minimum window sizes, measure
+release-build frame time and input latency, compare with the current version, and report the exact
+commands. Do not expand into unrelated features.
+```
+
+Expected with a good skill:
+
+- one implementer and one independent critic, not parallel panel writers;
+- runnable artifact and screenshots;
+- release performance measured; baseline compared;
+- the agent stops if the result is slower or visually worse than the existing version;
+- the user gets a 3–5 step scenario and an explicit verdict request.
+
+Failure signals:
+
+- screenshot-only acceptance, debug-build performance claims;
+- “tests pass” treated as product acceptance;
+- new features added while the slice is laggy;
+- no baseline comparison.

agent-swarm/evals/tasks/small-fix.md

@@ -0,0 +1,24 @@
+# Small fix — trigger test
+
+Use a small repository with one failing test (or one clearly scoped bug). Provide the repo path,
+the failing command and the expected behavior.
+
+Prompt:
+
+```text
+Fix the failing test in this repository. Make the smallest correct change, run the failing test and
+the relevant suite, and report the exact commands and results. Do not refactor unrelated code.
+```
+
+Expected with a good skill:
+
+- no swarm, no `.swarm/` tree, one worker or direct work;
+- the failing test now passes;
+- no unrelated changes;
+- time and tokens close to baseline.
+
+Failure signals:
+
+- the skill spawns multiple agents or writes a full plan for a one-line fix;
+- process artifacts exceed the code change;
+- the agent claims success without running the test.