harness-everything 0.19.0 → 0.19.1

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

@@ -4,7 +4,7 @@ description: Break a to-spec feature-spec, a plan, or a conversation into tracer
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.12.0
+  version: 0.19.1
 ---
 
 # To Tickets
@@ -33,7 +33,7 @@ Cuts a plan or spec into tracer-bullet vertical slices, each declaring its block
 ## Process
 
 1. Resolve path: script check (Exit 0 = configured location) → workspace convention dirs → platform fallback (`.claude`/`.github`/`.cursor` + `/harness-everything/tickets/`).
-2. Gather context: prefer a referenced to-spec spec — design-audit verification MANDATORY first, else refuse; no spec is fine.
+2. Gather context: **SHOULD** use a referenced to-spec spec when available — design-audit verification is MANDATORY first, else refuse; no spec is fine.
 3. Explore codebase (optional): evidence-cited findings only; prefactor first.
 4. Draft vertical slices: complete path through every layer, demoable alone, one context window each; declare blocking edges.
 5. Quiz the user on granularity and edges until approved (MANDATORY gate).

package/plugins/harness-everything/skills/using-git-worktrees/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: using-git-worktrees
-description: Use when starting feature work needing isolation or before implementation plans - recommends an isolated workspace via native tools or git worktree fallback
+description: Use when work needs isolation or before major implementation plans - resolves workspace isolation via native tools or git worktree fallback, with an explicit degraded fallback when isolation is unavailable
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.16.1
+  version: 0.19.1
 ---
 
 # Using Git Worktrees
@@ -13,9 +13,9 @@ Use native worktree support first; raw Git is the fallback.
 
 ## Contract
 
-- **Major workflow guidance** — Tier 3 / Fable-class engineering is safer in a linked worktree before broad source/artifact mutation. Reuse one or create one when practical.
-- **Ordinary mode** — isolation-needing feature work may honor an explicit user preference to stay in place.
-- Never nest a worktree inside an already isolated worktree.
+- **Tier 3 / Fable (MUST resolve)** — before broad source/artifact mutation, reuse/create a verified linked worktree. If isolation is unavailable or the user explicitly chooses to stay in place, MUST report an explicit degraded fallback/risk before continuing.
+- **Ordinary mode (SHOULD)** — use isolation when it materially reduces collision/risk; explicit user preference may keep work in place.
+- **MUST NOT** nest a worktree inside an already isolated worktree.
 
 ## Workflow
 
@@ -28,7 +28,7 @@ git rev-parse --show-superproject-working-tree
 ```
 Different git/common dirs and no superproject => already isolated; continue to Step 2. A submodule is a normal repo for this check.
 
-**Step 1 — Create/enter**: prefer native `EnterWorktree`, `/worktree`, or `--worktree`. Otherwise use `git worktree add "$path" -b "$BRANCH_NAME"`. Prefer an already-ignored or external/sibling path. If creation/entry fails, report it and continue only with explicit awareness of the isolation risk.
+**Step 1 — Create/enter**: use native `EnterWorktree`, `/worktree`, or `--worktree` first; otherwise use `git worktree add "$path" -b "$BRANCH_NAME"`. Use an already-ignored or external/sibling path when possible. If creation/entry fails, MUST surface the degraded isolation disposition before continuing.
 
 **Step 2 — Setup**: install project dependencies as needed.
 

package/rewrite-commits/SKILL.md

@@ -4,7 +4,7 @@ description: "Rewrite past Git history to comply with Angular Style conventions.
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.4.0
+  version: 0.19.1
 ---
 
 # Rewrite Commits
@@ -31,7 +31,7 @@ metadata:
 ## Workflow
 
 1. `[Discover]` Run `git log --oneline -n <num>` to confirm the range. If commits were already pushed to remote `main`/`master`, warn and require secondary human confirmation.
-2. `[Think] & [Try]` Create a temp branch. Never run bare interactive `git rebase -i`; prefer `git reset --soft HEAD~<N>` plus structured commits, or Node.js scripting (no hardcoded `sed -i`). Messages MUST follow Angular Style per the `git-commit` skill.
+2. `[Think/Try]` Create a temp branch. **MUST NOT** use bare `git rebase -i`; **SHOULD** use `git reset --soft HEAD~<N>` + structured commits or Node.js (no hardcoded `sed -i`). Messages MUST follow `git-commit`.
 3. `[Summarize]` Run `git log --oneline` for confirmation. On merge conflict, run `git rebase --abort`, STOP, and hand over to human decision or trigger `zoom-out`.
 
 Deep dive: <this-skill-dir>/references/workflow.md

package/scripts/lib/advisory-text.js

@@ -7,14 +7,14 @@ const MARKER = "Harness OS Guidance (Advisory)";
 
 const advisoryInstructions = [
   `\n# ${MARKER}`,
-  `Harness is an observer/router/reminder layer on this surface; do not treat its workflow guidance as a hard scheduler.`,
+  `Harness is an observer/router/reminder layer on this surface. Instruction/advisory delivery describes the mechanism, not semantic optionality; do not treat Harness as a hard scheduler.`,
   ``,
-  `## 🚦 ENTRY TRIAGE & WORKFLOW GUIDANCE`,
+  `## 🚦 ENTRY TRIAGE & SEMANTIC CONTRACT`,
   `For software/project work, load the \`harness-everything\` skill and establish routing context before broad mutation:`,
-  `1. Run \`npx github:dyphn1/Harness-everything next "<Brief summary of user's prompt>"\` when terminal execution is available.`,
-  `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.`,
+  `1. MUST route before broad mutation; run \`npx github:dyphn1/Harness-everything next "<Brief summary of user's prompt>"\` when terminal execution is available and no equivalent routing state was injected.`,
+  `2. MUST read/evaluate EVERY suggested skill. If applicable, MUST follow its core contract; if not-applicable, keep a flow-grounded reason.`,
+  `3. Selected-topology required obligations are MUSTs. Implementation tactics MAY adapt; numeric iteration/revision/replan/worker values MAY guide planning but never hard-block.`,
+  `4. MUST verify before claiming completion. Tier-3/Fable broad mutation MUST resolve isolation: linked worktree or explicit degraded fallback.`,
   `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)`,
@@ -31,10 +31,11 @@ const advisoryInstructions = [
   `- **No universal skill pipeline**: do not force every task through TODO/TDD/Fable.`,
   `- **Rule of 3**: after 3 same-signature failures, stop micro-retrying and use a fresh diagnosis / zoom-out. This reflection boundary may block mutation until completed.`,
   `- **Permission boundaries are separate**: explicit host/user approval for destructive or external actions remains authoritative.`,
-  `- **Verification is evidence, not a cage**: missing evidence should trigger a reminder, not a persistent workflow lock.`,
-  `- **Environment discovery**: discover OS, shell, package manager/runtime, and host capability before relying on them.`,
-  `- **Memory / self-evolve**: persist only verified reusable lessons.`,
-  `- **Prefer editing**: prefer targeted edits and logically complete commits over broad rewrites.`,
+  `- **Contract strength**: MUST = required semantic obligation; SHOULD = default with evidence-based exception; MAY = optional optimization. Reminder-only mechanics never downgrade MUST.`,
+  `- **Verification is evidence, not a cage**: MUST verify before completion claims; host hooks may remind rather than persistently block.`,
+  `- **Environment discovery**: MUST establish relevant OS/shell/toolchain/host facts before relying on environment-sensitive behavior.`,
+  `- **Memory / self-evolve**: durable writes MUST be authorized by the active workflow/session contract and backed by verified reusable evidence.`,
+  `- **Editing / commits**: targeted edits SHOULD be preferred; before committing, MUST inspect the staged diff and SHOULD split unrelated concerns.`,
   ``
 ].join('\n');
 
@@ -144,15 +145,16 @@ function buildCodexGlobalContent() {
     `# ${MARKER}`,
     `This instruction surface cannot be assumed to provide hard lifecycle blocking.`,
     ``,
-    `- 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.`,
+    `- MUST establish relevant environment/host facts before relying on environment-sensitive behavior.`,
+    `- For software/project work, MUST establish routing before broad mutation; use \`npx github:dyphn1/Harness-everything next "<summary>"\` when terminal execution is available and routing state was not already injected.`,
     `- 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.`,
+    `- MUST read/evaluate every suggested skill; applicable skill core contracts MUST be followed, while not-applicable needs a flow-grounded reason.`,
+    `- Selected-topology required obligations are MUSTs; implementation tactics MAY adapt and numeric planning values MAY guide but never hard-block.`,
     `- Do not impose a universal TODO/TDD/Fable sequence; use the smallest useful topology plus applicable skills.`,
-    `- Prefer objective verification before declaring done; missing verification is a reminder, not a persistent lock.`,
-    `- After 3 same-signature failures, stop retrying and use a fresh diagnosis / zoom-out.`,
-    `- Prefer targeted edits and logically complete commits.`,
+    `- MUST verify before declaring done; a reminder-only host mechanism does not make verification optional.`,
+    `- Tier-3/Fable broad mutation MUST resolve isolation: verified linked worktree or explicit degraded fallback.`,
+    `- After 3 same-signature failures, MUST stop retrying and use a fresh diagnosis / zoom-out.`,
+    `- Targeted edits SHOULD be preferred; before committing, MUST inspect the staged diff and SHOULD split unrelated concerns.`,
     ``
   ].join('\n');
 }

package/to-tickets/SKILL.md

@@ -4,7 +4,7 @@ description: Break a to-spec feature-spec, a plan, or a conversation into tracer
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.12.0
+  version: 0.19.1
 ---
 
 # To Tickets
@@ -33,7 +33,7 @@ Cuts a plan or spec into tracer-bullet vertical slices, each declaring its block
 ## Process
 
 1. Resolve path: script check (Exit 0 = configured location) → workspace convention dirs → platform fallback (`.claude`/`.github`/`.cursor` + `/harness-everything/tickets/`).
-2. Gather context: prefer a referenced to-spec spec — design-audit verification MANDATORY first, else refuse; no spec is fine.
+2. Gather context: **SHOULD** use a referenced to-spec spec when available — design-audit verification is MANDATORY first, else refuse; no spec is fine.
 3. Explore codebase (optional): evidence-cited findings only; prefactor first.
 4. Draft vertical slices: complete path through every layer, demoable alone, one context window each; declare blocking edges.
 5. Quiz the user on granularity and edges until approved (MANDATORY gate).

package/using-git-worktrees/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: using-git-worktrees
-description: Use when starting feature work needing isolation or before implementation plans - recommends an isolated workspace via native tools or git worktree fallback
+description: Use when work needs isolation or before major implementation plans - resolves workspace isolation via native tools or git worktree fallback, with an explicit degraded fallback when isolation is unavailable
 license: Apache-2.0
 metadata:
   author: Miya Daniel
-  version: 0.16.1
+  version: 0.19.1
 ---
 
 # Using Git Worktrees
@@ -13,9 +13,9 @@ Use native worktree support first; raw Git is the fallback.
 
 ## Contract
 
-- **Major workflow guidance** — Tier 3 / Fable-class engineering is safer in a linked worktree before broad source/artifact mutation. Reuse one or create one when practical.
-- **Ordinary mode** — isolation-needing feature work may honor an explicit user preference to stay in place.
-- Never nest a worktree inside an already isolated worktree.
+- **Tier 3 / Fable (MUST resolve)** — before broad source/artifact mutation, reuse/create a verified linked worktree. If isolation is unavailable or the user explicitly chooses to stay in place, MUST report an explicit degraded fallback/risk before continuing.
+- **Ordinary mode (SHOULD)** — use isolation when it materially reduces collision/risk; explicit user preference may keep work in place.
+- **MUST NOT** nest a worktree inside an already isolated worktree.
 
 ## Workflow
 
@@ -28,7 +28,7 @@ git rev-parse --show-superproject-working-tree
 ```
 Different git/common dirs and no superproject => already isolated; continue to Step 2. A submodule is a normal repo for this check.
 
-**Step 1 — Create/enter**: prefer native `EnterWorktree`, `/worktree`, or `--worktree`. Otherwise use `git worktree add "$path" -b "$BRANCH_NAME"`. Prefer an already-ignored or external/sibling path. If creation/entry fails, report it and continue only with explicit awareness of the isolation risk.
+**Step 1 — Create/enter**: use native `EnterWorktree`, `/worktree`, or `--worktree` first; otherwise use `git worktree add "$path" -b "$BRANCH_NAME"`. Use an already-ignored or external/sibling path when possible. If creation/entry fails, MUST surface the degraded isolation disposition before continuing.
 
 **Step 2 — Setup**: install project dependencies as needed.