harness-everything 0.18.0 → 0.19.0

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.18.0",
+  "version": "0.19.0",
   "runtime": "index.mjs",
   "hooks": {
     "verify": "hooks/verify.js"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "harness-everything",
-  "version": "0.18.0",
+  "version": "0.19.0",
   "description": "Harness OS: An Orchestrated Agent Operating System for AI-driven Development",
   "main": "harness-everything/scripts/bootstrap.js",
   "bin": {
@@ -17,7 +17,7 @@
     "repo:contract": "node scripts/repository-contract.js",
     "docs:sync": "node scripts/sync-current-docs.js",
     "test:repo-contract": "node ci/repository-contract.test.js",
-    "test:consistency": "node ci/consistency-check.js && node ci/doc-capability-consistency.test.js && node ci/repository-contract.test.js",
+    "test:consistency": "node ci/consistency-check.js && node ci/doc-capability-consistency.test.js && node ci/repository-contract.test.js && node ci/mechanism-2ao-plugin-sync.test.js",
     "test:docs:capabilities": "node ci/doc-capability-consistency.test.js",
     "test:references": "node ci/reference-check.js",
     "test:release": "node ci/release-consistency-check.js && node ci/mechanism-2x-release-automation.test.js && node ci/mechanism-2x-release-commit-message.test.js",
@@ -28,10 +28,12 @@
     "test:routing": "node ci/routing-check.js",
     "test:routing:invariants": "node ci/invariant-routing.test.js && node ci/router-workflow-plan.test.js && node ci/workflow-execution-contract.test.js",
     "plugin:sync": "node scripts/sync-openai-plugin.js",
+    "plugin:hosts": "node scripts/plugin-sync.js",
     "test:plugin:claude": "node ci/mechanism-2z-claude-plugin-manifest.test.js",
     "plugin:claude:stage": "node scripts/stage-claude-plugin.js",
     "plugin:claude:validate": "node scripts/validate-claude-plugin.js",
     "test:plugin:openai": "node ci/openai-plugin-package.test.js && node ci/openai-plugin-runtime.test.js",
+    "test:plugin:hosts": "node ci/mechanism-2ao-plugin-sync.test.js",
     "plugin:submission:build": "node scripts/build-openai-submission.js",
     "test:plugin:submission": "node ci/openai-plugin-submission.test.js",
     "test:platform:compatibility": "node ci/mechanism-2w-platform-compatibility.test.js",

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

@@ -1,6 +1,6 @@
 {
   "name": "harness-everything",
-  "version": "0.18.0",
+  "version": "0.19.0",
   "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.18.0",
+  "version": "0.19.0",
   "description": "Invariant-first engineering harness for routing, verification, and failure recovery while preserving agent autonomy.",
   "author": {
     "name": "Miya Daniel",

package/plugins/harness-everything/scripts/lib/advisory-text.js

@@ -15,15 +15,16 @@ const advisoryInstructions = [
   `2. For EVERY suggested skill, read its complete \`SKILL.md\` entry and evaluate applicability from \`USE FOR\`, \`DO NOT USE FOR\`, and its basic flow.`,
   `3. Treat the selected workflow topology and numeric limits as planning guidance, not a lock. Choose, combine, reorder, or skip steps when evidence supports it.`,
   `4. Prefer objective verification before declaring done and worktree isolation for broad/Tier-3 mutation.`,
-  `5. Use the routing checkpoint as source state for the first Harness Status; do not expose a competing progress format.`,
+  `5. Use the routing checkpoint only as internal source state for the first Harness Status; do not render a competing progress block.`,
   ``,
   `## 📣 USER-VISIBLE STATUS (MUST)`,
-  `For non-trivial software/project work, this semantic communication contract is mandatory even when the host integration itself is instruction-only:`,
-  `- \`Harness Status\``,
-  `- \`Current:\` what is being done now`,
-  `- \`Read/Evidence:\` important files, sources, or evidence read/confirmed`,
-  `- \`Next:\` the next intended action`,
-  `- \`Blocked/Risk:\` only when materially applicable`,
+  `For non-trivial software/project work, this semantic communication contract is mandatory even when the host integration itself is instruction-only. Render this Markdown shape:`,
+  `### 🚦 Harness Status`,
+  ``,
+  `- **Current:** <what is being done now>`,
+  `- **Read / Evidence:** <one short item inline, or nested bullets when there are multiple items>`,
+  `- **Next:** <next intended action>`,
+  `- **Risk / Blocked:** <only when materially applicable; omit otherwise>`,
   `Emit it before substantive execution, after a major phase, when direction materially changes, at meaningful long-running phase boundaries, and before final completion. This MUST does not imply a hard runtime lock.`,
   ``,
   `## 🤖 COGNITIVE COMPLIANCE`,
@@ -145,7 +146,7 @@ function buildCodexGlobalContent() {
     ``,
     `- Discover the environment and host capabilities before relying on them.`,
     `- For software/project work, run \`npx github:dyphn1/Harness-everything next "<summary>"\` before mutation and use the routing checkpoint as source state for the first Harness Status.`,
-    `- For non-trivial work, MUST keep the user informed with one Harness Status shape: Current, Read/Evidence, Next, plus Blocked/Risk only when material; repeat it at major phase/direction boundaries and before final completion.`,
+    `- For non-trivial work, MUST render one Markdown \`### 🚦 Harness Status\` with bullet-aligned bold \`Current\`, \`Read / Evidence\`, \`Next\`, and optional \`Risk / Blocked\`; repeat it at major phase/direction boundaries and before final completion.`,
     `- Read every suggested skill's complete \`SKILL.md\` entry before resolving applicability; do not omit it from metadata or confidence alone.`,
     `- Use the selected workflow topology as planning guidance; the model may adapt or skip steps with an explicit evidence-based reason.`,
     `- Do not impose a universal TODO/TDD/Fable sequence; use the smallest useful topology plus applicable skills.`,

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.18.0
+  version: 0.18.1
 ---
 
 # Harness Everything
@@ -23,12 +23,12 @@ Kernel routing entry.
 2. **Verify before claim** — seek objective evidence before saying work is done.
 3. **Zoom out on repetition** — after 3 same-signature failures, use `zoom-out`.
 4. **Evaluate before omission** — read each suggested skill's `SKILL.md` before deciding applicability.
-5. **Surface status** — non-trivial work MUST use one `Harness Status`: `Current`, `Read/Evidence`, `Next`, optional `Blocked/Risk`, at major phase/direction boundaries.
+5. **Surface status** — non-trivial work MUST render `### 🚦 Harness Status` with bold bullets: `Current`, `Read / Evidence`, `Next`; optional `Risk / Blocked`.
 6. **Keep agency** — workflow state and numeric limits guide; they do not hard-stop execution.
 
 ## Workflow
 1. Reuse kernel output, or run `node "<this-skill-dir>/scripts/kernel-router.js" "<prompt summary>"`.
-2. Use the **Harness Routing Checkpoint** to populate the first Harness Status; it is not a second progress format.
+2. Keep the **Harness Routing Checkpoint** internal; never render it separately.
 3. Read each suggested `SKILL.md`; evaluate `USE FOR`, `DO NOT USE FOR`, workflow/basic flow, and hard rules.
 4. Use the selected topology as planning guidance. Choose, combine, reorder, or skip steps when evidence supports doing so.
 5. Prefer worktree isolation for broad/Tier-3 mutation and objective verification before completion.

package/plugins/harness-everything/skills/harness-everything/references/triage-and-tiers.md

@@ -151,23 +151,28 @@ Never turn mechanism/package evidence into a cross-host live-enforcement claim.
 
 ## 6. User-visible status contract
 
-For non-trivial software/project work, user-facing progress **MUST** use one stable shape across direct, iterative, Fable, and multi-agent execution:
-
-```text
-Harness Status
-- Current: <what is being done now>
-- Read/Evidence: <important files/sources/evidence read or confirmed>
-- Next: <next intended action>
-- Blocked/Risk: <only when materially applicable>
+For non-trivial software/project work, user-facing progress **MUST** use one stable Markdown shape across direct, iterative, Fable, and multi-agent execution:
+
+```md
+### 🚦 Harness Status
+
+- **Current:** <what is being done now>
+- **Read / Evidence:**
+  - <important file/source/evidence read or confirmed>
+  - <another item when multiple evidence items improve scanability>
+- **Next:** <next intended action>
+- **Risk / Blocked:** <only when materially applicable; omit otherwise>
 ```
 
+When there is only one short evidence item, keep it inline on the **Read / Evidence** bullet. Use nested bullets when multiple items would otherwise become one dense sentence.
+
 Emit it before substantive execution, after a major phase completes, when the plan/assumption/direction materially changes, at meaningful phase boundaries during long-running work, and before final completion. The final response may merge the last status naturally.
 
 This is a semantic communication MUST. It does **not** create a runtime lock, counter, reset requirement, or permission boundary. The routing checkpoint below is source state for this format, not a second competing progress template.
 
 ## 7. Routing Checkpoint
 
-For software/project work, consume this runtime state when producing the first Harness Status:
+For software/project work, consume this internal runtime state when producing the first Harness Status; do not render the checkpoint as a separate user-facing block:
 
 ```markdown
 ## 🚦 Harness Routing Checkpoint

package/plugins/harness-everything/skills/harness-everything/scripts/kernel-router-core.js

@@ -24,7 +24,7 @@ const { applyEnsemblePolicy } = require('./ensemble-policy');
 const INVARIANT_TEXT = {
   'scope-lock': 'Route before execution: stay inside the authorized task/repository scope.',
   'verify-before-claim': 'Verify before claim: completion claims require objective evidence appropriate to the change.',
-  'visible-status-updates': 'User-visible status is mandatory: use the single Harness Status format with Current, Read/Evidence, and Next at required phase boundaries; add Blocked/Risk only when materially applicable.',
+  'visible-status-updates': 'User-visible status is mandatory: render the single Markdown Harness Status with a visible heading, bullet-aligned bold labels, Current, Read / Evidence, and Next; add Risk / Blocked only when materially applicable.',
   'replan-after-repeated-failure': 'Re-plan on repetition: after 3 same-signature failures, stop micro-retrying and zoom out/re-diagnose.',
   'evaluate-suggestions-before-skip': 'Evaluate before skip: read each suggested skill\'s complete SKILL.md entry/basic flow before omitting it.',
   'loop-awareness': 'When iterative work runs long, remind the agent to verify assumptions or re-plan; never hard-stop on a count.',
@@ -149,7 +149,7 @@ function printRoutingCheckpoint(plan) {
   const invariants = Array.isArray(plan.requiredInvariants) ? plan.requiredInvariants : [];
   const suggestions = uniqueSuggestedSkills(plan);
 
-  console.log('\n=> HARNESS ROUTING CHECKPOINT (REQUIRED VISIBLE STATE):');
+  console.log('\n=> HARNESS ROUTING CHECKPOINT (INTERNAL SOURCE STATE — DO NOT RENDER SEPARATELY):');
   console.log(`   - Tier: ${displayTier(plan.tier)}`);
   console.log(`   - Strategy: ${plan.strategy || 'deferred'}`);
   console.log(`   - Required invariants: ${invariants.length ? invariants.join(', ') : 'none'}`);
@@ -169,12 +169,16 @@ function printKernelContract(plan) {
   }
 
   console.log('\n=> USER-VISIBLE HARNESS STATUS CONTRACT (MUST):');
-  console.log('   - For non-trivial software/project work, the agent MUST use one compact user-visible status format:');
-  console.log('     Harness Status');
-  console.log('     - Current: <what is being done now>');
-  console.log('     - Read/Evidence: <important files/sources/evidence read or confirmed>');
-  console.log('     - Next: <next intended action>');
-  console.log('     - Blocked/Risk: <only when materially applicable>');
+  console.log('   - For non-trivial software/project work, the agent MUST render this single Markdown status shape:');
+  console.log('     ### 🚦 Harness Status');
+  console.log('');
+  console.log('     - **Current:** <what is being done now>');
+  console.log('     - **Read / Evidence:**');
+  console.log('       - <important file/source/evidence read or confirmed>');
+  console.log('       - <another item when multiple evidence items improve scanability>');
+  console.log('     - **Next:** <next intended action>');
+  console.log('     - **Risk / Blocked:** <only when materially applicable; omit otherwise>');
+  console.log('   - Keep evidence inline when there is only one short item; use nested bullets when there are multiple items.');
   console.log('   - Emit it before substantive execution, after a major phase, when direction materially changes, at meaningful long-running phase boundaries, and before final completion (the final response may merge it naturally).');
   console.log('   - This is a semantic communication MUST, not a hard execution lock, counter, or reset condition.');
 

package/scripts/lib/advisory-text.js

@@ -15,15 +15,16 @@ const advisoryInstructions = [
   `2. For EVERY suggested skill, read its complete \`SKILL.md\` entry and evaluate applicability from \`USE FOR\`, \`DO NOT USE FOR\`, and its basic flow.`,
   `3. Treat the selected workflow topology and numeric limits as planning guidance, not a lock. Choose, combine, reorder, or skip steps when evidence supports it.`,
   `4. Prefer objective verification before declaring done and worktree isolation for broad/Tier-3 mutation.`,
-  `5. Use the routing checkpoint as source state for the first Harness Status; do not expose a competing progress format.`,
+  `5. Use the routing checkpoint only as internal source state for the first Harness Status; do not render a competing progress block.`,
   ``,
   `## 📣 USER-VISIBLE STATUS (MUST)`,
-  `For non-trivial software/project work, this semantic communication contract is mandatory even when the host integration itself is instruction-only:`,
-  `- \`Harness Status\``,
-  `- \`Current:\` what is being done now`,
-  `- \`Read/Evidence:\` important files, sources, or evidence read/confirmed`,
-  `- \`Next:\` the next intended action`,
-  `- \`Blocked/Risk:\` only when materially applicable`,
+  `For non-trivial software/project work, this semantic communication contract is mandatory even when the host integration itself is instruction-only. Render this Markdown shape:`,
+  `### 🚦 Harness Status`,
+  ``,
+  `- **Current:** <what is being done now>`,
+  `- **Read / Evidence:** <one short item inline, or nested bullets when there are multiple items>`,
+  `- **Next:** <next intended action>`,
+  `- **Risk / Blocked:** <only when materially applicable; omit otherwise>`,
   `Emit it before substantive execution, after a major phase, when direction materially changes, at meaningful long-running phase boundaries, and before final completion. This MUST does not imply a hard runtime lock.`,
   ``,
   `## 🤖 COGNITIVE COMPLIANCE`,
@@ -145,7 +146,7 @@ function buildCodexGlobalContent() {
     ``,
     `- Discover the environment and host capabilities before relying on them.`,
     `- For software/project work, run \`npx github:dyphn1/Harness-everything next "<summary>"\` before mutation and use the routing checkpoint as source state for the first Harness Status.`,
-    `- For non-trivial work, MUST keep the user informed with one Harness Status shape: Current, Read/Evidence, Next, plus Blocked/Risk only when material; repeat it at major phase/direction boundaries and before final completion.`,
+    `- For non-trivial work, MUST render one Markdown \`### 🚦 Harness Status\` with bullet-aligned bold \`Current\`, \`Read / Evidence\`, \`Next\`, and optional \`Risk / Blocked\`; repeat it at major phase/direction boundaries and before final completion.`,
     `- Read every suggested skill's complete \`SKILL.md\` entry before resolving applicability; do not omit it from metadata or confidence alone.`,
     `- Use the selected workflow topology as planning guidance; the model may adapt or skip steps with an explicit evidence-based reason.`,
     `- Do not impose a universal TODO/TDD/Fable sequence; use the smallest useful topology plus applicable skills.`,