harness-everything 0.16.3 → 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.3",
+      "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.3",
+  "version": "0.16.4",
   "author": {
     "name": "Miya Daniel"
   },

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 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

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,9 +78,9 @@ 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)."
@@ -91,11 +90,8 @@ echo "✅ PASS: Valid reflection report released the breaker (self-recovery)."
 # 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: since #42 runtime state lives in the
-# global, workspace-keyed state root ($HARNESS_STATE_HOME or
-# ~/.agents/harness-everything/...), and a repo-relative seed only reaches the
-# hook while the one-time legacy migration can still move it.
-STATE_DIR=$(node -e "process.stdout.write(require('./hooks/scripts/lib/harness-state').getSessionDir(null, 'default'))")
+# 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
@@ -173,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
@@ -254,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
@@ -285,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=$?
@@ -294,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/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.3",
+  "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.3",
+  "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.3",
+  "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.3",
+  "version": "0.16.4",
   "description": "Invariant-first engineering harness for routing, verification, and failure recovery while preserving agent autonomy.",
   "author": {
     "name": "Miya Daniel",