Skip to content

0.24.0

Latest

Choose a tag to compare

@cliftonc cliftonc released this 30 Oct 07:23
0.24.0
4a379df

A renamed copy now carries none of the kit's own machinery: its maintainer scripts, hooks, project files and kit-only tests are removed at the rename, and the example plugin's agent tool and welcome note follow its flag.

  • kitOnly now also lists scripts/release.mjs, the two maintainer nudges and lib/nudge-lib, scripts/default-plugins.mjs, scripts/install.sh, CONTRIBUTING.md and CODE_OF_CONDUCT.md; the rename deletes them (CONCEPTS §13).
  • The rename also drops the kit:release script and the two nudge hooks from .claude/settings.json, writes the app its own SECURITY.md, and removes retiredSurfaces from .rocketflare.json.
  • Kit-only tests moved out of tests/config/: kit-check, kit-check-parsers, launch-kit-manifest (now kit-only/launch-kit-schema), gate-string, the release helpers' blocks of upgrade-lib/manifest-lib, and the manifest's "classifies every tracked file" check — an app's own new paths no longer fail its gate.
  • tests/config/kit-manifest.test.ts now also fails a copy whose package.json scripts or Claude Code hooks call a kit-only file.
  • ToolCtx (the plugin tool context) gains features(); example-feature's list_example_notes tool is offered only while the organisation has the flag, and its onTenantCreated note only when the deployment ships it.
  • The example agents are removable without test edits: core tests run on two fixture agents registered through mocked plugin barrels (apps/web/tests/helpers/fixture-agents.ts), tests/api-setup.ts imports the DB client lazily so a test's vi.mock of a barrel takes effect, and each example surface's paths now lists its own output view, eval suite, dataset, baseline and UI tests (triage-research requires research-topic).
  • apps/web/src/api/services/ai/kit.ts is now agent-loop.ts (same exports; tests/api/ai-kit.test.ts → agent-loop.test.ts), and source comments no longer carry design-decision numbers, "Ported from…" provenance or phase history — an app reads the rule, not the kit's past.
  • The docs say which rules are the kit repository's alone: porting notes and pnpm kit:release (CLAUDE.md, code-quality rules, SETUP §3.7, DEPLOY's version rule). An app releases by bumping its root version and tagging.
  • Learned from apps built on the kit: docs/upgrades/unreleased.md is kitOnly too (copies kept the kit's pending notes and went on writing their own); the rename now reports the licence and a missing kit.commit as careful rows; package descriptions no longer call the app a kit; and upgrade-lib.test.ts's ancestry case builds its own two-commit repository instead of reading HEAD~1, which a one-commit copy or a shallow CI checkout lacks.

See the porting note — it lists what an existing copy deletes by hand (kit:upgrade never deletes files).

Full changes: 0.23.0...0.24.0