specweave 3.1.9 → 3.1.11

package/src/core/schemas/specweave-config.schema.json

@@ -563,72 +563,57 @@
         }
       }
     },
+    "git": {
+      "type": "object",
+      "description": "Commits of the increment's own spec.md, ledger.jsonl and metadata.json",
+      "properties": {
+        "autoCommitIncrement": {
+          "type": "boolean",
+          "default": false,
+          "description": "Commit those files (pathspec only, hooks run) after task, create-increment and handoff; --no-commit skips one command"
+        },
+        "autoPushIncrement": {
+          "type": "boolean",
+          "default": false,
+          "description": "After an auto-commit, fast-forward push the branch to its upstream"
+        }
+      }
+    },
     "testing": {
       "type": "object",
-      "description": "Testing configuration including TDD mode, coverage targets, and browser automation",
+      "description": "Verification commands and optional test policy. Nothing here is set by default; TDD and coverage targets apply only when you set them.",
       "properties": {
-        "defaultTestMode": {
-          "type": "string",
-          "description": "Default test mode for new increments",
-          "enum": ["TDD", "test-first", "test-after"],
-          "default": "test-after"
+        "commands": {
+          "type": "array",
+          "description": "Commands `specweave verify` runs, in order. Empty or unset means auto-detect (package.json test, lint, build; Cargo, pytest or Go).",
+          "items": { "type": "string" }
         },
-        "defaultCoverageTarget": {
-          "type": "number",
-          "description": "Default code coverage target percentage",
-          "minimum": 0,
-          "maximum": 100,
-          "default": 80
+        "mode": {
+          "type": "string",
+          "description": "Optional. How tests are written for new work. Unset means no test-order rule. `TDD` adds 'all tests must pass' to `specweave auto` success criteria.",
+          "enum": ["TDD", "test-after", "manual", "none"]
         },
-        "coverageTargets": {
+        "coverage": {
           "type": "object",
-          "description": "Per-level coverage targets",
+          "description": "Optional coverage targets. Unset means no coverage check. Below target is a warning at close, never a block.",
           "properties": {
             "unit": {
               "type": "number",
               "description": "Unit test line coverage target (Istanbul/c8 percentage)",
               "minimum": 0,
-              "maximum": 100,
-              "default": 80
+              "maximum": 100
             },
             "integration": {
               "type": "number",
               "description": "Integration test line coverage target (Istanbul/c8 percentage)",
               "minimum": 0,
-              "maximum": 100,
-              "default": 70
+              "maximum": 100
             },
             "e2e": {
               "type": "number",
-              "description": "E2E test pass-rate target (percentage of written Playwright tests that must pass, not line coverage)",
+              "description": "Share of written end-to-end tests that must pass (not line coverage)",
               "minimum": 0,
-              "maximum": 100,
-              "default": 100
-            }
-          },
-          "additionalProperties": false
-        },
-        "tddEnforcement": {
-          "type": "string",
-          "description": "TDD enforcement level: strict blocks GREEN without RED, warn shows warning, off disables",
-          "enum": ["strict", "warn", "off"],
-          "default": "warn"
-        },
-        "playwright": {
-          "type": "object",
-          "description": "Playwright browser automation configuration for dual-mode (CLI vs MCP)",
-          "properties": {
-            "preferCli": {
-              "type": "boolean",
-              "description": "Prefer @playwright/cli over MCP plugin for automation tasks (98% token reduction). Set false to always use MCP.",
-              "default": true
-            },
-            "cliFlags": {
-              "type": "array",
-              "description": "Additional flags to pass to playwright-cli commands",
-              "items": {
-                "type": "string"
-              }
+              "maximum": 100
             }
           },
           "additionalProperties": false

package/src/templates/AGENTS.md.template

@@ -1,21 +1,21 @@
 <!-- SECTION:header required -->
 # {PROJECT_NAME}
 
-This project uses SpecWeave. Plan increments in `.specweave/increments/NNNN-slug/spec.md`: Problem, Scope, Acceptance Criteria, Approach and Tasks. Adjacent `ledger.jsonl` records claims and completions. Start sessions with `specweave pickup`.
+SpecWeave increments live in `.specweave/increments/NNNN-slug/spec.md`: Problem, Scope, Acceptance Criteria, Approach and Tasks. `ledger.jsonl` records claims and completions. Start with `specweave pickup`.
 <!-- /SECTION -->
 
 <!-- SECTION:loop required -->
 ## The loop
 
 1. `specweave pickup`: applies the latest handoff, prints the open increment, next task and ACs, claims, branch, notes and memory.
-2. New work needing ACs or handoff: `specweave create-increment "title"`, then fill spec.md. First ask the user only their critical decisions, one at a time with a recommended answer, and record them under `## Decisions` (sw-increment). If an open increment owns the files, add ACs and tasks there. Recommended for features, not required; to skip one run `specweave small-fix "<why>"`. Close what you open: its plan ends with "Verify and close NNNN".
+2. New work needing ACs or handoff: `specweave create-increment "title"`, then fill spec.md. Ask only critical decisions, one at a time with a recommendation, and record them under `## Decisions` (sw-increment). If an open increment owns the files, add ACs and tasks there. Recommended for features, not required; to skip one run `specweave small-fix "<why>"`. Close what you open: its plan ends with "Verify and close NNNN".
 3. `specweave task claim T-NN`, edit only that task's Files, commit as `NNNN: what changed`, then `specweave task done T-NN --run "<its Test>"`. `--line`/`--link` feed `specweave cards --md`.
 4. When the last task is done or skipped, without asking: `specweave verify`, a fresh-context review (subagent or new session) for anything that ships, `specweave complete NNNN`. PR-shipped work needs `task done` first.
 5. Stopping with tasks left, or switching tools: `specweave handoff --reason "<why>"`.
 
 **Handoff.** When the user says "hand off", "out of tokens" or "switching accounts", or "[Usage limit reached" appears (outside SpecWithCode), run `specweave handoff --reason "<why>"`; tell them to say "pick up" in the other tool. "[Usage limit approaching" or usage heads-ups mean keep working; say so. When the user says "pick up", run `specweave pickup`; continue through step 4, passing any given id/title. Take the newest handoff if several; say which.
 
-Tasks in spec.md: `### T-01 Title`, then `- AC: AC-01 | Files: src/a.ts, tests/e2e/a.test.ts | Test: npm test -- e2e/a`. An AC is met when its tasks are done. Leave notes with `specweave note "<text>"`. Skills: `.agents/skills/sw-*` and `.claude/skills/sw-*`; other tools: `npx vskill install anton-abyzov/specweave/sw-do`.
+Tasks in spec.md: `### T-01 Title`, then `- AC: AC-01 | Files: src/a.ts, tests/e2e/a.test.ts | Test: npm test -- e2e/a`. ACs derive from done tasks. Notes: `specweave note "<text>"`. Skills: `.agents/skills/sw-*` and `.claude/skills/sw-*`; other tools: `npx vskill install anton-abyzov/specweave/sw-do`.
 <!-- /SECTION -->
 
 <!-- SECTION:rules required -->
@@ -24,8 +24,9 @@ Tasks in spec.md: `### T-01 Title`, then `- AC: AC-01 | Files: src/a.ts, tests/e
 - Use headless Chrome/Playwright CLI for browser tests and automation: `headless: true`, `PWDEBUG=0`, `PLAYWRIGHT_HTML_OPEN=never`, HTML reports `open: 'never'`. Save captures to files; propagate to subagents. Before opening an essential visible browser, ask the user and wait for explicit approval. Headless failure is not approval.
 - A task is done when its Test exits 0 and you have seen the real output. A Test checks the AC as users would (CLI, HTTP, UI, API); add unit tests only when asked or when config or conventions require them. Never skip, weaken or delete a test to pass, and never set a status by hand.
 - One agent per branch/worktree: `git worktree add .worktrees/NNNN-<agent> -b inc/NNNN-<agent>` (never `../`). Claims older than 2h are stale. On `ledger.jsonl` conflicts keep both sides' lines.
-- Decisions that must outlive this session go in spec.md Approach, or as one file per fact in `.specweave/memory/` with a line in its `MEMORY.md` index. Memory is committed, so every tool and account sees it.
+- Commit durable decisions in spec.md Approach or one fact per file in `.specweave/memory/`, indexed in `MEMORY.md`, for all tools.
 - Check a secret exists without printing it; never commit `.env*`.
+- Honor project identity and licensing. Keep provenance and required notices; never infer license grants or history rewrites from branding changes.
 - Without the CLI, append ledger lines yourself, one JSON object per line, UTF-8, LF: `{"t":"T-01","e":"claim","by":"<tool>@<host>","at":"<ISO time>"}` (`e` is claim, done, release, skip or block; `done` needs `"evidence":"<commit sha>"`, `skip` needs `"note":"<why>"`).
 <!-- /SECTION -->
 

package/src/templates/CLAUDE.md.template

@@ -8,6 +8,7 @@ Everything shared by every tool is in AGENTS.md, imported above. Only Claude-spe
 - Skills: `/sw-increment "title"`, `/sw-do`, `/sw-auto`, `/sw-review`, `/sw-done`, `/sw-handoff`, from `.claude/skills/`, so they load in cloud sessions too. With the `sw` plugin they are also `/sw:do` and so on.
 - With the plugin, the SessionStart hook prints a short pickup; run `specweave pickup` for the next task's acceptance criteria.
 - Use plan mode before writing a spec for anything bigger than a small fix.
+- Follow AGENTS.md for product identity and licensing; preserve required third-party notices and accurate provenance.
 <!-- /SECTION -->
 
 <!-- SECTION:jev when="jev" -->