@vaubaan/harness 2.0.0 → 2.1.0

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/README.md CHANGED
@@ -44,9 +44,9 @@ Each pillar stores one kind of information the code cannot carry, and links to t
44
44
  | ----------------- | -------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
45
45
  | `README.md` | What this is, how to run it. | `package.json` scripts, the quick start. |
46
46
  | `docs/spec/` | What we want, for whom, what we refuse to do. Vocabulary. Tech-agnostic. | The modules and entry points that realize each requirement. A requirement with no pointer is a todo or dead. |
47
- | `docs/decisions/` | Why it is built this way, what was rejected, what changed since. | The config files and commits that embody the decision: `tsconfig.json`, `ci.yml`, a sha. |
47
+ | `docs/decisions/` | The structural choices in force: why, and what was rejected. | The config files and commits that embody the decision: `tsconfig.json`, `ci.yml`, a sha. |
48
48
  | `docs/handbook/` | The map: where to look, the invariants the code assumes, the gotchas. | The files it describes, declared in `tracks:`. A map, not a retelling. |
49
- | `docs/tests/` | Which scenarios matter, what "done" means. | The test that implements each scenario. A scenario with no test is an acceptance criterion still open. |
49
+ | `docs/tests/` | Test scope, stack, conventions, known gaps. Never the covered scenarios. | The test files: their titles say what is covered. A spec with no test is a known gap. |
50
50
  | `docs/workflow/` | What lives outside the repo: approvals, protections, secrets, languages. | `ci.yml`, build scripts, pre-commit hook. |
51
51
  | `docs/quality/` | Optional. The code rules this team holds, and the deviations it accepts. | The linter and formatter configs that enforce the mechanical part. |
52
52
  | `docs/skills/` | Optional. Domain know-how the agent should load. | Whatever the skill needs. |
@@ -103,7 +103,7 @@ status: draft
103
103
  - Multi-currency: not before a customer asks.
104
104
  ```
105
105
 
106
- **`docs/decisions/postgres-over-sqlite.md`**: the why, the rejected options, the history. Current state, rewritten when you change your mind, with a one-line history per reversal; git holds the rest.
106
+ **`docs/decisions/postgres-over-sqlite.md`**: one structural decision in force, about 40 lines: the why and the rejected options. When you change your mind, a new file replaces it; git holds the rest.
107
107
 
108
108
  ```markdown
109
109
  # Postgres over SQLite for the invoice store
@@ -119,11 +119,8 @@ and `src/db/client.ts`. Introduced in commit `4f1c2ab`.
119
119
  Local setup needs Docker. Migrations live in `db/migrations/`.
120
120
 
121
121
  ## Rejected alternatives
122
- | SQLite | single-writer lock under two workers |
123
-
124
- ## History
125
- - 2026-03-02 `9a0b7e1`: started on SQLite for speed of setup.
126
- - 2026-06-14 `4f1c2ab`: moved to Postgres after the first lost write.
122
+ ### SQLite
123
+ Where it started; its single-writer lock lost a write under two workers.
127
124
  ```
128
125
 
129
126
  **`docs/handbook/invoice-pipeline.md`**: the map, declared with `tracks:` so the linter notices when the code moves.
@@ -147,17 +144,18 @@ Gotcha: `void.ts` keeps the row and flips `status`; reports must filter
147
144
  on it (`src/reports/monthly.ts`).
148
145
  ```
149
146
 
150
- **`docs/tests/integration-tests.md`**: which scenarios matter, and the test that holds each one.
147
+ **`docs/tests/integration-tests.md`**: scope, stack, conventions and known gaps. The covered scenarios are the test titles, never copied here.
151
148
 
152
149
  ```markdown
153
150
  ---
154
- tracks: [tests/integration/**/*.test.ts]
151
+ tracks: [vitest.config.ts, tests/integration/fixtures/*.ts]
155
152
  ---
156
- | Scenario | Test |
157
- |---|---|
158
- | Issuing a draft twice fails the second time | `tests/integration/issue.test.ts` › "is irreversible" |
159
- | Voiding keeps the invoice visible in reports | `tests/integration/void.test.ts` › "stays in monthly report" |
160
- | Two workers issue the same draft | *open*: no test yet |
153
+ ## Scope
154
+ Invoicing modules against a throwaway Postgres; no browser (→ e2e-tests.md).
155
+ ## Conventions
156
+ One database per worker (`fixtures/db.ts`); never share a draft across tests.
157
+ ## Known gaps
158
+ - ⚠️ Two workers issuing the same draft (spec invoicing §3) — not tested yet.
161
159
  ```
162
160
 
163
161
  **`docs/workflow/coding-workflow.md`**: what lives outside the repo, and pointers to what lives in it.
package/dist/cli/index.js CHANGED
@@ -436,7 +436,7 @@ import { join as join5 } from "path";
436
436
  import { z } from "zod";
437
437
 
438
438
  // src/version.ts
439
- var VERSION = "2.0.0";
439
+ var VERSION = "2.1.0";
440
440
 
441
441
  // src/cli/manifest.ts
442
442
  var MANIFEST_FILENAME = ".harness-manifest.json";
@@ -683,9 +683,9 @@ function buildUmbrellaBody(extras) {
683
683
  "",
684
684
  "- `README.md` \u2014 pitch, quick start, scripts. Entry point.",
685
685
  "- `docs/spec/<subsystem>.md` \u2014 *what* and *why* (tech-agnostic).",
686
- "- `docs/handbook/<feature>.md` \u2014 *how it actually works* today.",
686
+ "- `docs/handbook/<feature>.md` \u2014 what the code does not say: entry points, traps, settings outside the repo, manual procedures.",
687
687
  "- `docs/decisions/<slug>.md` \u2014 ADRs: structural choices and rejected alternatives.",
688
- "- `docs/tests/integration-tests.md` & `e2e-tests.md` \u2014 core scenarios.",
688
+ "- `docs/tests/integration-tests.md` & `e2e-tests.md` \u2014 test scope, stack, conventions, known gaps.",
689
689
  "- `docs/workflow/coding-workflow.md` \u2014 CI, branches, PR, release. How this team works: follow it.",
690
690
  ...extras.hasProjectSkills ? ["- `docs/skills/*.skill.md` \u2014 the project's domain skills."] : [],
691
691
  ...extras.hasQualityDoc ? [