@christang/keel 5.39.0 → 5.46.0

package/README.md

@@ -132,7 +132,7 @@ because a permission granted in conversation does not survive a context reset. D
 `keel/config.yaml` instead:
 
 ```yaml
-authorize:          # accepted names: commit, push, release, archive
+authorize:          # accepted names: commit, push, release, archive, continuation
   - commit
   - push
 ```
@@ -141,6 +141,16 @@ A task that authors no `Autonomy boundary:` inherits the declaration, and the co
 names `keel/config.yaml` as that entry's source so an inherited authorization is never mistaken
 for one the task decided. A task that authors its own boundary keeps it.
 
+`continuation`, the fifth name, is the between-task one: it covers exactly the boundary between a
+durably complete task and the next unchecked task of the same change, inside a change whose
+`tasks.md` you approved — the stop that re-asks for an approval already given. It removes only that
+confirmation: the next task still starts through `keel gate task-start` with its own recorded
+fingerprint, every gate, evidence requirement, semantic Review, and the write guard run unchanged,
+and a stop with its own trigger — a blocker, fingerprint drift, an out-of-scope need, an unresolved
+question — still stops. It authorizes no repository action and schedules nothing. On an older Keel
+whose vocabulary predates the word, the entry is unrecognized and the whole declaration authorizes
+nothing until corrected — fail-closed, never a silent grant.
+
 Three things the declaration is not:
 
 - **Not a way past a gate.** It authorizes the action, never the proof. `keel gate task-complete`
@@ -148,7 +158,7 @@ Three things the declaration is not:
   anything.
 - **Not a trigger.** It removes a confirmation, not the step that reaches the action. Nothing
   schedules itself, and no next task is selected for you.
-- **Not open-ended.** The four names above are the whole vocabulary. An unrecognized entry is
+- **Not open-ended.** The five names above are the whole vocabulary. An unrecognized entry is
   reported with the accepted names and the declaration authorizes nothing until you fix it — a
   typo never becomes a silent grant.
 

package/assets/bootstrap/AGENTS.md

@@ -1,4 +1,4 @@
-<!-- keel:start version=5.39.0 -->
+<!-- keel:start version=5.46.0 -->
 ## Keel Bootstrap
 
 - Start every session with `keel context`; OpenSpec artifacts and Git are the only durable authority — never native memory, goals, or transcripts.

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.39.0",
+  "version": "5.46.0",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -17,7 +17,9 @@
     "src/core/",
     "assets/",
     "README.md",
-    "plugins/"
+    "plugins/",
+    "!**/__pycache__",
+    "!**/*.pyc"
   ],
   "scripts": {
     "validate": "node scripts/run_python.js scripts/validate_plugin.py",

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

@@ -1,6 +1,6 @@
 {
   "name": "keel",
-  "version": "5.39.0",
+  "version": "5.46.0",
   "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.39.0",
+  "version": "5.46.0",
   "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/skills/keel-run-single-task-goal/SKILL.md

@@ -50,7 +50,7 @@ If any of these hold, stop and use the normal manual Keel loop.
 4. Surface every command result and gate outcome in the transcript before any success claim.
 5. Pass the current agent's Review, then `keel gate task-complete`.
 6. The current agent durably checks the task checkbox.
-7. Stop. Continuing to another task requires a new explicit user instruction and a new start fingerprint; there is no hidden scheduler or automatic next-task selection.
+7. Stop. Continuing to another task requires a new explicit user instruction and a new start fingerprint; a standing `continuation` authorization in `keel/config.yaml` is the durable form of that instruction, covering only the next unchecked task of the same change in its approved `tasks.md` order. Each next task still passes `keel gate task-start` with its own recorded fingerprint, and there is still no hidden scheduler or automatic next-task selection — the declaration removes the confirmation, never the selection, the gates, or the evidence.
 
 Resume reconstructs the goal from OpenSpec and Git only. Fingerprint drift, checkout divergence, a completed authorization, or missing authorization hard-stops before any product write; pass `--expected-fingerprint` and `--expected-owner` to assert the recorded authorization.
 

package/scripts/install_to_repo.py

@@ -112,7 +112,7 @@ TASKS_COMMIT_STATUS_PATTERNS = (
         "remove dirty/uncommitted state from tasks.md; keep durable work state in OpenSpec and use HANDOFF only as an explicit pointer override",
     ),
     (
-        re.compile(r"(?:未提交|待提交|已提交|尚未提交|未合入|待合入|已合入|合入\s*(?:master|main))"),
+        re.compile(r"(?:未合入|待合入|已合入|合入\s*(?:master|main))"),
         "remove commit or merge state from tasks.md; git log is the source of truth",
     ),
     (
@@ -120,6 +120,28 @@ TASKS_COMMIT_STATUS_PATTERNS = (
         "remove branch merge state from tasks.md; git log is the source of truth",
     ),
 )
+# 合入 names the git act and has no other reading, so it is refused on its own
+# above. 提交 is an ordinary transitive verb — 提交资料, 提交审核, 提交申请 — and
+# matching it bare refused an Evidence line about a third-party review queue
+# while accepting the same sentence in English (#103). A check whose verdict
+# depends on which language the author wrote in is not checking what it claims
+# to, so this family is refused only where the line says the subject is git.
+TASKS_SUBMISSION_STATE_RE = re.compile(r"(?:未提交|待提交|已提交|尚未提交)")
+# The words that name git or a git object. Deliberately not `_HASH_CONTEXT_WORD`:
+# that list holds 提交 and 合入 themselves, because its job is to let a state word
+# supply context to a hash-shaped token, and reusing it here would let 已提交
+# supply its own context and change nothing. The ASCII words carry boundaries for
+# the reason #65 established; the Chinese ones cannot and do not.
+TASKS_GIT_CONTEXT_RE = re.compile(
+    r"(?i)\b(?:git|commits?|committed|committing|master|main|HEAD|branch(?:es)?"
+    r"|PR|merges?|merged)\b"
+    r"|分支|仓库|代码库|代码|合入|工作区|暂存"
+)
+TASKS_SUBMISSION_MESSAGE = (
+    "remove commit or merge state from tasks.md; git log is the source of truth"
+)
+
+
 # A commit identifier is hexadecimal, and `a`-`f` are the only reason those
 # letters appear in one. A run of decimal digits alone is a phone number, a
 # timestamp, an order number, or a port — evidence prose, not state git owns.
@@ -137,8 +159,10 @@ _HASH_SHAPED_TOKEN = r"\b(?=[0-9a-f]{7,40}\b)[0-9a-f]*[a-f][0-9a-f]*\b"
 # the words an author writes about the act this rule exists to catch, and the
 # stricter list that drops `committed` and `hashes` would cost real refusals.
 # The Chinese words carry no boundary because none is definable between two
-# word characters — `\b提交\b` matches neither `已提交` nor `未提交`, which are
-# exactly what the wording rule is for.
+# word characters — `\b提交\b` matches neither `已提交` nor `未提交`. What that
+# buys is this rule: a state word beside a hash-shaped token still supplies the
+# context that makes the token an identifier. The wording rule above no longer
+# rests on it, because 提交 needs a git word of its own (#103).
 _HASH_CONTEXT_WORD = (
     r"(?:\b(?:commits?|committed|committing|master|main|HEAD|hash(?:es)?)\b"
     r"|提交|合入|哈希)"
@@ -704,6 +728,37 @@ def covers_field_lines(content: str) -> set[int]:
     return lines
 
 
+# What an author quotes is content they cite, not a claim they make. Evidence
+# prose quotes the command that ran, the output it printed, the branch base it
+# ran against, and the name of the requirement under change — and every one of
+# those carries exactly the words these rules refuse. `withoutInlineCode()` in
+# `src/core/task-contract.js` settled this shape for the field reader; the two
+# reports that reached this reader (#65 items 2 and 4) are the same shape
+# arriving late.
+#
+# The ASCII single quote is deliberately absent. It is an apostrophe far more
+# often than a quotation mark, and a span opened by `doesn't` would silence the
+# remainder of the line — a rule that stops running without saying so, which is
+# the failure no fixture catches by accident.
+QUOTED_SPAN_RE = re.compile(
+    r"`[^`\n]*`"
+    r"|\"[^\"\n]*\""
+    r"|\u201c[^\u201d\n]*\u201d"
+    r"|\u300c[^\u300d\n]*\u300d"
+    r"|\u300a[^\u300b\n]*\u300b"
+)
+FENCE_RE = re.compile(r"^\s*(?:```|~~~)")
+
+
+def without_quoted_spans(line: str) -> str:
+    """Blank out the quoted spans of a line, leaving its length reading intact.
+
+    The replacement is a space rather than nothing so two tokens either side of
+    a span cannot be joined into a third word that neither of them was.
+    """
+    return QUOTED_SPAN_RE.sub(" ", line)
+
+
 def check_tasks_semantics(repo: Path) -> list[str]:
     changes_root = repo / OPENSPEC_ROOT / "changes"
     if not changes_root.is_dir():
@@ -725,12 +780,27 @@ def check_tasks_semantics(repo: Path) -> list[str]:
                 errors.append(f"{relative}:{line}: {message}")
 
         cited = covers_field_lines(content)
+        fenced = False
         for line_number, line in enumerate(content.splitlines(), start=1):
-            if is_tasks_rule_line(line) or line_number in cited:
+            # A fenced block is one long quoted span, and its own delimiter
+            # lines carry no prose. Tracking the state here rather than
+            # pre-stripping the file keeps every reported line number the
+            # line number the author sees.
+            if FENCE_RE.match(line):
+                fenced = not fenced
                 continue
+            if fenced or is_tasks_rule_line(line) or line_number in cited:
+                continue
+            line = without_quoted_spans(line)
             for pattern, message in TASKS_COMMIT_STATUS_PATTERNS:
                 if pattern.search(line):
                     errors.append(f"{relative}:{line_number}: {message}")
+            if TASKS_SUBMISSION_STATE_RE.search(line) and TASKS_GIT_CONTEXT_RE.search(
+                line
+            ):
+                errors.append(
+                    f"{relative}:{line_number}: {TASKS_SUBMISSION_MESSAGE}"
+                )
             if TASKS_CONTEXTUAL_HASH_RE.search(line):
                 errors.append(
                     f"{relative}:{line_number}: remove contextual commit hash from tasks.md; git log is the source of truth"