claude-code-kit 0.75.0__tar.gz → 0.76.0__tar.gz

claude_code_kit-0.76.0/.claude-plugin/marketplace.json

@@ -0,0 +1,19 @@
+{
+  "name": "claude-kit",
+  "description": "claude-kit — an autonomous, stack-agnostic SDLC for Claude Code, delivered as a plugin.",
+  "owner": {
+    "name": "Arjunsingh Yadav",
+    "url": "https://github.com/ajyadav013"
+  },
+  "plugins": [
+    {
+      "name": "claude-kit",
+      "displayName": "Claude Kit SDLC",
+      "source": "./",
+      "description": "Evidence-gated SDLC for Claude Code, installed as configuration (no app code, no Docker): install CLAUDE.md + .claude/ (rules, the profile's agents/skills, hooks, artifact templates) + optional .mcp.json, then run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates with a tamper-evident gate ledger, working memory, and a self-improving learnings loop.",
+      "version": "0.76.0",
+      "license": "MIT",
+      "keywords": ["sdlc", "agents", "orchestration", "quality-gates", "workflow", "scaffold", "cookiecutter"]
+    }
+  ]
+}

claude_code_kit-0.76.0/.claude-plugin/plugin.json

@@ -0,0 +1,25 @@
+{
+  "name": "claude-kit",
+  "displayName": "Claude Kit SDLC",
+  "version": "0.76.0",
+  "description": "Evidence-gated SDLC for Claude Code, installed as configuration (no app code, no Docker). `claude-kit init` asks ordered questions and installs CLAUDE.md + .claude/ (rules, the profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates with a tamper-evident gate ledger, working memory, and a self-improving learnings loop.",
+  "author": {
+    "name": "Arjunsingh Yadav",
+    "url": "https://github.com/ajyadav013"
+  },
+  "homepage": "https://github.com/ajyadav013/claude-kit",
+  "repository": "https://github.com/ajyadav013/claude-kit",
+  "license": "MIT",
+  "keywords": [
+    "sdlc",
+    "agents",
+    "orchestration",
+    "code-review",
+    "testing",
+    "quality-gates",
+    "workflow",
+    "automation",
+    "scaffold",
+    "cookiecutter"
+  ]
+}

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/CHANGELOG.md

@@ -4,6 +4,77 @@ All notable changes to claude-kit are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/), and the project uses
 [semantic versioning](https://semver.org/).
 
+## [0.76.0] — 2026-08-01
+
+**The Trust Release — enforcement catches up with the promise.** The kit has always *claimed* that
+no gate passes without evidence; this release makes the deterministic state layer actually refuse
+the ways that claim could be quietly violated: gates closed out of order, evidence files swapped
+after the fact, snapshots corrupted mid-write, Mode E runs rejected by the very validator meant to
+protect them, and a learning-capture job that ran before anyone consented to it.
+
+### Added
+
+- **Gate ledger** (`claude-kit pipeline`): every `close-gate` now appends an entry to an append-only
+  `gate_history` in the pipeline snapshot — gate, status (`passed` / `skipped` / `overridden`),
+  evidence path **and its sha256**, a `verification` level (`agent` today; `mechanical` / `human`
+  reserved for the parser ladder in #74), and a UTC timestamp. `validate` re-hashes **every** ledger
+  entry, so tampering with an already-cited evidence file turns the run red.
+- **Gate-order enforcement.** `close-gate` derives the expected next gate from the profile's ordered
+  gate list and refuses out-of-order or already-recorded closes; `--force --override-reason` records
+  an honest `overridden` entry instead of a silent pass. The first recorded gate anchors anywhere in
+  the sequence, so adopting the ledger mid-run works.
+- **`pipeline skip-gate <gate> --reason`** — the honest path for conditional gates (e.g.
+  `contract-clear` on a stack with no API surface): recorded as `skipped` with the reason, never as
+  a fake pass.
+- **`--strict` for `pipeline validate` / `close-gate`** — a missing or unreadable install snapshot
+  fails closed instead of warning (for CI); the default stays lenient for back-compat.
+- **`claude-kit privacy-report`** — one line per installed hook: what it reads, what it writes,
+  whether it spawns a background job, whether learning capture is on, and how to turn it off.
+  Non-kit hook commands found in `settings.json` are flagged for the user's own review.
+- **Mode E** (`"mode": "E"`) is now accepted by the pipeline validator — it shipped in the
+  orchestrator in 0.58 but `pipeline.py` still rejected it. A drift-guard test now parses the mode
+  line out of `rules/continuity.md` and asserts it equals `pipeline.MODES`, so the two can't
+  diverge again.
+
+### Changed
+
+- **Learning capture is now opt-in** on every non-interactive path: the plugin manifest, the no-pip
+  starter `settings.json`, and `init --defaults` all install **no capture hooks**; `capture_mode`
+  defaults to `off`. The interactive `init` question *is* the consent — it still recommends
+  `session-end-catchup`. Recall (`load-learnings`, reading your own committed `agent-memory/`) is
+  unaffected and stays on. Documented in `SECURITY.md`.
+- **Snapshot writes are atomic and locked** — temp file + `os.replace` under an `O_EXCL` lockfile,
+  so a crash mid-`close-gate` can no longer leave a torn state file.
+- **Gates now resolve in execution order.** Fixed a real resolver bug the new order enforcement
+  uncovered: child profiles' gate lists were being union-merged behind the parent's, contradicting
+  the documented "execution-ordered" contract. `catalog/profiles.yaml` now documents the ordering
+  convention and the resolver preserves the child's declared order.
+- **Truth-in-advertising pass across every advertised surface.** The README headline now claims
+  exactly what ships ("every gate verdict must cite real command output, and the deterministic
+  state layer refuses to close a gate out of order or with unresolved findings"); "configuration
+  only" is spelled out (no app code in your repo, no daemon); the category line is now
+  **"Evidence-gated SDLC for Claude Code"** (plugin `displayName`: **Claude Kit SDLC**) across
+  plugin/marketplace manifests, PyPI metadata, `llms.txt`, and the CLI docstrings — the
+  `cookiecutter` search keywords stay. README hero restructured: proof (`examples/real-run/`)
+  before pitch, qualified install (`/plugin install claude-kit@claude-kit`), non-affiliation note
+  in the footer.
+- **Count drift fixed and pinned**: "28-agent roster" → 29 (README, `docs/agentic-patterns.md`),
+  both now anchored in `scripts/check_docs_consistency.py`; `docs/rules-context-budget.md`'s
+  numbers are annotated as the 2026-07-07 measurement snapshot; `docs/launch/posts.md` gains a
+  historical-snapshot banner.
+
+### Not adopted (deliberately)
+
+- **Splitting the plugin into core/standard/enterprise packages.** Profiles already gate what a
+  given install receives; a package split would break the one-source-of-truth layout for a
+  distribution problem no user has reported. Revisit with adoption data.
+- **A config-file source of truth for pipeline modes.** A drift-guard test asserting
+  `rules/continuity.md` ≡ `pipeline.MODES` is cheaper than a third artifact both would then have to
+  agree with.
+- **Mechanical evidence parsing in this release** (JUnit/coverage/SARIF verdicts refusing a close).
+  Deliberately sequenced as the next release so this one stays reviewable; the ledger's
+  `verification` enum already reserves `mechanical` / `human` for it (issue #74).
+
 ## [0.75.0] — 2026-07-31
 
 **The Devil's Advocate learns to weigh, not only to prosecute — a premortem, a merits-and-costs

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/CLAUDE.md

@@ -4,8 +4,9 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 # Developing claude-kit
 
-This repository **is** claude-kit — a Cookiecutter-style scaffolder that installs a stack-agnostic,
-autonomous-SDLC **configuration** (no application code, no Docker) into a Claude Code project. It is
+This repository **is** claude-kit — an evidence-gated SDLC for Claude Code: a scaffolder that
+installs a stack-agnostic, autonomous-SDLC **configuration** (no application code, no Docker) into
+a Claude Code project. It is
 distributed two ways from one source of truth:
 
 1. **As a Claude Code plugin** — components are auto-discovered from the repo root.
@@ -122,7 +123,7 @@ root are read directly by the plugin **and** bundled into the wheel (mapped to
 
 ## Dogfooding / local testing
 
-- **Plugin:** `claude` → `/plugin marketplace add .` → `/plugin install claude-kit` (loads the
+- **Plugin:** `claude` → `/plugin marketplace add .` → `/plugin install claude-kit@claude-kit` (loads the
   agents/skills/commands/hooks from this checkout).
 - **CLI:** `pip install -e '.[dev]'` then `claude-kit init /tmp/demo --defaults` (or interactive),
   `claude-kit validate /tmp/demo`, `claude-kit diff /tmp/demo`, and inspect the result.

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/CONTRIBUTING.md

@@ -59,7 +59,7 @@ locally, and how to release.
 
 ```bash
 # Plugin (dogfood this checkout):
-#   in Claude Code:  /plugin marketplace add .   then   /plugin install claude-kit
+#   in Claude Code:  /plugin marketplace add .   then   /plugin install claude-kit@claude-kit
 
 # CLI:
 pip install -e '.[dev]'
@@ -107,6 +107,9 @@ a specific stack — `pytest` enforces the no-Docker invariant on a scaffolded p
 4. CI auto-publishes to PyPI on merge to `main` when the version is new (`.github/workflows/publish.yml`,
    OIDC trusted publishing). Manual `python3 -m twine upload dist/*` is the fallback.
 5. Tag the release and push so plugin users get the update.
+6. Publish the context-cost report for the release: run `claude plugin details claude-kit@claude-kit`
+   in Claude Code and paste the token/context figures into the release notes, so users can see what
+   the plugin costs their context window before installing.
 
 ## License
 

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: claude-code-kit
-Version: 0.75.0
-Summary: Cookiecutter-style scaffolder for an autonomous Claude Code SDLC configuration (no app code, no Docker). Asks ordered questions and installs CLAUDE.md + .claude/ (rules, the chosen profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates, working memory, and a self-improving learnings loop.
+Version: 0.76.0
+Summary: Evidence-gated SDLC for Claude Code, installed as configuration (no app code, no Docker). Asks ordered questions and installs CLAUDE.md + .claude/ (rules, the chosen profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates with a tamper-evident gate ledger, working memory, and a self-improving learnings loop.
 Project-URL: Homepage, https://github.com/ajyadav013/claude-kit
 Project-URL: Repository, https://github.com/ajyadav013/claude-kit
 Project-URL: Issues, https://github.com/ajyadav013/claude-kit/issues
@@ -35,13 +35,29 @@ Description-Content-Type: text/markdown
 
 # claude-kit
 
+### Evidence-gated SDLC for Claude Code
+
 **Turn Claude Code into a disciplined engineering team: one command — `/sdlc <task>` — runs your
 request through spec → review → code → test → security → PR, with a quality gate between every
 phase.**
 
-The differentiator is trust: **no gate passes without real, cited command output**, so a green
-result means the checks actually ran. It installs as **configuration only** — no runtime, no
-application code, no Docker.
+The differentiator is trust: **every gate verdict must cite real command output, and the
+deterministic state layer refuses to close a gate out of order or with unresolved
+Critical/High/Medium findings.** It installs as **configuration, not a runtime** — no application
+code in your repo and no daemon: Claude Code configuration, local hooks, and an optional CLI.
+
+</div>
+
+**Proof over pitch:** in the captured run in [`examples/real-run/`](examples/real-run/), a unanimous
+review PASS triggered the adversarial `devils-advocate` — it caught a Medium bug every reviewer had
+missed, and the gate refused to advance until the fix landed. The run is checked in verbatim: state
+file, agent verdicts, diff, asciicast.
+
+```text
+/plugin marketplace add ajyadav013/claude-kit
+/plugin install claude-kit@claude-kit
+/claude-kit:sdlc Add a /health endpoint that returns the build version
+```
 
 <!-- DEMO PLACEHOLDER — a 60–90s terminal capture of a gated `/sdlc` run belongs here once recorded.
      Shot list, timing, and which real assets to show: docs/launch/demo-script.md.
@@ -49,6 +65,8 @@ application code, no Docker.
      Medium bug a unanimous review missed, and the gate refusing to advance until it was fixed).
      Until the GIF exists, that folder IS the evidence — linked from "How it works" and "The pipeline" below. -->
 
+<div align="center">
+
 [![PyPI](https://img.shields.io/pypi/v/claude-code-kit.svg)](https://pypi.org/project/claude-code-kit/)
 [![Python](https://img.shields.io/pypi/pyversions/claude-code-kit.svg)](https://pypi.org/project/claude-code-kit/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
@@ -89,16 +107,13 @@ The fastest path to a gated run — **no CLI install, no `init`, no restart:**
 
 ```text
 /plugin marketplace add ajyadav013/claude-kit
-/plugin install claude-kit
+/plugin install claude-kit@claude-kit        # qualified name: the claude-kit plugin from the claude-kit marketplace
 /claude-kit:sdlc Add a /health endpoint that returns the build version
 ```
 
 That's the whole loop in three lines: the standard pipeline runs immediately — spec → review →
-build → test, gate by gate — with every verdict backed by real output.
-
-**Proof it works:** [`examples/real-run/`](examples/real-run/) is a genuine captured run where the
-`devils-advocate` caught a Medium bug a unanimous review missed, and the gate refused to advance
-until it was fixed.
+build → test, gate by gate — with every verdict backed by real output. (The proof run lives in
+[`examples/real-run/`](examples/real-run/) — see the top of this page.)
 
 When you want the pipeline tuned to *your* repo — your stack, commands, rigor profile, and the
 safety hooks — run `init`:
@@ -373,7 +388,7 @@ Report vulnerabilities privately — see [`SECURITY.md`](SECURITY.md).
 |---|---|
 | [`docs/install.md`](docs/install.md) | Every install detail: prerequisites, Windows, plugin updates, all `init` questions, `init.yaml`, what lands on disk |
 | [`docs/cli.md`](docs/cli.md) | Full CLI command reference, safe-upgrade mechanics, troubleshooting |
-| [`docs/agents.md`](docs/agents.md) | How to drive the agents + the full 28-agent roster and per-run cost |
+| [`docs/agents.md`](docs/agents.md) | How to drive the agents + the full 29-agent roster and per-run cost |
 | [`docs/architecture.md`](docs/architecture.md) | Diagrams: distribution, catalog resolution, the state machine — and how to extend via the catalog |
 | [`docs/influences.md`](docs/influences.md) | The reuse-first adoption history: what we learned, shipped, and deliberately skipped |
 | [`docs/autonomous-operation.md`](docs/autonomous-operation.md) | Unattended runs: permission modes × autonomy levels, headless mode, the bounded loop script, CI-trigger design |
@@ -391,10 +406,12 @@ Report vulnerabilities privately — see [`SECURITY.md`](SECURITY.md).
 Issues and PRs welcome — see [`CONTRIBUTING.md`](CONTRIBUTING.md). To dogfood a local checkout:
 
 ```bash
-# As a plugin:  /plugin marketplace add .   then   /plugin install claude-kit
+# As a plugin:  /plugin marketplace add .   then   /plugin install claude-kit@claude-kit
 # As the CLI:   pip install -e '.[dev]'   then   claude-kit init /tmp/demo --defaults   &&   pytest
 ```
 
 ## License
 
 [MIT](LICENSE) © Arjunsingh Yadav
+
+claude-kit is an independent open-source project — not affiliated with or endorsed by Anthropic.

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/README.md

@@ -2,13 +2,29 @@
 
 # claude-kit
 
+### Evidence-gated SDLC for Claude Code
+
 **Turn Claude Code into a disciplined engineering team: one command — `/sdlc <task>` — runs your
 request through spec → review → code → test → security → PR, with a quality gate between every
 phase.**
 
-The differentiator is trust: **no gate passes without real, cited command output**, so a green
-result means the checks actually ran. It installs as **configuration only** — no runtime, no
-application code, no Docker.
+The differentiator is trust: **every gate verdict must cite real command output, and the
+deterministic state layer refuses to close a gate out of order or with unresolved
+Critical/High/Medium findings.** It installs as **configuration, not a runtime** — no application
+code in your repo and no daemon: Claude Code configuration, local hooks, and an optional CLI.
+
+</div>
+
+**Proof over pitch:** in the captured run in [`examples/real-run/`](examples/real-run/), a unanimous
+review PASS triggered the adversarial `devils-advocate` — it caught a Medium bug every reviewer had
+missed, and the gate refused to advance until the fix landed. The run is checked in verbatim: state
+file, agent verdicts, diff, asciicast.
+
+```text
+/plugin marketplace add ajyadav013/claude-kit
+/plugin install claude-kit@claude-kit
+/claude-kit:sdlc Add a /health endpoint that returns the build version
+```
 
 <!-- DEMO PLACEHOLDER — a 60–90s terminal capture of a gated `/sdlc` run belongs here once recorded.
      Shot list, timing, and which real assets to show: docs/launch/demo-script.md.
@@ -16,6 +32,8 @@ application code, no Docker.
      Medium bug a unanimous review missed, and the gate refusing to advance until it was fixed).
      Until the GIF exists, that folder IS the evidence — linked from "How it works" and "The pipeline" below. -->
 
+<div align="center">
+
 [![PyPI](https://img.shields.io/pypi/v/claude-code-kit.svg)](https://pypi.org/project/claude-code-kit/)
 [![Python](https://img.shields.io/pypi/pyversions/claude-code-kit.svg)](https://pypi.org/project/claude-code-kit/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
@@ -56,16 +74,13 @@ The fastest path to a gated run — **no CLI install, no `init`, no restart:**
 
 ```text
 /plugin marketplace add ajyadav013/claude-kit
-/plugin install claude-kit
+/plugin install claude-kit@claude-kit        # qualified name: the claude-kit plugin from the claude-kit marketplace
 /claude-kit:sdlc Add a /health endpoint that returns the build version
 ```
 
 That's the whole loop in three lines: the standard pipeline runs immediately — spec → review →
-build → test, gate by gate — with every verdict backed by real output.
-
-**Proof it works:** [`examples/real-run/`](examples/real-run/) is a genuine captured run where the
-`devils-advocate` caught a Medium bug a unanimous review missed, and the gate refused to advance
-until it was fixed.
+build → test, gate by gate — with every verdict backed by real output. (The proof run lives in
+[`examples/real-run/`](examples/real-run/) — see the top of this page.)
 
 When you want the pipeline tuned to *your* repo — your stack, commands, rigor profile, and the
 safety hooks — run `init`:
@@ -340,7 +355,7 @@ Report vulnerabilities privately — see [`SECURITY.md`](SECURITY.md).
 |---|---|
 | [`docs/install.md`](docs/install.md) | Every install detail: prerequisites, Windows, plugin updates, all `init` questions, `init.yaml`, what lands on disk |
 | [`docs/cli.md`](docs/cli.md) | Full CLI command reference, safe-upgrade mechanics, troubleshooting |
-| [`docs/agents.md`](docs/agents.md) | How to drive the agents + the full 28-agent roster and per-run cost |
+| [`docs/agents.md`](docs/agents.md) | How to drive the agents + the full 29-agent roster and per-run cost |
 | [`docs/architecture.md`](docs/architecture.md) | Diagrams: distribution, catalog resolution, the state machine — and how to extend via the catalog |
 | [`docs/influences.md`](docs/influences.md) | The reuse-first adoption history: what we learned, shipped, and deliberately skipped |
 | [`docs/autonomous-operation.md`](docs/autonomous-operation.md) | Unattended runs: permission modes × autonomy levels, headless mode, the bounded loop script, CI-trigger design |
@@ -358,10 +373,12 @@ Report vulnerabilities privately — see [`SECURITY.md`](SECURITY.md).
 Issues and PRs welcome — see [`CONTRIBUTING.md`](CONTRIBUTING.md). To dogfood a local checkout:
 
 ```bash
-# As a plugin:  /plugin marketplace add .   then   /plugin install claude-kit
+# As a plugin:  /plugin marketplace add .   then   /plugin install claude-kit@claude-kit
 # As the CLI:   pip install -e '.[dev]'   then   claude-kit init /tmp/demo --defaults   &&   pytest
 ```
 
 ## License
 
 [MIT](LICENSE) © Arjunsingh Yadav
+
+claude-kit is an independent open-source project — not affiliated with or endorsed by Anthropic.

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/catalog/capture.yaml

@@ -15,9 +15,13 @@
 
 version: 1
 
-# Used by `--defaults`, the plugin install, and shown as the recommended pick. The interactive prompt
-# overrides this to `off` for the lean profile (lean is intentionally minimal).
-default: session-end-catchup
+# CONSENT GATE (0.76.0): background capture reads session transcript content, so it is opt-in —
+# `default` (used by every NON-interactive path: `--defaults`, config files without the key) is
+# `off`. The interactive `init` prompt asks explicitly and preselects `recommended` (off for the
+# lean profile — lean is intentionally minimal). The plugin channel and the no-pip starter ship no
+# capture hooks at all (see PLUGIN_HOOK_IDS / STARTER_HOOK_IDS in src/claude_kit/hooks.py).
+default: "off"
+recommended: session-end-catchup
 
 modes:
   "off":

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/catalog/profiles.yaml

@@ -5,6 +5,12 @@
 # another profile (this profile's lists are unioned with the inherited ones). The special value
 # `all` means "every available item discovered in the payload" (agents/, skills/, hooks/).
 #
+# ORDER CONVENTION for `gates:` — gates are the one list where order is data: the resolved list
+# lands execution-ordered in stack-catalog.snapshot.yaml and `claude-kit pipeline close-gate`
+# enforces it. A profile that inherits MUST therefore declare its FULL gate list in execution
+# order (standard and enterprise below do); the resolver keeps the profile's own order and lets
+# inherited gates only fill gaps.
+#
 # Agent and skill names must match files in agents/ and skills/. Hook ids map to entries in the
 # hook registry in scaffold.py (script-backed hooks copy their .sh; inline/prompt hooks don't).
 

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/docs/agentic-patterns.md

@@ -23,9 +23,9 @@ they are already embodied in its rules, agents, skills, and the orchestration mo
 | 4 | Reflection | `rules/rarv-cycle.md` (Reflect); `agents/devils-advocate.md`; `skills/doubt-driven-development`; blind review in `rules/quality-gates.md` | covered (strong) |
 | 5 | Tool Use | each agent's `tools:` frontmatter; MCP integration; design principles in **`rules/tool-design.md`** (new) | covered (rule added) |
 | 6 | Planning | `agents/spec-doc-writer`, `story-planner`, `technical-architect`; `skills/spec-driven-development`, `planning-and-task-breakdown`, `scope`, `sprint` | covered (strong) |
-| 7 | Multi-Agent Collaboration | 28 agents; subagents + Agent-Teams worked example in orchestration-patterns | covered (strong) |
+| 7 | Multi-Agent Collaboration | 29 agents; subagents + Agent-Teams worked example in orchestration-patterns | covered (strong) |
 | 8 | Memory Management | `rules/continuity.md` (working) + `rules/agent-memory.md` (durable, now with the **working/episodic/semantic/procedural** taxonomy); `skills/remember`, `consolidate-learnings`, `context-engineering` | covered (taxonomy added) |
-| 9 | Learning & Adaptation | `rules/agent-memory.md`; `skills/remember`; the `load-learnings` SessionStart hook; **auto-capture** — the configurable `capture-learnings` hook (a non-blocking background job over Claude's own work, fired per the init-time `capture_mode`: SessionEnd · +SessionStart catch-up for abrupt closes · per-task Stop) | covered |
+| 9 | Learning & Adaptation | `rules/agent-memory.md`; `skills/remember`; the `load-learnings` SessionStart hook; **auto-capture** — the **opt-in** `capture-learnings` hook (a non-blocking background job over Claude's own work, fired per the init-time `capture_mode`, default off: SessionEnd · +SessionStart catch-up for abrupt closes · per-task Stop) | covered |
 | 10 | Model Context Protocol (MCP) | `catalog/mcp.yaml` → `.mcp.json`; `skills/browser-testing-with-devtools`; design guidance in `rules/tool-design.md` | covered (strong) |
 | 11 | Goal Setting & Monitoring | **`rules/goal-setting-and-monitoring.md`** (new) + spec acceptance criteria + `acceptance-reviewer` + quality-gates process signals | **rule added** |
 | 12 | Exception Handling & Recovery | **`rules/agent-resilience.md`** (new) + gate retry budgets + `skills/debugging-and-error-recovery` (product bugs) | **rule added** |

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/docs/agents.md

@@ -4,7 +4,7 @@ claude-kit installs a team of focused agents plus an **orchestrator** that runs
 software-delivery pipeline with a quality gate between phases. This guide shows how to drive them.
 
 > Prerequisite: the agents load when claude-kit is active in a project — installed as a plugin
-> (`/plugin install claude-kit`) or scaffolded with `claude-kit init`. Which agents are present
+> (`/plugin install claude-kit@claude-kit`) or scaffolded with `claude-kit init`. Which agents are present
 > depends on the **profile** you chose at init (`lean ⊊ standard ⊊ enterprise`). After installing
 > into a project, **restart Claude Code** so the agents, skills, and hooks load.
 >

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/docs/architecture.md

@@ -26,7 +26,7 @@ flowchart LR
     SRC -->|"auto-discovered at repo root"| MKT["GitHub marketplace<br/>.claude-plugin/marketplace.json"]
 
     PKG -->|"pip install claude-code-kit<br/>claude-kit init"| PROJ
-    MKT -->|"/plugin marketplace add ajyadav013/claude-kit<br/>/plugin install claude-kit"| CC["Claude Code session<br/>(agents · skills · commands · hooks live)"]
+    MKT -->|"/plugin marketplace add ajyadav013/claude-kit<br/>/plugin install claude-kit@claude-kit"| CC["Claude Code session<br/>(agents · skills · commands · hooks live)"]
     CC -->|"/claude-kit:init"| PROJ["Your project:<br/>CLAUDE.md + .claude/{rules,agents,skills,hooks,templates,config}"]
 
     PROJ --> RUN(["/sdlc — autonomous SDLC active"])

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/docs/cli.md

@@ -14,8 +14,9 @@ exports the kit's configuration. Install: `pip install claude-code-kit` (see
 | `diff [path]` | Preview what an `upgrade` would change (no writes) |
 | `export [path] -t cursor\|agents\|copilot [--force] [--dry-run] [--json]` | Project the config into Cursor (`.cursor/`), a root `AGENTS.md`, or GitHub Copilot (`.github/copilot-instructions.md`) for editors that aren't Claude Code |
 | `upgrade [path] [--force]` | Refresh kit/overlay files; protect your edits; prune orphans |
-| `pipeline validate · status · close-gate · abort` | Inspect/mutate the `/sdlc` state files (gate/lane/evidence coherence); **does not run** the pipeline |
+| `pipeline validate · status · close-gate · skip-gate · abort` | Inspect/mutate the `/sdlc` state files; **does not run** the pipeline. `close-gate` appends to the gate ledger (evidence sha256 + UTC timestamp) and refuses out-of-order or findings-blocked closes; `skip-gate --reason` records a conditional gate that doesn't apply; `validate` re-hashes **every** ledger entry; `--strict` fails closed when the install snapshot is missing (CI) |
 | `list-options` | List available frontend/backend/database/profile/MCP options |
+| `privacy-report [path] [--json]` | One line per installed hook: what it reads/writes/spawns; flags non-kit hook commands; states whether background learning capture is on and how to disable it |
 | `status [path]` | Show what's installed, the selection, and working memory |
 | `tickets [ID] [--path DIR] [--graph\|--graph-git] [--html] [--watch N] [--json]` | Live ticket board with tokens / model / agent / elapsed per ticket; `--graph` for the dependency graph, `--graph-git` for the commit graph, `--html` for a browser Kanban board, an `ID` for the detail view |
 | `version` | Print the version |

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/docs/install.md

@@ -22,7 +22,7 @@ Makes all agents, skills, commands, and hooks available inside Claude Code:
 
 ```text
 /plugin marketplace add ajyadav013/claude-kit
-/plugin install claude-kit
+/plugin install claude-kit@claude-kit        # qualified name: the claude-kit plugin from the claude-kit marketplace
 ```
 
 Then, inside any project you want the pipeline to manage:

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/docs/launch/github-about.md

@@ -9,7 +9,7 @@ Internal checklist for setting the GitHub repository "About" sidebar (descriptio
 Ready-to-paste candidates (kept within a self-imposed 120-character budget):
 
 1. **Recommended:**  
-   `Stack-agnostic SDLC config scaffolder for Claude Code. Quality gates, 28 agents, no Docker. MIT. pip install.` (109 chars)
+   `Evidence-gated SDLC for Claude Code — gates close only on cited evidence. Stack-agnostic config, no Docker. MIT.` (113 chars)
 
 2. **Alternative (simpler):**  
    `Autonomous SDLC pipeline for Claude Code. Spec→review→build→test→ship. Stack-agnostic config, no app code.` (106 chars)

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/docs/launch/posts.md

@@ -1,5 +1,9 @@
 # Launch Announcement Drafts
 
+> **Historical snapshot.** These drafts were written for an earlier release and are kept for
+> reference — component counts and claims reflect the kit at that time. The README carries the
+> current numbers (enforced by `scripts/check_docs_consistency.py`).
+
 ## Show HN
 
 ### Title

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/docs/rules-context-budget.md

@@ -22,7 +22,8 @@ exactly: OK"` runs, 2026-07-07; total input = `input + cache_creation + cache_re
 | Same project, `.claude/rules/` removed | 66,728 |
 
 **Attribution: `.claude/rules/` = 97,031 tokens (93% of the kit's 103,916-token injection).
-Everything else the kit installs — CLAUDE.md, 42 skills, 28 agents, hooks, settings — totals
+Everything else the kit installs — CLAUDE.md, 42 skills, 28 agents, hooks, settings (component
+counts as of the 2026-07-07 measurement; a historical snapshot, not the live roster) — totals
 6,885 tokens.** The lean design works everywhere except the one directory the original design
 assumed was inert, on-demand reference material. `CLAUDE.md`'s "live on-demand in
 `.claude/rules/`" sentence is false under real semantics.

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/hooks/hooks.json

@@ -15,10 +15,6 @@
           {
             "type": "command",
             "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/load-autonomy.sh\""
-          },
-          {
-            "type": "command",
-            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/capture-learnings.sh\" catchup"
           }
         ]
       }
@@ -99,18 +95,6 @@
           }
         ]
       }
-    ],
-    "SessionEnd": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/scripts/capture-learnings.sh\" end",
-            "timeout": 30
-          }
-        ]
-      }
     ]
   }
 }

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/pyproject.toml

@@ -4,8 +4,8 @@ build-backend = "hatchling.build"
 
 [project]
 name = "claude-code-kit"
-version = "0.75.0"
-description = "Cookiecutter-style scaffolder for an autonomous Claude Code SDLC configuration (no app code, no Docker). Asks ordered questions and installs CLAUDE.md + .claude/ (rules, the chosen profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates, working memory, and a self-improving learnings loop."
+version = "0.76.0"
+description = "Evidence-gated SDLC for Claude Code, installed as configuration (no app code, no Docker). Asks ordered questions and installs CLAUDE.md + .claude/ (rules, the chosen profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates with a tamper-evident gate ledger, working memory, and a self-improving learnings loop."
 readme = "README.md"
 requires-python = ">=3.9"
 license = "MIT"

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/rules/continuity.md

@@ -34,13 +34,25 @@ Schema (keep it small and truthful — omit a field rather than guess it):
   "task": "<one-line description of the run>",
   "profile": "lean | standard | enterprise",
   "scope": "individual | team | organization",
-  "mode": "A | B | C | D",
+  "mode": "A | B | C | D | E",
   "stage": "<current PIPELINE stage label>",
   "lanes": { "<lane>": "not-started | in-progress | passed | failed" },
   "last_gate_passed": "<gate token, e.g. code-review>",
   "open_findings": { "critical": 0, "high": 0, "medium": 0 },
   "gate_evidence": { "<gate token>": "<path to the evidence artifact>" },
   "gate_overrides": { "<gate token>": "<why a blocking gate was force-closed>" },
+  "gate_history": [
+    {
+      "gate": "<gate token>",
+      "status": "passed | skipped | overridden",
+      "evidence_path": "<path, null for skipped>",
+      "evidence_sha256": "<sha256 of the evidence file at close time>",
+      "verification": "agent | mechanical | human | override",
+      "recorded_at": "<UTC ISO timestamp>",
+      "override": "<reason when force-closed, else null>",
+      "reason": "<why a skipped gate does not apply (skipped entries only)>"
+    }
+  ],
   "git": { "branch": "<branch>", "sha": "<HEAD sha>", "worktrees": { "<lane>": "<path>" } },
   "pr": { "number": "<n>", "url": "<url>", "state": "<open|merged|closed>", "base": "<base>", "head": "<head>" },
   "next": "<the immediate next action>"
@@ -68,6 +80,15 @@ checks adapted, in the kit's own terms, from the MIT-licensed
 
 A gate is PASS only when zero **critical/high/medium** findings remain open (low/cosmetic may pass with notes). `gate_evidence` records the artifact backing each passed gate; `gate_overrides` is written **only** when a gate is deliberately force-closed despite open blocking findings, so a reviewer (or `claude-kit pipeline validate`) can surface and re-examine it.
 
+`gate_history` is the **append-only ledger** behind those mirrors: gates close **in the installed
+order** (the `gates:` list in `stack-catalog.snapshot.yaml` is execution-ordered; the first record
+may anchor anywhere so a run can be adopted mid-flight), a conditional gate that doesn't apply is
+recorded `skipped` with a reason (`claude-kit pipeline skip-gate`), and each closed entry carries
+the evidence file's **sha256** — `validate` re-hashes every entry, so evidence cannot silently
+change after its gate closed. `verification` records *how* the evidence was checked: `agent`
+(a reviewer agent cited it), `mechanical` / `human` (reserved for parsed evidence and explicit
+human sign-off), `override` (force-closed). Old snapshots without `gate_history` stay valid.
+
 **Resume by reloading, not by re-running.** On resume, read the snapshot as *context* to decide where to continue — then continue from there. Do **not** re-run setup that already ran, re-apply edits already committed, or re-open a gate already PASSed. Re-enter at the first gate *after* `last_gate_passed`, re-running only un-passed or defect-affected lanes. The snapshot records what was *true when written*, so the verify-before-trust check still applies (`.claude/rules/agent-memory.md`): if a "passed" gate's artifact is gone, treat it as not passed. If the snapshot is absent or unparseable, fall back to the freeform CONTINUITY state (back-compatible) and proceed.
 
 ## Concurrency

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/scripts/check_docs_consistency.py

@@ -123,7 +123,9 @@ def _actuals() -> dict[str, int]:
 # found". Subset counts elsewhere ("8 agent-operation rules") are deliberately NOT anchored.
 _ANCHORS: list[tuple[str, str, str]] = [
     ("agents", "README.md", r"\*\*(\d+)\*\* tiered agents"),
+    ("agents", "README.md", r"the full (\d+)-agent roster"),
     ("agents", "docs/agents.md", r"(\d+) specialized roles"),
+    ("agents", "docs/agentic-patterns.md", r"(\d+) agents; subagents"),
     ("rules", "README.md", r"\*\*(\d+)\*\* stack-agnostic core rules"),
     # The headline skill number is the FULL catalog (core + collection); the breakdown pins each part.
     ("skills", "README.md", r"\*\*(\d+)\*\* context-activated skills"),

{claude_code_kit-0.75.0 → claude_code_kit-0.76.0}/src/claude_kit/__init__.py

@@ -1,10 +1,10 @@
-"""claude-kit — an autonomous, stack-agnostic SDLC for Claude Code.
+"""claude-kit — an evidence-gated, stack-agnostic SDLC for Claude Code.
 
-A Cookiecutter-style scaffolder for a Claude Code **configuration** (no application code, no
+A scaffolder for a Claude Code **configuration** (no application code, no
 Docker): ``claude-kit init`` asks ordered questions and lays down ``CLAUDE.md`` + ``.claude/``
 (rules, the chosen profile's agents/skills, hooks, artifact templates, config) plus an optional
 ``.mcp.json``. The same payload is consumed directly by Claude Code when claude-kit is installed
 as a plugin. Extensibility is data-driven via the ``catalog/`` (stacks, profiles, MCP).
 """
 
-__version__ = "0.75.0"
+__version__ = "0.76.0"