pi-ptc-subagents 7.6.0 → 7.7.1

package/CHANGELOG.md

@@ -5,6 +5,58 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [7.7.1] - 2026-11-02
+
+### Fixed
+
+- **The new-version check now caches what it learned** (Kimi face, ADR-0023): the probe
+  state was written only when a newer release was found, so in the common case — the plugin
+  being up to date — `checkedAt` never landed on disk and the 6-hour TTL never took effect:
+  every single user message re-queried GitHub's `/releases/latest`. It now persists the
+  state as soon as it has fetched. Measured on the installed 7.7.0: the cache file was empty
+  after a run; it now holds `checkedAt` and `latest`.
+
+## [7.7.0] - 2026-11-02
+
+### Added
+
+- **The plugin now says so when a newer release exists** (Kimi face, ADR-0023): a
+  `UserPromptSubmit` hook compares the plugin's own manifest version against the latest
+  GitHub Release and, when they differ, attaches the notice to your next message — the
+  agent then says so in its reply, with the update command. Nothing to configure, no
+  marketplace to point at. Kimi Code has no plugin auto-update path: the update badge
+  only exists for plugins a marketplace catalog can match by id, and pointing Kimi Code
+  at a custom catalog _replaces_ the default one (measured: the default catalog has 7
+  entries — 3 official, 4 curated — a custom one has 1; the official plugins drop out of
+  the panel and lose their "update detected" notification, which requires the default
+  CDN catalog). The badge is also only visible when you open `/plugins`: the desktop
+  "installed" row shows version, toggle and delete, and no update button.
+  The check reads the latest release through `/releases/latest` (a redirect, so
+  `api.github.com` is never called), accepts plain `x.y.z` only, caches for 6 hours,
+  speaks once per version (again after 7 ignored days), and stays silent offline —
+  fail-open, it never blocks a turn. Probes: `tests/kimi/version-check.test.mjs`, 7/7 —
+  one of them caught a real bug while it was being written (the cache stored a parsed
+  array and re-parsed it as a string, so the check exited silently — exactly the failure
+  this feature exists to prevent).
+
+- **Artifact import gate** (`scripts/check-artifact-imports.mjs`, wired into `pnpm test`): a
+  built artifact's bare imports must be declared by the package that produced them. The rule is
+  "the declaration follows the artifact, not just the source" — moving code between packages used
+  to carry the dependency declaration along with the source, while the built `dist/index.js` kept
+  importing the package: on a clean install the extension could not resolve it (7 probes red, CI
+  red too; the local tree only stayed green because a months-old symlink in the root
+  `node_modules` happened to cover it). `dependencies` / `peerDependencies` /
+  `optionalDependencies` count, `devDependencies` does not (they do not ship), and imports shown
+  inside comments or strings are not imports.
+
+### Fixed
+
+- **Marketplace catalog entry** (`plugin-marketplace.json`, ADR-0021): the entry's `tier`
+  must be `official` or `curated` — that is the parser's whitelist, which is stricter than
+  the response schema's enum. Writing `third-party` (read off the response schema) made the
+  whole catalog fail to load, taking the official entries with it. The entry now omits
+  `tier`, and `build:kimi` fails the build if a `tier` ever shows up.
+
 ## [7.6.0] - 2026-11-02
 
 ### Added

package/README.md

@@ -81,25 +81,18 @@ URL tracks the latest GitHub Release (pinned URLs get no update checks); run `/r
 activate. A bundled `ptc` skill teaches the model when to write a program instead of
 fanning out tool calls one by one.
 
-**Update badges need a marketplace entry.** Kimi Code only offers "update 7.1.0 → 7.5.0" in
-`/plugins` for plugins the marketplace catalog can match by id — a bare GitHub install is
-installed but never listed, so it never gets a badge. This repo ships the catalog; point
-Kimi Code at it:
-
-```bash
-/plugins marketplace https://raw.githubusercontent.com/a1121611810/pi-ptc-subagents/main/plugin-marketplace.json
-```
-
-or keep it for every session (desktop app included):
-
-```bash
-export KIMI_CODE_PLUGIN_MARKETPLACE_URL=https://raw.githubusercontent.com/a1121611810/pi-ptc-subagents/main/plugin-marketplace.json
-```
-
-The entry deliberately omits `version`: Kimi Code resolves it from the latest GitHub
-Release, so the catalog never goes stale. A custom catalog **replaces** the official one
-rather than adding to it, and updates stay one keystroke (`Enter` in `/plugins`) — Kimi
-Code has no auto-download path.
+**You get told when a new version lands.** The plugin ships a `UserPromptSubmit` hook that
+compares its own version against the latest GitHub Release; when they differ, the notice is
+attached to your next message and the agent says so in its reply. No marketplace setup, no
+config, nothing to click. Update with
+`/plugins install https://github.com/a1121611810/pi-ptc-subagents` — the bare repo URL
+installs the latest release.
+
+**Optional: the marketplace badge.** Kimi Code also shows "update 7.1.0 → 7.5.0" in `/plugins`
+for plugins a marketplace catalog can match by id, and this repo ships such a catalog
+(`plugin-marketplace.json`). But pointing Kimi Code at it _replaces_ the default catalog, so
+the official plugins drop out of the panel and lose their update notifications. Treat it as
+opt-in, not as a setup step.
 
 ## The engine on its own (no model, no pi)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-ptc-subagents",
-  "version": "7.6.0",
+  "version": "7.7.1",
   "description": "Programmable tool calling (PTC) and subagent fan-out for pi",
   "keywords": [
     "pi",
@@ -39,8 +39,9 @@
     "build:kimi": "pnpm --filter @pi-ptc/kimi-mcp run build && node scripts/assemble-kimi.mjs",
     "prepack": "pnpm run build && rm -rf dist docs/routes && cp -R packages/entry/dist dist && cp -R packages/ptc/dist dist/ptc && cp -R packages/routes/docs/routes docs/routes",
     "check": "pnpm -r --filter=!@pi-ptc/website run check",
+    "check:imports": "node scripts/check-artifact-imports.mjs",
     "lint": "oxlint",
-    "test": "pnpm run test:pi && pnpm run test:output && pnpm run test:kimi && pnpm run test:standalone",
+    "test": "pnpm run check:imports && pnpm run test:pi && pnpm run test:output && pnpm run test:kimi && pnpm run test:standalone",
     "test:pi": "node --test tests/pi/*.test.mjs",
     "test:output": "node --test tests/output/*.test.mjs",
     "test:kimi": "node --test tests/kimi/*.test.mjs",