genesis-compiler 1.2.2 → 1.2.4

package/stacks/pieces/jskit-mysql.md

@@ -35,6 +35,16 @@ JSKIT MySQL runtime, live-schema CRUD generation, and persistence conventions.
 }
 ```
 
+## Adoption
+
+- Confirm that the application's effective MySQL environment alternatives and
+  driver match this Resource declaration; add a project Resource contract when
+  the existing application legitimately differs.
+- Verify from source that the database preparation path discovers every
+  package-owned migration, preserves the existing ledger, orders cross-package
+  constraints safely, and invokes an app-owned idempotent seed. Do not execute
+  it during adoption.
+
 ## Deslop
 
 - Use the installed JSKIT database runtime and generated resource/repository

package/stacks/pieces/jskit-postgresql.md

@@ -35,6 +35,16 @@ JSKIT PostgreSQL runtime, live-schema CRUD generation, and persistence conventio
 }
 ```
 
+## Adoption
+
+- Confirm that the application's effective PostgreSQL environment alternatives
+  and driver match this Resource declaration; add a project Resource contract
+  when the existing application legitimately differs.
+- Verify from source that the database preparation path discovers every
+  package-owned migration, preserves the existing ledger, orders cross-package
+  constraints safely, and invokes an app-owned idempotent seed. Do not execute
+  it during adoption.
+
 ## Deslop
 
 - Use the installed JSKIT database runtime and generated resource/repository

package/stacks/pieces/jskit.md

@@ -27,6 +27,29 @@ application-owned composition.
   user-command failures through JSKIT's shared non-layout-shifting action
   feedback/snackbar path.
 
+## Adoption
+
+- Read the installed JSKIT skill's existing-application migration guidance
+  completely before editing Stack or assessing readiness.
+- Inventory the coordinated `@jskit-ai/*` package graph, application-owned
+  composition, package-owned migrations, explicit repositories/features/named
+  actions, and current client resources without running a broad package update.
+- Compare the real package scripts with JSKIT's current Workspace setup,
+  Launch, verification, and Deployment declarations. Older source needs complete
+  project-owned overrides until a separately approved port supplies the current
+  commands.
+- Inspect existing setup and database preparation for both migration discovery
+  and an app-owned idempotent seed. Never infer `db:prepare` from the selected
+  component when the script or preparation file does not exist.
+- When authenticated Preview exists, preserve the app-owned Preview identity
+  command, selectors, protocol, environment names, runtime, and timeout in the
+  project's Launch declaration. A host-saved identity name/value is not a
+  substitute for this application contract.
+- Treat generator descriptors, receipts, sync commands, legacy service
+  locators, and retired tool manifests as migration evidence only. Translate
+  live facts into current source/Stack and report remaining port work; do not
+  add compatibility readers or claim adoption performed the port.
+
 ## Workspace setup
 
 - Prepare `Install dependencies` with `nodejs` when `package.json` exists: `npm` `install`
@@ -36,6 +59,17 @@ application-owned composition.
 
 - Dotenv `.env`
 
+## City regions
+
+- Ignore `**/test/**`
+- Ignore `**/tests/**`
+- Ignore `**/__tests__/**`
+- Ignore `**/*.test.*`
+- Ignore `**/*.spec.*`
+- Match `packages` as `Packages`: `packages/**`
+- Match `source` as `Source`: `src/**`
+- Fallback `everything-else` as `Everything else`
+
 ## Launch
 
 ### Target `app`: Run app

package/stacks/pieces/mysql.md

@@ -8,6 +8,17 @@ MySQL persistence and migration conventions.
 
 - Nothing.
 
+## Adoption
+
+- Identify the application's accepted connection alternatives, client/driver,
+  migration directories and ledger, transaction ownership, and the exact
+  preparation command without connecting to or mutating a database.
+- Distinguish fresh-schema creation from existing-database upgrade. Record how
+  package/application migrations are ordered and how a retained ledger prevents
+  historical migrations from rerunning.
+- Identify app-owned seed behavior and whether it is deterministic and
+  idempotent. A migration-only command is not a complete seed contract.
+
 ## Deslop
 
 - Keep connection configuration, transaction ownership, and database error

package/stacks/pieces/nodejs.md

@@ -12,6 +12,17 @@ Node.js package, command, module, dependency, and test conventions.
 
 - `javascript`
 
+## Adoption
+
+- Identify the package manager from the lockfile and preserve the existing
+  module system, supported Node.js version, package entrypoints, and executable
+  commands.
+- Record the source's real dependency installation, build, verification,
+  development, and production commands. Do not assume `npm run develop`,
+  `npm test`, or `npm start` exists merely because a current foundation uses it.
+- Identify every long-running process, its workdir, host/port handling,
+  readiness signal, and shutdown ownership before declaring Launch.
+
 ## Deslop
 
 - Preserve the package's existing module system, package manager, public

package/stacks/pieces/postgresql.md

@@ -8,6 +8,18 @@ PostgreSQL persistence and migration conventions.
 
 - Nothing.
 
+## Adoption
+
+- Identify the application's accepted connection alternatives, client/driver,
+  migration directories and ledger, transaction ownership, search-path/schema
+  assumptions, and the exact preparation command without connecting to or
+  mutating a database.
+- Distinguish fresh-schema creation from existing-database upgrade. Record how
+  package/application migrations are ordered and how a retained ledger prevents
+  historical migrations from rerunning.
+- Identify app-owned seed behavior and whether it is deterministic and
+  idempotent. A migration-only command is not a complete seed contract.
+
 ## Deslop
 
 - Keep connection configuration, transaction ownership, and database error

package/stacks/pieces/vue.md

@@ -17,3 +17,12 @@ Vue component, reactive state, resource hydration, routing, and screen-state con
 - Keep genuinely change-only watchers non-immediate.
 - Persist user-selected filters and screen context in the URL when they must survive navigation.
 - Test stateful screens by navigating away and back with a warm query cache, including browser back/forward navigation.
+
+## Adoption
+
+- Identify the real client entrypoint, router, build tool, development command,
+  production build output, API proxy/origin contract, and environment-file
+  conventions.
+- Record existing unit and browser-test commands plus their base-URL, storage
+  state, and managed-browser assumptions. Do not install a browser or replace a
+  working host-managed browser contract during adoption.