@jaybeeuu/agent-cortex 1.20.0 → 1.37.1

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

@@ -0,0 +1,101 @@
+---
+name: style-versioning
+description: Automated release workflow using changesets. Use when completing work that needs a release, asking "how do I version this?", or when any change needs to be shipped to npm.
+---
+
+# style-versioning
+
+This repo uses **changesets** for fully automated versioning and publishing. No manual version bumps, no manual releases.
+
+## When to use
+
+Trigger this skill when:
+- Completing work that needs a release
+- Asking "how do I version this change?"
+- Creating a PR that changes shipped behaviour
+
+## Creating a changeset (agent instructions)
+
+**Do NOT run `pnpm changeset`** — it is interactive and will waste tokens on prompts and ANSI codes. Instead, write the changeset file directly.
+
+### File format
+
+A changeset is a markdown file in `.changeset/` with YAML frontmatter:
+
+```markdown
+---
+"@jaybeeuu/agent-cortex": <bump>
+---
+
+<Short description of the change>
+```
+
+Where `<bump>` is one of: `patch`, `minor`, or `major`.
+
+### How to create one
+
+1. Choose a descriptive kebab-case filename (e.g., `fix-status-bug.md`, `add-webhook-skill.md`)
+2. Choose the bump type:
+   - `patch` — bug fix, clarification, no behaviour change
+   - `minor` — new skill, agent, feature, or meaningful behaviour change
+   - `major` — breaking change (removed skill, renamed agent, incompatible workflow)
+3. Write the file directly using the `write` tool:
+
+```
+write(".changeset/fix-status-bug.md", `---
+"@jaybeeuu/agent-cortex": patch
+---
+
+Fix status bead showing wrong priority after update
+`)
+```
+
+4. Commit the changeset file along with the code changes
+
+### Rules
+
+- The frontmatter package name must match exactly: `"@jaybeeuu/agent-cortex"`
+- The description should be one or two sentences, user-facing (it goes into CHANGELOG.md)
+- One changeset per PR. If a PR has multiple unrelated changes, use multiple changeset files.
+- The filename doesn't matter to changesets — only the frontmatter and description do.
+
+## After merge to main
+
+The `release.yml` workflow handles everything automatically:
+
+1. **Detects new changesets** on main
+2. **Creates or updates a "Version Packages" PR** with bumped versions and updated CHANGELOG
+3. **When "Version Packages" is merged**:
+   - Bumps `package.json` version
+   - Syncs `plugin.json` version (via `scripts/sync-plugin-version.sh`)
+   - Updates `CHANGELOG.md`
+   - Creates a git tag
+   - Publishes to npm via OIDC (no `NPM_TOKEN` needed)
+   - Creates a GitHub release automatically
+
+### Version lockstep
+
+All version numbers stay 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
+
+**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.
+- **Skipping the changeset**: A PR without a changeset won't trigger a release. The changesets bot will remind you.
+- **Wrong bump type**: `patch` for fixes, `minor` for additions, `major` for breakage. When in doubt, ask the user.
+- **Wrong package name in frontmatter**: Must be `"@jaybeeuu/agent-cortex"` exactly.
+
+## What changed from the old workflow
+
+| Before (manual) | After (changesets) |
+|---|---|
+| Agent bumps versions locally | Agent writes a changeset file |
+| Manual GitHub release creation | Automated via `release.yml` |
+| `publish.yml` triggered by release | `release.yml` triggered by push to main |
+| Version sync was manual | `sync-plugin-version.sh` runs automatically |

package/.changeset/README.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets).
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md).

package/.changeset/config.json

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@3.1.4/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "public",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

package/.github/workflows/ci.yml

@@ -7,6 +7,45 @@ on:
   pull_request:
 
 jobs:
+  changeset:
+    name: Changeset check
+    if: github.event_name == 'pull_request'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Check for changeset
+        env:
+          BASE_REF: ${{ github.event.pull_request.base.ref }}
+        run: |
+          # Paths that require a changeset when modified
+          VERSIONED_PATHS='extensions/\|skills/\|agents/\|package.json\|plugin.json'
+
+          changed=$(git diff --name-only "origin/${BASE_REF}...HEAD")
+          echo "Changed files:"
+          echo "$changed"
+
+          versioned=$(echo "$changed" | grep -E "$VERSIONED_PATHS" || true)
+          if [ -z "$versioned" ]; then
+            echo "No versioned paths changed — skipping changeset check."
+            exit 0
+          fi
+
+          changesets=$(echo "$changed" | grep -E '^\.changeset/.*\.md$' | grep -v 'README.md' || true)
+          if [ -z "$changesets" ]; then
+            echo ""
+            echo "::error::This PR modifies versioned paths but does not include a changeset."
+            echo "Run 'pnpm changeset' to add one. See: style-versioning skill."
+            echo ""
+            echo "Versioned paths changed:"
+            echo "$versioned"
+            exit 1
+          fi
+
+          echo "Changeset found: $changesets"
+
   checks:
     runs-on: ubuntu-latest
     steps:

package/.github/workflows/release.yml

@@ -0,0 +1,58 @@
+name: Release
+
+on:
+  push:
+    branches:
+      - main
+
+concurrency: ${{ github.workflow }}-${{ github.ref }}
+
+jobs:
+  release:
+    name: Release
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+      id-token: write
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      # changesets/action is used ONLY to version packages and open/update
+      # the "Version Packages" PR. We deliberately do NOT pass a publish
+      # script here - changesets/action does not propagate the OIDC env vars
+      # (ACTIONS_ID_TOKEN_REQUEST_URL / _TOKEN) to the spawned npm process,
+      # so npm publish would fail with ENEEDAUTH. Publishing happens in a
+      # separate top-level step below where env vars flow through cleanly.
+      - name: Create Version Packages PR
+        id: changesets
+        uses: changesets/action@v1
+        with:
+          version: pnpm version-packages
+          commit: "chore: version packages"
+          title: "chore: version packages"
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      # When there are no changesets (i.e. the "Version Packages" PR was
+      # merged), changesets/action does nothing - so we publish directly.
+      # NOTE: @v1 (v1.9.0) exposes the output as 'hasChangesets' (camelCase).
+      - name: Publish to npm
+        if: steps.changesets.outputs.hasChangesets == 'false'
+        run: bash scripts/publish-release.sh

package/AGENTS.md

@@ -32,27 +32,13 @@ agent-cortex/
 
 ## Versioning
 
-**Always bump `plugin.json` version** when making any change to agents or skills. Follow
-semantic versioning:
-
-| Change type | Bump |
-|---|---|
-| New skill or agent added | `minor` |
-| Existing skill or agent meaningfully changed (new behaviour, new steps, restructured workflow) | `minor` |
-| Bug fix or clarification with no behaviour change | `patch` |
-| Breaking change (removed skill, renamed agent, incompatible workflow change) | `major` |
-
-The version bump must be included in the same commit as the change — do not leave it for a
-follow-up commit.
+Use `pnpm changeset` for all version bumps. Never edit versions manually.
+`package.json`, `plugin.json`, and `CHANGELOG.md` stay in lockstep automatically.
+See the `style-versioning` skill for the full workflow.
 
 ## Changelog
 
-- Keep a root `CHANGELOG.md` for repository changes.
-- When making any repo change (agents, skills, docs, scripts, or workflow rules), update
-  `CHANGELOG.md` in the same commit.
-- Write entries under a version header that matches the bumped `plugin.json` version
-  (e.g. `## 0.40.0`). Add a new version section on every change.
-- Keep entries user-facing and outcome-focused (what changed and why it matters).
+Generated automatically by changesets. Do not edit `CHANGELOG.md` manually.
 
 ## Skill Conventions
 

package/CHANGELOG.md

@@ -1,7 +1,79 @@
 # Changelog
 
+## 1.37.1
+
+### Patch Changes
+
+- 62bfbfe: Fix OIDC publishing by using custom publish script instead of changeset publish
+
+  Changesets doesn't natively support OIDC trusted publishing - it tries to use
+  `changeset publish` which requires an NPM_TOKEN. Replace with a custom script
+  that uses `pnpm pack` + `npm publish` directly, which properly picks up OIDC
+  tokens in GitHub Actions.
+
+## 1.37.0
+
+### Minor Changes
+
+- 75e2111: Switch to changesets for automated releases
+
+  Replace manual version bumping and GitHub release creation with changesets automation:
+
+  - Added `@changesets/cli` for intent-based versioning
+  - Added `release.yml` workflow that creates "Version Packages" PRs and auto-publishes via OIDC
+  - Added `scripts/sync-plugin-version.sh` to keep `plugin.json` in lockstep with `package.json`
+  - Updated `style-versioning` skill to document the new workflow
+  - Removed old `publish.yml` (release-triggered) workflow
+
+  Going forward: run `pnpm changeset` to describe changes, merge to main, and the rest is automatic.
+
+### Patch Changes
+
+- ad7ac8d: **Enforce changeset requirement in CI** — PRs that modify `extensions/`, `skills/`, `agents/`, `package.json`, or `plugin.json` now fail CI unless they include a `.changeset/*.md` file. Prevents merges that the release pipeline can't pick up.
+- 1ad1920: Fix changesets workflow by adding root package to workspace
+
+  Changesets couldn't find @jaybeeuu/agent-cortex because pnpm-workspace.yaml
+  only listed skills/_/scripts and extensions/_. Adding "." makes the root
+  a workspace member so changesets can version it.
+
+- 75e2111: Trim AGENTS.md versioning section to reference style-versioning skill instead of duplicating detail
+
 All notable changes to this repository are documented in this file.
 
+## 1.37.0
+
+### Added
+
+- **Changesets for automated releases** — replaced manual version bumping and GitHub
+  release creation with `@changesets/cli` and `release.yml` workflow. PRs include
+  changeset files, merging to main triggers automatic "Version Packages" PRs, and
+  publishing to npm via OIDC happens automatically. `plugin.json` stays in lockstep
+  via `scripts/sync-plugin-version.sh`.
+
+### Removed
+
+- **`publish.yml`** — old release-triggered publish workflow. Replaced by `release.yml`.
+
+## 1.36.1
+
+### Added
+
+- **`.agents/skills/style-versioning/`** — new repo-local skill enforcing
+  version lockstep across `package.json`, `plugin.json`, and `CHANGELOG.md`.
+  Discovered by pi, Copilot CLI, and Claude Code when working in this repo;
+  not distributed with the plugin.
+
+### Changed
+
+- **Version alignment** — `package.json` version aligned to match `plugin.json`
+  (both now `1.36.1`). Going forward, all versions (`package.json`, `plugin.json`,
+  and `CHANGELOG.md` top header) must stay in lockstep. See AGENTS.md versioning
+  section for rules.
+- **AGENTS.md** — versioning section updated to require lockstep across all
+  three version files (package.json, plugin.json, CHANGELOG.md).
+- **First npm release via Trusted Publishing** — this is the first version
+  published to npm using OIDC (no `NPM_TOKEN` secret).
+
 ## 1.36.0
 
 ### Added
@@ -21,11 +93,11 @@ All notable changes to this repository are documented in this file.
 
 - **`.github/workflows/publish.yml`** — replaced `NPM_TOKEN` secret auth with
   npm Trusted Publishing (OIDC). The publish job now grants `contents: read`
-  + `id-token: write` permissions and runs Node 24 / setup-node v6
-  (npm >= 11.5.1, required for OIDC). The publish step packs with
-  `pnpm pack` and uploads the tarball with `npm publish` (pnpm 11's OIDC
-  publish path is broken — pnpm#11513). Publishing no longer needs a
-  long-lived npm token in repository secrets.
+  - `id-token: write` permissions and runs Node 24 / setup-node v6
+    (npm >= 11.5.1, required for OIDC). The publish step packs with
+    `pnpm pack` and uploads the tarball with `npm publish` (pnpm 11's OIDC
+    publish path is broken — pnpm#11513). Publishing no longer needs a
+    long-lived npm token in repository secrets.
 - **`.github/workflows/ci.test.ts`** — updated publish-workflow assertions to
   expect the OIDC shape: `contents: read` + `id-token: write` permissions,
   `pnpm pack` + `npm publish`, and no `NPM_TOKEN` / `NODE_AUTH_TOKEN`

package/extensions/session-start.ts

@@ -1,5 +1,5 @@
 import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
-import { loadSessionContext } from "./context-loader.js";
+import { loadSessionContext } from "./lib/context-loader.js";
 
 /**
  * Session-start extension.

package/extensions/skill-stats/context-loader.test.ts

@@ -7,7 +7,7 @@ import { tmpdir } from "node:os";
 import {
   loadContextFile,
   loadSessionContext,
-} from "../context-loader.ts";
+} from "../lib/context-loader.ts";
 
 // ─── loadContextFile ─────────────────────────────────────────────────────────
 

package/extensions/skill-stats/node_modules/.bin/pi

@@ -0,0 +1,21 @@
+#!/bin/sh
+basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')")
+
+case `uname` in
+    *CYGWIN*|*MINGW*|*MSYS*)
+        if command -v cygpath > /dev/null 2>&1; then
+            basedir=`cygpath -w "$basedir"`
+        fi
+    ;;
+esac
+
+if [ -z "$NODE_PATH" ]; then
+  export NODE_PATH="/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/@earendil-works+pi-coding-agent@0.78.1_ws@8.21.0_zod@4.4.3/node_modules/@earendil-works/pi-coding-agent/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/@earendil-works+pi-coding-agent@0.78.1_ws@8.21.0_zod@4.4.3/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/node_modules"
+else
+  export NODE_PATH="/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/@earendil-works+pi-coding-agent@0.78.1_ws@8.21.0_zod@4.4.3/node_modules/@earendil-works/pi-coding-agent/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/@earendil-works+pi-coding-agent@0.78.1_ws@8.21.0_zod@4.4.3/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/node_modules:$NODE_PATH"
+fi
+if [ -x "$basedir/node" ]; then
+  exec "$basedir/node"  "$basedir/../@earendil-works/pi-coding-agent/dist/cli.js" "$@"
+else
+  exec node  "$basedir/../@earendil-works/pi-coding-agent/dist/cli.js" "$@"
+fi

package/extensions/skill-stats/node_modules/.bin/tsc

@@ -0,0 +1,21 @@
+#!/bin/sh
+basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')")
+
+case `uname` in
+    *CYGWIN*|*MINGW*|*MSYS*)
+        if command -v cygpath > /dev/null 2>&1; then
+            basedir=`cygpath -w "$basedir"`
+        fi
+    ;;
+esac
+
+if [ -z "$NODE_PATH" ]; then
+  export NODE_PATH="/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/typescript@5.9.3/node_modules/typescript/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/typescript@5.9.3/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/node_modules"
+else
+  export NODE_PATH="/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/typescript@5.9.3/node_modules/typescript/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/typescript@5.9.3/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/node_modules:$NODE_PATH"
+fi
+if [ -x "$basedir/node" ]; then
+  exec "$basedir/node"  "$basedir/../typescript/bin/tsc" "$@"
+else
+  exec node  "$basedir/../typescript/bin/tsc" "$@"
+fi

package/extensions/skill-stats/node_modules/.bin/tsserver

@@ -0,0 +1,21 @@
+#!/bin/sh
+basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')")
+
+case `uname` in
+    *CYGWIN*|*MINGW*|*MSYS*)
+        if command -v cygpath > /dev/null 2>&1; then
+            basedir=`cygpath -w "$basedir"`
+        fi
+    ;;
+esac
+
+if [ -z "$NODE_PATH" ]; then
+  export NODE_PATH="/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/typescript@5.9.3/node_modules/typescript/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/typescript@5.9.3/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/node_modules"
+else
+  export NODE_PATH="/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/typescript@5.9.3/node_modules/typescript/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/typescript@5.9.3/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/node_modules:$NODE_PATH"
+fi
+if [ -x "$basedir/node" ]; then
+  exec "$basedir/node"  "$basedir/../typescript/bin/tsserver" "$@"
+else
+  exec node  "$basedir/../typescript/bin/tsserver" "$@"
+fi

package/extensions/skill-stats/node_modules/.bin/tsx

@@ -0,0 +1,21 @@
+#!/bin/sh
+basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')")
+
+case `uname` in
+    *CYGWIN*|*MINGW*|*MSYS*)
+        if command -v cygpath > /dev/null 2>&1; then
+            basedir=`cygpath -w "$basedir"`
+        fi
+    ;;
+esac
+
+if [ -z "$NODE_PATH" ]; then
+  export NODE_PATH="/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/tsx@4.22.4/node_modules/tsx/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/tsx@4.22.4/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/node_modules"
+else
+  export NODE_PATH="/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/tsx@4.22.4/node_modules/tsx/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/tsx@4.22.4/node_modules:/home/runner/work/agent-cortex/agent-cortex/node_modules/.pnpm/node_modules:$NODE_PATH"
+fi
+if [ -x "$basedir/node" ]; then
+  exec "$basedir/node"  "$basedir/../tsx/dist/cli.mjs" "$@"
+else
+  exec node  "$basedir/../tsx/dist/cli.mjs" "$@"
+fi

package/package.json

@@ -1,15 +1,12 @@
 {
   "name": "@jaybeeuu/agent-cortex",
-  "version": "1.20.0",
+  "version": "1.37.1",
   "description": "Personal PI package with custom agents, skills, and extensions",
   "keywords": [
     "pi-package"
   ],
   "license": "MIT",
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/jaybeeuu/agent-cortex"
-  },
+  "repository": "https://github.com/jaybeeuu/agent-cortex",
   "bin": {
     "agent-cortex": "./bin/agent-cortex.mjs"
   },
@@ -17,6 +14,7 @@
     "access": "public"
   },
   "devDependencies": {
+    "@changesets/cli": "^2.31.1",
     "tsx": "^4.0.0",
     "yaml": "^2.0.0"
   },
@@ -34,6 +32,9 @@
     "test": "pnpm -r test",
     "typecheck": "pnpm -r typecheck",
     "build:claude": "node scripts/build-claude-agents.mjs",
+    "changeset": "changeset",
+    "version-packages": "changeset version && bash scripts/sync-plugin-version.sh",
+    "release": "changeset publish",
     "postinstall": "bash scripts/install-instructions.sh"
   }
 }

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "agent-cortex",
   "description": "Personal Copilot CLI plugin with custom agents and skills",
-  "version": "1.36.0",
+  "version": "1.37.1",
   "author": {
     "name": "jaybeeuu"
   },

package/pnpm-workspace.yaml

@@ -1,4 +1,5 @@
 packages:
+  - "."
   - "skills/*/scripts"
   - "extensions/*"
 allowBuilds:

package/scripts/publish-release.sh

@@ -0,0 +1,32 @@
+#!/usr/bin/env bash
+# Custom publish script for changesets that uses pnpm pack + npm publish
+# This is needed because changeset publish doesn't properly handle OIDC
+
+set -euo pipefail
+
+# Check if there are any packages to publish
+VERSION=$(node -p "require('./package.json').version")
+PACKAGE_NAME=$(node -p "require('./package.json').name")
+
+echo "Publishing $PACKAGE_NAME@$VERSION"
+
+# Check if this version is already published
+if npm view "$PACKAGE_NAME@$VERSION" version 2>/dev/null; then
+  echo "Version $VERSION is already published, skipping"
+  exit 0
+fi
+
+# Pack the tarball
+TARBALL=$(pnpm pack | tail -n 1)
+echo "Created tarball: $TARBALL"
+
+# Publish using npm with OIDC trusted publishing.
+# NOTE: provenance is disabled because this repo is private - npm's
+# trusted publishing auto-enables provenance, but sigstore only supports
+# public repos. The masked error would be ENEEDAUTH.
+npm publish "$TARBALL" --access public --no-provenance
+
+echo "✓ Published $PACKAGE_NAME@$VERSION"
+
+# Create git tag
+git tag -a "v$VERSION" -m "Release $PACKAGE_NAME@$VERSION" || echo "Tag already exists"

package/scripts/sync-plugin-version.sh

@@ -0,0 +1,17 @@
+#!/usr/bin/env bash
+# Sync plugin.json version with package.json
+# Called by changesets after versioning to keep them in lockstep
+
+set -euo pipefail
+
+VERSION=$(node -p "require('./package.json').version")
+
+# Update plugin.json version field
+node -e "
+const fs = require('fs');
+const plugin = JSON.parse(fs.readFileSync('plugin.json', 'utf8'));
+plugin.version = '$VERSION';
+fs.writeFileSync('plugin.json', JSON.stringify(plugin, null, 2) + '\n');
+"
+
+echo "✓ Synced plugin.json to version $VERSION"

package/.beads/README.md

@@ -1,81 +0,0 @@
-# Beads - AI-Native Issue Tracking
-
-Welcome to Beads! This repository uses **Beads** for issue tracking - a modern, AI-native tool designed to live directly in your codebase alongside your code.
-
-## What is Beads?
-
-Beads is issue tracking that lives in your repo, making it perfect for AI coding agents and developers who want their issues close to their code. No web UI required - everything works through the CLI and integrates seamlessly with git.
-
-**Learn more:** [github.com/steveyegge/beads](https://github.com/steveyegge/beads)
-
-## Quick Start
-
-### Essential Commands
-
-```bash
-# Create new issues
-bd create "Add user authentication"
-
-# View all issues
-bd list
-
-# View issue details
-bd show <issue-id>
-
-# Update issue status
-bd update <issue-id> --claim
-bd update <issue-id> --status done
-
-# Sync with Dolt remote
-bd dolt push
-```
-
-### Working with Issues
-
-Issues in Beads are:
-- **Git-native**: Stored in Dolt database with version control and branching
-- **AI-friendly**: CLI-first design works perfectly with AI coding agents
-- **Branch-aware**: Issues can follow your branch workflow
-- **Always in sync**: Auto-syncs with your commits
-
-## Why Beads?
-
-✨ **AI-Native Design**
-- Built specifically for AI-assisted development workflows
-- CLI-first interface works seamlessly with AI coding agents
-- No context switching to web UIs
-
-🚀 **Developer Focused**
-- Issues live in your repo, right next to your code
-- Works offline, syncs when you push
-- Fast, lightweight, and stays out of your way
-
-🔧 **Git Integration**
-- Automatic sync with git commits
-- Branch-aware issue tracking
-- Dolt-native three-way merge resolution
-
-## Get Started with Beads
-
-Try Beads in your own projects:
-
-```bash
-# Install Beads
-curl -sSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash
-
-# Initialize in your repo
-bd init
-
-# Create your first issue
-bd create "Try out Beads"
-```
-
-## Learn More
-
-- **Documentation**: [github.com/steveyegge/beads/docs](https://github.com/steveyegge/beads/tree/main/docs)
-- **Quick Start Guide**: Run `bd quickstart`
-- **Examples**: [github.com/steveyegge/beads/examples](https://github.com/steveyegge/beads/tree/main/examples)
-
----
-
-*Beads: Issue tracking that moves at the speed of thought* ⚡

package/.beads/config.yaml

@@ -1 +0,0 @@
-no-git-ops: true