genesis-compiler 1.2.6 → 1.2.8

package/stacks/pieces/jskit-postgresql.md

@@ -1,56 +0,0 @@
-# Stack piece: jskit-postgresql
-
-## Description
-
-JSKIT PostgreSQL runtime, live-schema CRUD generation, and persistence conventions.
-
-## Requires
-
-- `jskit`
-- `postgresql`
-
-## Conflicts
-
-- `jskit-mysql`
-
-## Environment defaults
-
-- Default `DB_CLIENT`: `pg`
-
-## Resources
-
-```json genesis-resource
-{
-  "id": "database",
-  "kind": "postgresql",
-  "environmentAlternatives": [
-    {
-      "required": ["DATABASE_URL"]
-    },
-    {
-      "required": ["DB_HOST", "DB_PORT", "DB_NAME", "DB_USER", "DB_PASSWORD"],
-      "allowEmpty": ["DB_PASSWORD"]
-    }
-  ]
-}
-```
-
-## 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
-  seams; do not add a second client, connection factory, CRUD transport, or
-  file-persistence fallback.
-- Keep environment normalization, transactions, row mapping, and database
-  error translation at one established persistence boundary.
-- Never compete with or rewrite a generator-owned baseline migration. Preserve
-  retained migration history and data semantics.

package/stacks/pieces/jskit.md

@@ -1,114 +0,0 @@
-# Stack piece: jskit
-
-## Description
-
-AI-first JSKIT runtime capabilities, tested source patterns, Vue surfaces, and
-application-owned composition.
-
-## Requires
-
-- `nodejs`
-
-## Skill
-
-- Package: `@jskit-ai/agent-docs`
-- Path: `skills/jskit`
-
-## Guidance
-
-- Before creating or modifying JSKIT Vue/Vuetify UI, load the installed
-  `jskit` Agent Skill and read its `references/material-3.md` completely.
-- Implement Material 3 through JSKIT patterns, shared screens, shell and
-  placement seams, app-owned theme configuration, and supported Vuetify APIs.
-- Use geometry-preserving Material skeletons for all user-visible loading;
-  never use a generic spinner or circular progress indicator, or let content
-  jump when data arrives. Actions use stable disabled/pending labels.
-- Keep resource-load and field errors in context, but route transient
-  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`
-- Prepare `Prepare database` with `nodejs` if `scripts/prepare-database.js` exists: `npm` `run` `db:prepare`
-
-## Environment files
-
-- 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
-
-- Default.
-- Preferred port: `3000`
-- URL path: `/`
-- Ready when: `GET` `/api/health` returns `200`
-- Runtimes: `nodejs`
-- Serve `Develop`: `npm` `run` `develop`
-
-## Deployment
-
-- Runtimes: `nodejs`
-- Ready when: `GET` `/api/health` returns `200`
-- Prepare `Install dependencies`: `npm` `install`
-- Build `Build`: `npm` `run` `build`
-- Migrate `Prepare database`: `npm` `run` `db:prepare`
-- Serve `Start`: `npm` `start`
-
-## Deslop
-
-- For every affected JSKIT screen, load the installed `jskit` Agent Skill,
-  read `references/material-3.md`, and execute its Material 3 audit.
-- Use JSKIT patterns, packages, resources, composables, screens, and placement
-  seams instead of parallel framework plumbing.
-- Treat copied pattern source as app-owned and customizable. Adapt routes,
-  placements, and infrastructure tests coherently; when replacing a foundation
-  route, update its baseline browser coverage instead of deleting it.
-- Consolidate repeated validation, pending/error state, API access, and page
-  behavior at the shared resource or established JSKIT seam.
-- Replace transient command-error alerts that shift page content with the
-  established JSKIT action feedback/snackbar seam; preserve stable in-page
-  resource-load errors, retry states, and field validation.
-- Replace generic in-content spinners with Material skeletons that reserve the
-  final layout, and verify that loading completion does not shift content.
-- Remove pass-through wrappers and abandoned scaffold code only when doing so
-  preserves routes, placements, baseline tests, and observable behavior.
-
-## Commands
-
-- Verify `application`: `npm` `run` `verify`

package/stacks/pieces/kotlin.md

@@ -1,22 +0,0 @@
-# Stack piece: kotlin
-
-## Description
-
-Kotlin package, public callable, coroutine, nullability, build, and test conventions.
-
-## Requires
-
-- Nothing.
-
-## Indexers
-
-- `kotlin`
-
-## Deslop
-
-- Preserve package visibility, nullability, coroutine ownership, public types,
-  dependency injection, and Gradle or multiplatform conventions.
-- Keep private functions near their caller. Consolidate repeated mapping,
-  validation, state, and error translation at an existing boundary.
-- Remove redundant extension functions, wrappers, sealed hierarchies, and
-  generic layers that do not make the domain or lifecycle clearer.

package/stacks/pieces/mysql.md

@@ -1,29 +0,0 @@
-# Stack piece: mysql
-
-## Description
-
-MySQL persistence and migration conventions.
-
-## Requires
-
-- 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
-  translation at one persistence boundary.
-- Use the selected integration's client and migration lifecycle instead of
-  adding parallel connection factories or schema-management code.
-- Preserve migration history and data semantics. Deslop is not permission for
-  destructive schema changes.

package/stacks/pieces/nodejs.md

@@ -1,36 +0,0 @@
-# Stack piece: nodejs
-
-## Description
-
-Node.js package, command, module, dependency, and test conventions.
-
-## Requires
-
-- Nothing.
-
-## Indexers
-
-- `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
-  exports, registered commands, and supported runtime.
-- Prefer direct modules and Node.js built-ins over wrappers that merely rename
-  an operation.
-- Keep single-consumer helpers private and close to their caller. Consolidate
-  repeated argument, path, serialization, error, and process-lifecycle logic
-  only when one clear shared operation exists.
-- Make subprocess, listener, timer, and cleanup ownership obvious. Remove dead
-  entrypoints and duplicate public exports instead of maintaining aliases.

package/stacks/pieces/php.md

@@ -1,23 +0,0 @@
-# Stack piece: php
-
-## Description
-
-PHP package, namespace, callable, dependency, and test conventions.
-
-## Requires
-
-- Nothing.
-
-## Indexers
-
-- `php`
-
-## Deslop
-
-- Preserve established namespaces, package boundaries, public interfaces,
-  framework lifecycle, dependency injection, and Composer conventions.
-- Keep private and protected helpers close to their owning class. Consolidate
-  repeated request, validation, mapping, and persistence behavior at the
-  existing application seam rather than adding generic utility layers.
-- Remove abandoned service wrappers, duplicated facades, and aliases that do
-  not protect a real compatibility boundary.

package/stacks/pieces/postgresql.md

@@ -1,30 +0,0 @@
-# Stack piece: postgresql
-
-## Description
-
-PostgreSQL persistence and migration conventions.
-
-## Requires
-
-- 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
-  translation at one persistence boundary.
-- Use the selected integration's client and migration lifecycle instead of
-  adding parallel connection factories or schema-management code.
-- Preserve migration history and data semantics. Deslop is not permission for
-  destructive schema changes.

package/stacks/pieces/python.md

@@ -1,23 +0,0 @@
-# Stack piece: python
-
-## Description
-
-Python package, module, callable, dependency, and test conventions.
-
-## Requires
-
-- Nothing.
-
-## Indexers
-
-- `python`
-
-## Deslop
-
-- Preserve established package boundaries, public imports, typing style,
-  dependency injection, and synchronous or asynchronous execution conventions.
-- Keep single-consumer helpers private and close to their caller. Consolidate
-  repeated validation, serialization, resource lifetime, and error translation
-  only at one clear existing seam.
-- Remove pass-through modules, speculative base classes, and utility wrappers
-  that merely rename standard Python or framework operations.

package/stacks/pieces/ruby.md

@@ -1,22 +0,0 @@
-# Stack piece: ruby
-
-## Description
-
-Ruby module, class, callable, dependency, lifecycle, and test conventions.
-
-## Requires
-
-- Nothing.
-
-## Indexers
-
-- `ruby`
-
-## Deslop
-
-- Preserve established modules, public entry points, dependency boundaries,
-  lifecycle callbacks, and Bundler and test conventions.
-- Keep private methods with their owning class or module. Consolidate repeated
-  coercion, validation, persistence, and error handling at an existing seam.
-- Remove forwarding objects, metaprogramming, concerns, and service layers that
-  obscure a direct operation without protecting a real shared boundary.

package/stacks/pieces/rust.md

@@ -1,22 +0,0 @@
-# Stack piece: rust
-
-## Description
-
-Rust module, public item, ownership, error, async, Cargo, and test conventions.
-
-## Requires
-
-- Nothing.
-
-## Indexers
-
-- `rust`
-
-## Deslop
-
-- Preserve module visibility, ownership and borrowing, error types, feature
-  gates, async runtime boundaries, and Cargo workspace conventions.
-- Keep private functions near their callers. Consolidate repeated conversion,
-  validation, and resource cleanup only when one ownership model remains clear.
-- Remove needless traits, boxes, clones, wrapper types, and generic layers that
-  do not protect a real semantic or compatibility boundary.

package/stacks/pieces/shell.md

@@ -1,23 +0,0 @@
-# Stack piece: shell
-
-## Description
-
-Shell script function, process, environment, portability, and test conventions.
-
-## Requires
-
-- Nothing.
-
-## Indexers
-
-- `shell`
-
-## Deslop
-
-- Preserve the script's supported shell, command-line contract, environment
-  semantics, quoting rules, exit statuses, and process ownership.
-- Keep private functions close to their callers. Consolidate repeated argument
-  parsing, validation, cleanup, and command execution only at a clear script or
-  sourced-library boundary.
-- Remove needless command wrappers, subshells, pipelines, aliases, and dynamic
-  evaluation that obscure a direct, safely quoted operation.

package/stacks/pieces/vue.md

@@ -1,28 +0,0 @@
-# Stack piece: vue
-
-## Description
-
-Vue component, reactive state, resource hydration, routing, and screen-state conventions.
-
-## Requires
-
-- `nodejs`
-
-## Guidance
-
-### Reactive state hydration
-
-- Cached query/resource data and route state may already exist when a component is created. Never rely on a default lazy `watch()` to initialize writable UI state.
-- Prefer a computed source of truth. When local writable state is necessary, initialize it synchronously and use `{ immediate: true }` for watchers that hydrate or validate from resource data, query results, props, or `route.query`.
-- 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.