Repository navigation
ADR 0051
Status: accepted · Built: done · Date: 2026-11-22 · Supersedes: 0019, 0034, 0035, 0036, 0042
Partly supersedes 0019 (the kit as an npm package of the project), 0034 (apps made before it keep their own database), 0035 (the one-time move), 0036 (the kit kept in this repository while deprecated) and 0042 (kit-v tags and kit release branches). Built: packages/kit, its CI job and kit-v tags, check-versions --kit, the agent's POST /apps/:name/move and GET /apps/:name/database, the dashboard's Own database form and the CLI's own-database branch are gone. The CI check keeps its name, kit and CLI on Node 24, because the branch ruleset requires it by name; so does the KIT_TEST_POSTGRES_URL variable. Deprecating @spotcraft/kit on npm is left to the owner.
ADR 0036 moved provisioning into the CLI package and the app helpers into
@kodentuzo/spotkit. It kept @spotcraft/kit in this repository, deprecated, and the agent kept
apps made before ADR 0034 in their own database until a one-time move
(ADR 0035) put them in a schema and their guests in the pool.
Nothing uses either any more. The only instance is new, every app on it has a schema, and no app imports the kit. Keeping them costs code in the agent, the dashboard, the CLI and CI, and a second release process.
This record replaces these parts of older ones:
- ADR 0019: the kit as one of the project's npm packages, and its exports as public API.
- ADR 0034: "Apps made before this record keep their own database until they move into a schema."
- ADR 0035: the one-time move of an app's guests and tables.
- ADR 0036: the kit kept in this repository while deprecated.
-
ADR 0042:
kit-v*tags andchore/release-kit-A.B.Cbranches.
-
The kit is gone from this repository.
packages/kit, its guides, its CI job,kit-v*tags andcheck-versions --kitare removed. Spotcraft has one version and one release again. Apps use@kodentuzo/spotkit. -
@spotcraft/kitstays on npm, deprecated, pointing to spotkit. Nothing is unpublished. -
Every app lives in a schema of the
appsdatabase. The agent and the CLI no longer know an app's own database: no move (POST /apps/:name/move), no layout endpoint (GET /apps/:name/database), no own-database dumps, and purging drops the schema and the role only. - An instance with such an app moves it with 0.14 first, from the dashboard's Settings → Own database, and upgrades after.
- Less code in every part: the agent's move, the dashboard's form, the CLI's second layout, a CI job and a release process.
- An instance that still has an app in its own database can't upgrade past 0.14 until it moves that app. The changelog says so.
- The CI check named
kit and CLI on Node 24keeps its name, because the branch ruleset requires it by name; renaming it needs the ruleset changed too. The tests'KIT_TEST_POSTGRES_URLkeeps its name as well. - The tag ruleset may still name
kit-v*; it protects nothing now and can go when the ruleset is next edited.
Published from docs/. Edit the files there; changes here are overwritten.