@christang/keel 5.61.0 → 5.62.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, continuation
+authorize:          # accepted names: commit, push, release, archive, continuation, issue:<owner>/<repo>
   - commit
   - push
 ```
@@ -151,6 +151,16 @@ question — still stops. It authorizes no repository action and schedules nothi
 whose vocabulary predates the word, the entry is unrecognized and the whole declaration authorizes
 nothing until corrected — fail-closed, never a silent grant.
 
+`issue:<owner>/<repo>`, the sixth name, is the only one that names the resource it reaches, and
+it is refused without one. The other five act on the checkout the declaration sits in, so each is
+already bounded by the repository you declared it in. The credentials that open an issue are not:
+`gh` is account-wide, so a bare `issue` would reach every repository your account can touch —
+silently the widest entry in the file, and wider than `push`. Naming the repository keeps the
+grant the size of what it says. Keel carries that scope to `keel --doctor` and to the compiled
+capsule and **does not enforce it**: it invokes no tracker client and cannot observe one, exactly
+as it never commits on your behalf either. Closing an issue is not in scope and does not need to
+be — a pull request body carrying `Closes #<n>` does that when it lands.
+
 Three things the declaration is not:
 
 - **Not a way past a gate.** It authorizes the action, never the proof. `keel gate task-complete`
@@ -158,7 +168,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 five names above are the whole vocabulary. An unrecognized entry is
+- **Not open-ended.** The six 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.61.0 -->
+<!-- keel:start version=5.62.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/bin/keel.js

@@ -1776,7 +1776,7 @@ function gitConfigHooksPath(repo) {
 
 function printStandingAuthorizationSurface(repo) {
   process.stdout.write("\nStanding authorization:\n");
-  const { declared, unknown, message } = readStandingAuthorization(repo);
+  const { declared, scopes, unknown, message } = readStandingAuthorization(repo);
   if (unknown.length > 0) {
     printDoctorLine("authorize", "failed", message);
     return false;
@@ -1789,9 +1789,32 @@ function printStandingAuthorizationSurface(repo) {
       : "undeclared; every action stays hard-stop"
   );
   for (const action of STANDING_AUTHORIZATION_ACTIONS) {
+    // Keyed on the action, never on the declared string. A scoped entry is
+    // `issue:acme/widgets` in the file, so a membership test against the bare
+    // name reports it `not authorized` on the same screen that has just listed
+    // it as declared — a diagnostic contradicting itself six lines apart.
+    if (!scopes.has(action)) {
+      printDoctorLine(action, "not authorized");
+      continue;
+    }
+    const scope = scopes.get(action);
     printDoctorLine(
       action,
-      declared.includes(action) ? "authorized" : "not authorized"
+      "authorized",
+      scope ? `scoped to ${scope}` : ""
+    );
+  }
+  // Said once, and only where it applies. Keel invokes no tracker client and
+  // observes none that an agent runs, so the scope is a declaration carried to
+  // the people who read it rather than a boundary anything holds. A reader who
+  // took it for a sandbox would be relying on nothing.
+  if ([...scopes.values()].some((scope) => scope !== null)) {
+    printDoctorLine(
+      "scope",
+      "carried",
+      "Keel records a scope and does not enforce it — it invokes no tracker "
+        + "client and cannot observe one, so the boundary is kept by whoever "
+        + "acts, not by this check"
     );
   }
   return true;

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.61.0",
+  "version": "5.62.0",
   "license": "MIT",
   "repository": {
     "type": "git",

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

@@ -1,6 +1,6 @@
 {
   "name": "keel",
-  "version": "5.61.0",
+  "version": "5.62.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.61.0",
+  "version": "5.62.0",
   "description": "Keel OpenSpec execution discipline: stateless continuity, task capsules, deterministic gates, and expectation alignment for Codex and Claude Code.",
   "author": {
     "name": "TanglmChris",

package/scripts/validate_plugin.py

@@ -38,8 +38,8 @@ REQUIRED_SCRIPTS = [
     "scripts/validate_plugin.py",
 ]
 
-PACKAGE_VERSION = "5.61.0"
-PROTOCOL_VERSION = "5.61.0"
+PACKAGE_VERSION = "5.62.0"
+PROTOCOL_VERSION = "5.62.0"
 LEGACY_MANAGED_START = "<!-- keel:start version=2.1 -->"
 OPENSPEC_SCHEMA_NAME = "keel-spec-driven"
 # Mirrors KEEL_PACKAGE_NAME in scripts/install_to_repo.py, one of the two
@@ -19808,19 +19808,20 @@ def validate_continuation_docs_scenario() -> int:
 
     readme = (ROOT / "README.md").read_text(encoding="utf-8")
     for needle in (
-        "accepted names: commit, push, release, archive, continuation",
+        "accepted names: commit, push, release, archive, continuation, "
+        "issue:<owner>/<repo>",
         "next unchecked task of the same change",
         "the stop that re-asks for an approval already given",
-        "The five names above are the whole vocabulary.",
+        "The six names above are the whole vocabulary.",
     ):
         if needle not in readme:
             report(f"{label}: README.md lacks: {needle}")
             return 1
 
     config_text = (ROOT / "keel/config.yaml").read_text(encoding="utf-8")
-    if "commit, push, release, archive,\n# continuation" not in config_text:
+    if "commit, push, release, archive,\n# continuation, issue:<owner>/<repo>" not in config_text:
         report(
-            f"{label}: keel/config.yaml's comment does not name the five-name "
+            f"{label}: keel/config.yaml's comment does not name the six-name "
             "vocabulary."
         )
         return 1
@@ -27626,6 +27627,163 @@ def validate_a_filter_drops_only_what_it_named_scenario() -> int:
     return 0
 
 
+def validate_an_authorization_names_its_repository_scenario() -> int:
+    """Issue #136: the vocabulary had no name for a tracker write.
+
+    `change-close` routes an unresolved follow-up to a durable owner and accepts
+    an absolute https reference, which in practice is a tracker issue — while the
+    standing-authorization vocabulary had no way to say the agent may create one.
+    The entry added for it is the first whose credential reaches further than the
+    checkout the declaration sits in: `gh` is account-wide, so a bare `issue`
+    would be the widest entry in a file whose other entries the checkout bounds.
+    It therefore names the repository it reaches, and the bare form is refused.
+    """
+    label = "an-authorization-names-its-repository"
+
+    with tempfile.TemporaryDirectory(prefix="keel-issue-scope-") as raw:
+        root = Path(raw)
+
+        def fixture(name: str, body: str) -> Path:
+            repo = root / name
+            repo.mkdir()
+            write_authorize_config(repo, body)
+            return repo
+
+        # M1 — the scoped form is accepted, beside an ordinary entry so the
+        # assertion is about this entry and not about the block parsing at all.
+        scoped = fixture(
+            "scoped", "authorize:\n  - commit\n  - issue:acme/widgets\n"
+        )
+        out = run_keel(scoped, "--doctor").stdout
+        if "authorize: ok" not in out or "issue:acme/widgets" not in out:
+            report(
+                f"{label}: a scoped tracker entry was refused. `gh` is "
+                "account-wide, so this is the one entry that has to name its "
+                "repository, and it is the one the vocabulary rejects."
+            )
+            report(out)
+            return 1
+        if "commit: authorized" not in out:
+            report(
+                f"{label}: the entry beside the scoped one lost its "
+                "authorization, so the scoped entry voided the declaration "
+                "rather than joining it."
+            )
+            report(out)
+            return 1
+
+        # The per-action line, which is the half a reader looks at. Without it
+        # the same screen lists the entry as declared and reports the action as
+        # unauthorized.
+        if "issue: authorized" not in out or "acme/widgets" not in out.split(
+            "issue: authorized", 1
+        )[-1].split("\n", 1)[0]:
+            report(
+                f"{label}: the per-action line does not report the scoped entry "
+                "as authorized and name its scope."
+            )
+            report(out)
+            return 1
+        if "issue: not authorized" in out:
+            report(
+                f"{label}: the doctor lists the entry as declared and reports "
+                "`issue: not authorized` on the same screen, so the diagnostic "
+                "contradicts itself."
+            )
+            report(out)
+            return 1
+        # D2 is unfixable by mechanism, so it is owed to wording: a reader must
+        # not take the scope for a sandbox.
+        if "does not enforce" not in out:
+            report(
+                f"{label}: the output does not say Keel carries the scope "
+                "without enforcing it, so a reader can take it for a fence."
+            )
+            report(out)
+            return 1
+
+        # M2 — the bare form is refused, and the refusal carries the form it
+        # needs. The refusal alone is not the assertion: a bare `issue` was
+        # already refused before this existed, by not being a name at all.
+        bare = fixture("bare", "authorize:\n  - commit\n  - issue\n")
+        out = run_keel(bare, "--doctor").stdout
+        if "authorize: failed" not in out:
+            report(f"{label}: a bare tracker entry was granted.")
+            report(out)
+            return 1
+        if "issue:<owner>/<repo>" not in out:
+            report(
+                f"{label}: the bare-entry refusal does not name the form it "
+                "requires, so a reader is told `issue` is not a name rather "
+                "than that it is a name needing a scope."
+            )
+            report(out)
+            return 1
+
+        # M3 — the shape is checked, on both sides of correct.
+        for name, body in (
+            ("short", "authorize:\n  - issue:acme\n"),
+            ("long", "authorize:\n  - issue:acme/widgets/extra\n"),
+            ("empty-owner", "authorize:\n  - issue:/widgets\n"),
+            ("empty-repo", "authorize:\n  - issue:acme/\n"),
+        ):
+            repo = fixture(name, body)
+            out = run_keel(repo, "--doctor").stdout
+            if "authorize: failed" not in out:
+                report(
+                    f"{label}: a malformed scope ({name}) was accepted; a shape "
+                    "check that passes everything checks nothing."
+                )
+                report(out)
+                return 1
+            declared_entry = body.strip().splitlines()[-1].strip("- ")
+            if declared_entry not in out:
+                report(
+                    f"{label}: the refusal for {name} does not name the "
+                    f"offending entry {declared_entry!r}."
+                )
+                report(out)
+                return 1
+
+        # M3 — and fail-closed is unchanged by the new form: a valid scoped
+        # entry beside an unrecognized one authorizes nothing.
+        mixed = fixture(
+            "mixed", "authorize:\n  - issue:acme/widgets\n  - deploy\n"
+        )
+        out = run_keel(mixed, "--doctor").stdout
+        if "authorize: failed" not in out or "deploy" not in out:
+            report(f"{label}: an unrecognized entry beside a scoped one did not fail closed.")
+            report(out)
+            return 1
+        if "issue: authorized" in out:
+            report(
+                f"{label}: the scoped entry stayed authorized beside an "
+                "unrecognized one, so the declaration did not fail closed."
+            )
+            report(out)
+            return 1
+
+
+        # M3 — the new rendering did not turn an undeclared action into a
+        # declared one.
+        only_commit = fixture("only-commit", "authorize:\n  - commit\n")
+        out = run_keel(only_commit, "--doctor").stdout
+        for action in ("push", "release", "archive", "continuation", "issue"):
+            if f"{action}: not authorized" not in out:
+                report(
+                    f"{label}: {action} is not reported as unauthorized in a "
+                    "repository that declared only commit."
+                )
+                report(out)
+                return 1
+
+    if label not in {name for name, _ in SCENARIOS}:
+        report(f"{label}: the scenario registry does not include it.")
+        return 1
+    report(f"{label} scenario passed.")
+    return 0
+
+
 SCENARIOS: tuple = (
     ("stateless-continuity", validate_stateless_continuity_scenario),
     ("core-gates", validate_core_gates_scenario),
@@ -27972,6 +28130,10 @@ SCENARIOS: tuple = (
         "a-filter-drops-only-what-it-named",
         validate_a_filter_drops_only_what_it_named_scenario,
     ),
+    (
+        "an-authorization-names-its-repository",
+        validate_an_authorization_names_its_repository_scenario,
+    ),
 )
 
 

package/src/core/config.js

@@ -13,8 +13,53 @@ const STANDING_AUTHORIZATION_ACTIONS = [
   "release",
   "archive",
   "continuation",
+  "issue",
 ];
 
+// The actions whose credential reaches further than the checkout the
+// declaration sits in. Every other name here acts on this repository, so the
+// declaration and the thing it permits are the same size; `gh` is account-wide,
+// so a bare `issue` would silently be the widest entry in the file. Those
+// actions are declared with the resource they may reach and refused bare —
+// accepting the bare form as a convenience would make the narrow form optional
+// and the wide one the default, which is the decision inverted.
+const SCOPED_AUTHORIZATION_ACTIONS = new Set(["issue"]);
+
+// `<owner>/<repo>`: two non-empty segments and nothing else. The shape is
+// checked and the existence is not, for the reason `triage` never fetches an
+// issue — a check that reaches the network trades the local, offline,
+// deterministic evaluation its verdict rests on.
+const AUTHORIZATION_SCOPE_PATTERN = /^[A-Za-z0-9._-]+\/[A-Za-z0-9._-]+$/;
+
+// How the accepted names are spelled back to an author: the scoped ones carry
+// their form, so the list is copyable rather than a name the next message
+// refuses.
+const STANDING_AUTHORIZATION_ACCEPTED_FORMS = STANDING_AUTHORIZATION_ACTIONS.map(
+  (action) =>
+    SCOPED_AUTHORIZATION_ACTIONS.has(action) ? `${action}:<owner>/<repo>` : action
+);
+
+// One declared entry, split into the action and the resource it names. Returns
+// the action and scope when the entry is usable, and otherwise why it is not,
+// so the caller can say which of the three mistakes an author made.
+function classifyAuthorizationEntry(entry) {
+  const separator = entry.indexOf(":");
+  const action = separator === -1 ? entry : entry.slice(0, separator);
+  const scope = separator === -1 ? null : entry.slice(separator + 1);
+  if (!STANDING_AUTHORIZATION_ACTIONS.includes(action)) {
+    return { ok: false, entry, reason: "unknown-action" };
+  }
+  if (!SCOPED_AUTHORIZATION_ACTIONS.has(action)) {
+    if (scope !== null) return { ok: false, entry, action, reason: "unexpected-scope" };
+    return { ok: true, entry, action, scope: null };
+  }
+  if (scope === null) return { ok: false, entry, action, reason: "missing-scope" };
+  if (!AUTHORIZATION_SCOPE_PATTERN.test(scope)) {
+    return { ok: false, entry, action, reason: "malformed-scope" };
+  }
+  return { ok: true, entry, action, scope };
+}
+
 // The closed vocabulary of capability tiers a repository may declare for a
 // delegated task. The names describe the capability the work requires, never
 // the size of the work: a tier named for size would authorize the agent's guess
@@ -162,24 +207,64 @@ function readTriagePolicy(repo) {
 // both — but only `archive` is a name this vocabulary accepts (#93). Naming
 // that confusion only when `sync` is the entry present keeps every other
 // unrecognized name (a genuine typo) unchanged.
-function standingAuthorizationUnknownMessage(unknown) {
+function standingAuthorizationUnknownMessage(unknown, problems = []) {
   const base = `keel/config.yaml declares unrecognized ${
     unknown.length === 1 ? "action" : "actions"
   }: ${unknown.join(", ")}; accepted names are `
-    + `${STANDING_AUTHORIZATION_ACTIONS.join(", ")}. The whole declaration `
+    + `${STANDING_AUTHORIZATION_ACCEPTED_FORMS.join(", ")}. The whole declaration `
     + "authorizes nothing until it is corrected.";
-  if (!unknown.includes("sync")) return base;
-  return `${base} \`sync\` is a value of \`change-close --action\`, not a `
-    + "name `authorize:` accepts; declare `archive` if you mean to authorize "
-    + "the gate that runs it.";
+  const notes = [];
+  if (unknown.includes("sync")) {
+    notes.push(
+      "`sync` is a value of `change-close --action`, not a name `authorize:` "
+        + "accepts; declare `archive` if you mean to authorize the gate that "
+        + "runs it."
+    );
+  }
+  // A scoped action refused for its scope is not a typo, and saying "accepted
+  // names are ... issue" beside "unrecognized action: issue" would contradict
+  // itself. Name what is missing instead, and why this one name carries it.
+  for (const problem of problems) {
+    if (problem.reason === "missing-scope") {
+      notes.push(
+        `\`${problem.action}\` names no repository; write it as `
+          + `\`${problem.action}:<owner>/<repo>\`. The credentials that open an `
+          + "issue are account-wide, so an unscoped grant would reach every "
+          + "repository the account can touch — wider than commit or push, "
+          + "which this checkout bounds."
+      );
+    } else if (problem.reason === "malformed-scope") {
+      notes.push(
+        `\`${problem.entry}\` does not name a repository as `
+          + `\`<owner>/<repo>\` — two non-empty segments and nothing else.`
+      );
+    } else if (problem.reason === "unexpected-scope") {
+      notes.push(
+        `\`${problem.action}\` takes no scope; it acts on this checkout, which `
+          + "already bounds it."
+      );
+    }
+  }
+  return notes.length === 0 ? base : `${base} ${notes.join(" ")}`;
 }
 
 function readStandingAuthorization(repo) {
   const declared = [];
   const unknown = [];
+  const problems = [];
+  // Action -> the resource it names, or null for an action the checkout bounds.
+  // Additive: `declared` stays the entries as written, so the capsule's
+  // inherited autonomy line reads back what the file says.
+  const scopes = new Map();
   for (const entry of configList(repo, "authorize")) {
-    if (STANDING_AUTHORIZATION_ACTIONS.includes(entry)) declared.push(entry);
-    else unknown.push(entry);
+    const classified = classifyAuthorizationEntry(entry);
+    if (classified.ok) {
+      declared.push(entry);
+      scopes.set(classified.action, classified.scope);
+      continue;
+    }
+    unknown.push(entry);
+    if (classified.reason !== "unknown-action") problems.push(classified);
   }
   // Fail closed. A declaration Keel cannot fully read authorizes nothing,
   // because the alternative is granting the entries beside a typo while the
@@ -187,11 +272,12 @@ function readStandingAuthorization(repo) {
   if (unknown.length > 0) {
     return {
       declared: [],
+      scopes: new Map(),
       unknown,
-      message: standingAuthorizationUnknownMessage(unknown),
+      message: standingAuthorizationUnknownMessage(unknown, problems),
     };
   }
-  return { declared, unknown, message: null };
+  return { declared, scopes, unknown, message: null };
 }
 
 // A nested block of `name: value` entries under one top-level key. Delegation
@@ -389,6 +475,7 @@ module.exports = {
   CONFIG_RELATIVE_PATH,
   DELEGATION_TIERS,
   STANDING_AUTHORIZATION_ACTIONS,
+  SCOPED_AUTHORIZATION_ACTIONS,
   readDelegationPolicy,
   readPrecedentStore,
   readStandingAuthorization,