harness-everything 0.16.2 → 0.16.4

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
       "name": "harness-everything",
       "source": "./",
       "description": "Harness OS: an orchestrated agent operating system — tier routing, circuit breaker guardrails, verification gates, WAL session memory, and self-evolving workspace rules.",
-      "version": "0.16.2",
+      "version": "0.16.4",
       "author": {
         "name": "Miya Daniel"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "harness-everything",
   "description": "Harness OS: an orchestrated agent operating system — tier routing, circuit breaker guardrails, verification gates, WAL session memory, and self-evolving workspace rules.",
-  "version": "0.16.2",
+  "version": "0.16.4",
   "author": {
     "name": "Miya Daniel"
   },

package/CHANGELOG.md

@@ -2,6 +2,18 @@
 
 All notable changes to this project are documented in this file.
 
+## [0.16.4](https://github.com/dyphn1/Harness-everything/compare/v0.16.3...v0.16.4) (2026-09-20)
+
+### Bug Fixes
+
+* **repo:** close issues 205-207 ([423ff63](https://github.com/dyphn1/Harness-everything/commit/423ff638f08cdaa14d4ab0856bfe2d2bc6b050db)), closes [#205](https://github.com/dyphn1/Harness-everything/issues/205) [#206](https://github.com/dyphn1/Harness-everything/issues/206) [#205](https://github.com/dyphn1/Harness-everything/issues/205) [#206](https://github.com/dyphn1/Harness-everything/issues/206) [#207](https://github.com/dyphn1/Harness-everything/issues/207)
+
+## [0.16.3](https://github.com/dyphn1/Harness-everything/compare/v0.16.2...v0.16.3) (2026-09-20)
+
+### Bug Fixes
+
+* **docker:** Verify current re-trip contract in docker-verify.sh ([#200](https://github.com/dyphn1/Harness-everything/issues/200)) ([610ce32](https://github.com/dyphn1/Harness-everything/commit/610ce32733a74dd4a16f68d171346ea8b10f8d62)), closes [#190](https://github.com/dyphn1/Harness-everything/issues/190) [#42](https://github.com/dyphn1/Harness-everything/issues/42)
+
 ## [0.16.2](https://github.com/dyphn1/Harness-everything/compare/v0.16.1...v0.16.2) (2026-09-20)
 
 ### Bug Fixes

package/ci/consistency-check.js

@@ -164,6 +164,106 @@ for (const [rel, pattern] of retiredClaims) {
   check(`${rel}: retired enforcement claim absent (${pattern})`, !pattern.test(text), 'stale pre-#190 contract wording');
 }
 
+// The per-file entries above only freeze the files a past fix touched, so the
+// same retired wording survived elsewhere (#204: docs/workflows/zoom-out.md,
+// docker-verify.sh). Scan the whole agent-facing surface instead: docs, routed
+// skills, shared references, the OpenCode README, root shell/container entry
+// points, and the packaged plugin copies that ship to other hosts.
+const RETIRED_CLAIM_DIRS = [
+  'docs',
+  'zoom-out',
+  'fable-mode',
+  'harness-everything/references',
+  'plugins/harness-everything',
+];
+const RETIRED_CLAIM_EXTENSIONS = new Set(['.md', '.sh', '.js', '.mjs']);
+
+// Files that legitimately keep the retired wording: retained pre-#190
+// live-host evidence, release history, capability docs whose hard-lock lines
+// are explicitly labelled historical/reported-only, code that strips the
+// retired state field, and the CI guards that assert its absence.
+const RETIRED_CLAIM_ALLOWLIST = [
+  /^benchmarks\/results\/live-host\/opencode-2026-09-16\//,
+  /^CHANGELOG\.md$/,
+  /^docs\/platform-capabilities\.md$/,
+  /^opencode-plugin\/index\.mjs$/,
+  /^ci\//,
+  /^behavioral-evals\/[^/]+\.js$/,
+];
+
+// A line that denies the retired behavior or dates it ("no permanent hard
+// lock", "historical hard-lock evidence", "predates #190") is the correct
+// wording, not drift. Only the broad hard-lock family needs this escape; the
+// assertive patterns below are wrong in any context, so they never get it.
+const HISTORICAL_CONTEXT =
+  /pre-#190|\b(?:no|not|never|without|remove[sd]?|retired|historical|predates|former(?:ly)?|legacy|post-reset|no longer)\b|rather than|instead of/i;
+
+const RETIRED_CLAIM_SCAN = [
+  { label: 'hard-lock escalation', pattern: /hard[\s-]?lock/i, historicalAllowed: true },
+  { label: 'reset gated on a second cycle', pattern: /only after the (?:second|repeated) cycle/i },
+  { label: 'cycle-escalation reset branch', pattern: /\|\s*(?:second|repeated|repeat) cycle\s*\|\s*reset/i },
+  { label: 'machine-blocked disposition', pattern: /machine[\s-]blocked/i },
+  { label: 'replan budget', pattern: /replan[\s-]budget/i },
+  { label: 'runtime worker leases', pattern: /worker lease/i },
+  { label: 'retired loop-budget invariant', pattern: /\bloop-budget\b/i },
+  { label: 'explicit iteration budget', pattern: /explicit iteration budget/i },
+];
+
+function collectRetiredClaimTargets() {
+  const targets = new Set();
+  const walk = (dir) => {
+    let entries;
+    try { entries = fs.readdirSync(dir, { withFileTypes: true }); } catch { return; }
+    for (const entry of entries) {
+      const p = path.join(dir, entry.name);
+      if (entry.isDirectory()) {
+        if (!entry.name.startsWith('.') && entry.name !== 'node_modules') walk(p);
+      } else if (RETIRED_CLAIM_EXTENSIONS.has(path.extname(entry.name))) {
+        targets.add(p);
+      }
+    }
+  };
+  for (const dir of RETIRED_CLAIM_DIRS) walk(path.join(ROOT, dir));
+  for (const entry of fs.readdirSync(ROOT, { withFileTypes: true })) {
+    if (entry.isFile() && (entry.name.endsWith('.sh') || entry.name === 'Dockerfile')) {
+      targets.add(path.join(ROOT, entry.name));
+    }
+  }
+  const behavioralDir = path.join(ROOT, 'behavioral-evals');
+  if (fs.existsSync(behavioralDir)) {
+    for (const entry of fs.readdirSync(behavioralDir, { withFileTypes: true })) {
+      if (entry.isFile() && entry.name.endsWith('.md')) targets.add(path.join(behavioralDir, entry.name));
+    }
+  }
+  const opencodeReadme = path.join(ROOT, 'opencode-plugin', 'README.md');
+  if (fs.existsSync(opencodeReadme)) targets.add(opencodeReadme);
+  return [...targets].sort();
+}
+
+const retiredClaimTargets = collectRetiredClaimTargets();
+const retiredClaimHits = new Map(RETIRED_CLAIM_SCAN.map((rule) => [rule.label, []]));
+for (const file of retiredClaimTargets) {
+  const rel = path.relative(ROOT, file).split(path.sep).join('/');
+  if (RETIRED_CLAIM_ALLOWLIST.some((allowed) => allowed.test(rel))) continue;
+  const lines = fs.readFileSync(file, 'utf8').split(/\r?\n/);
+  lines.forEach((line, index) => {
+    for (const rule of RETIRED_CLAIM_SCAN) {
+      if (!rule.pattern.test(line)) continue;
+      if (rule.historicalAllowed && HISTORICAL_CONTEXT.test(line)) continue;
+      retiredClaimHits.get(rule.label).push(`${rel}:${index + 1}`);
+    }
+  });
+}
+for (const rule of RETIRED_CLAIM_SCAN) {
+  const hits = retiredClaimHits.get(rule.label);
+  check(
+    `retired-claim scan: ${rule.label} absent across the agent-facing surface`,
+    hits.length === 0,
+    `stale pre-#190 contract wording at ${hits.join(', ')}`
+  );
+}
+console.log(`Scanned ${retiredClaimTargets.length} file(s) for retired advisory-contract claims.`);
+
 // --- 3+4. Distribution manifests -----------------------------------------
 const pkg = JSON.parse(fs.readFileSync(path.join(ROOT, 'package.json'), 'utf8'));
 const pluginJsonPath = path.join(ROOT, '.claude-plugin', 'plugin.json');

package/ci/mechanism-33-issues-205-207.test.js

@@ -0,0 +1,59 @@
+#!/usr/bin/env node
+'use strict';
+
+const fs = require('fs');
+const os = require('os');
+const path = require('path');
+const { spawnSync } = require('child_process');
+
+const ROOT = path.resolve(__dirname, '..');
+let failed = 0;
+
+function check(condition, message) {
+  if (condition) {
+    console.log(`PASS ${message}`);
+  } else {
+    failed += 1;
+    console.error(`FAIL ${message}`);
+  }
+}
+
+const dockerVerify = fs.readFileSync(path.join(ROOT, 'docker-verify.sh'), 'utf8');
+const legacyStatePath = '.claude/harness-everything/state/sessions/default';
+check(/STATE_DIR=\$\(node -e[\s\S]*getSessionDir\(null, 'default'\)/.test(dockerVerify),
+  '#205 docker verifier resolves one canonical session state directory');
+check(!dockerVerify.includes(legacyStatePath),
+  '#205 docker verifier does not seed or read the legacy repo-relative state directory');
+check((dockerVerify.match(/\$STATE_DIR\//g) || []).length >= 10,
+  '#205 docker verifier routes all state checks through STATE_DIR');
+
+const architecture = fs.readFileSync(path.join(ROOT, 'docs/architecture.md'), 'utf8');
+check(architecture.includes('advisory loop-awareness reminders'),
+  '#206 architecture names loop-awareness as advisory');
+check(!/\bloop budgets\b/.test(architecture),
+  '#206 architecture does not describe retired loop budgets as enforcement');
+
+const commitlintConfig = require(path.join(ROOT, 'commitlint.config.js'));
+check(JSON.stringify(commitlintConfig.rules['subject-case']) === JSON.stringify([2, 'always', 'lower-case']),
+  '#207 commitlint aligns subject-case with repository Conventional Commit history');
+
+const tempDir = fs.mkdtempSync(path.join(os.tmpdir(), 'harness-issue-207-'));
+const messageFile = path.join(tempDir, 'commit-message.txt');
+fs.writeFileSync(messageFile, 'fix(runtime): align post-190 advisory contracts\n', 'utf8');
+const commitlintPackage = require.resolve('@commitlint/cli/package.json');
+const commitlintMeta = JSON.parse(fs.readFileSync(commitlintPackage, 'utf8'));
+const commitlintBin = typeof commitlintMeta.bin === 'string'
+  ? commitlintMeta.bin
+  : commitlintMeta.bin.commitlint;
+const commitlintCli = path.resolve(path.dirname(commitlintPackage), commitlintBin);
+const result = spawnSync(process.execPath, [commitlintCli, '--edit', messageFile], {
+  cwd: ROOT,
+  encoding: 'utf8',
+});
+check(result.status === 0,
+  '#207 representative lowercase repository subject passes commitlint');
+
+fs.rmSync(tempDir, { recursive: true, force: true });
+
+console.log(`\n${failed === 0 ? 'PASS' : 'FAIL'}: issues #205-#207 regression mechanism (${failed} failure${failed === 1 ? '' : 's'})`);
+process.exit(failed === 0 ? 0 : 1);

package/commitlint.config.js

@@ -18,8 +18,8 @@ module.exports = {
         'build'
       ]
     ],
-    'subject-case': [2, 'always', 'sentence-case'],
+    'subject-case': [2, 'always', 'lower-case'],
     'subject-empty': [2, 'never'],
     'header-max-length': [2, 'always', 100]
   }
-};
+};

package/docker-verify.sh

@@ -26,13 +26,12 @@ npm test
 echo -e "\n[Step 3] Running Mechanism Checks..."
 
 # 3a. Rule of 3 Circuit Breaker actually blocks
-# Runtime state lives under .claude/harness-everything/state/sessions/<session_id>/;
-# invocations with no session_id (like these bare/manual calls) fall into a
-# fixed sessions/default/ bucket.
+# Runtime state is resolved once through the same workspace-keyed helper used by
+# the hooks. Invocations with no session_id use the fixed default session.
+STATE_DIR=$(node -e "process.stdout.write(require('./hooks/scripts/lib/harness-state').getSessionDir(null, 'default'))")
 echo -e "\n---> Running 3a: Rule of 3 Circuit Breaker"
-mkdir -p .claude/harness-everything/state/sessions/default
-rm -f .claude/harness-everything/state/sessions/default/zoom-out-report.md
-echo '{"count":3,"lastHash":"verify-test","zoomOutResolved":false}' > .claude/harness-everything/state/sessions/default/rule-of-3-state.json
+rm -f "$STATE_DIR/zoom-out-report.md"
+echo '{"count":3,"lastHash":"verify-test","zoomOutResolved":false}' > "$STATE_DIR/rule-of-3-state.json"
 
 # We expect this to exit with 2 and print CRITICAL trigger message
 set +e
@@ -68,8 +67,8 @@ echo "✅ PASS: Rule of 3 reset check passed."
 
 # 3a-bis. Zoom-out reflection report releases the breaker (self-recovery path)
 echo -e "\n---> Running 3a-bis: Zoom-out report releases the breaker"
-echo '{"count":3,"lastHash":"verify-test","zoomOutResolved":false,"lastFailureAt":0,"zoomOutCycles":0}' > .claude/harness-everything/state/sessions/default/rule-of-3-state.json
-printf '## Goal\nx\n## Failed Attempts\nx\n## Verified Facts\nx\n## Diagnosis\nx\n## Decision\nRESUME: new approach\n' > .claude/harness-everything/state/sessions/default/zoom-out-report.md
+echo '{"count":3,"lastHash":"verify-test","zoomOutResolved":false,"lastFailureAt":0,"zoomOutCycles":0}' > "$STATE_DIR/rule-of-3-state.json"
+printf '## Goal\nx\n## Failed Attempts\nx\n## Verified Facts\nx\n## Diagnosis\nx\n## Decision\nRESUME: new approach\n' > "$STATE_DIR/zoom-out-report.md"
 
 set +e
 node hooks/scripts/rule-of-3.js
@@ -79,31 +78,67 @@ if [ "$EXIT_CODE" -ne 0 ]; then
   echo "❌ FAIL: Valid reflection report did not release the breaker (expected 0, got $EXIT_CODE)"
   exit 1
 fi
-if ! node -e "const s=require('./.claude/harness-everything/state/sessions/default/rule-of-3-state.json'); process.exit(s.count===0 && s.zoomOutResolved===true && s.zoomOutCycles===1 ? 0 : 1)"; then
+if ! node -e "const s=require(process.argv[1]); process.exit(s.count===0 && s.zoomOutResolved===true && s.zoomOutCycles===1 ? 0 : 1)" "$STATE_DIR/rule-of-3-state.json"; then
   echo "❌ FAIL: Breaker state not updated after report release"
-  cat .claude/harness-everything/state/sessions/default/rule-of-3-state.json
+  cat "$STATE_DIR/rule-of-3-state.json"
   exit 1
 fi
 echo "✅ PASS: Valid reflection report released the breaker (self-recovery)."
 
-# Second trip on the same signature must hard-lock even though a report exists
-# (the report is stale relative to lastFailureAt, and the cycle budget is spent).
-node -e "require('fs').writeFileSync('.claude/harness-everything/state/sessions/default/rule-of-3-state.json', JSON.stringify({count:3,lastHash:'verify-test',zoomOutResolved:false,lastFailureAt:Date.now()+60000,zoomOutCycles:1}))"
+# 3a-ter. Re-trip: three more failures on the same signature after a released
+# cycle ask for ANOTHER zoom-out. #190 retired the second-stage escalation, so
+# the contract is exit 2 plus the reflection-required message the hook actually
+# prints - never a permanent lock (ci/mechanism-2a-rule-of-3.test.js:58-64).
+echo -e "\n---> Running 3a-ter: Re-trip requests another zoom-out"
+# Seed through the hooks' own resolver in the already resolved workspace-keyed
+# state root.
+RETRIP_AT=$(node -e "process.stdout.write(String(Date.now()))")
+node -e "require('fs').writeFileSync(process.argv[1], JSON.stringify({count:3,lastHash:'verify-test',zoomOutResolved:false,lastFailureAt:Number(process.argv[2]),zoomOutCycles:1}))" "$STATE_DIR/rule-of-3-state.json" "$RETRIP_AT"
 set +e
 node hooks/scripts/rule-of-3.js 2>rule-of-3-err.log
 EXIT_CODE=$?
 set -e
 if [ "$EXIT_CODE" -ne 2 ]; then
-  echo "❌ FAIL: Second trip did not hard-lock (expected 2, got $EXIT_CODE)"
+  echo "❌ FAIL: Re-trip did not request another zoom-out (expected 2, got $EXIT_CODE)"
   cat rule-of-3-err.log
   exit 1
 fi
-if ! grep -q "hard lock" rule-of-3-err.log; then
-  echo "❌ FAIL: Second-trip output did not contain hard-lock escalation message"
+if ! grep -q "RULE OF 3 CIRCUIT BREAKER TRIGGERED" rule-of-3-err.log; then
+  echo "❌ FAIL: Re-trip output did not contain the circuit-breaker trigger message"
   cat rule-of-3-err.log
   exit 1
 fi
-echo "✅ PASS: Second trip on the same signature hard-locked for human decision."
+if ! grep -q "ACTION REQUIRED (reflect first)" rule-of-3-err.log; then
+  echo "❌ FAIL: Re-trip output did not demand reflection"
+  cat rule-of-3-err.log
+  exit 1
+fi
+# Negative guard: the retired escalation wording must never come back (#190).
+if grep -qi "hard lock" rule-of-3-err.log; then # this must never match
+  echo "❌ FAIL: Re-trip printed the retired hard-lock escalation, which no longer exists"
+  cat rule-of-3-err.log
+  exit 1
+fi
+echo "✅ PASS: Re-trip asked for another zoom-out, with no retired escalation wording."
+
+# A fresh report, written after the re-trip failure, releases the breaker again.
+printf '## Goal\nx\n## Failed Attempts\nx\n## Verified Facts\nx\n## Diagnosis\nx\n## Decision\nRESUME: second untried approach\n' > "$STATE_DIR/zoom-out-report.md"
+set +e
+node hooks/scripts/rule-of-3.js
+EXIT_CODE=$?
+set -e
+if [ "$EXIT_CODE" -ne 0 ]; then
+  echo "❌ FAIL: Fresh reflection report did not release the re-tripped breaker (expected 0, got $EXIT_CODE)"
+  exit 1
+fi
+if ! node -e "const s=JSON.parse(require('fs').readFileSync(process.argv[1],'utf8')); process.exit(s.count===0 && s.zoomOutResolved===true && s.zoomOutCycles===2 ? 0 : 1)" "$STATE_DIR/rule-of-3-state.json"; then
+  echo "❌ FAIL: Breaker state not updated after the second report release"
+  cat "$STATE_DIR/rule-of-3-state.json"
+  exit 1
+fi
+echo "✅ PASS: A fresh report released the re-tripped breaker (advisory re-trip, not an escalation)."
+
+# harness:reset stays an optional manual clear, not a required escalation step.
 npm run harness:reset
 
 
@@ -134,17 +169,17 @@ echo "✅ PASS: Boundary Guard blocked large read successfully."
 
 # 3c. State persistence (WAL) records failure and handles clear
 echo -e "\n---> Running 3c: State persistence (WAL)"
-rm -f .claude/harness-everything/state/sessions/default/handoff-state.json
+rm -f "$STATE_DIR/handoff-state.json"
 
 # Record failure
 echo '{"tool_name":"Bash","tool_response":{"stdout":"","stderr":"npm ERR! verify-test failure"}}' | node hooks/scripts/state-persist.js
 
-if [ ! -f ".claude/harness-everything/state/sessions/default/handoff-state.json" ]; then
+if [ ! -f "$STATE_DIR/handoff-state.json" ]; then
   echo "❌ FAIL: handoff-state.json was not created"
   exit 1
 fi
 
-STATUS=$(node -e "console.log(JSON.parse(require('fs').readFileSync('.claude/harness-everything/state/sessions/default/handoff-state.json','utf8')).status)")
+STATUS=$(node -e "console.log(JSON.parse(require('fs').readFileSync(process.argv[1],'utf8')).status)" "$STATE_DIR/handoff-state.json")
 if [ "$STATUS" != "failed" ]; then
   echo "❌ FAIL: Expected status to be 'failed', got '$STATUS'"
   exit 1
@@ -215,8 +250,8 @@ echo "✅ PASS: Subagent scope guard successfully blocked out-of-scope modificat
 
 # 3f. Stop gate bounces an unverified-edit stop exactly once
 echo -e "\n---> Running 3f: Stop Gate"
-rm -f .claude/harness-everything/state/sessions/default/stop-gate-state.json
-node -e "require('fs').mkdirSync('.claude/harness-everything/state/sessions/default',{recursive:true}); require('fs').writeFileSync('.claude/harness-everything/state/sessions/default/handoff-state.json', JSON.stringify({status:'idle',lastEditAt:Date.now(),lastVerifyAt:0}))"
+rm -f "$STATE_DIR/stop-gate-state.json"
+node -e "require('fs').writeFileSync(process.argv[1], JSON.stringify({status:'idle',lastEditAt:Date.now(),lastVerifyAt:0}))" "$STATE_DIR/handoff-state.json"
 echo "dirty" > .verify-dirty.tmp
 
 set +e
@@ -246,7 +281,7 @@ if [ "$EXIT_CODE" -ne 0 ]; then
 fi
 
 # Loop guard: stop_hook_active always passes
-rm -f .claude/harness-everything/state/sessions/default/stop-gate-state.json
+rm -f "$STATE_DIR/stop-gate-state.json"
 set +e
 echo '{"stop_hook_active":true}' | node hooks/scripts/stop-gate.js
 EXIT_CODE=$?
@@ -255,7 +290,7 @@ if [ "$EXIT_CODE" -ne 0 ]; then
   echo "❌ FAIL: Stop gate blocked despite stop_hook_active (expected 0, got $EXIT_CODE)"
   exit 1
 fi
-rm -f .verify-dirty.tmp .claude/harness-everything/state/sessions/default/handoff-state.json .claude/harness-everything/state/sessions/default/stop-gate-state.json
+rm -f .verify-dirty.tmp "$STATE_DIR/handoff-state.json" "$STATE_DIR/stop-gate-state.json"
 echo "✅ PASS: Stop gate bounced once, then respected the batch and loop guards."
 
 # Clean up temporary test output logs

package/docs/architecture.md

@@ -71,7 +71,7 @@ For selected Fable topologies on Claude:
 - `workflow-stop-gate.js` reports unresolved stage/verification evidence without rejecting Stop;
 - `workflow-disposition.js` records explicit lifecycle/audit decisions; numeric budgets are no longer authoritative control state.
 
-Other topologies use their own applicable mechanisms: loop budgets, regular verification stop-gates, action gates, and task-specific skills. Mechanism coverage is not assumed identical across hosts.
+Other topologies use their own applicable mechanisms: advisory loop-awareness reminders, regular verification stop-gates, action gates, and task-specific skills. Mechanism coverage is not assumed identical across hosts.
 
 ### Scoped runtime advisories and capabilities
 

package/docs/mechanism-first-skill-mesh.md

@@ -55,7 +55,7 @@ HARNESS_DECISION
 tier: 2
 strategy: iterative-single
 workflow_state: active
-required: route-before-execution, objective-verification, loop-budget
+required: scope-lock, objective-verification, loop-awareness
 suggest: tdd, verification-loop
 suggestion_policy: evaluate-applicability
 escape_policy: workflow-uncovered-scope-only

package/docs/workflows/zoom-out.md

@@ -4,7 +4,7 @@
 
 Source of truth: `zoom-out/SKILL.md`.
 
-Contract summary from SKILL.md — Trigger: three same-signature failures or an explicit loop/rethink request. Output: fact-checked report ending in `RESUME` or `ESCALATE`. State: writes the session `zoom-out-report.md`; reset may clear breaker state. Gate: `hooks/scripts/rule-of-3.js` plus a valid report; reset only after the second cycle. USE FOR: "you are stuck in a loop", "the same error keeps failing", "rethink your assumptions". DO NOT USE FOR: routine single-failure debugging, greenfield planning without failures.
+Contract summary from SKILL.md — Trigger: three same-signature failures or an explicit loop/rethink request. Output: fact-checked report ending in `RESUME` or `ESCALATE`. State: writes the session `zoom-out-report.md`; reset may clear breaker state. Gate: `hooks/scripts/rule-of-3.js` plus a valid report; a later three-failure cycle requests another reflection. USE FOR: "you are stuck in a loop", "the same error keeps failing", "rethink your assumptions". DO NOT USE FOR: routine single-failure debugging, greenfield planning without failures.
 
 ## 1. Skill Behavior Workflow
 
@@ -16,9 +16,9 @@ graph TD
   Fill --> Decide{RESUME or ESCALATE?}
   Decide -->|untried path| Resume[RESUME On Untried Path]
   Decide -->|genuine user decision| Escalate[ESCALATE With Options]
-  Resume --> Again{Repeated Breaker Cycle?}
-  Again -->|second cycle| Reset[npm run harness reset]
-  Reset --> Evolve[Record Insight With self-evolve]
+  Resume --> Again{Three More Matching Failures?}
+  Again -->|yes| Cycle[Another Zoom-Out Cycle]
+  Cycle --> Evolve[Record Insight With self-evolve]
   Again -->|no| Done([Report Complete])
   Escalate --> Done
 ```
@@ -47,7 +47,7 @@ graph TD
   Write --> Choice{Untried Path Exists?}
   Choice -->|yes| Resume2[RESUME On Untried Path]
   Choice -->|no| Esc2[ESCALATE With Options]
-  Resume2 -->|repeated cycle| Reset2[npm run harness reset Then self-evolve]
+  Resume2 -->|three more matching failures| Cycle2[Another Zoom-Out Cycle Then self-evolve]
 ```
 
 Template: `zoom-out/templates/zoom-out-report.template.md`. Enforcement: `hooks/scripts/rule-of-3.js`. Deep dive: `zoom-out/references/circuit-breaker.md`.
@@ -58,5 +58,5 @@ Template: `zoom-out/templates/zoom-out-report.template.md`. Enforcement: `hooks/
 - [ ] Goal, files, configuration, and logs were rechecked with read-only tools before any resume
 - [ ] `templates/zoom-out-report.template.md` was filled and the session `zoom-out-report.md` ends in `RESUME` or `ESCALATE`
 - [ ] Resume targeted only an untried path; genuine user decisions were escalated with options
-- [ ] Reset via `npm run harness:reset` happened only after the second cycle, with the insight recorded via `self-evolve`
+- [ ] A later three-failure cycle ran another zoom-out; `npm run harness:reset` was used only as an optional manual clear, with the insight recorded via `self-evolve`
 - [ ] Routine single-failure debugging and greenfield planning without failures were not routed here

package/fable-mode/CONTRACT-FORMAT.md

@@ -2,7 +2,8 @@
 
 Issue #85 Phase 3 makes the stage map a machine-readable execution contract.
 The router still chooses only the execution topology. Fable owns the stage map,
-model selector, worker briefs, stage audit, replan budget, and cold verifier.
+model selector, worker briefs, stage audit, advisory replan limits, and cold
+verifier.
 Phase 4 adds an optional bounded ensemble modifier without creating a new base
 topology.
 

package/fable-mode/SKILL.md

@@ -4,7 +4,7 @@ description: "Stage large, multi-source or multi-session tasks through a written
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.16.2
+  version: 0.16.3
 ---
 
 # Fable Mode (v3)

package/fable-mode/agents/fable-orchestrator.md

@@ -77,11 +77,12 @@ spawn workers.
 
 For `fable-parallel`, spawn only stages in the same validated execution batch;
 never invent an additional parallel edge. A stage depending on another stage is
-not in the same ready batch. Never exceed `workflowPlan.limits.maxWorkers`. The router plan is the numeric
-source of truth; `workflow-plan-consumer.js` chunks ready sets to that cap and
-runtime worker leases enforce it when the host exposes stable worker IDs. For
-other Fable strategies, serialize the returned batches unless a later validated
-plan says otherwise.
+not in the same ready batch. Treat `workflowPlan.limits.maxWorkers` as a
+planning cap you are expected to respect: it is advisory. `workflow-plan-consumer.js`
+returns every dependency-ready stage without chunking to that cap, and nothing
+leases or counts workers at runtime, so exceeding it is your own judgement call,
+not a blocked action. For other Fable strategies, serialize the returned batches
+unless a later validated plan says otherwise.
 
 **3. Verify with a check that can fail — external artifacts only.** Each stage
 defines a pass condition an external artifact satisfies: a test that runs, a file

package/fable-mode/execution-guardrails/SKILL.md

@@ -7,7 +7,7 @@ description: >-
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.16.2
+  version: 0.16.3
 ---
 
 # Execution Guardrails

package/fable-mode/fable-haiku/SKILL.md

@@ -4,7 +4,7 @@ description: "Run staged fable work on Haiku for bulk mechanical tasks with expl
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.16.2
+  version: 0.16.3
 ---
 
 # Fable Mode — Haiku

package/fable-mode/fable-opus/SKILL.md

@@ -4,7 +4,7 @@ description: "Run staged fable orchestration on Opus for cross-stage synthesis,
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.16.2
+  version: 0.16.3
 ---
 
 # Fable Mode — Opus

package/fable-mode/fable-sonnet/SKILL.md

@@ -4,7 +4,7 @@ description: "Run staged fable work on Sonnet for non-trivial implementation, re
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.16.2
+  version: 0.16.3
 ---
 
 # Fable Mode — Sonnet

package/harness-everything/SKILL.md

@@ -4,7 +4,7 @@ description: "Route software/project work through the Harness kernel: classify T
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.16.2
+  version: 0.16.3
 ---
 
 # Harness Everything

package/harness-everything/references/router-workflow-plan.md

@@ -110,7 +110,7 @@ This does not choose a topology and does not itself enforce the gate. Phase 5 ow
 
 Examples:
 
-- `objective-verification` and `loop-budget` are mandatory for `iterative-single`;
+- `loop-awareness` and `objective-verification` are mandatory for `iterative-single`, on top of the base `scope-lock`, `verify-before-claim`, and `replan-after-repeated-failure`;
 - `tdd` and `verification-loop` remain advisory skill suggestions;
 - `stage-contracts` and `cold-verification` are mandatory for Fable topologies;
 - `multi-agent-workspace` is suggested only when the selected topology actually requires durable workspace behavior.

package/opencode-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "harness-enforcement",
   "description": "Repository inventory for the opencode enforcement plugin and its standalone helper",
-  "version": "0.16.2",
+  "version": "0.16.4",
   "runtime": "index.mjs",
   "hooks": {
     "verify": "hooks/verify.js"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "harness-everything",
-  "version": "0.16.2",
+  "version": "0.16.4",
   "description": "Harness OS: An Orchestrated Agent Operating System for AI-driven Development",
   "main": "harness-everything/scripts/bootstrap.js",
   "bin": {

package/plugins/harness-everything/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "harness-everything",
-  "version": "0.16.2",
+  "version": "0.16.4",
   "description": "Invariant-first engineering harness for routing, verification, and failure recovery while preserving agent autonomy.",
   "author": {
     "name": "Miya Daniel",

package/plugins/harness-everything/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "harness-everything",
-  "version": "0.16.2",
+  "version": "0.16.4",
   "description": "Invariant-first engineering harness for routing, verification, and failure recovery while preserving agent autonomy.",
   "author": {
     "name": "Miya Daniel",

package/plugins/harness-everything/skills/fable-mode/CONTRACT-FORMAT.md

@@ -2,7 +2,8 @@
 
 Issue #85 Phase 3 makes the stage map a machine-readable execution contract.
 The router still chooses only the execution topology. Fable owns the stage map,
-model selector, worker briefs, stage audit, replan budget, and cold verifier.
+model selector, worker briefs, stage audit, advisory replan limits, and cold
+verifier.
 Phase 4 adds an optional bounded ensemble modifier without creating a new base
 topology.
 

package/plugins/harness-everything/skills/fable-mode/SKILL.md

@@ -4,7 +4,7 @@ description: "Stage large, multi-source or multi-session tasks through a written
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.16.2
+  version: 0.16.3
 ---
 
 # Fable Mode (v3)

package/plugins/harness-everything/skills/fable-mode/agents/fable-orchestrator.md

@@ -77,11 +77,12 @@ spawn workers.
 
 For `fable-parallel`, spawn only stages in the same validated execution batch;
 never invent an additional parallel edge. A stage depending on another stage is
-not in the same ready batch. Never exceed `workflowPlan.limits.maxWorkers`. The router plan is the numeric
-source of truth; `workflow-plan-consumer.js` chunks ready sets to that cap and
-runtime worker leases enforce it when the host exposes stable worker IDs. For
-other Fable strategies, serialize the returned batches unless a later validated
-plan says otherwise.
+not in the same ready batch. Treat `workflowPlan.limits.maxWorkers` as a
+planning cap you are expected to respect: it is advisory. `workflow-plan-consumer.js`
+returns every dependency-ready stage without chunking to that cap, and nothing
+leases or counts workers at runtime, so exceeding it is your own judgement call,
+not a blocked action. For other Fable strategies, serialize the returned batches
+unless a later validated plan says otherwise.
 
 **3. Verify with a check that can fail — external artifacts only.** Each stage
 defines a pass condition an external artifact satisfies: a test that runs, a file

package/plugins/harness-everything/skills/fable-mode/execution-guardrails/SKILL.md

@@ -7,7 +7,7 @@ description: >-
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.16.2
+  version: 0.16.3
 ---
 
 # Execution Guardrails

package/plugins/harness-everything/skills/fable-mode/fable-haiku/SKILL.md

@@ -4,7 +4,7 @@ description: "Run staged fable work on Haiku for bulk mechanical tasks with expl
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.16.2
+  version: 0.16.3
 ---
 
 # Fable Mode — Haiku

package/plugins/harness-everything/skills/fable-mode/fable-opus/SKILL.md

@@ -4,7 +4,7 @@ description: "Run staged fable orchestration on Opus for cross-stage synthesis,
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.16.2
+  version: 0.16.3
 ---
 
 # Fable Mode — Opus

package/plugins/harness-everything/skills/fable-mode/fable-sonnet/SKILL.md

@@ -4,7 +4,7 @@ description: "Run staged fable work on Sonnet for non-trivial implementation, re
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.16.2
+  version: 0.16.3
 ---
 
 # Fable Mode — Sonnet

package/plugins/harness-everything/skills/harness-everything/SKILL.md

@@ -4,7 +4,7 @@ description: "Route software/project work through the Harness kernel: classify T
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.16.2
+  version: 0.16.3
 ---
 
 # Harness Everything

package/plugins/harness-everything/skills/harness-everything/references/router-workflow-plan.md

@@ -110,7 +110,7 @@ This does not choose a topology and does not itself enforce the gate. Phase 5 ow
 
 Examples:
 
-- `objective-verification` and `loop-budget` are mandatory for `iterative-single`;
+- `loop-awareness` and `objective-verification` are mandatory for `iterative-single`, on top of the base `scope-lock`, `verify-before-claim`, and `replan-after-repeated-failure`;
 - `tdd` and `verification-loop` remain advisory skill suggestions;
 - `stage-contracts` and `cold-verification` are mandatory for Fable topologies;
 - `multi-agent-workspace` is suggested only when the selected topology actually requires durable workspace behavior.