release: v0.4.0 — Apache-2.0, core@v0.8.0, and a marketplace path that resolves

.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "Signetry — govern coding-agent changes in Claude Code. Real-time contract enforcement with signed receipts.",
-    "version": "0.3.0"
+    "version": "0.4.0"
   },
   "plugins": [
     {

.github/workflows/reviewer.yml

@@ -34,7 +34,7 @@ jobs:
         with:
           python-version: "3.12"
       - name: Install signetry-reviewer
-        run: pip install "signetry-reviewer @ git+https://github.com/Signetry/reviewer@v0.2.0"
+        run: pip install "signetry-reviewer @ git+https://github.com/Signetry/reviewer@v0.3.0"
       - name: Compute the PR diff
         env:
           BASE_SHA: ${{ github.event.pull_request.base.sha }}

CHANGELOG.md

@@ -2,7 +2,19 @@
 
 Follows [Keep a Changelog](https://keepachangelog.com/) / [SemVer](https://semver.org/).
 
-## [Unreleased]
+## [0.4.0] — 2026-09-01
+
+> First release **tagged in this repository**. The `0.3.0` entry below describes a
+> release cut in the pre-move repo, whose tag did not survive the org move.
+
+### Fixed — the documented install command pointed at a 404
+
+- `README.md` told Claude Code users to run
+  `/plugin marketplace add bkd-dotcom/signetry-claude-code`. That repository has not
+  existed since the move to the `Signetry` org, so the plugin's primary install path
+  could not work for anyone. Now `Signetry/claude-code`.
+- The marketplace *name* in `/plugin install signetry@signetry-claude-code` is
+  unchanged and correct — it comes from `marketplace.json`'s `name`, not the repo path.
 
 ### Changed — the project is now open source (Apache-2.0)
 
@@ -49,9 +61,9 @@ Follows [Keep a Changelog](https://keepachangelog.com/) / [SemVer](https://semve
   `signetry_core`; and shell functions use the `signetry_*` prefix.
 - The `signetry/` plugin asset directory (hooks, skills, scripts) and all
   references to it use the Signetry name.
-- Pinned `signetry-core[...] @ git+https://github.com/Signetry/core@v0.6.0`
+- Pinned `signetry-core[...] @ git+https://github.com/Signetry/core@v0.8.0`
   and the advisory reviewer to
-  `signetry-reviewer @ git+https://github.com/Signetry/reviewer@v0.1.2`.
+  `signetry-reviewer @ git+https://github.com/Signetry/reviewer@v0.3.0`.
 
 ## [0.3.0] — 2026-07-26
 

README.md

@@ -13,7 +13,7 @@ code, never by the model itself (an agent can't approve its own change).
 
 Part of the [Signetry platform](https://github.com/Signetry/signetry).
 
-> Prerequisite: `pip install "signetry-core @ git+https://github.com/Signetry/core@v0.7.0"` and a `.signetry/admission.yaml` in
+> Prerequisite: `pip install "signetry-core @ git+https://github.com/Signetry/core@v0.8.0"` and a `.signetry/admission.yaml` in
 > your repo (a conservative default applies without one).
 
 ## What it does
@@ -32,7 +32,7 @@ out-of-scope or forbidden actions before they happen — using `signetry guard`
 ## Install
 
 ```
-/plugin marketplace add bkd-dotcom/signetry-claude-code
+/plugin marketplace add Signetry/claude-code
 /plugin install signetry@signetry-claude-code
 ```
 

signetry/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "signetry",
   "description": "Govern coding-agent edits in real time: block out-of-scope or forbidden file writes and dangerous commands before they happen, using your repo's .signetry/admission.yaml. Deterministic (not the model). From signetry-core.",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "author": {
     "name": "Signetry",
     "url": "https://github.com/Signetry"

signetry/hooks/signetry-lib.sh

@@ -66,7 +66,7 @@ signetry_provision() {
   venv_py="$venv/bin/python"
   {
     "$py" -m venv "$venv" \
-      && "$venv_py" -m pip install --quiet --disable-pip-version-check "signetry-core @ git+https://github.com/Signetry/core@v0.7.0"
+      && "$venv_py" -m pip install --quiet --disable-pip-version-check "signetry-core @ git+https://github.com/Signetry/core@v0.8.0"
   } >/dev/null 2>&1 || true
   [ -x "$venv_py" ] && "$venv_py" -c "import signetry_core" >/dev/null 2>&1
 }

signetry/hooks/signetry-session-start.sh

@@ -22,8 +22,8 @@ fi
 
 # Could not activate. Say so LOUDLY and specifically — do not pretend to protect.
 if signetry_py311plus >/dev/null 2>&1; then
-  echo "Signetry plugin loaded but INACTIVE: could not install signetry-core (offline?). The guard is NOT enforcing anything. Fix with: pip install 'signetry-core @ git+https://github.com/Signetry/core@v0.7.0'"
+  echo "Signetry plugin loaded but INACTIVE: could not install signetry-core (offline?). The guard is NOT enforcing anything. Fix with: pip install 'signetry-core @ git+https://github.com/Signetry/core@v0.8.0'"
 else
-  echo "Signetry plugin loaded but INACTIVE: needs Python >=3.11, which was not found (your default python3 may be older). The guard is NOT enforcing anything. Install Python 3.11+ and: pip install 'signetry-core @ git+https://github.com/Signetry/core@v0.7.0'"
+  echo "Signetry plugin loaded but INACTIVE: needs Python >=3.11, which was not found (your default python3 may be older). The guard is NOT enforcing anything. Install Python 3.11+ and: pip install 'signetry-core @ git+https://github.com/Signetry/core@v0.8.0'"
 fi
 exit 0

signetry/scripts/signetry-mcp.sh

@@ -15,5 +15,5 @@ for PY in python3.13 python3.12 python3.11 python3 python; do
     exec "$PY" -m signetry_core.mcp_server
   fi
 done
-echo "signetry-core[mcp] not available on a Python >=3.11; run: pip install 'signetry-core[mcp] @ git+https://github.com/Signetry/core@v0.7.0'" >&2
+echo "signetry-core[mcp] not available on a Python >=3.11; run: pip install 'signetry-core[mcp] @ git+https://github.com/Signetry/core@v0.8.0'" >&2
 exit 1

signetry/skills/admit/SKILL.md

@@ -10,7 +10,7 @@ report the result to the user.
 Steps:
 
 1. Confirm `signetry` is available: run `signetry --help`. If it is not installed, tell
-   the user to run `pip install "signetry-core @ git+https://github.com/Signetry/core@v0.7.0"` and stop.
+   the user to run `pip install "signetry-core @ git+https://github.com/Signetry/core@v0.8.0"` and stop.
 2. Run admission over the change already present in the working tree (no agent is
    re-invoked — the change being governed is what's on disk):