v1.1.1 — install-blocking fix

v1.1.1 — install-blocking fix

v1.1.0 failed to install with Validation errors: skills: Invalid input because plugin.json shipped a skills array that Claude Code's current plugin schema rejects. v1.1.1 removes the field so the install validator accepts the manifest.

Fixed

• Removed obsolete skills array from plugin.json. The skill is auto-discovered from skills/bug-echo/SKILL.md frontmatter regardless. The skills array was metadata for an older plugin schema; the current validator rejects it. This is not a regression from v1.1.0 — the field shape has been identical since v1.0.0 (commit 9d54335 and earlier). The schema tightened between v1.0.0 and now.

Changed

• Version bumped to 1.1.1 across plugin.json, marketplace.json, SKILL.md frontmatter, and README.md.

Compatibility

• All v1.1.0 features remain. No spec changes, no behavior changes. Same WATCH class, same managed-commit step, same hardened git show strategy, same output-dir override.
• If you tried to install v1.1.0 and it failed: retry the install command. v1.1.1 supersedes it.

Note on v1.1.0

The v1.1.0 GitHub Release stays published as a historical artifact but is known-broken-on-install for users on the current Claude Code plugin schema. Anyone reading the v1.1.0 release notes should install v1.1.1 instead.

v1.1.0 — bug-prospector handoff + WATCH class

v1.1.0 — bug-prospector handoff + WATCH class

Review-driven release closing 13 recommendations from a self-applied skill-reviewer audit. Three waves: critical version sync, spec consistency, and polish. All edits are documentation/spec; no behavior changes to existing reports.

Added

• Companion-skill handoff — when bug-echo can't infer a pattern from a recent fix (no diff, or self-validation fails), the skill now points the user at bug-prospector for forward-looking analysis instead of synthesizing a catalog (SKILL.md § When inference fails: delegate to bug-prospector).
• WATCH classification — a fourth match class for findings that match the anti-pattern but are contextually near-threshold or already have architectural defense in place (e.g., a SwiftUI conditional cluster inside a @ViewBuilder split that scoped a known crash). WATCH findings get the same 9-column rating-table shape as BUG but with documentation-only suggested fixes. Usable today; the canonical example at skills/bug-echo/examples/2026-05-03-bug-echo-deep-viewbuilder-crash.md already demonstrates it.
• Managed-commit step after guided fixes — Step 6 now offers to commit applied fixes as bug-echo: applied <N> fixes from <slug> report, staging only files the skill itself edited. Closes the Pre-flight/re-run collision: subsequent bug-echo invocations no longer trip on the previous run's uncommitted edits.
• Hardened git show strategy — Step 2B's self-validation now uses an explicit decision tree for four cases: staged diff (git show HEAD:path), unstaged diff (git show HEAD:path), most recent commit (git show HEAD~1:path, with an abort condition for single-commit repos detected via git rev-list --count HEAD), and file-renamed-in-HEAD (git log --follow --name-status -1 to find the prior path). Previously the no-HEAD~1 and rename cases failed silently.
• Custom analyzers acknowledged as third scan tool — Step 3 now documents that for patterns neither regex nor AST-grep can express cleanly (e.g., counting scope-direct conditional children at the lexical scope level), a custom Bash-invoked analyzer (Python, Swift, etc.) is acceptable. Priority: Grep → AST-grep → custom.
• Output directory override — /bug-echo output=docs/audits/ writes the report to a custom location instead of .agents/research/. Pre-flight Step 3 resolves the path; Step 5 honors it. The default remains .agents/research/ (a convention shared with radar-suite, bug-prospector, and other Coffee & Code audit skills).
• Metadata-keys documentation — frontmatter's tier and category keys are now documented in a ## Metadata keys section listing the legal values (tier: execution/planning/review; category: debugging/architecture/release-prep/documentation/ui-audit/data-model) and the cross-skill ontology source (the radar-suite README).

Changed

• Pre-flight step 2 renamed "Check the codebase compiles (best-effort)" → "Note build manifest presence (advisory)". The body now matches the heading: detect build manifests via Glob, record in report header, do not run a build.
• Pre-flight uncommitted-changes prompt points users at the prior-bug-echo-session case explicitly so they recognize the source of friction.
• README Output Format section replaced forward-looking "axis classification" copy with the actual 9-column shape (ending in Status) and the new 4-class classification (BUG/WATCH/OK/REVIEW).
• README describe-mode example link carries a (synthesized) caveat in both spots, matching the honesty already inside the example file's frontmatter.
• describe-mode example now ships a real ast-grep YAML rule alongside the natural-language description, plus a runnable ast-grep scan --rule <file> command and a two-stage approximation for inline use without a config file.
• SKILL.md v1.x references consolidated — five scattered inline "v1.0 / future v1.1 may add..." mentions collapsed to four cross-references pointing at the single canonical ## Deferred to v1.1+ section. Three stale "in v1.0" claims replaced with present-tense language.

Fixed

• Version number unified to 1.1.0 across plugin.json, marketplace.json, SKILL.md frontmatter, and both README.md mentions. The marketplace install dialog had been showing 1.0.0 since the bug-prospector handoff features shipped in commit c2bcd2d.
• Description strings converged to three intentional variants (router-facing, marketplace install dialog, plugin-technical) instead of five accidental ones across the manifests and frontmatter.

Compatibility

• Backwards-compatible. Existing BUG/OK/REVIEW reports remain valid. WATCH is additive (new class, no reclassification of existing findings). The managed-commit and output-dir-override features are opt-in via AskUserQuestion and prompt argument respectively.
• Marketplace re-install: if you installed bug-echo before v1.1.0, run /plugin marketplace update bug-echo followed by /plugin install bug-echo@bug-echo to pick up the new manifest. Claude Code may cache the 1.0.0 manifest briefly after release; if the install dialog still shows 1.0.0, retry after a minute.

Acknowledgment

This release closes the audit at skill-reviewer review /Volumes/2 TB Drive/Coding/GitHub/bug-echo/skills/bug-echo/. Running skill-reviewer against its own findings before publishing is the simplest sanity check that the loop closed.