@stardeck-customer-apps/compose 0.14.1 → 0.16.0

package/SKILL.md

@@ -38,6 +38,7 @@ Compose turns that declaration into the code Next.js actually builds:
 ```bash
 npx stardeck-compose [--enabled=a,b,c] [--prune] [--cwd=<repo root>]
 npx stardeck-compose --check-boundaries [--cwd=<repo root>]
+npx stardeck-compose --check-ownership [--cwd=<repo root>]
 ```
 
 Run it from the repo root (the directory holding `apps/web`). The Blueprint
@@ -110,6 +111,21 @@ a silent fallback. It holds deployment facts: gitignore it (`apps/web/.gitignore
   listing the offending files. Library Modules are always composed and never
   count. Run it in Blueprint CI so such an import is caught before a customer
   prunes.
+- `--check-ownership` — lint and pre-push; composes nothing. Exits 1 when the
+  checkout changed a Stardeck-owned file (a file in a Stardeck Module's folder
+  or in `apps/web/src/lib/modules/`, except `app-extensions.ts`). It compares
+  with Stardeck's newest version in the repo's history and counts staged,
+  unstaged, committed and new files, so it catches an edit before it is pushed.
+  `stardeck.ownership.json` at the repo root, written by Stardeck from the
+  Modules tab, says which Modules the app has taken over: the screens of a
+  customized Module (`components/`, `routes/`) and the whole folder of a Module
+  whose updates were stopped are the app's. Without that file every Stardeck
+  Module counts as Stardeck's. A failure lists the files and what to do
+  instead. Never edit `stardeck.ownership.json`: the editing tools refuse it,
+  and the pull-request check flags it. The check skips a repo with no Stardeck
+  version in its history (or one nested in a larger repo), and warns instead
+  of checking in a shallow clone (`git fetch --unshallow` fixes that). Needs
+  compose 0.15.0 or later.
 
 ## Rules