genesis-stack 1.0.8 → 1.1.1

package/README.md

@@ -27,8 +27,8 @@ one-time preparation prompt. Later commands and other hosts resolve the same
 catalog without another flag, while catalog upgrades cannot silently rewrite
 the established project operations.
 
-The package contains static Markdown declarations only and has no framework
-dependencies. Genesis reads its manifest and Stack pieces; it never imports or
+The package contains static Markdown declarations and a JSON starter catalogue,
+and has no framework dependencies. Genesis reads its manifest and Stack pieces; it never imports or
 executes catalog code. Framework pieces such as JSKIT and Vue link to their
 authoritative documentation in ordinary Stack guidance.
 
@@ -37,7 +37,29 @@ any resolvable package may declare one when selecting that piece should install
 that skill. Documentation alone does not require a skill declaration or a
 catalog dependency.
 
+With Genesis 1.4 or newer, `genesis templates list` also lists the JSKIT starters
+in `genesis.templates.json`. Both variants come from
+[vibe64-dev/seed-jskit](https://github.com/vibe64-dev/seed-jskit):
+`official:jskit/public` and `official:jskit/accounts`. Apply one to an empty
+Git/Genesis bootstrap project with `genesis templates apply <id>`. Template IDs
+name complete applications; selecting a Skill never silently chooses a starter.
+
 New curated technologies should normally contribute a piece to this catalog.
 Do not add technology-specific knowledge or dependencies to
 `genesis-compiler`, and do not create one catalog package per framework unless
 the single-catalog model becomes genuinely unworkable.
+
+## Resource-estimate proposals
+
+JSKIT proposes Vibe64's optional `Resource estimates` section for its concrete
+`app` output and Workspace setup. The startup, running and preparation values
+are initial planning estimates, not measured minima, reservations or memory
+limits. Vibe64 owns the grammar and a host owns admission, learned consumption
+and owner settings; Genesis only materializes and transports the exact text.
+
+Node and Vue contribute adoption guidance without competing section proposals.
+Their estimates must not be added to JSKIT's for the same process tree. A
+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.

package/genesis.templates.json

@@ -0,0 +1,21 @@
+{
+  "schemaVersion": 1,
+  "templates": [
+    {
+      "id": "jskit/public",
+      "technology": "jskit",
+      "name": "JSKIT · Public app",
+      "description": "Fastify and Vue with an adaptive shell. No accounts or database.",
+      "repository": "https://github.com/vibe64-dev/seed-jskit.git",
+      "branch": "public"
+    },
+    {
+      "id": "jskit/accounts",
+      "technology": "jskit",
+      "name": "JSKIT · Accounts and database",
+      "description": "Adaptive shell, sign-up and login, a private home, and MySQL persistence.",
+      "repository": "https://github.com/vibe64-dev/seed-jskit.git",
+      "branch": "accounts"
+    }
+  ]
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "genesis-stack",
-  "version": "1.0.8",
+  "version": "1.1.1",
   "description": "The optional curated technology Stack catalog for Genesis projects.",
   "type": "module",
   "repository": {
@@ -13,6 +13,7 @@
   },
   "homepage": "https://github.com/mobily-enterprises/genesis-compiler/tree/genesis-next/packages/genesis-stack#readme",
   "files": [
+    "genesis.templates.json",
     "stacks"
   ],
   "scripts": {
@@ -31,6 +32,10 @@
     "ai"
   ],
   "genesis": {
+    "templates": {
+      "namespace": "official",
+      "path": "genesis.templates.json"
+    },
     "stackPieces": "stacks/pieces"
   }
 }

package/stacks/pieces/jskit.md

@@ -69,6 +69,14 @@ https://mobily-enterprises.github.io/jskit-ai/
   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.
+- Review the Vibe64-owned Resource estimates proposal against the application's
+  actual Outputs target ids and Workspace setup. Its initial Node development
+  estimates are planning hints, not measured requirements, hard memory limits,
+  or a promise of available capacity. Keep startup/build and ready runtime
+  separate, and give an isolated test target its own estimates. Do not add a
+  shared database's full footprint to every application target. Hosts own
+  measured history, admission and limits outside project source; they do not
+  rewrite this section as they learn. Preserve an existing project section.
 
 ## Workspace setup
 
@@ -105,6 +113,20 @@ https://mobily-enterprises.github.io/jskit-ai/
 - URL path: `/`
 - Ready when: `GET` `/api/health` returns `200`
 
+## Resource estimates
+
+### Output `app`
+
+- Startup typical MiB: `1024`
+- Startup high MiB: `1536`
+- Running typical MiB: `768`
+- Running high MiB: `1536`
+
+### Workspace setup
+
+- Typical MiB: `1024`
+- High MiB: `1536`
+
 ## Deployment
 
 - Runtimes: `nodejs`

package/stacks/pieces/nodejs.md

@@ -22,6 +22,17 @@ Node.js package, command, module, dependency, and test conventions.
   `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 Outputs.
+- For Vibe64's optional Resource estimates, distinguish dependency preparation,
+  startup/build, and the ready runtime of each real declared output. For an
+  unmeasured Node web development target, initial planning candidates are
+  startup 1024 MiB typical / 1536 MiB high and running 768 MiB typical / 1536 MiB
+  high; preparation can initially use 1024 MiB typical / 1536 MiB high. These
+  are not benchmarks, guaranteed minima, or hard limits, and are not defaults
+  for every small Node command. Prefer the selected framework's concrete
+  proposal or measured application evidence, preserving an existing project
+  declaration. Never infer a command or add Node's estimate to a framework
+  estimate for the same process tree. Host measurements and owner limits stay
+  in runtime-local state, not in this source contract.
 
 ## Deslop
 

package/stacks/pieces/vue.md

@@ -35,3 +35,7 @@ conventions. Authoritative framework documentation: https://vuejs.org/
 - 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.
+- Attribute a Vue build/dev server's memory to its actual Node output target.
+  Vue selection does not create a second service or another memory charge.
+  Review any Vibe64 Resource estimates in the project's existing complete
+  section; this piece does not propose a competing section alongside a framework.