arggon-harness 0.2.2 → 0.2.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arggon-harness",
-  "version": "0.2.2",
+  "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/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