arggon-harness 0.2.1 → 0.2.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arggon-harness",
-  "version": "0.2.1",
+  "version": "0.2.3",
   "description": "Spec-driven SDLC workflow for OpenCode — plugin, skills, commands, and init system",
   "type": "module",
   "main": "dist/plugin/index.js",

package/src/agents/spec-verify.md

@@ -7,6 +7,7 @@ permission:
   glob: allow
   grep: allow
   spec_change_list: allow
+  spec_change_status: allow
   spec_verify: allow
   spec_integrity_check: allow
   write: deny
@@ -59,7 +60,8 @@ Run 5-dimension verification on a spec change.
    - Read spec/config.yaml for project context
 
 2. **Run verification**
-   - Call `spec_verify` with change name
+   - Call the `spec_verify` tool with the change name (this runs all 5 dimensions server-side)
+   - Do NOT attempt to run tests or commands via bash — the tool handles test execution
    - Optionally specify dimensions (default: all)
 
 3. **Show report**
@@ -76,7 +78,7 @@ Run 5-dimension verification on a spec change.
    - For CRITICAL issues: must fix before archive
    - For WARNINGs: should fix, but not blocking
    - For SUGGESTIONs: nice to fix
-   - Offer to help fix issues
+   - Offer to help fix issues (use read/grep to investigate — not bash)
 
 5. **Re-verify**
    - After fixes, run verification again
@@ -88,11 +90,11 @@ Run 5-dimension verification on a spec change.
 
 ## Verification Heuristics
 
-- **Integrity**: Hash comparison, field validation
-- **Compliance**: Grep for requirement IDs in code, check test files
-- **Tasks**: Parse task status, check git diff for changes
-- **Coherence**: Extract design decisions, search for patterns
-- **Regression**: Compare delta specs with main specs
+- **Integrity**: Call `spec_integrity_check` tool — it handles hash comparison and field validation server-side
+- **Compliance**: Use `grep` tool to find requirement IDs in source files; use `read` to check test files
+- **Tasks**: Call `spec_task_progress` to get task completion status; use `read` to verify affected files exist
+- **Coherence**: Use `read` to extract design decisions from design-tech.yaml; use `grep` to search for implementation patterns
+- **Regression**: Use `read` to compare delta specs with main specs; no command execution needed
 
 ## Guardrails
 
@@ -101,3 +103,6 @@ Run 5-dimension verification on a spec change.
 - Every issue must have actionable recommendation
 - Include file/line references
 - Note which checks were skipped and why
+- Do NOT attempt to run tests, commands, or git operations via bash — use read/grep/glob for file checks
+- The spec_verify tool handles all verification server-side (integrity, test execution, compliance)
+- If you need to check something not covered by the tool, use read/grep/glob — never bash

package/src/schemas/hybrid.yaml

@@ -16,6 +16,7 @@ artifacts:
       - Define the behavior
       - List acceptance criteria
       - Identify test interfaces
+      Note which context files this change affects (spec/config.yaml, README.md, docs/).
     requires: []
 
   - id: specs

package/src/schemas/spec-driven.yaml

@@ -15,6 +15,7 @@ artifacts:
       
       Be specific about capabilities - each becomes a spec file.
       Use kebab-case for capability IDs.
+      Note which context files this change affects (spec/config.yaml, README.md, docs/).
     requires: []
 
   - id: specs

package/src/schemas/tdd.yaml

@@ -18,6 +18,7 @@ artifacts:
       Use language like:
       "The system SHALL allow users to..."
       "When X happens, the system MUST..."
+      Note which context files this change affects (spec/config.yaml, README.md, docs/).
     requires: []
 
   - id: specs

package/src/templates/hybrid/proposal.yaml

@@ -41,3 +41,4 @@ body:
       change: <what changes in this file>
     - path: <src/another.ts>
       change: <description>
+# Consider: which context/docs files does this change affect?

package/src/templates/hybrid/tasks.yaml

@@ -101,3 +101,17 @@ tasks:
       - Code is clean and follows conventions
     tdd_phase: refactor
     status: pending
+
+  # ── Context Documentation ──
+  # These tasks ensure project context stays in sync with the change.
+  # Uncomment and adjust affected_file paths as needed.
+
+  # - id: t5
+  #   group: Documentation
+  #   description: Update spec/config.yaml context to reflect scope changes
+  #   depends_on: []
+  #   complexity: low
+  #   estimated_minutes: 5
+  #   affected_files: [spec/config.yaml]
+  #   acceptance:
+  #     - config.yaml context accurately reflects the new project state

package/src/templates/spec-driven/proposal.yaml

@@ -41,3 +41,4 @@ body:
       change: <what changes in this file>
     - path: <src/another.ts>
       change: <description>
+# Consider: which context/docs files does this change affect?

package/src/templates/spec-driven/tasks.yaml

@@ -56,3 +56,17 @@ tasks:
       - All tests pass
       - No linting errors
     status: pending
+
+  # ── Context Documentation ──
+  # These tasks ensure project context stays in sync with the change.
+  # Uncomment and adjust affected_file paths as needed.
+  
+  # - id: t4
+  #   group: Documentation
+  #   description: Update spec/config.yaml context to reflect scope changes
+  #   depends_on: []
+  #   complexity: low
+  #   estimated_minutes: 5
+  #   affected_files: [spec/config.yaml]
+  #   acceptance:
+  #     - config.yaml context accurately reflects the new project state

package/src/templates/tdd/proposal.yaml

@@ -41,3 +41,4 @@ body:
       change: <what changes in this file>
     - path: <src/another.ts>
       change: <description>
+# Consider: which context/docs files does this change affect?

package/src/templates/tdd/tasks.yaml

@@ -75,3 +75,17 @@ tasks:
       - Names and structure are clean
     tdd_phase: refactor
     status: pending
+
+  # ── Context Documentation ──
+  # These tasks ensure project context stays in sync with the change.
+  # Uncomment and adjust affected_file paths as needed.
+  
+  # - id: t4
+  #   group: Documentation
+  #   description: Update spec/config.yaml context to reflect scope changes
+  #   depends_on: []
+  #   complexity: low
+  #   estimated_minutes: 5
+  #   affected_files: [spec/config.yaml]
+  #   acceptance:
+  #     - config.yaml context accurately reflects the new project state