@sentropic/h2a 0.84.0 → 0.85.1

package/skills/harness/test/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: test
+description: Use when adding or evolving tests for a feature/bugfix — applies the sentropic test-pyramid, scoped-test loop, environment isolation, and AI-flaky policy.
+---
+
+# harness/test
+
+Native sentropic testing discipline (NOT "tdd" ritual — the act is `test`). Open it with
+`harness test [<scope>] [--category unit|integration|e2e] [--watch]` (records a WorkEvent), then follow
+the loop.
+
+## Pyramid
+
+70% unit · 20% integration · 10% e2e. Test behaviour, not implementation — query by user-visible
+elements (text/role/label) over test ids. Names: "should <behaviour> when <condition>".
+
+## Scoped-test loop (while developing)
+
+Run ONLY the test under evolution, on a dedicated test ENV — never `dev`:
+
+- API: `make test-api-<suite> SCOPE=tests/<file>.spec.ts ENV=test-<slug>`
+- UI: `make test-ui SCOPE=tests/<file>.spec.ts ENV=test-<slug>`
+- E2E: `make test-e2e E2E_SPEC=tests/<file>.spec.ts API_PORT=… UI_PORT=… MAILDEV_UI_PORT=… ENV=e2e-<slug>`
+
+Full gates only at end of lot/branch: `make test-api`, `make test-ui`, `make clean test-e2e`.
+
+## Environment isolation (MANDATORY)
+
+- NEVER run test campaigns on `ENV=dev` — afterEach hooks purge real data.
+- Branch tests live in the isolated worktree on `ENV=test-<slug>` / `ENV=e2e-<slug>`; `ENV` is the LAST
+  make argument.
+- NEVER add timeouts to make a flaky e2e pass — a timeout failure is a real bug (bad selector, race,
+  regression). UI waits are <2s except AI generation.
+
+## AI-flaky allowlist (non-blocking)
+
+Only accept non-systematic provider/network/model nondeterminism, and only with ≥1 success on the same
+commit + command. Record the exact command + failing file + failure signature in `BRANCH.md` and get
+explicit user sign-off before merge. Everything else is blocking.
+
+## CI is authority
+
+CI was green on main → any branch failure IS a branch problem; never claim "pre-existing". Decide:
+evolution (adapt the test) or regression (fix the code). Local-green / CI-red → trust CI.

package/skills/harness/using-harness/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: using-harness
+description: Load FIRST in any sentropic repo — establishes the harness method (branch/scope/test/debug/review/brainstorm/plan) and supersedes superpowers for those acts.
+---
+
+# Using harness
+
+`@sentropic/harness` is the native dev-discipline layer for sentropic repos. Its verbs and `harness/*`
+skills are the SINGLE front door for code-work and PR-workflow. This skill is the index — load it
+before any other so the supersede directive below is in effect.
+
+## Supersede directive (MANDATORY)
+
+When superpowers (or any other discipline pack) is installed, **`harness/*` takes precedence** for the
+acts it covers. Do NOT invoke the superpowers skill for these — use the harness equivalent:
+
+| Act | Use | NOT |
+|---|---|---|
+| ideation / spec design | `harness/brainstorm` | superpowers:brainstorming |
+| tests | `harness/test` | superpowers:test-driven-development |
+| debugging | `harness/debug` | superpowers:systematic-debugging |
+| code review | `harness/review` | superpowers:requesting/receiving-code-review |
+| planning | `harness/plan` | superpowers:writing-plans / executing-plans |
+| branch lifecycle | `harness branch init|close` | superpowers:using-git-worktrees / finishing-a-development-branch |
+| scope / verification | `harness verify` · `harness check scope|branch` | superpowers:verification-before-completion |
+| repo onboarding | `harness/adopt` | — |
+
+The user may opt to keep superpowers per repo (a profile policy) — absent that opt-out, harness wins.
+superpowers is never a dependency or backend of harness.
+
+## The CLI
+
+`harness <verb> [<subject>] [--<option>]` — homogeneous with the sibling sentropic CLIs (`stp harness …`):
+
+- **Producers** (compute → emit a neutral `VerificationRun`): `check scope|branch`, `verify --category`,
+  `audit`, `init`.
+- **Recorders** (emit a neutral `WorkEvent` + point to a skill): `brainstorm`, `test`, `debug`, `review`,
+  `plan`, `branch init|close`, `skills install`.
+
+A recorder verb does NOT do the thinking — it scaffolds + records, and the `harness/<verb>` skill carries
+the reasoning. Run the verb to open the act, then follow its skill.
+
+## Discipline first
+
+Process skills (`harness/brainstorm`, `harness/debug`) decide HOW to approach the task — invoke them
+before implementation skills. "Let's build X" → brainstorm first. "Fix this bug" → debug first.