docs: CHANGELOGs + freshness riders conformance wave (10 plugins)

plugins/ai-briefing/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "ai-briefing",
-  "version": "0.5.1",
+  "version": "0.5.2",
   "description": "Build source-backed AI-industry briefings from official vendor publications, configured RSS/Atom feeds, GitHub releases, reputable secondary reporting, and user-supplied URLs. Deduplicate, rank, and present results as markdown or optional HTML/PPTX decks, with repository-owned profile, audience, and brand configuration. Automated X/Twitter collection is disabled; Playwright is used only for deterministic local rendering.",
   "author": {
     "name": "Melodic Software",

plugins/ai-briefing/CHANGELOG.md

@@ -3,6 +3,16 @@
 All notable changes to the `ai-briefing` plugin are documented here. Format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning.
 
+## [0.5.2]
+
+### Changed
+
+- **Freshness rider on the Playwright environment matrix** (fleet conformance
+  wave: volatile platform facts carry a verified-date + official link). The
+  README matrix is dated and re-verified against Playwright's system
+  requirements; the setup skill no longer restates the version matrix and
+  defers to the linked page as authoritative.
+
 ## [0.5.1]
 
 ### Changed

plugins/ai-briefing/README.md

@@ -23,7 +23,10 @@ and presents the result as markdown or an optional HTML/PPTX deck.
 
 ## Optional build prerequisites
 
-The presentation pipeline follows Playwright's current supported environment matrix:
+The presentation pipeline follows Playwright's current supported environment matrix
+(verified 2026-07-18 against
+[Playwright system requirements](https://playwright.dev/docs/intro#system-requirements) —
+re-check that page before installing, the matrix moves with Playwright releases):
 
 - the latest Node.js 22.x, 24.x, or 26.x release, with npm;
 - Windows 11+ or Windows Server 2019+;
@@ -33,7 +36,6 @@ The presentation pipeline follows Playwright's current supported environment mat
 Setup preflights Node, npm, and the OS family. On Linux, Playwright's documented
 `install --with-deps` flow may invoke the system package manager and require elevation.
 Unsupported or missing prerequisites are reported before the existing runtime is changed.
-See [Playwright system requirements](https://playwright.dev/docs/intro#system-requirements).
 
 The `setup --with-build-deps` install step is a POSIX-shell script: it requires
 Bash — on native Windows that is Git Bash (its platform gate accepts

plugins/ai-briefing/skills/setup/SKILL.md

@@ -127,10 +127,10 @@ Tracked profile configuration belongs in the consuming repository. Never write i
    only to render and inspect generated local HTML/PDF artifacts; it must not be used as a
    collection browser. On Linux, Playwright's documented `--with-deps` path installs required
    operating-system packages. Other supported platforms install the browser shell and rely
-   on their platform prerequisites. Current supported targets are Windows 11+/Server 2019+,
-   macOS 14+, Debian 12/13, and Ubuntu 22.04/24.04/26.04 on x86-64 or arm64, using the latest
-   Node.js 22.x, 24.x, or 26.x with npm. The launch probe runs before the runtime swap. See
-   <https://playwright.dev/docs/intro#system-requirements>.
+   on their platform prerequisites. Supported OS and Node targets are whatever
+   [Playwright's system requirements](https://playwright.dev/docs/intro#system-requirements)
+   currently list (the README's matrix is a dated snapshot of that page — the link is
+   authoritative). The launch probe runs before the runtime swap.
 
 5. **Confirm.** Report the profile path, whether `sources.md` was created or preserved,
    which optional overlays were created, and whether build dependencies were installed or

plugins/claude-ops/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "claude-ops",
-  "version": "0.11.2",
+  "version": "0.11.3",
   "description": "Claude Code operations toolkit. Five skills: observability (read locally captured telemetry — OTEL store, collector, hook-event JSONL, ccusage — with trend reports and store pruning), known-issues (search known Claude product GitHub bugs, check service health, maintain a persistent tracked-issue registry), changelog (ingest Claude Code changelog entries and integrate them into the current repo), plugins (bring a machine's plugin fleet current on demand — marketplace refresh, effective-scope updates including in-repo project/local installs, new-plugin install per policy, scope-divergence detection and explicit convergence), and a re-runnable setup action that settles where the known-issues registry lives. Plus a family of seven advisory *-audit telemetry-emitter hooks (API errors, config changes, instruction loads, permission denials, pre-compaction, skill usage, tool failures) that emit the shared hook-telemetry envelope, and a reference sink that maps envelopes into the hook-events.jsonl the observability skill reads.",
   "author": {
     "name": "Melodic Software",

plugins/claude-ops/CHANGELOG.md

@@ -3,6 +3,17 @@
 All notable changes to the `claude-ops` plugin are documented here. Format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning.
 
+## [0.11.3]
+
+### Changed
+
+- **Freshness riders on platform-fact docs** (fleet conformance wave). The
+  `plugins` skill's scope-semantics doc now carries a verified-date header
+  (all version-gated claims re-verified: `/reload-plugins --force` ≥ 2.1.163,
+  renames ≥ 2.1.193, `plugin prune` ≥ 2.1.121, `userConfig` type set); the
+  monitor-restart claim now cites its actual source (plugins-reference). The
+  setup skill's `pluginConfigs` claim is dated and pinned to ≥ 2.1.207.
+
 ## [0.11.2]
 
 ### Changed

plugins/claude-ops/skills/plugins/context/scope-semantics.md

@@ -1,9 +1,11 @@
 # Scope semantics — verified facts this skill depends on
 
 Every claim below was verified against a fetched official-docs page or an empirical test on a real
-machine during this skill's implementation, not assumed from training data. Re-verify against
-`code.claude.com/docs/en/plugins-reference` and `discover-plugins` if Claude Code's plugin CLI
-changes shape.
+machine, not assumed from training data. Last re-verified 2026-07-18 against
+[plugins-reference](https://code.claude.com/docs/en/plugins-reference),
+[discover-plugins](https://code.claude.com/docs/en/discover-plugins), the published plugin-manifest
+JSON Schema, and the Claude Code changelog (version gates). Re-verify against those pages if Claude
+Code's plugin CLI changes shape.
 
 ## Scope-by-cwd loading
 
@@ -55,8 +57,8 @@ remove an `enabledPlugins` entry, and only that action surfaces a settings diff.
 ## `/reload-plugins` — bare by default, `--force` for the MCP-cache-invalidation case
 
 **Verified against `code.claude.com/docs/en/discover-plugins`**: `/reload-plugins` refreshes skills,
-agents, hooks, MCP, and LSP servers in-process. It does **not** cover monitors — a monitor requires a
-full session restart. Recommend bare `/reload-plugins` by default; call out the restart requirement
+agents, hooks, MCP, and LSP servers in-process. It does **not** cover monitors — per
+`code.claude.com/docs/en/plugins-reference`, "monitors require a session restart". Recommend bare `/reload-plugins` by default; call out the restart requirement
 only when an updated plugin ships a monitor.
 
 `--force` is real (Claude Code ≥ 2.1.163), but scoped to one specific case: a plugin that provides an

plugins/claude-ops/skills/setup/SKILL.md

@@ -11,9 +11,10 @@ disable-model-invocation: true
 Confirm the known-issues registry and skill-usage-log locations without editing Claude Code
 settings. `registry_dir` and `skill_usage_dir` are personal `userConfig` options. Claude Code
 prompts for them when the plugin is enabled, stores non-sensitive options in user settings, and
-ignores `pluginConfigs` entries in project and local settings on current releases.
+ignores `pluginConfigs` entries in project and local settings on current releases (≥ 2.1.207).
 
-Official contract: <https://code.claude.com/docs/en/plugins-reference#user-configuration>.
+Official contract (verified 2026-07-18):
+<https://code.claude.com/docs/en/plugins-reference#user-configuration>.
 
 ## Task
 

plugins/context7/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "context7",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Looks up current library documentation, API references, and code examples via Context7 (ctx7 CLI or the Context7 MCP server) with a two-step resolve-then-query workflow: a lookup skill (default lookup plus an upstream drift-check action) and a setup skill for CLI install, auth, and MCP configuration.",
   "author": {
     "name": "Melodic Software",

plugins/context7/CHANGELOG.md

@@ -3,6 +3,21 @@
 All notable changes to the `context7` plugin are documented here. Format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning.
 
+## [0.3.1]
+
+### Changed
+
+- **CLI/platform facts re-verified against `ctx7` 0.5.5 and corrected**
+  (fleet conformance wave: freshness riders). `--base-url` default is
+  `https://context7.com` (not `/api`), version flag is lowercase `-v`,
+  `library`'s query argument is optional, the `skills` surface is deprecated
+  upstream (this plugin never invokes it), and new top-level
+  `remove`/`uninstall` + `upgrade` commands are listed.
+- **Claude Code unset-env-var MCP behavior corrected**: the config loads with
+  a missing-variable warning and the literal `${VAR}` text is sent as-is
+  (silently broken auth) — it is not a parse failure. Both context docs now
+  carry verified-date + official-link riders.
+
 ## [0.3.0]
 
 ### Changed

plugins/context7/skills/lookup/context/cli.md

@@ -2,11 +2,15 @@
 
 Install, configure, command reference, flags, env vars, and Windows-specific gotchas.
 
+> Verified 2026-07-18 against `ctx7` 0.5.5 (live `--help`/`--version` output) and
+> [Context7's CLI docs](https://context7.com/docs/clients/cli).
+> The CLI moves fast — re-check against a current install before acting on a row.
+
 ## Install
 
 ```bash
 npm install -g ctx7@latest
-ctx7 --version  # 0.3.13 or later
+ctx7 --version  # 0.5.5 or later
 ```
 
 Fallback (no global install): `npx ctx7@latest <command>` — slower per-invocation, no PATH ceremony.
@@ -27,10 +31,12 @@ Set it wherever your project manages local environment variables (shell profile,
 
 | Command | Purpose |
 |---|---|
-| `ctx7 library <name> <query>` | Resolve library name → Context7 library ID |
+| `ctx7 library <name> [query]` | Resolve library name → Context7 library ID (query optional since 0.5.x; still pass one for ranking) |
 | `ctx7 docs <libraryId> <query>` | Fetch documentation for a resolved library |
 | `ctx7 setup [flags]` | Configure Context7 for an IDE (this plugin does NOT use it — see below) |
 | `ctx7 login` / `logout` / `whoami` | OAuth flow (this plugin does NOT use it — env var is enough) |
+| `ctx7 remove` / `uninstall` | Remove a `setup`-installed agent configuration (this plugin does NOT use it) |
+| `ctx7 upgrade` | Self-upgrade the CLI |
 | `ctx7 skills install <repo> [skill]` | Install skills from a GitHub repo (this plugin does NOT use it — see below) |
 | `ctx7 skills search <keywords>` | Search the Context7 skills registry |
 | `ctx7 skills suggest` | Auto-suggest skills based on project dependencies |
@@ -39,16 +45,20 @@ Set it wherever your project manages local environment variables (shell profile,
 | `ctx7 skills list` | List installed skills in the current directory |
 | `ctx7 skills remove <name>` | Uninstall a skill |
 
-Short aliases: `ctx7 skills` ↔ `ctx7 skill`, `install` ↔ `i`, `list` ↔ `ls`, `search` ↔ `s`, `generate` ↔ `gen/g`.
+**The whole `ctx7 skills` surface is deprecated upstream as of 0.5.5** — hidden from `--help`, still
+runnable, with an in-tool warning that it "will stop working in the next major release". This plugin
+never invokes it (see below), so no behavior here depends on it.
+
+Short aliases: `ctx7 skills` ↔ `ctx7 skill`, `install` ↔ `i`, `list` ↔ `ls`, `search` ↔ `s`, `generate` ↔ `gen`, `remove` ↔ `rm`.
 
 ## Flags
 
 ### Global
 
 | Flag | Default | Purpose |
 |---|---|---|
-| `--base-url <url>` | `https://context7.com/api` | Point at a custom Context7 backend |
-| `-V, --version` | | Print version |
+| `--base-url <url>` | `https://context7.com` | Point at a custom Context7 backend (API paths are appended) |
+| `-v, --version` | | Print version |
 | `-h, --help` | | Help for the current command |
 
 ### Per-command (`library`, `docs`)
@@ -57,7 +67,7 @@ Short aliases: `ctx7 skills` ↔ `ctx7 skill`, `install` ↔ `i`, `list` ↔ `ls
 |---|---|
 | `--json` | Structured JSON output (vs. formatted text). Useful for scripts / `jq` extraction |
 
-**No `--tokens`, `--limit`, `--format`, or `-v/--verbose` flag exists.** Default content depth is server-controlled. For more content per call, prefer MCP (`mcp__context7__query-docs`) — returns ~1.8× more content by default.
+**No `--tokens`, `--limit`, `--format`, or `--verbose` flag exists.** Default content depth is server-controlled. For more content per call, prefer MCP (`mcp__context7__query-docs`) — returns ~1.8× more content by default.
 
 ### Setup / install flags (why this plugin doesn't use them)
 

plugins/context7/skills/lookup/context/mcp.md

@@ -2,6 +2,10 @@
 
 Context7 HTTP MCP server — reads the same backend as the `ctx7` CLI. This plugin does NOT ship or auto-start an MCP server; the consuming project opts in by declaring it in its own MCP configuration.
 
+> Server URL and header facts verified 2026-07-18 against `ctx7` 0.5.5 source and
+> [Context7's docs](https://context7.com/docs); Claude Code config behavior verified against
+> [the MCP docs](https://code.claude.com/docs/en/mcp). Re-check both before acting on a row.
+
 ## Configuration (consumer-side, optional)
 
 Add to the consuming project's `.mcp.json` (or user-scope MCP config) — server entries live under the top-level `mcpServers` key. Anonymous (low-rate) usage needs no headers:
@@ -17,7 +21,7 @@ Add to the consuming project's `.mcp.json` (or user-scope MCP config) — server
 }
 ```
 
-With an API key (higher limits), add the `CONTEXT7_API_KEY` request header (the header name Context7's server expects) — but note Claude Code **fails to parse the config** when a referenced env var is unset with no default, so only use this form once `CONTEXT7_API_KEY` is actually set in your environment:
+With an API key (higher limits), add the `CONTEXT7_API_KEY` request header (the header name Context7's server expects). When a referenced env var is unset with no default, Claude Code still loads the config: it reports a missing-variable warning in `claude mcp list` and sends the **literal `${CONTEXT7_API_KEY}` text as-is** — silently broken auth, not a parse failure. Only use this form once `CONTEXT7_API_KEY` is actually set in your environment (or add a `${VAR:-default}` fallback):
 
 ```json
 {

plugins/desktop-notification/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "desktop-notification",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "Alert you when Claude Code needs input — an audible terminal bell, an OSC 9 terminal notification, and an OS-native toast (macOS/Linux) on permission and idle prompts.",
   "author": {
     "name": "Melodic Software",

plugins/desktop-notification/CHANGELOG.md

@@ -3,6 +3,22 @@
 All notable changes to the `desktop-notification` plugin are documented here. Format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning.
 
+## [0.3.2]
+
+### Changed
+
+- **Freshness rider on the channel table** (fleet conformance wave). The
+  `terminalSequence` / Claude Code v2.1.141+ claim is re-verified against the
+  Claude Code changelog and dated, with links to the changelog and the hooks
+  reference.
+
+## [0.3.1]
+
+### Changed
+
+- Shared `hook-utils.sh` resynced from the repository library (no behavior
+  change in this plugin's hook).
+
 ## [0.3.0]
 
 ### Changed

plugins/desktop-notification/README.md

@@ -19,6 +19,10 @@ notification, and — on macOS and Linux — an OS-native desktop toast.
 | `terminal_notify` | `desktop_notification_terminal_notify_enabled` | OSC 9 desktop notification, emitted via the hook's `terminalSequence` output (Claude Code v2.1.141+ writes it through its own terminal path). |
 | `os_toast` | `desktop_notification_os_toast_enabled` | OS-native toast (see per-OS table). |
 
+Platform facts verified 2026-07-18: hook `terminalSequence` output landed in Claude Code
+v2.1.141 per the [Claude Code changelog](https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md);
+channel semantics per the [hooks reference](https://code.claude.com/docs/en/hooks).
+
 ### Per-OS `os_toast` behavior
 
 | OS | Tool | Requirement |

plugins/firecrawl/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "firecrawl",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "Web scraping, search, crawling, and file parsing through the firecrawl-cli binary with a write-to-disk-then-Read pattern that keeps large results out of context — plus a gated maintainer update flow tracking the upstream CLI and skill source.",
   "author": {
     "name": "Melodic Software",

plugins/firecrawl/CHANGELOG.md

@@ -0,0 +1,16 @@
+# Changelog
+
+All notable changes to the `firecrawl` plugin are documented here. Format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning.
+
+## [0.2.2]
+
+### Added
+
+- This changelog (fleet conformance wave: every versioned plugin ships a
+  Keep-a-Changelog file).
+
+## [0.2.1]
+
+First versioned release covered by this changelog; see the git history of
+`plugins/firecrawl/` for earlier changes.

plugins/miro/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "miro",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Miro board management over the Model Context Protocol: create and manage boards, sticky notes, shapes, frames, connectors, and tags for EventStorming, brainstorming, and diagramming. Bundles a local stdio MCP server (single self-contained Node artifact); installs disabled — opt in and supply a Miro API token.",
   "author": {
     "name": "Melodic Software",

plugins/miro/CHANGELOG.md

@@ -0,0 +1,22 @@
+# Changelog
+
+All notable changes to the `miro` plugin are documented here. Format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning.
+
+## [0.1.2]
+
+### Added
+
+- This changelog (fleet conformance wave: every versioned plugin ships a
+  Keep-a-Changelog file).
+
+### Changed
+
+- MCP server version aligned with the plugin: `package.json`, the server's
+  MCP `Implementation` version, and the committed bundle now all report
+  `0.1.2` (they had drifted to `0.1.0` while `plugin.json` was `0.1.1`).
+
+## [0.1.1]
+
+First versioned release covered by this changelog; see the git history of
+`plugins/miro/` for earlier changes.

plugins/miro/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@melodic-software/miro-mcp",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "General-purpose Miro MCP server. Creates and manages sticky notes, shapes, frames, connectors, and tags on Miro boards via the Model Context Protocol.",
   "type": "module",
   "private": true,

plugins/miro/src/index.ts

@@ -13,7 +13,7 @@ import { registerStickyNoteTools } from "./tools/sticky-notes.js";
 import { registerTagTools } from "./tools/tags.js";
 
 const server = new McpServer(
-  { name: "miro-mcp", version: "0.1.0" },
+  { name: "miro-mcp", version: "0.1.2" },
   {
     instructions:
       "Miro board management for visual collaboration. " +