forge-orkes 0.9.5 → 0.9.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "forge-orkes",
-  "version": "0.9.5",
+  "version": "0.9.6",
   "description": "Set up the Forge meta-prompting framework for Claude Code in your project",
   "bin": {
     "create-forge": "./bin/create-forge.js"

package/template/.claude/agents/verifier.md

@@ -60,6 +60,7 @@ Run: {n} | Passed: {n} | Failed: {n} | Coverage: {if available}
 Read: .forge/phases/m{M}-{N}-{name}/plan.md → extract must_haves
 Read: .forge/state/milestone-{id}.yml → reported progress
 Read: .forge/context.md → locked decisions
+Read: .forge/deferred-issues.md → known pre-existing failures (if exists; treat as advisory)
 ```
 
 ### 2. Truths
@@ -90,6 +91,10 @@ npm run build 2>&1
 npm run lint 2>&1
 ```
 
+Cross-reference failures against `deferred-issues.md`:
+- Match on test name or summary → advisory; label "Pre-existing (deferred: DI-{N})"
+- No match → regression; include in Issues (Critical) and gaps
+
 ### 6. Anti-Pattern Scan
 
 | Pattern | Command | Severity |

package/template/.claude/skills/executing/SKILL.md

@@ -10,6 +10,18 @@ description: "Build to plan with atomic commits, deviation rules, and context en
 - [ ] Context.md locked decisions noted
 - [ ] Constitution.md gates satisfied
 - [ ] Milestone state updated to `status: executing`
+- [ ] Baseline snapshot captured (see below)
+
+## Baseline Snapshot
+
+Run **before the first task begins**. Makes failure causality mechanical — no self-assessment.
+
+1. Run all non-advisory verification commands
+2. Record which tests/checks pass and which fail — this is the baseline
+3. After each commit: failures **not in baseline** = introduced by this task = **must fix under Rule 3**
+4. Failures **present in baseline** = pre-existing → append to `.forge/deferred-issues.md`, mark `status: pending`
+
+Skip only if re-entering an in-progress execution and `deferred-issues.md` already documents all current failures.
 
 ## Deviation Rules
 
@@ -116,9 +128,9 @@ For each command, in order:
 ```
 Attempt 1:
   1. Read error output
-  2. Caused by current task?
-     - YES → fix code, stage fixes, amend commit
-     - NO → mark advisory for this session; append to .forge/deferred-issues.md; continue
+  2. In baseline snapshot?
+     - YES (pre-existing) → mark advisory for this session; append to .forge/deferred-issues.md; continue
+     - NO (introduced by this task) → fix code, stage fixes, amend commit
   3. Re-run command
   4. Pass → next command
   5. Fail → next attempt (up to max_retries)
@@ -133,7 +145,7 @@ After max_retries exhausted:
 Verification retries count toward the task's 3-strike limit. 2 strikes used = 1 verification retry max.
 
 ### Do NOT Fix
-- **Pre-existing failures** not from current task → mark advisory; append to `.forge/deferred-issues.md`
+- **Pre-existing failures** present in baseline snapshot → mark advisory; append to `.forge/deferred-issues.md`
 - **Flaky tests** passing on re-run without changes → note in summary, no strike
 - **Unrelated warnings** (deprecation, non-blocking lint) → ignore
 
@@ -190,7 +202,8 @@ After completing all tasks in a plan:
 - src/components/Login.tsx (created)
 
 ## Notes
-[Anything the verifier should know]
+[Genuine handoff context only: environment requirements, seed data, external services needed (e.g. "Redis must be running for auth tests").
+Do NOT list test failures here — pre-existing failures belong in deferred-issues.md; task-introduced failures must be fixed before committing.]
 ```
 
 ## State Updates

package/template/.claude/skills/verifying/SKILL.md

@@ -21,8 +21,33 @@ Read: .forge/project.yml → tech stack (for running tests)
 Read: .forge/phases/m{M}-{N}-{name}/plan-{NN}.md → must_haves (truths, artifacts, key_links)
 Read: .forge/context.md → locked decisions
 Read: .forge/requirements.yml → requirement IDs for coverage check
+Read: .forge/deferred-issues.md → known pre-existing failures (if exists; treat as advisory)
 ```
 
+## Deferred Issues
+
+If `.forge/deferred-issues.md` exists, load it before running any tests.
+
+When test results come in, cross-reference failures against known deferred issue IDs:
+
+- **Failure matches a deferred ID** → advisory only — note as "Pre-existing (deferred: DI-{N})", do NOT fail verification for this
+- **Failure not in deferred-issues.md** → regression introduced after the baseline — **FAIL** and include in gaps
+
+In the Test Results section of the report, split accordingly:
+
+```markdown
+## Test Results
+Run: {n} | Passed: {n} | Failed: {n}
+
+### Regressions (block release)
+- {test name}: {error}
+
+### Pre-existing / Deferred (advisory)
+- DI-{N}: {test name} — {summary from deferred-issues.md}
+```
+
+Verdict: FAIL only triggers for regressions. Known deferred failures do not block a PASSED verdict — they are tracked separately and must be worked off via the refactor backlog or a dedicated fix phase.
+
 ## Interface Testing Gate
 
 Read `interface` from `.forge/project.yml`. If absent, `[]`, or `[none]` → skip gate, proceed to 3-level verification.