agentopology 0.9.1 → 0.10.0

package/spec/claude-code/hooks-contract.json

@@ -0,0 +1,142 @@
+{
+  "source": "https://code.claude.com/docs/en/hooks.md",
+  "fetched": "2026-11-10",
+  "claudeCode": "2.1.319",
+  "events": [
+    "SessionStart",
+    "Setup",
+    "InstructionsLoaded",
+    "UserPromptSubmit",
+    "UserPromptExpansion",
+    "MessageDisplay",
+    "PreToolUse",
+    "PermissionRequest",
+    "PostToolUse",
+    "PostToolUseFailure",
+    "PostToolBatch",
+    "PermissionDenied",
+    "Notification",
+    "SubagentStart",
+    "SubagentStop",
+    "TaskCreated",
+    "TaskCompleted",
+    "Stop",
+    "StopFailure",
+    "TeammateIdle",
+    "ConfigChange",
+    "CwdChanged",
+    "DirectoryAdded",
+    "FileChanged",
+    "WorktreeCreate",
+    "WorktreeRemove",
+    "PreCompact",
+    "PostCompact",
+    "PreModelSwitch",
+    "PostModelSwitch",
+    "SessionEnd",
+    "Elicitation",
+    "ElicitationResult"
+  ],
+  "eventRequires": {
+    "PreModelSwitch": "2.1.251",
+    "PostModelSwitch": "2.1.251"
+  },
+  "noMatcherEvents": [
+    "CwdChanged",
+    "MessageDisplay",
+    "PostToolBatch",
+    "Stop",
+    "TaskCompleted",
+    "TaskCreated",
+    "TeammateIdle",
+    "UserPromptSubmit",
+    "WorktreeCreate",
+    "WorktreeRemove"
+  ],
+  "handlerTypes": [
+    "command",
+    "http",
+    "mcp_tool",
+    "prompt",
+    "agent"
+  ],
+  "fields": {
+    "common": {
+      "type": {
+        "required": true
+      },
+      "if": {
+        "required": false
+      },
+      "timeout": {
+        "required": false
+      },
+      "statusMessage": {
+        "required": false
+      },
+      "once": {
+        "required": false
+      }
+    },
+    "command": {
+      "command": {
+        "required": true
+      },
+      "args": {
+        "required": false
+      },
+      "async": {
+        "required": false
+      },
+      "asyncRewake": {
+        "required": false
+      },
+      "shell": {
+        "required": false
+      },
+      "onFailure": {
+        "required": false,
+        "requires": "2.1.295"
+      }
+    },
+    "http": {
+      "url": {
+        "required": true
+      },
+      "headers": {
+        "required": false
+      },
+      "allowedEnvVars": {
+        "required": false
+      },
+      "onFailure": {
+        "required": false,
+        "requires": "2.1.295"
+      }
+    },
+    "mcp_tool": {
+      "server": {
+        "required": true
+      },
+      "tool": {
+        "required": true
+      },
+      "input": {
+        "required": false
+      }
+    },
+    "prompt": {
+      "prompt": {
+        "required": true
+      },
+      "model": {
+        "required": false
+      }
+    }
+  },
+  "matcherRules": [
+    "`\"*\"`, `\"\"`, or omitted → Match all",
+    "Only letters, digits, `_`, `-`, spaces, `,`, and `|` → Exact string, or list of exact strings separated by `|` or `,` with optional surrounding whitespace",
+    "Contains any other character → JavaScript regular expression, unanchored"
+  ]
+}

package/spec/grammar.md

@@ -472,6 +472,7 @@ action <name> {
 | `source` | string | no | -- |
 | `commands` | name-list | no | `[]` |
 | `description` | string | no | -- |
+| `unit-from` | string (regex) | no | -- | One capture group that reads the unit (an episode id, a ticket) from the command line, e.g. `"./tool publish (\\S+)"`. Needs a capture group (V111) |
 
 **action-kind:** `external` | `git` | `decision` | `inline` | `report`
 
@@ -941,6 +942,11 @@ flow {
 | `[when x.y == z]` | Conditional: edge taken only when condition is true |
 | `[max N]` | Bounded loop: back-edge limited to N iterations |
 | `[per ticket]` | One instance per unit (currently only `ticket` is valid) |
+| `[strength: none]` | Enforcement written down: `refuse`, `detect`, `hope` or `none` (V104), so an absence is declared, not implied |
+| `[at: "story/SKILL.md"]` | Where the enforcement, or the prose that hopes, lives (V106) |
+| `[guard: lock-bash]` / `[guard: [a, b]]` | The hooks or gates that guard this edge, by id (V105) |
+
+**Enforcement.** `strength` says what stops a step: code or a hook **refuses** it, a critic **detects** it after the fact, prose **hopes**, or **none**. `by` names the mechanism (`code`, `hook`, `settings`, `gate`); `at` cites it, `match` is the text expected there, and `bypass` names the way around it. A gate or hook carries the evidence; an edge cites it with `guard:` or writes its strength down. Hooks take `strength` and `bypass`. validate checks the words and the references (V104 to V106) and never reads the project. Reading the cited files (does the line exist, is the `match` text there) is `guard --check`'s job, and lands with it in 0.10.0.
 
 **Chained flows:** `a -> b -> c [when x]` desugars to `a -> b` + `b -> c [when x]`. Edge attributes apply to the **last edge only**.
 
@@ -1004,6 +1010,30 @@ gates {
 | `on-fail` | `bounce-back` / `halt` | no | `halt` | Failure behavior |
 | `behavior` | `advisory` / `blocking` | no | `blocking` | Advisory gates never block |
 | `description` | string | no | -- | What the gate checks, in words. Prose goes here, never in `run` (V96) |
+| `strength` | `refuse` / `detect` / `hope` / `none` | no | -- | What stops the step, as written down (V104). See "Enforcement" below |
+| `by` | `code` / `hook` / `settings` / `gate` | no | -- | Which mechanism refuses (V104) |
+| `at` | `"path"` or `"path:line"` | no | -- | The code that refuses, project-relative (V106) |
+| `match` | string | no | -- | Text expected within 5 lines of `at`, so a refactor that removes the check is caught. Needs `at` (V106) |
+| `bypass` | string | no | -- | The declared way around it (an env switch, a flag) |
+| `ledger` | record id | no | the only record | The record a gate before a script step reads. Omitted, a topology with exactly one `record` uses it (V112) |
+
+**Gates before a script step.** A gate whose `before:` is an `action` with `commands:` refuses that step in Claude Code sessions. The claude-code binding writes one script, `before-action.sh`, wired as a `PreToolUse` hook on `Bash` with `onFailure: "block"`. When the Bash command starts with one of the action's `commands:` (leading `VAR=value` words are ignored), the script checks the gate: if it has a ledger, the **last** line for the `after:` step (and the same unit, when the command names one with `unit-from`) must have `ok: true`; if it has `run:`, that wrapper must exit 0. Anything else exits 2 and says which gate, step, unit and ledger path refused. A gate with neither a ledger nor `run:` has nothing to check (V110).
+
+```agenttopology
+records {
+  record trace { path: "logs/{unit}/trace.jsonl" }
+}
+```
+
+`records { record <id> { path: "<project-relative path>" } }` declares ledgers. `path` may contain `{unit}`. `append-only` and `written-by` are reserved and not implemented.
+
+**Ledger line format** (JSON Lines, one object per line). The step's own script appends the line when it finishes; agentopology only reads it:
+
+```json
+{"step": "<node id>", "unit": "<unit, omitted when none>", "ok": true, "at": "<ISO time>"}
+```
+
+A hook only covers Claude Code sessions. A step run from a terminal or a scheduler checks itself, by calling `agentopology step check <file.at> <step-id> [--unit U] [--dir D]` at its start (`by: code`): it exits 0 when every gate before that step is satisfied and 1 otherwise, naming each failing gate and why. A gate is satisfied when its ledger shows the `after:` step ok (for the unit, if given) **and**, if it has `run:`, that command exits 0 from `--dir` (default `.`); a gate with neither is unsatisfiable ("nothing to check"). A step no gate guards exits 0 with `no gate guards <step>`. It reads and runs check scripts; it never writes. The hook sees a step inside a chained command (`cd dir && cmd`, `a; cmd`, `a || cmd`, `a | cmd`, a later line) and checks each segment; it does not see one run indirectly (`bash -c`, `eval`, a script that calls the step).
 
 ---
 
@@ -1180,6 +1210,7 @@ hooks {
 |-------|------|----------|---------|
 | `on` | hook-event | yes | -- |
 | `matcher` | string | no | -- |
+| `if` | permission rule | no (tool events only) | -- |
 | `run` | string | command, prompt, agent, mod | -- |
 | `type` | hook-type | no | `command` |
 | `url` | string | http | -- |
@@ -1200,6 +1231,16 @@ Code function hooks). Its `on:` is an `engine-event` (V95); a command or
 prompt hook takes a PascalCase event. `flag:` names the env variable that
 switches the Mod on. Fields are one per line (V90).
 
+A `matcher` is tested against the tool name (or agent type, or path) alone, the
+way Claude Code reads it: only letters, digits, `_`, `-`, spaces, `,` and `|`
+mean an exact name or a list; any other character makes it an unanchored
+regex. An MCP tool is `mcp__<server>__<tool>`. Permission-rule syntax
+(`Bash(rm -rf *)`) goes in `if:`, which Claude Code reads on tool events only.
+V107 refuses a matcher that can never match and an `if:` that is never read.
+`run: "exit 2"` runs as written; only exit 2 blocks, and V108 warns on any
+other code. V109 warns when a hook with `strength: refuse` guards a server but
+its matcher misses one of the server's tools that the topology names.
+
 ---
 
 ### 4.17 `settings`
@@ -1889,13 +1930,10 @@ Bindings map universal permissions to platform-specific modes:
 | Binding | Status | Target |
 |---------|--------|--------|
 | `claude-code` | Stable | Claude Code agent files, settings, MCP config (the event-driven HOST layer) |
-| `claude-workflow` | Stable | Claude Workflow tool script (`<topology>.workflow.js`) for the deterministic fan-out rung, plus SEAM/README/LOSSY-REPORT companion files |
-| `codex` | Stable | Codex agent definitions and config |
-| `gemini-cli` | Stable | Gemini CLI agent definitions and config |
-| `copilot-cli` | Stable | GitHub Copilot CLI agent definitions and config |
-| `openclaw` | Stable | OpenClaw soul.md, skill files, channel/gateway/workspace config |
-| `kiro` | Stable | Kiro agent definitions and config |
-| `cursor` | Stable | Cursor rules and agent config |
+| `claude-workflow` | Experimental | Claude Workflow tool script (`<topology>.workflow.js`) for the deterministic fan-out rung, plus SEAM/README/LOSSY-REPORT companion files |
+| `codex` | Experimental | Codex agent definitions and config |
+| `cursor` | Experimental | Cursor rules and agent config |
+| `gemini-cli`, `copilot-cli`, `openclaw`, `kiro` | Removed in 0.10.0 | Use agentopology 0.9.x |
 | `agent-sdk` | Planned | Anthropic Agent SDK tool definitions |
 | `e2b` | Planned | E2B sandbox configuration |
 | `openai-swarm` | Planned | OpenAI Swarm agent definitions |

package/spec/testing.md

@@ -79,6 +79,21 @@ Run the live suite before every release, and after any change to a binding.
 | I3 | Import reports the flow honestly: sources used and skipped, agents wired and unknown, agents with no file; no edge is invented | e2e/import-project.test.ts |
 | N23 | Every field and block name in a node, `meta`, a hook, job, artifact, tool or skill, and every topology section, is in the AST or a V102 error naming it and its block (with the field it resembles, or the node type it belongs to); validate exits 1 and scaffold writes nothing; every field the docs list passes | e2e/unknown-names.test.ts |
 | N24 | An agent's or gate's `behavior:` outside `advisory`/`blocking` is a V103 error, never emitted unchecked | e2e/unknown-names.test.ts |
+| N27 | A generated gate fails closed: before-agent.sh and gate wrappers turn any error (unset CLAUDE_PROJECT_DIR, a missing jq or interpreter) into exit 2, a gate script nobody has written exits 2, and the guard's settings entry sets `onFailure: "block"` | e2e/fail-closed.test.ts |
+| N28 | Every generated command hook names its script by a path anchored to `$CLAUDE_PROJECT_DIR`, because Claude Code runs a hook in the session's current directory: run from a subfolder, each one is found, exits 0 or 2, and prints stdout its event accepts (conformance v0, checked against Claude Code 2.1.319) | e2e/conformance.test.ts |
+| N31 | `guard <file> --check` reads a project and reports, for every gate, approval step and deny/ask rule, how it is enforced today: refuse (its hook or rule is on disk), none (the binding generates one that is missing, or names its script by a relative path; exit 1), or hope (no hook exists for it). It prints `enforcement: k of m steps refuse` and writes nothing | e2e/guard-check.test.ts |
+| N32 | A step's enforcement is written in the file and read: `strength`, `by`, `at`, `match`, `bypass` on a gate; `strength`, `bypass` on a hook; `[strength: …, at: "…", guard: …]` on a flow edge. All round-trip through serialize, V102 knows them, and V104 to V106 check the words, the guard names and the citation form | e2e/strength.test.ts |
+| N33 | `guard --check` reads what the file cites: a gate's `at: "path:line"` is checked on disk (the file, the line, the `match:` text within 5 lines), so a refactor that moves or removes the check is `none` and exits 1; a gate with no hook of its own is credited by the hook its edge cites (`[guard: name]`) when that hook is in settings.json and declares its strength; an edge's written `[strength: none]` is reported, not failed. Credit reads "cited, not proven" | e2e/guard-check.test.ts |
+| N34 | `inventory <dir>` lists what is live in a project (the .claude tree with a sha256 per file, each settings.json hook handler, .mcp.json servers, package.json scripts) and writes nothing; `validate <file> --inventory <dir or inventory.json>` prints `coverage: k of n live things are in the .at`, lists what nothing in the .at accounts for (unmapped, a warning) and what the .at points at by hand that is not on disk (missing, exit 1); things tagged `e` are counted apart | e2e/inventory.test.ts |
+| N29 | A hook `run:` that is a shell command (`run: "exit 2"`) is written as the command itself, with no stub script named after its first word; V108 warns that `exit 1` (any code but 0 and 2) does not block | e2e/matcher.test.ts |
+| N30 | A hook matcher in permission-rule syntax (`Bash(rm -rf *)`) is a V107 error that names the fix (`matcher: "Bash"`, `if: "Bash(rm -rf *)"`); `if:` is read, round-trips, is written on the handler, and is an error on an event that is not a tool event | e2e/matcher.test.ts |
+| N36 | A matcher is read the way Claude Code reads it (exact names and lists, unanchored regex, match-all; `mcp__server` alone matches nothing). V107 refuses a matcher that can never match. V109 warns when a refuse hook guards an MCP server but misses one of its tools, from the topology's tool names or, with `--inventory`, the inventory's (`matcher gaps`) | e2e/matcher.test.ts, e2e/inventory.test.ts |
+| N37 | Claude Code's hook contract is a committed snapshot extracted from the hooks reference page (events, no-matcher events, matcher rules, handler fields, "Requires vX"), with the minimum version's contract derived from it. The conformance constants match the snapshot, and every event and handler field the binding writes exists at the minimum version. `npm run drift` diffs the snapshot with the live page and exits 1 on drift | e2e/contract-drift.test.ts |
+| N38 | A gate whose `before:` is a script step (an action with `commands:`) refuses it in Claude Code sessions. One generated `before-action.sh`, a PreToolUse Bash hook with `onFailure: "block"`, reads the command, ignores leading `VAR=value`, reads the unit with `unit-from`, and lets it through only when the LAST ledger line for the gate's `after:` step and unit has `ok: true` (missing ledger, other unit, later `ok: false`, bad JSON, unset `CLAUDE_PROJECT_DIR` all exit 2); a gate's `run:` wrapper runs too. `records`, `ledger`, `unit-from` parse and round-trip. V110 (nothing to check), V111 (bad `unit-from`), V112 (unknown ledger, unsafe record path, ambiguous ledger); V25 no longer warns for such a gate. `guard --check` reports refuse by hook, with the note that it covers Claude Code sessions only | e2e/action-guard.test.ts |
+| N39 | `agentopology step check <file.at> <step-id> [--unit U] [--dir D]` lets a script step check itself when no hook guards it (a terminal, a scheduler). It exits 0 when every gate with `before: <step-id>` holds, else 1 naming each failing gate and why: with a ledger, the last record for the `after:` step (same unit, if given) is ok; with `run:`, it exits 0 from D (default `.`); with both, both; with neither, "nothing to check" (V110's case). An unguarded step exits 0 with "no gate guards <step>"; a step that is no node exits 1. It reads and runs check scripts and never writes | e2e/step-check.test.ts |
+| N40 | `validate` ends every run (clean, warnings, errors, `--inventory`) with one dim line, `checked against Claude Code 2.1.319 (supports 2.1.295 and later)`, built from VERIFIED_ON and MINIMUM_VERSION in src/conformance/claude-code.ts; `scaffold --target claude-code` and the claude-code row of `targets` carry it too | e2e/verified-on.test.ts |
+| N41 | `guard <file> --target claude-code` writes only the guard part of scaffold into a hand-built project: the scripts settings.json hook commands run, the gate wrappers they call and the checks the gates run (found by following script paths, not listed), and the `hooks` and `permissions` of settings.json merged by the scaffold merger. No agent, skill, command, rule, .mcp.json or CLAUDE.md is written; a user's hook, permission and other keys stay; a rerun changes nothing (not even the manifest) and adds no duplicates; an edited script and a check that is no longer a stub are kept and reported; `--dry-run` writes nothing; it then prints the `--check` report and exits like it | e2e/guard-target.test.ts |
+| N42 | `before-action.sh` finds a guarded step anywhere in a chained Bash command, not only at the start of the whole line (measured: `cd repo && ./tool publish ep1`, `true; ./tool publish ep1` and `make x \|\| ./tool publish ep1` ran the step while `guard --check` reported the gate as refuse). It splits on `&&`, `\|\|`, `;`, `\|`, `&` and newlines (quoting is not parsed, which can only over-block), strips a leading `(`, `{`, `then`, `do`, `exec`, `time`, `nohup`, `env` and `VAR=value` per segment, reads `unit-from` from the matching segment, and checks every matching segment (two guarded steps in one command need both gates; a gate's check script that reads stdin does not hide a later step). `echo ./tool publish ep1` is not a step. `guard --check` notes that an indirect run (`bash -c`, `eval`, a script that calls the step) is not seen | e2e/action-guard.test.ts |
 | L2 | Real Claude Code loads a hand-built project after import then scaffold | live/claude-code.live.test.ts |
 | L3 | Real Claude Code registers a manual agent and an agent with a regex matcher and the phase-4 fields, registers `runs: fork`/`inline` nodes as skills, and runs a prompt hook | live/claude-code.live.test.ts |
 | L1 | Real Claude Code loads every scaffolded example: every agent, skill and command registers, and the session succeeds | live/claude-code.live.test.ts |
@@ -98,3 +113,4 @@ real test and the row moves to Guarantees. Source: the compile audit,
 | F4 | Agent `memory` scope (user/project/local) and `autoCompactWindow` are not first-class; `memory:` already names stores, so the scope needs another word | later |
 | N25 | An agent's `role:` is documented (spec/grammar.md §4.6) but the parser never reads it: the role text comes only from the `roles` block by agent id, so `role: analyst` on `agent classifier` is lost | later |
 | N26 | V102 does not look inside free-form or not-yet-listed blocks (`prompt`, `extensions`, `settings`, `env`, `memory`, `providers`, `mcp-servers`, `interfaces`, `triggers`, `depth`, `flow`, `defaults`, `observability`, `checkpoint`, ...): an unknown name there can still vanish | later |
+| N35 | A second `hooks { }` block in a file is dropped without a word: the parser keeps the first block's hooks, validation reports nothing, and the second block's hooks are never scaffolded | later |

package/spec/validation.md

@@ -665,7 +665,7 @@ agent researcher {
 
 ## Summary Table
 
-All 103 rules, generated from `src/parser/validator.ts` so the spec cannot drift
+All 112 rules, generated from `src/parser/validator.ts` so the spec cannot drift
 from the implementation. Rules V8, V12, V23, V24, V89, V90, V98 and V102 are collected at
 **parse time** — the misuse they catch leaves no trace in the AST — and surfaced
 through the validator like any other rule.
@@ -698,7 +698,7 @@ through the validator like any other rule.
 | V22 | error/warning | Every model in a fallback-chain should exist in at least one provider's models list |
 | V23 | error/warning | Duplicate top-level singleton sections |
 | V24 | error/warning | Unknown sub-blocks in the `memory` section |
-| V25 | error/warning | `on-fail: bounce-back` enforcement depends on the gate's `after` target |
+| V25 | error/warning | `on-fail: bounce-back` enforcement depends on the gate's `after` target (a gate before an action with `commands:` is compiled to before-action.sh and does not warn) |
 | V26 | error/warning | `action.kind` must be one of the allowed values |
 | V27 | error/warning | `agent.permissions` should be one of the known values |
 | V28 | error/warning | `metering.format` must be one of the allowed values |
@@ -777,6 +777,15 @@ through the validator like any other rule.
 | V101 | error | An agent's `runs:` is `subagent`, `inline` or `fork`, and an `independent` node does not run `inline` (it would read the author's reasoning) |
 | V102 | error | Every field and block name in a node, `meta`, a hook, job, artifact, tool or skill, and every topology section, is one the parser reads — a typo, a field of another node type or an unknown block vanished from the AST while validate passed. Contents of free-form blocks (`prompt`, `extensions`, `settings`, `env`, `memory`, ...) are not checked yet |
 | V103 | error | An agent's or gate's `behavior:` is `advisory` or `blocking` — any other value was kept and emitted into the scaffold unchecked |
+| V104 | error | `strength:` (on a gate, a hook or a flow edge) is `refuse`, `detect`, `hope` or `none`, and a gate's `by:` is `code`, `hook`, `settings` or `gate` |
+| V105 | error | A flow edge's `guard:` names a hook in `hooks { }` or a gate in `gates { }`, so an edge is never credited with a refusal nothing provides |
+| V106 | error | An `at:` citation is a safe project-relative `"path"` or `"path:line"`, and a gate's `match:` has an `at:` to be looked for in. Whether the file, line and match text exist is read by `guard --check`, never by validate |
+| V107 | error | A hook matcher can match: not permission-rule syntax (`Bash(rm -rf *)`, which belongs in `if:`), not the dotted `mcp.server.*` form, not a bare `mcp__server` (which matches no tool), and a regex that compiles. A hook's `if:` sits on a tool event, the only ones Claude Code reads it on |
+| V108 | warning | A hook's `run: "exit N"` with N other than 0 or 2 does not block: only exit 2 blocks |
+| V109 | warning | A hook with `strength: refuse` on PreToolUse or PermissionRequest that matches a tool of an MCP server matches every tool of that server the topology names (`validate --inventory` adds the inventory's tool names) |
+| V110 | warning | A gate before an action with `commands:` has neither a ledger (explicit, or the only record) nor `run:`, so there is nothing to check |
+| V111 | error | An action's `unit-from` is not a valid regex, or has no capture group |
+| V112 | error | A gate's `ledger:` names no declared record; a record path is unsafe (`{unit}` allowed); or a gate before an action needs a ledger, names none, and several records exist |
 
 > Sections above document the first 35 rules with worked examples. The rest are
 > single-line entries here plus their doc comment in the source. Adding an

package/dist/__tests__/live/zz-debug.test.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=zz-debug.test.d.ts.map

package/dist/__tests__/live/zz-debug.test.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"zz-debug.test.d.ts","sourceRoot":"","sources":["../../../src/__tests__/live/zz-debug.test.ts"],"names":[],"mappings":""}

package/dist/__tests__/live/zz-debug.test.js

@@ -1,4 +0,0 @@
-import { it } from "vitest";
-import { spawnSync } from "node:child_process";
-it("debug", () => { const r = spawnSync("sh", ["-c", "command -v claude; claude --version; echo $PATH | tr ':' '\n' | head -5"], { encoding: "utf8" }); console.log(r.stdout, r.stderr); });
-//# sourceMappingURL=zz-debug.test.js.map

package/dist/__tests__/live/zz-debug.test.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"zz-debug.test.js","sourceRoot":"","sources":["../../../src/__tests__/live/zz-debug.test.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,EAAE,EAAE,MAAM,QAAQ,CAAC;AAC5B,OAAO,EAAE,SAAS,EAAE,MAAM,oBAAoB,CAAC;AAC/C,EAAE,CAAC,OAAO,EAAE,GAAG,EAAE,GAAG,MAAM,CAAC,GAAG,SAAS,CAAC,IAAI,EAAE,CAAC,IAAI,EAAE,yEAAyE,CAAC,EAAE,EAAE,QAAQ,EAAE,MAAM,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,GAAG,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC"}

package/dist/bindings/copilot-cli.d.ts

@@ -1,20 +0,0 @@
-/**
- * GitHub Copilot CLI binding.
- *
- * Generates the `.github/` directory structure for GitHub Copilot CLI
- * (terminal agent) and Copilot Coding Agent (server-side):
- * - `.github/copilot-instructions.md` — project-level instructions
- * - `.github/instructions/{id}.instructions.md` — per-agent scoped instructions
- * - `.github/agents/{id}.agent.md` — per-agent definitions with tools and prompt
- * - `.github/copilot/settings.json` — CLI config (MCP, permissions)
- * - `.github/skills/{name}/SKILL.md` — agent skills
- * - `.github/hooks/{name}.json` — preToolUse/postToolUse hooks
- * - `.github/workflows/copilot-setup-steps.yml` — server-side env setup
- * - `AGENTS.md` — topology overview
- *
- * @module
- */
-import type { BindingTarget } from "./types.js";
-/** GitHub Copilot CLI binding. */
-export declare const copilotCliBinding: BindingTarget;
-//# sourceMappingURL=copilot-cli.d.ts.map

package/dist/bindings/copilot-cli.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"copilot-cli.d.ts","sourceRoot":"","sources":["../../src/bindings/copilot-cli.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AAeH,OAAO,KAAK,EAAE,aAAa,EAAiB,MAAM,YAAY,CAAC;AAm/C/D,kCAAkC;AAClC,eAAO,MAAM,iBAAiB,EAAE,aAiF/B,CAAC"}