@christang/keel 5.3.6 → 5.3.8

package/assets/bootstrap/AGENTS.md

@@ -1,8 +1,8 @@
-<!-- keel:start version=5.3.6 -->
+<!-- keel:start version=5.3.8 -->
 ## Keel Bootstrap
 
 - Start every session with `keel context`; OpenSpec artifacts and Git are the only durable authority — never native memory, goals, or transcripts.
-- Obey the selected task capsule: `keel gate task-start` before implementing, record its fingerprint in Evidence `Contract`, and pass `keel gate task-complete` before checking complete. Touch bounds product writes; the change's own dir is exempt. On Claude a passing `task-start` guards it by default (`--no-guard` opts out).
+- Obey the selected task capsule: `keel gate task-start` before implementing, `--record` its fingerprint to Evidence `Contract`, which `task-complete` requires, before checking complete. Touch bounds product writes; the change's own dir is exempt. On Claude a passing `task-start` guards it by default (`--no-guard` opts out).
 - One current agent owns writes; helpers return read-only report/evidence only. No commit, sync, or archive without explicit authorization.
 - Native plugin projections (SessionStart context) are disposable views, never authority; without the plugin or hook, run the commands manually.
 - Keel skills and hooks come from the `keel` native plugin (`codex plugin add` / `claude plugin install`); `keel --init` owns only the OpenSpec schema, overlays, and this bootstrap.

package/assets/openspec/schemas/keel-spec-driven/schema.yaml

@@ -75,7 +75,10 @@ artifacts:
       Every executable task MUST be a checkbox authored in the compact v4 form
       from the template: Covers, Touch, Verify (Strategy plus ordered M<n>
       public checks), and an Evidence anchor with its Contract line, per-check
-      results, semantic Review, and Blocker state. Omitted fields inherit
+      results, semantic Review, and Blocker state. `task-start --record` writes
+      the compiled fingerprint into that Contract line, and task-complete
+      refuses a task that recorded none: without an anchor there is nothing for
+      completion to compare against, so the task has no drift detection. Omitted fields inherit
       versioned keel-task-capsule/v1 defaults: Owner is the current Keel
       agent, Mode is implementation, Read is the change artifacts plus
       discovered repository context, Acceptance derives from the resolved
@@ -108,8 +111,11 @@ artifacts:
       Accepted hidden-knowledge assumptions from risk-triggered deep
       alignment or a domain lens are critical expectations when they
       affect completion definition or execution boundaries.
-      Covers references the relevant D/F/A/Q identifiers. An unresolved Q<n>
-      without an authorized fallback blocks implementation.
+      Covers references the relevant D/F/A/Q identifiers. A Q<n> that opens a
+      Covers entry is an open question and blocks implementation without an
+      authorized fallback; the same identifier named inside an entry whose
+      subject is a fact is a citation and does not block, so a resolved question
+      can be cited beside the fact that closed it.
       A new or materially expanded dedicated skill remains non-executable until
       design or task evidence identifies authoritative sources, provenance and license
       implications, realistic positive and negative trigger cases, and

package/assets/openspec/schemas/keel-spec-driven/templates/spec.md

@@ -1,7 +1,9 @@
 ## ADDED Requirements
 
 ### Requirement: <!-- requirement name -->
-<!-- requirement text -->
+<!-- The requirement text MUST contain SHALL or MUST; validation refuses a
+     requirement without one, so keep the modal verb when filling this in. -->
+The system SHALL <!-- observable behavior -->
 
 #### Scenario: <!-- scenario name -->
 - **WHEN** <!-- condition -->

package/assets/openspec/schemas/keel-spec-driven/templates/tasks.md

@@ -11,7 +11,7 @@
 
 - [ ] 1.1 <!-- Task description -->
   - Covers:
-    - <source expectation: spec scenario as `capability / requirement or scenario heading`, hidden-knowledge assumption, domain lens requirement, or critical D<n>/F<n>/A<n>/Q<n>; an unresolved Q<n> requires an authorized fallback>
+    - <source expectation: spec scenario as `capability / requirement or scenario heading`, hidden-knowledge assumption, domain lens requirement, or critical D<n>/F<n>/A<n>/Q<n>; a Q<n> that OPENS an entry is an open question and requires an authorized fallback, while one named inside an entry about a fact is a citation and does not>
   - Touch:
     - <path>
   - Verify:
@@ -82,6 +82,36 @@
       - Findings: pending
     - Blocker: none
 
+## 3. <!-- Task Group Name -->
+
+- [ ] 3.1 <!-- Red-green example: a vertical-tdd task and the Evidence it must record -->
+  - Covers:
+    - <source expectation whose observable behavior this slice proves>
+  - Touch:
+    - <path>
+  - Verify:
+    <!-- The untagged check below is load-bearing: a red-green strategy whose
+         every check is tagged (regression) is refused as regression-only,
+         because a regression check has no honest red to record. -->
+    - Strategy: vertical-tdd
+    - M1: <public behavior check for the new behavior>
+    - M2 (regression): <check asserting behavior that is already green stays green>
+  - Evidence:
+    <!-- M1 is red-green, so it records THREE entries: the bare M1 plus M1.red
+         and M1.green. M2 is tagged regression, so it records only its bare
+         entry — it is exempt from .red/.green, not from Evidence. -->
+    - Contract: pending
+    - M1: pending
+    - M1.red: pending
+    - M1.green: pending
+    - M2: pending
+    - Review:
+      - Status: pending
+      - Acceptance check: pending
+      - Scope check: pending
+      - Findings: pending
+    - Blocker: none
+
 ## Invalidates
 
 <!-- task-start requires this section before any task of this change runs, so

package/package.json

@@ -2,7 +2,7 @@
   "name": "@christang/keel",
   "displayName": "Keel",
   "description": "Keel OpenSpec execution discipline CLI for Claude Code, Codex, and OpenCode.",
-  "version": "5.3.6",
+  "version": "5.3.8",
   "license": "MIT",
   "repository": {
     "type": "git",

package/plugins/keel/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "keel",
-  "version": "5.3.6",
+  "version": "5.3.8",
   "description": "Keel OpenSpec execution discipline: stateless continuity, task capsules, deterministic gates, and expectation alignment for Codex and Claude Code.",
   "author": {
     "name": "TanglmChris",

package/plugins/keel/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "keel",
-  "version": "5.3.6",
+  "version": "5.3.8",
   "description": "Keel OpenSpec execution discipline: stateless continuity, task capsules, deterministic gates, and expectation alignment for Codex and Claude Code.",
   "author": {
     "name": "TanglmChris",