genesis-stack 1.1.4 → 1.1.6

package/README.md

@@ -68,3 +68,19 @@ project's complete reviewed section wins; a catalog upgrade never rewrites it.
 Projects with different output ids or commands must review the proposal during
 preparation. A project can omit estimates and use its host's generic starting
 policy. Neither the catalog nor the project stores host observations or limits.
+
+## Connected package default
+
+Node proposes Vibe64's opaque `Connected development` section containing only
+`- Default package type: \`npm\``. Vibe64 can inspect this default without treating
+it as a prepared development recipe. The project must add its real source-map,
+preparation and verification declarations before connected development can run;
+no repositories or commands are inferred from selecting Node. A project-owned
+section wins unchanged, including an explicit different default.
+
+For an existing current-format project whose selected Node catalog gains this
+proposal, Genesis reports `STACK_PROJECT_CONTRACTS_INCOMPLETE` if the project
+section is missing. Explicitly reconcile the already-selected Stack with
+`genesis stack add nodejs`, then review the materialized contract. Older project
+formats use the normal `genesis migrate` workflow. Catalog updates never install
+a hidden runtime default or rewrite an existing project section.

package/genesis.templates.json

@@ -4,16 +4,24 @@
     {
       "id": "jskit/public",
       "technology": "jskit",
-      "name": "JSKIT · Public app",
-      "description": "Fastify and Vue with an adaptive shell. No accounts or database.",
+      "name": "JSKIT · Basic app",
+      "description": "Adaptive shell and ready unit, client and browser tests. No accounts or database.",
       "repository": "https://github.com/vibe64-dev/seed-jskit.git",
       "branch": "public"
     },
+    {
+      "id": "jskit/database",
+      "technology": "jskit",
+      "name": "JSKIT · Database app",
+      "description": "Adaptive shell, MySQL migrations and isolated database/browser tests. No accounts.",
+      "repository": "https://github.com/vibe64-dev/seed-jskit.git",
+      "branch": "database"
+    },
     {
       "id": "jskit/accounts",
       "technology": "jskit",
-      "name": "JSKIT · Accounts and database",
-      "description": "Adaptive shell, sign-up and login, a private home, and MySQL persistence.",
+      "name": "JSKIT · Accounts app",
+      "description": "Sign-up, login, a private home, MySQL persistence and isolated database/browser tests.",
       "repository": "https://github.com/vibe64-dev/seed-jskit.git",
       "branch": "accounts"
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "genesis-stack",
-  "version": "1.1.4",
+  "version": "1.1.6",
   "description": "The optional curated technology Stack catalog for Genesis projects.",
   "type": "module",
   "repository": {

package/stacks/pieces/jskit.md

@@ -111,6 +111,18 @@ https://mobily-enterprises.github.io/jskit-ai/
 
 - Dotenv `.env`
 
+## UI discovery
+
+### Discovery `vue-pages`: Application pages
+
+- Adapter: `jskit`
+- Surface: `app`
+- Mode: `filesystem`
+- Page root: `src/pages`
+- Registration: `vite.config.mjs`
+- Component root: `src/components`
+- Component root: `packages`
+
 ## City regions
 
 - Ignore `**/test/**`

package/stacks/pieces/nodejs.md

@@ -31,9 +31,28 @@ Node.js package, command, module, dependency, and test conventions.
 
 ## Adoption
 
+- The proposed `## Connected development` section declares Vibe64's default
+  connected package type, `npm`. It does not declare repositories or executable
+  preparation. When connected development is needed, preserve that default in
+  the complete project-owned section and declare the application's real source
+  map, preparation and verification commands. An explicit `custom` connection
+  uses its project-defined script instead of npm treatment. Do not invent a
+  working recipe from the component name.
 - Identify the package manager from the lockfile and preserve the existing
   module system, supported Node.js version, package entrypoints, and executable
   commands.
+- For optional architecture package boundaries, propose a project-owned
+  `## Package discovery` section with `### Discovery \`npm\`: Direct dependencies`,
+  `- Adapter: \`npm\``, `- Manifest: \`package.json\`` and
+  `- Package root: \`node_modules\``. These are npm's usual project defaults,
+  not a scan of every manifest or dependency tree. Declare additional manifests
+  explicitly for independent packages, relative to the project; the package root
+  is relative to each manifest's directory. Preserve an existing declaration.
+  Only direct declarations and declared public entry files are inspected.
+  Project-owned `file:` dependencies remain inspectable source; installed
+  external packages are opaque. Linked or unavailable entries, runtime exports,
+  re-exports and unsupported parsers retain explicit partial coverage. Do not
+  install dependencies just to open an architecture view.
 - 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.
@@ -51,6 +70,10 @@ Node.js package, command, module, dependency, and test conventions.
   estimate for the same process tree. Host measurements and owner limits stay
   in runtime-local state, not in this source contract.
 
+## Connected development
+
+- Default package type: `npm`
+
 ## Deslop
 
 - Preserve the package's existing module system, package manager, public

package/stacks/pieces/sqlite.md

@@ -10,6 +10,13 @@ SQLite file-backed persistence, migrations, and backup conventions.
 
 ## Guidance
 
+- For application integrations and payments, `integrations.json` remains the
+  configuration authority; SQLite stores app-owned connections, provider mappings,
+  event receipts, subscriptions and credit records only when the app needs them.
+  Keep provider secrets under the application's secret-storage policy.
+- Provider calls, signature verification and authorization belong to the app's
+  runtime. Database configuration alone does not implement a provider, and the
+  editor does not acquire ownership of application billing records.
 - Use the application's existing SQLite driver and migration owner. Declare a
   persistent database filename through the `database` resource semantic and
   the environment name the application actually reads. A driver selector such