@jaybeeuu/agent-cortex 1.43.0 → 2.1.0

package/.agents/skills/style-versioning/SKILL.md

@@ -82,7 +82,7 @@ changeset to make it green.
 The `release` job in `.github/workflows/ci.yml` handles everything automatically:
 
 1. **Detects new changesets** on main
-2. **Creates a "Version Packages" PR** — the `version` step runs `pnpm version-packages`, which bumps `package.json`, syncs `plugin.json` (via `scripts/sync-plugin-version.sh`), updates `CHANGELOG.md`, and regenerates the committed Copilot output (`pnpm build:copilot`; the Claude plugin is materialised at install time with the package version, so it has no committed output to regenerate) so the drift gates never fail on a version bump
+2. **Creates a "Version Packages" PR** — the `version` step runs `pnpm version-packages` (`changeset version`), which bumps `package.json` and rewrites `CHANGELOG.md`. That is the whole release surface: every plugin this package ships is materialised at install time with the package version, so there is no generated output to regenerate and no drift gates to satisfy on a version bump
 3. **When "Version Packages" is merged**:
    - Creates a git tag
    - Publishes to npm — `pnpm publish-package` packs with `pnpm pack` and publishes with `npm publish --provenance --access public`. Authenticates via npm Trusted Publishing (OIDC): the release job's `id-token` permission lets npm exchange a GitHub OIDC token for a short-lived npm token at publish time, so no `NPM_TOKEN` secret or `.npmrc` auth config is required — only the one-time npm-side Trusted Publishing setup on npmjs.com (package → Access → Trusted Publishing → GitHub repo `jaybeeuu/agent-cortex` + workflow `.github/workflows/ci.yml`)
@@ -141,18 +141,17 @@ human-only follow-ups, including the merge probe that closes AC1.
 
 ### Version lockstep
 
-All version numbers stay in lockstep automatically:
+Two files carry the version, in lockstep automatically:
 
 1. `package.json` → bumped by changesets
-2. `plugin.json` → synced by `scripts/sync-plugin-version.sh`
-3. `CHANGELOG.md` → generated by changesets
+2. `CHANGELOG.md` → generated by changesets
 
 **Never bump versions manually.** Always create a changeset file.
 
 ## Common mistakes
 
 - **Running `pnpm changeset`**: Interactive, wastes tokens. Write the file directly.
-- **Bumping versions manually**: Don't touch `"version"` in `package.json` or `plugin.json`. Create a changeset.
+- **Bumping versions manually**: Don't touch `"version"` in `package.json`. Create a changeset.
 - **Omitting the changeset**: CI fails the PR. Publishing is the default; the only
   opt-out is the `no-publish` label, which must already exist in the repo's settings.
 - **Wrong bump type**: `patch` for fixes, `minor` for additions, `major` for breakage. When in doubt, ask the user.
@@ -170,4 +169,4 @@ All version numbers stay in lockstep automatically:
 | Agent bumps versions locally | Agent writes a changeset file |
 | Manual GitHub release creation | Automated by the `release` job in `ci.yml` |
 | `publish.yml` triggered by release | `ci.yml` release job on push to main |
-| Version sync was manual | `sync-plugin-version.sh` runs automatically |
+| Version files synced by hand | changesets bumps `package.json` + `CHANGELOG.md` |

package/.github/workflows/ci.yml

@@ -220,11 +220,6 @@ jobs:
           PLUGIN_VERSION=$(node -p "require('$OUT/.claude-plugin/plugin.json').version")
           test "$PKG_VERSION" = "$PLUGIN_VERSION"
 
-      - name: Check generated Copilot agent files are up to date
-        run: |
-          pnpm build:copilot
-          git diff --exit-code -- 'agents/*.agent.md'
-
   release:
     name: Release
     needs: [lint, test, claude-plugin-check]
@@ -288,12 +283,10 @@ jobs:
           # changesets/action execs these inputs via @actions/exec with NO shell:
           # the string is split by argStringToArray on whitespace (single quotes
           # survive literally), so each must be a single unquoted command token
-          # that runs a pnpm script. version-packages bumps versions, syncs
-          # plugin.json, THEN regenerates the committed Copilot output
-          # (build:copilot re-derives agents/*.agent.md; the Claude plugin is
-          # materialised at install time with the package version, so nothing
-          # committed needs regenerating) before the action commits, so the
-          # Version Packages PR always passes the drift gates.
+          # that runs a pnpm script. version-packages bumps the package version
+          # and rewrites CHANGELOG.md, and nothing else is committed: the Claude
+          # plugin is materialised at install time with the package version, so
+          # there is no committed output to regenerate.
           version: pnpm version-packages
           # pnpm publish-package when the merged PR is unlabelled, pnpm
           # publish-noop when it carries `no-publish`.

package/AGENTS.md

@@ -4,20 +4,17 @@ Instructions for agents working on this repository.
 
 ## What This Repo Is
 
-A personal Copilot CLI plugin containing custom agents and skills, shipped to Copilot, pi,
-and Claude Code, plus PI extensions and Claude hooks for enhancing the coding agent
-runtime. Changes here affect the behaviour of every agent, skill, and PI extension
-available in the author's coding sessions.
+A personal collection of custom agents and skills, shipped to pi and Claude Code, plus PI
+extensions and Claude hooks for enhancing the coding agent runtime. Changes here affect the
+behaviour of every agent, skill, and PI extension available in the author's coding sessions.
 
 ## Structure
 
 ```
 agent-cortex/
 ├── package.json           # PI package manifest (pi: { extensions, skills }) + pi runtime deps
-├── plugin.json            # GitHub Copilot plugin manifest — agents, skills, MCP servers
 ├── agents/                # Custom agents — canonical composable <name>/ dirs
-│   ├── *.agent.md         #   generated from <name>/ by scripts/build-copilot-agents.mjs
-│   ├── ralph/             #   composable format — see agents/README.md
+│   ├── ralph/             #   composable format (shared agent.md + pi/, claude/) — see agents/README.md
 │   ├── plan/              #   "
 │   ├── ralph-plan/        #   "
 │   └── strategy/          #   "
@@ -44,7 +41,7 @@ agent-cortex/
 ## Versioning
 
 Use `pnpm changeset` for all version bumps. Never edit versions manually.
-`package.json`, `plugin.json`, and `CHANGELOG.md` stay in lockstep automatically.
+`package.json` and `CHANGELOG.md` stay in lockstep automatically.
 See the `style-versioning` skill for the full workflow.
 
 ## Changelog
@@ -69,12 +66,14 @@ Generated automatically by changesets. Do not edit `CHANGELOG.md` manually.
 ## Skill Conventions
 
 - **Skills are portable, not repo documentation.** `skills/` is installed onto arbitrary machines
-  (Copilot, pi, Claude Code), so it describes general practice and the author's portable
+  (pi, Claude Code), so it describes general practice and the author's portable
   preferences — never how this repository is configured or how to work in it. Facts about this
   checkout (branch bases, merge method, signature rules, required checks, release mechanics) belong
   in `AGENTS.md`, `docs/`, or the tracker. Repo-local `.agents/skills/` follows the same rule: a
   skill is a skill, not a place for this repo's configuration.
-- `SKILL.md` must include a YAML front-matter block with `name` and `description`.
+- `SKILL.md` must include a YAML front-matter block with `name` and `description`. `pnpm lint`
+  enforces this (`pnpm check:skills`), because PI silently drops a skill whose frontmatter it
+  cannot parse.
 - `description` must be ≤ 1024 characters. First sentence: what it does. Second: "Use when…".
 - Keep `SKILL.md` near the ~150-line target in `docs/skills/skill-anatomy.md`, overflowing into
   purpose-named support files (`REFERENCE.md`, `EXAMPLES.md`, `FORMAT.md`). `style-tests`
@@ -88,13 +87,10 @@ Generated automatically by changesets. Do not edit `CHANGELOG.md` manually.
 ## Agent Conventions
 
 - Agents live in composable `<name>/` directories under `agents/`: a shared `agent.md` body plus
-  per-harness subdirectories `pi/`, `copilot/`, `claude/` (frontmatter.json and optional section
-  files) per the spec in `agents/README.md`. `ralph`, `plan`, `ralph-plan`, and `strategy` all use
-  the composable layout. The flat `agents/*.agent.md` files are **generated output** — composed
-  from the canonical directories by the shared `bin/installers/copilot.mjs` code path behind both
-  `agent-cortex install copilot` and `scripts/build-copilot-agents.mjs` (thin wrapper), and
-  committed for Copilot CLI (plugin.json `agents: "agents/"` scans for `*.agent.md`); never edit
-  them by hand. The Claude plugin is materialised by the install-time generator
+  per-harness subdirectories `pi/` and `claude/` (frontmatter.json and optional section files) per
+  the spec in `agents/README.md`. `ralph`, `plan`, `ralph-plan`, and `strategy` all use the
+  composable layout, and no flat agent file is committed — each harness renders its own at install
+  time. The Claude plugin is materialised by the install-time generator
   `bin/installers/claude.mjs`: a plain `agent-cortex install claude` copies it into
   `~/.agent-cortex/claude` (skills copied flat with `{{TOOL:...}}`/`{{PATH:...}}` substituted,
   never symlinked), writes the marketplace manifest at

package/CHANGELOG.md

@@ -1,5 +1,71 @@
 # Changelog
 
+## 2.1.0
+
+### Minor Changes
+
+- a4658cf: Add the `output-style` pi extension: it appends an always-on reply-shape block to the PI
+  system prompt — lead with the action, write in Simplified Technical English (ASD-STE100),
+  and restate context instead of citing beads, phases, or stages by ID alone.
+
+  The block lives in `extensions/output-style/output-style.md` and is also written to the managed
+  section of `~/.claude/CLAUDE.md` by `agent-cortex install claude`, so Claude Code receives the
+  same rules alongside pi.
+
+### Patch Changes
+
+- a30f3c4: Make ralph's PR gate brake depend on a gate being _unblocked_, and count gates
+  on the current HITL label axis.
+
+  `create-chores` pre-creates a `lifecycle:feature-pr` gate for every planned
+  feature, blocked behind that feature's own `document` chore. Ralph's rule — "do
+  not schedule new parent features while any HITL gate bead is open" — therefore
+  matched every unstarted feature, so the brake was permanently on: with eight
+  open gates, none of them actionable, no new feature could ever be dispatched.
+  The pause query had drifted the other way: it filtered on the legacy
+  `implementation-type:hitl` axis only, so gates migrated to `execution:hitl`
+  were invisible and pending human action was under-reported.
+
+  - `skills/workflow/ralph/scripts/pending-gates.mjs` resolves the question in one
+    place: `pendingHumanAction` holds unblocked gates plus epics tagged
+    `awaiting-epic-pr-merge` and is the only scheduling brake; `parked` holds
+    gates still blocked behind their own pipeline, which never stop dispatch and
+    never appear in the Pending Human Action table.
+  - Gate queries match `lifecycle:feature-pr` on either HITL axis, so gates
+    created on either side of the two-axis migration are counted.
+  - ralph's composable agent source (`agents/ralph/agent.md`) and the ralph skill
+    and REFERENCE now point at the script instead of restating ad-hoc `bd` queries
+    that had already drifted.
+  - `agents-native/ralph.md` (the Claude harness) keeps the **open**-gate form and
+    only takes the dual-axis query: its gates stay blocked for their whole life —
+    `create-task` blocks them behind a `document` chore no Claude ralph closes, and
+    the native route deps them onto the still-open feature bead — so the unblocked
+    predicate would never fire there and ralph would report "All beads complete."
+    with PRs unmerged. REFERENCE.md now states the invariant: a gate blocked by its
+    parent feature bead is not parked in any harness, so a gate must not carry a
+    `blocks` dependency onto its own feature.
+
+  Reconcile with agnt-ctx-s5xd.10 (ralph harness unification) when that rewrites
+  ralph's agent files — it owns collapsing the two predicates into one.
+
+- e5e7683: Fail `pnpm lint` when a SKILL.md frontmatter cannot be parsed, is missing `name` or `description`, or has a description longer than 1024 characters. PI previously dropped such skills silently.
+
+## 2.0.0
+
+### Major Changes
+
+- 847ce42: Remove Copilot CLI as a deploy target. `agent-cortex install copilot` is gone (the
+  supported harnesses are now `claude` and `pi`), along with the Copilot plugin manifest
+  `plugin.json`, the `build:copilot` script and its committed `agents/*.agent.md` output,
+  the `agents/*/copilot/` harness dirs, `scripts/sync-plugin-version.sh`, the `postinstall`
+  hook and `scripts/install-instructions.sh` that wrote `~/.copilot/copilot-instructions.md`,
+  and the Copilot column of `token-map.json`.
+
+  `version-packages` is now plain `changeset version`: the release surface is
+  `package.json` + `CHANGELOG.md`, since every plugin is materialised at install time with
+  the package version. Nothing is swept from an existing `~/.copilot` install — remove
+  `~/.copilot/installed-plugins/_direct/agent-cortex` by hand.
+
 ## 1.43.0
 
 ### Minor Changes

package/README.md

@@ -1,21 +1,18 @@
 # agent-cortex
 
-A personal collection of custom agents and skills, shipped to three harnesses from one
-source: the [GitHub Copilot CLI](https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/plugins-creating),
-pi, and [Claude Code](https://code.claude.com/docs) (as a plugin).
+A personal collection of custom agents and skills, shipped to two harnesses from one
+source: pi and [Claude Code](https://code.claude.com/docs) (as a plugin).
 
 ## Structure
 
 ```
 agent-cortex/
-├── plugin.json               # Copilot plugin manifest
 ├── agents/                   # Canonical agents — composable <name>/ dirs (see agents/README.md)
-│   ├── *.agent.md            #   ralph, ralph-plan, plan, strategy — GENERATED from <name>/ by scripts/build-copilot-agents.mjs
-│   ├── ralph/                #   composable form (shared agent.md + per-harness pi/, copilot/, claude/)
+│   ├── ralph/                #   composable form (shared agent.md + per-harness pi/, claude/)
 │   ├── plan/                 #   "
 │   ├── ralph-plan/           #   "
 │   └── strategy/             #   "
-├── agents-native/            # Claude-only agents with no Copilot equivalent
+├── agents-native/            # Claude-only agents
 │   └── ralph.md              #  the lean Claude Ralph
 ├── skills/                   # Skills (grouped by domain) — shared by all harnesses
 │   ├── engineering/          #  tdd, improve-codebase-architecture, …
@@ -27,6 +24,7 @@ agent-cortex/
 ├── extensions/               # pi extensions (pi only)
 │   ├── agent-guardrails/     #   behavioural circuit-breakers in the system prompt
 │   ├── agent-modes/          #   switchable agent modes (reads composable agents/)
+│   ├── output-style/         #   reply shape: STE, action-first, restated context
 │   ├── skill-stats/
 │   └── notify/
 ├── pi/                       # Committed pi config templates (see below)
@@ -37,23 +35,18 @@ agent-cortex/
 ├── bin/
 │   ├── agent-cortex.mjs      # CLI entrypoint
 │   └── installers/
-│       ├── copilot.mjs       # shared generator: agent-cortex install copilot + scripts/build-copilot-agents.mjs
-│       └── claude.mjs        # materialises ~/.agent-cortex/claude + ~/.claude/settings.json, registers with Claude Code (--output <dir> = generate-only)
-├── scripts/
-│   └── build-copilot-agents.mjs  # thin wrapper over bin/installers/copilot.mjs (regenerates agents/*.agent.md)
+│       ├── claude.mjs        # materialises ~/.agent-cortex/claude + ~/.claude/settings.json, registers with Claude Code (--output <dir> = generate-only)
+│       └── pi.mjs            # stages ~/.agent-cortex/pi + registers it with pi (--output <dir> = stage-only)
 ├── claude/                   # Committed Claude user-settings template (settings.json) — merged into ~/.claude/settings.json
 └── claude-extras/            # Hand-authored Claude plugin extras
     ├── .mcp.json             #  MCP servers (context7, github) — copied into installs
     └── scripts/              #  statusline-command.sh — copied into installs (executable)
 ```
 
-The same `agents/` and `skills/` power three harnesses (Copilot, pi, Claude Code).
-The composable `agents/<name>/` directories are the single source of truth; the flat
-`agents/*.agent.md` files are **generated** by the shared copilot installer
-(`agent-cortex install copilot`, or `scripts/build-copilot-agents.mjs` via
-`pnpm build:copilot` — both run the same `bin/installers/copilot.mjs` code path, so
-install-time and build-time output can never diverge) and committed so Copilot CLI
-(plugin.json `agents: "agents/"`) and pi keep loading the agents — don't hand-edit them.
+The same `agents/` and `skills/` power two harnesses (pi and Claude Code). The composable
+`agents/<name>/` directories are the single source of truth, and no flat agent file is
+committed: `agent-cortex install claude` and `agent-cortex install pi` each render their own
+from the canonical directories, so install-time output can never drift from the sources.
 The `{{TOOL:...}}` / `{{PATH:...}}` tokens written in agent and skill files are resolved
 per harness at install time from `token-map.json`, the single source of truth for
 canonical tool/path/agent names (see `token-map.README.md` and the `contract` section).
@@ -76,15 +69,13 @@ temp-dir install plus structural checks:
 - **Agents** can't be shared files (the frontmatter formats differ), so the materialised
   plugin's `agents/*.md` are composed from the canonical `agents/<name>/` directories' `claude/`
   harness dirs
-  (frontmatter.json + section files), exactly like the Copilot flats are composed from their
-  `copilot/` dirs. Claude only loads agents from a plugin's default `agents/` dir, so the plugin
-  ships them at its own root (default `~/.agent-cortex/claude/agents/`) — isolating them from the
-  Copilot `.agent.md` files.
-- **Claude-native agents** that have no Copilot equivalent live in `agents-native/*.md` and are
-  copied verbatim into the materialised plugin's `agents/`. `ralph` is one: it is reimplemented
-  for Claude around
-  background workers + an independent review gate (the Copilot Ralph's `task`/`read_agent`
-  poll loop has no Claude equivalent), so it can't be mechanically converted.
+  (frontmatter.json + section files). Claude only loads agents from a plugin's default `agents/`
+  dir, so the plugin ships them at its own root (default `~/.agent-cortex/claude/agents/`).
+- **Claude-native agents** that cannot be composed from a shared body live in
+  `agents-native/*.md` and are copied verbatim into the materialised plugin's `agents/`. `ralph`
+  is one: it is reimplemented for Claude around background workers + an independent review gate
+  (Claude's event-driven completion delivery has no `task`/`read_agent` poll loop to reuse), so
+  it can't be mechanically converted.
 - **Manifests** are generated too: the plugin's `.claude-plugin/plugin.json` (its `version`
   tracks `package.json`, so it never goes stale) and `hooks.json` (copied from the canonical
   `hooks/claude/hooks.json` source), plus any support files under `hooks/claude/` bundled into
@@ -94,8 +85,8 @@ temp-dir install plus structural checks:
   extension→hook mapping and the rejections (auto-name, agent-guardrails, skill-stats, subagent, agent-modes).
 
 Edit the sources (`agents/<name>/` composable dirs, `agents-native/*.md`, `skills/**`,
-`hooks/claude/`, `claude-extras/`, `package.json`), never the generated
-`agents/*.agent.md` files or anything under the materialised `~/.agent-cortex/claude`.
+`hooks/claude/`, `claude-extras/`, `package.json`), never anything under the materialised
+`~/.agent-cortex/claude`.
 
 ## CI
 
@@ -117,9 +108,8 @@ validates the Claude plugin **materialiser** instead of diffing a committed mirr
 it runs `node bin/agent-cortex.mjs install claude --output <tmp dir>` and checks the
 result structurally — `plugin.json` version tracks `package.json`, every generated and
 hand-authored piece is present, no literal `{{TOOL:...}}`/`{{PATH:...}}` tokens survive,
-and no symlinks leak into the copied tree. The Copilot drift check
-(`pnpm build:copilot` + `git diff --exit-code -- 'agents/*.agent.md'`) still guards the
-committed flat agent files.
+and no symlinks leak into the copied tree. There is no committed agent file to drift-check:
+the `agents/` tree holds the composable sources only, and both installers render from them.
 
 A separate `changeset-check` job runs on every pull request and fails it unless the
 PR adds a `.changeset/*.md` file. **Publishing is the default and `no-publish` is the
@@ -133,11 +123,10 @@ changeset.
 On pushes to `main`, a `release` job (gated on `lint`, `test`, and
 `claude-plugin-check`) runs changesets to open a `chore: version packages` PR when
 changesets are pending, then publishes to npm once it lands. The version step runs
-`pnpm version-packages` — bumping `package.json`, syncing `plugin.json`, and
-regenerating the committed Copilot agent files (the Claude plugin is materialised at
-install time with the package version, so it has no committed output to regenerate)
-so the drift gates stay green; the publish step runs `pnpm publish-package` (pack +
-provenance publish), or
+`pnpm version-packages` — `changeset version`, which bumps `package.json` and rewrites
+`CHANGELOG.md` and touches nothing else (both plugins are materialised at install time
+with the package version, so there is no committed output to regenerate); the publish
+step runs `pnpm publish-package` (pack + provenance publish), or
 `pnpm publish-noop` when the merged PR carried `no-publish`. Labels are invisible on
 a push event, so the job resolves the PR merged for the pushed commit through the
 GitHub API and reads its labels — no extra secret or scope, since the job already
@@ -262,18 +251,25 @@ templates** for your own pi configuration. They are not installer output: pi's
 `settings.json` and `keybindings.json` are pi's own user config, so
 `agent-cortex install pi` leaves them alone.
 
-### Copilot plugin (separate)
+### Removing a stale Copilot install
 
-```sh
-copilot plugin install jaybeeuu/agent-cortex
-```
-
-Or install a local checkout:
+Copilot CLI is no longer a deploy target: `agent-cortex install copilot` and the
+`plugin.json` manifest are gone, and nothing in this package reads or writes `~/.copilot`
+any more. No installer sweeps an existing install, so a machine that used the old target
+keeps a stale plugin, a cached marketplace, and an instruction block until you remove them
+by hand:
 
 ```sh
-copilot plugin install ./agent-cortex
+rm -rf ~/.copilot/installed-plugins/_direct/agent-cortex
+rm -rf ~/.cache/copilot/marketplaces/https---github-com-jaybeeuu-agent-cortex
+sed -i.bak '/<!-- agent-cortex:start -->/,/<!-- agent-cortex:end -->/d' \
+  ~/.copilot/copilot-instructions.md
 ```
 
+The first two paths are the old install and its marketplace cache. The `sed` deletes only
+the agent-cortex block the removed `postinstall` hook appended to Copilot's own
+instructions file, leaving the rest of that file — and a `.bak` copy — intact.
+
 ### Claude Code plugin (separate)
 
 A plain `agent-cortex install claude` **materialises** the plugin into the home install
@@ -284,7 +280,10 @@ manifest at `~/.agent-cortex/.claude-plugin/marketplace.json` exposing `./claude
 registers it with Claude Code, and merges the committed `claude/settings.json` template into
 `~/.claude/settings.json`: the template supplies defaults, personal values win, and the
 installer owns exactly `enabledPlugins` + `extraKnownMarketplaces` — every other key
-(`permissions`, `hooks`, `env`, `statusLine`, unknown keys) is preserved. The only committed
+(`permissions`, `hooks`, `env`, `statusLine`, unknown keys) is preserved. It also writes the
+managed section of `~/.claude/CLAUDE.md` — the reply-shape block the pi `output-style`
+extension appends, taken from the same source file — and leaves every other line of that
+file alone. The only committed
 Claude config is that template plus the hand-authored extras in `claude-extras/`
 (`.mcp.json`, `scripts/`); the plugin subtree is generated at install time — there is nothing
 to drift.
@@ -293,10 +292,6 @@ The generate-only `--output <dir>` form is for previewing and CI validation; the
 documented path is the plain install to `~/.agent-cortex/claude`:
 
 ```sh
-pnpm build:copilot   # or: node scripts/build-copilot-agents.mjs (regenerates agents/*.agent.md)
-node bin/agent-cortex.mjs install copilot          # regenerates agents/*.agent.md in place
-node bin/agent-cortex.mjs install copilot --dry-run       # plan only, no writes
-node bin/agent-cortex.mjs install copilot --output /tmp/x # preview the flat files elsewhere
 node bin/agent-cortex.mjs install claude           # materialises ~/.agent-cortex/claude + marketplace manifest AND registers it with Claude Code (user scope, idempotent)
 node bin/agent-cortex.mjs install claude --dry-run       # plan generation + registration, no writes/spawns
 node bin/agent-cortex.mjs install claude --require-register  # fail (non-zero exit) when the claude CLI can't drive registration
@@ -350,6 +345,12 @@ supplies defaults and personal values win; the installer owns exactly `enabledPl
 never touched. A legacy symlinked `settings.json` is replaced with a real file rather than
 written through, and `--output` leaves the user's Claude config alone.
 
+It also writes the managed section of `~/.claude/CLAUDE.md` (Claude's user memory), delimited
+by `<!-- BEGIN agent-cortex:output-style -->` / `<!-- END agent-cortex:output-style -->`. The
+content is `extensions/output-style/output-style.md` — the same file the pi extension appends
+to its system prompt — so both harnesses carry one copy of the rules. Text outside the
+markers is never touched; a file with only one marker is left unchanged with a warning.
+
 The equivalent manual registration adds a marketplace root by **absolute path** (a bare `.` is
 rejected) — the home install root (`~/.agent-cortex`) is the marketplace root written by
 the plain install; the repo checkout ships no manifest:
@@ -428,18 +429,19 @@ extension→hook audit.
 #### Not ported / follow-ups
 
 - Only `session-start` and `notify` had Claude equivalents (both ported to hooks); the other
-  pi `extensions/` (auto-name, agent-guardrails, skill-stats, subagent, agent-modes) have none — the audit and
+  pi `extensions/` (auto-name, agent-guardrails, skill-stats, subagent, agent-modes) have none — `output-style`
+  reaches Claude through the managed `CLAUDE.md` section instead; the audit and
   rejection rationale live in `docs/claude-hooks.md`.
 - Ralph follow-ups: multi-feature epic branches, and a GitHub-trigger routine to auto-resume
   after a PR merge (instead of manual re-invocation).
-- The Copilot/pi Ralph (the 4-stage `run-pipeline-stage` pipeline) is unchanged; those two
+- The pi Ralph (the 4-stage `run-pipeline-stage` pipeline) is unchanged; those two
   ralph-coupled skills (`ralph`, `run-pipeline-stage`) are intentionally not shipped to Claude.
 
 #### Contributing to the Claude plugin
 
 Edit the **sources** — the composable `agents/<name>/` directories (shared `agent.md` +
-per-harness frontmatter/sections, auto-composed by `scripts/build-copilot-agents.mjs` and
-`bin/installers/claude.mjs`), `agents-native/*.md` (Claude-only
+per-harness frontmatter/sections, composed by `bin/installers/claude.mjs`),
+`agents-native/*.md` (Claude-only
 agents like `ralph` — the canonical bodies the installer copies verbatim), `skills/**`,
 `hooks/claude/hooks.json` (hook config), `claude/settings.json` (the user-settings template
 merged into `~/.claude/settings.json`), `claude-extras/` (hand-authored `.mcp.json` and
@@ -449,7 +451,5 @@ version — picked up at install time) — then run
 re-registers it; `--output <dir>` generates a preview only). The only committed file under
 `claude/` is the settings template; `~/.agent-cortex/claude` is generated in full
 (`.claude-plugin/plugin.json`, `agents/`, `skills/`, `hooks.json`, `.mcp.json`, `scripts/`)
-so never edit anything under it. The generated `agents/*.agent.md` files are still
-drift-checked by CI (`git diff --exit-code -- 'agents/*.agent.md'`), and CI validates the
-Claude materialiser (structural checks on a temp-dir install) so sources and installer can
-never silently diverge.
+so never edit anything under it. CI validates the Claude materialiser (structural checks on
+a temp-dir install) so sources and installer can never silently diverge.

package/agents/README.md

@@ -4,7 +4,7 @@ This document defines the canonical format for composable agent directories in a
 
 ## Motivation
 
-The original format used a single `*.agent.md` file per agent, combining harness-agnostic logic with harness-specific configuration. This created duplication when the same agent needed to run on multiple harnesses (PI, Copilot, Claude) with different tool names and polling mechanisms.
+The original format used a single `*.agent.md` file per agent, combining harness-agnostic logic with harness-specific configuration. This created duplication when the same agent needed to run on multiple harnesses (PI, Claude) with different tool names and polling mechanisms.
 
 The composable directory format separates concerns:
 
@@ -21,9 +21,6 @@ agents/
 │   ├── pi/
 │   │   ├── frontmatter.json        # PI-specific metadata
 │   │   └── <section>.md            # Optional: PI-specific sections
-│   ├── copilot/
-│   │   ├── frontmatter.json        # Copilot-specific metadata
-│   │   └── <section>.md            # Optional: Copilot-specific sections
 │   └── claude/
 │       ├── frontmatter.json        # Claude-specific metadata
 │       └── <section>.md            # Optional: Claude-specific sections
@@ -37,9 +34,6 @@ agents/ralph/
 ├── pi/
 │   ├── frontmatter.json            # PI tools: ["bash", "task", "read_agent", "wait_for_agents"]
 │   └── polling.md                  # PI completion: blocking wait_for_agents (no poll timer)
-├── copilot/
-│   ├── frontmatter.json            # Copilot tools: ["bash", "task", "read_agent"]
-│   └── polling.md                  # Copilot completion: sleep-120 poll timer + read_agent
 └── claude/
     ├── frontmatter.json            # Claude tools: ["bash", "task"]
     └── polling.md                  # Claude event-driven (no polling)
@@ -52,8 +46,6 @@ agents/plan/
 ├── agent.md                        # Shared body (planning workflow)
 ├── pi/
 │   └── frontmatter.json            # PI tools
-├── copilot/
-│   └── frontmatter.json            # Copilot tools
 └── claude/
     └── frontmatter.json            # Claude tools
 ```
@@ -143,9 +135,8 @@ When composing the final agent file for a specific harness:
 2. Replace `{{SECTION:name}}` with content from `<harness>/<name>.md`
 3. `{{TOOL:name}}` and `{{PATH:name}}` are resolved against `token-map.json` — the
    canonical tool/path/agent names per harness. `scripts/lib/compose-agent.mjs` (used by
-   `build:copilot` and by `bin/installers/claude.mjs` / `bin/installers/pi.mjs`) resolves them when
-   generating the flat files / installing for claude and pi; pi's `agent-modes` extension does the
-   same at runtime. See the `contract` section of `token-map.json` and
+   `bin/installers/claude.mjs` / `bin/installers/pi.mjs`) resolves them when generating the flat
+   files / installing for claude and pi; pi's `agent-modes` extension does the same at runtime. See the `contract` section of `token-map.json` and
    `token-map.README.md` for the rules.
 
 The pi harness's `agent-modes` extension is a runtime consumer of this format: it
@@ -201,7 +192,6 @@ Agents like `plan`, `ralph-plan`, and `strategy` that have identical behavior ac
 agents/plan/
 ├── agent.md              # Shared body (same for all harnesses)
 ├── pi/frontmatter.json   # PI tools
-├── copilot/frontmatter.json  # Copilot tools
 └── claude/frontmatter.json    # Claude tools
 ```
 
@@ -211,14 +201,12 @@ agents/plan/
 2. Migrate ralph agent first (proves the pattern) — DONE
 3. Migrate plan, ralph-plan, strategy agents — DONE
 4. Update the installer/composer to handle the new format
-5. Remove old `*.agent.md` files — DONE (the flat files are now **generated output**, see below)
+5. Remove old `*.agent.md` files — DONE (the composable directories are the only committed
+   form; every harness composes or renders its own agent files at install time)
 
-All four agents (`ralph`, `plan`, `ralph-plan`, `strategy`) use the composable layout and the
-flat `agents/*.agent.md` files are built from them:
+All four agents (`ralph`, `plan`, `ralph-plan`, `strategy`) use the composable layout, and no
+flat agent file is committed:
 
-- `scripts/build-copilot-agents.mjs` (`pnpm build:copilot`) composes `agents/*.agent.md` from
-  each agent's `copilot/` harness dir — committed for Copilot CLI, which loads `*.agent.md`
-  from `plugin.json`'s `agents: "agents/"` path.
 - `bin/installers/claude.mjs` (plain `agent-cortex install claude` materialises the plugin
   into `~/.agent-cortex/claude` and registers it with Claude Code; `--output <dir>` is its
   generate-only form, used by tests/CI) composes the plugin's
@@ -239,9 +227,7 @@ via `bin/installers/claude.mjs`, the generator behind plain `agent-cortex instal
 `claude/settings.json` into `~/.claude/settings.json`, and registers the plugin with Claude
 Code); the only committed `claude/` file is that settings template (hand-authored extras live
 in `claude-extras/`), and CI validates the materialiser with structural checks on a temp-dir
-install; `copilot` ships via
-`bin/installers/copilot.mjs`, the shared code path behind both `agent-cortex install
-copilot` and `scripts/build-copilot-agents.mjs`; `pi` ships via
+install; `pi` ships via
 `bin/installers/pi.mjs`, which stages a self-contained pi package (manifest, rendered
 agents, token-substituted skills, extensions) at `~/.agent-cortex/pi`.
 
@@ -264,7 +250,7 @@ The validator checks:
 
 - JSON has strict syntax (no comments, no ambiguity)
 - Easier to validate with JSON Schema
-- Consistent with existing tooling (package.json, plugin.json)
+- Consistent with existing tooling (package.json)
 - No need for YAML parser dependency
 
 ### Why separate section files instead of inline sections?