From 4a5953c271edb10fdaeec77db740aecd412c1a51 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Wed, 12 Aug 2026 07:40:50 +0000 Subject: [PATCH 1/2] fix(architecture): correct improve Gotcha on CLAUDE_PLUGIN_DATA Fixes #2207 Co-authored-by: Kyle Sexton --- plugins/architecture/CHANGELOG.md | 7 +++++++ plugins/architecture/skills/improve/SKILL.md | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/plugins/architecture/CHANGELOG.md b/plugins/architecture/CHANGELOG.md index 3b4cdc607f..1427243388 100644 --- a/plugins/architecture/CHANGELOG.md +++ b/plugins/architecture/CHANGELOG.md @@ -3,6 +3,13 @@ All notable changes to the `architecture` plugin are documented here. Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning. +## [0.5.2] + +### Fixed + +- **The `improve` Gotcha now states why `${CLAUDE_PLUGIN_DATA}` is wrong for per-project artifacts + beyond substitution mechanics** (#2207). + ## [0.5.1] ### Fixed diff --git a/plugins/architecture/skills/improve/SKILL.md b/plugins/architecture/skills/improve/SKILL.md index 6086870140..b89eda8530 100644 --- a/plugins/architecture/skills/improve/SKILL.md +++ b/plugins/architecture/skills/improve/SKILL.md @@ -68,5 +68,5 @@ Graceful degradation — where a named step below is not available in the consum Observed failure history — patterns that have actually bitten. Add here when a new one surfaces. -- **The durable candidate artifact is a per-project memory-tier file, never `${CLAUDE_PLUGIN_DATA}`.** Even resolved it points at a plugin-global dir that collides candidates across projects. The artifact resolves through the marketplace topic-docs convention (the plugin's topic-docs [binding](../../reference/topic-docs.md)) — memory tier, default `.work//`. A `${CLAUDE_PROJECT_DIR}/.claude/...` path is also wrong: `.claude/` generated output is reserved for observability, and an unignored artifact there leaks scan output into git. +- **The durable candidate artifact is a per-project memory-tier file, never `${CLAUDE_PLUGIN_DATA}`.** Even resolved it points at a plugin-global dir with no project dimension that collides candidates across projects, and uninstalling from the last remaining scope deletes the directory — the documented use is deps/caches/generated code, not per-project artifacts. The artifact resolves through the marketplace topic-docs convention (the plugin's topic-docs [binding](../../reference/topic-docs.md)) — memory tier, default `.work//`. A `${CLAUDE_PROJECT_DIR}/.claude/...` path is also wrong: `.claude/` generated output is reserved for observability, and an unignored artifact there leaks scan output into git. - **Scan-agent claims are shipped only after Phase 1.5 reproduction.** Explore agents have a demonstrated error rate: a real run reported a service "registered but never composed — a bug in the seam" that one grep disproved (it *is* consumed, via a different consumer, with tests). Any candidate headed for a `Strong` badge and any runtime-bug / dead-code claim is reproduced against the actual code before it reaches the user-facing report — the report lends every claim its authority, so an unreproduced overstatement is cheap to make and expensive to reputation. From b30c5c5ffbc36568b78fbe9bcc623be32215c2ea Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Wed, 12 Aug 2026 08:35:56 +0000 Subject: [PATCH 2/2] fix(architecture): bump manifest to 0.5.2 for changelog parity --- plugins/architecture/.claude-plugin/plugin.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/architecture/.claude-plugin/plugin.json b/plugins/architecture/.claude-plugin/plugin.json index 5e2dcda01f..0b4b42f831 100644 --- a/plugins/architecture/.claude-plugin/plugin.json +++ b/plugins/architecture/.claude-plugin/plugin.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json", "name": "architecture", - "version": "0.5.1", + "version": "0.5.2", "description": "Scans an existing codebase for module-level architecture friction — shallow modules, seam leaks, and locality gaps — using Ousterhout's deep-module lens, presents candidates as a self-contained HTML report, and runs an interview loop on the selected candidate before handing off for planning.", "author": { "name": "Melodic Software",