@jumentix/cli-init 0.0.0

package/fixtures/invalid-no-core.yml

@@ -0,0 +1,21 @@
+openapi: 3.1.0
+info:
+  title: Invalid — no core service
+  version: 1.0.0
+x-services:
+  - id: billing
+    name: Billing
+    kind: domain
+components:
+  schemas:
+    Invoice:
+      type: object
+      x-primary-key: id
+      x-domain: Billing
+      x-entity: Invoice
+      x-service: billing
+      properties:
+        id:
+          type: string
+        total:
+          type: number

package/fixtures/invalid-no-primary-key.yml

@@ -0,0 +1,18 @@
+openapi: 3.1.0
+info:
+  title: Invalid — missing primary key
+  version: 1.0.0
+x-services:
+  - id: core
+    name: Core
+    kind: core
+components:
+  schemas:
+    Widget:
+      type: object
+      x-domain: Catalog
+      x-entity: Widget
+      x-service: core
+      properties:
+        name:
+          type: string

package/fixtures/users-oas.yml

@@ -0,0 +1,79 @@
+openapi: 3.1.0
+info:
+  title: Users Preset API
+  version: 1.0.0
+servers:
+  - url: http://localhost:3000/api/1.0.0
+    x-service-id: core
+x-services:
+  - id: core
+    name: Core
+    kind: core
+    url: http://localhost:3000/api/1.0.0
+paths:
+  /users:
+    get:
+      tags: [user]
+      operationId: listUsers
+      summary: List users
+      responses:
+        "200":
+          description: ok
+          content:
+            application/json:
+              schema:
+                type: array
+                items:
+                  $ref: "#/components/schemas/User"
+  /organizations:
+    get:
+      tags: [organization]
+      operationId: listOrganizations
+      summary: List organizations
+      responses:
+        "200":
+          description: ok
+          content:
+            application/json:
+              schema:
+                type: array
+                items:
+                  $ref: "#/components/schemas/Organization"
+components:
+  schemas:
+    User:
+      type: object
+      description: Port output object for User resource.
+      x-primary-key: id
+      x-service: core
+      x-domain: Users
+      x-entity: User
+      required: [id, username]
+      properties:
+        id:
+          type: string
+          format: uuid
+        username:
+          type: string
+        organization:
+          type: string
+          format: uuid
+          x-relation:
+            entity: Organization
+            match: id
+            display: name
+            kind: belongsTo
+    Organization:
+      type: object
+      description: Port output object for Organization resource.
+      x-primary-key: id
+      x-service: core
+      x-domain: Users
+      x-entity: Organization
+      required: [id, name]
+      properties:
+        id:
+          type: string
+          format: uuid
+        name:
+          type: string

package/package.json

@@ -0,0 +1,63 @@
+{
+  "name": "@jumentix/cli-init",
+  "version": "0.0.0",
+  "description": "Jumentix factory generator CLI (Req 037 v2)",
+  "main": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "bin": {
+    "cli-init": "./bin/jumentix.js",
+    "jumentix": "./bin/jumentix.js",
+    "jumentix-init": "./bin/jumentix-init.js",
+    "jumentix-bootstrap": "./bin/jumentix-init.js"
+  },
+  "files": [
+    "bin",
+    "dist",
+    "templates",
+    "templates.manifest.json",
+    "fixtures",
+    "README.md",
+    "LICENSE.md",
+    "README.pt-BR.md"
+  ],
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "build-templates": "bun scripts/build-templates.js",
+    "check-template-freshness": "bun scripts/check-template-freshness.js",
+    "pretest": "bun run build",
+    "test": "bun test --isolate ./test",
+    "lint": "echo \"cli-init: lint managed by root workspace\"",
+    "typecheck": "tsc -p tsconfig.json --noEmit",
+    "clean": "rm -rf dist",
+    "prepublishOnly": "bun run clean && bun run build"
+  },
+  "dependencies": {
+    "@jumentix/designer-core": "0.1.0",
+    "yaml": "^2.5.1"
+  },
+  "license": "MIT",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js",
+      "require": "./dist/index.js",
+      "default": "./dist/index.js"
+    },
+    "./package.json": "./package.json"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/web2solutions/Jumentix.git",
+    "directory": "packages/cli-init"
+  },
+  "homepage": "https://jumentix-website.vercel.app",
+  "bugs": {
+    "url": "https://github.com/web2solutions/Jumentix/issues"
+  },
+  "engines": {
+    "node": ">=20"
+  }
+}

package/templates/backend/README.md

@@ -0,0 +1,42 @@
+# @jumentix/backend-template
+
+Workspace app target for backend-template migration.
+
+Technical hub:
+
+- [Backend Template Documentation](./documentation/README.md)
+
+## Current status
+
+- Transitional workspace app with executable scripts mapped to the current root runtime.
+- Canonical backend runtime still remains in root (`src`, `spec`, `test`, `pm2`, `docker`, docs) during Wave 5.
+
+## Current executable scripts
+
+- `build` -> root `build:dev`
+- `build:dev` -> root `build:dev`
+- `test` -> root `test:unit`
+- `test:unit` -> root `test:unit`
+- `test:integration` -> root `test:integration`
+- `test:integration:smoke` -> root `ci:smoke`
+- `lint` -> root `lint`
+- `coverage:patch` -> root `coverage:patch`
+- `ci:gate` -> root `ci:gate`
+- `ci:gate:strict` -> root `ci:gate:strict`
+- `dev:rest` -> root `dev:http`
+- `dev:websocket-rest` -> root `dev:websocket`
+- `dev:grpc-rest` -> root `dev:grpc`
+- `pm2:start:*` -> root PM2 profile starters for dev/staging/production
+
+## Planned cutover (Wave 5)
+
+1. Move backend runtime files into `apps/backend-template`.
+2. Keep imports wired to `@jumentix/*` shared packages.
+3. Preserve CI gates and coverage thresholds.
+4. Keep PM2 process profiles functional after re-homing.
+
+## Wave 5 progress
+
+- Service Management app has already been re-homed to `apps/service-management`.
+- Backend-template now owns an operational script surface in workspace context, so pipelines can call app-level commands while code still resides at root.
+- Next slice is physical runtime move (`src/spec/test/pm2`) with path rewrites and PM2 parity validation.

package/templates/backend/README.pt-BR.md

@@ -0,0 +1,46 @@
+<!--
+Arquivo gerado automaticamente a partir de: apps/backend-template/README.md
+Idioma alvo: Português (Brasil)
+-->
+# @jumentix/backend-template
+
+Destino do aplicativo Workspace para migração de modelo de back-end.
+
+Centro técnico:
+
+- [Documentação do modelo de back-end](./documentation/README.md)
+
+## Status atual
+
+- Aplicativo de espaço de trabalho transitório com scripts executáveis ​​mapeados para o tempo de execução raiz atual.
+- O tempo de execução de backend canônico ainda permanece na raiz (`src`, `spec`, `test`, `pm2`, `docker`, docs) durante a Onda 5.
+
+## Scripts executáveis ​​atuais
+
+- `construir` -> raiz `construir:dev`
+- `build:dev` -> raiz `build:dev`
+- `teste` -> raiz `teste:unidade`
+- `teste:unidade` -> raiz `teste:unidade`
+- `teste:integração` -> raiz `teste:integração`
+- `teste:integração:smoke` -> raiz `ci:smoke`
+- `lint` -> raiz `lint`
+- `cobertura:patch` -> root `cobertura:patch`
+- `ci:gate` -> raiz `ci:gate`
+- `ci:gate:strict` -> raiz `ci:gate:strict`
+- `dev:rest` -> raiz `dev:http`
+- `dev:websocket-rest` -> raiz `dev:websocket`
+- `dev:grpc-rest` -> raiz `dev:grpc`
+- `pm2:start:*` -> iniciadores de perfil PM2 raiz para dev/staging/produção
+
+## Corte planejado (onda 5)
+
+1. Mova os arquivos de tempo de execução de back-end para `apps/backend-template`.
+2. Mantenha as importações conectadas aos pacotes compartilhados `@jumentix/*`.
+3. Preservar portas CI e limites de cobertura.
+4. Mantenha os perfis de processo PM2 funcionais após a realocação.
+
+## Progresso da onda 5
+
+- O aplicativo Service Management já foi realocado para `apps/service-management`.
+- O modelo de back-end agora possui uma superfície de script operacional no contexto do espaço de trabalho, para que os pipelines possam chamar comandos no nível do aplicativo enquanto o código ainda reside na raiz.
+- A próxima fatia é a movimentação física do tempo de execução (`src/spec/test/pm2`) com reescrita de caminho e validação de paridade PM2.

package/templates/backend/docker/services/Dockerfile.functions

@@ -0,0 +1,17 @@
+FROM node:22-alpine
+
+WORKDIR /app
+
+COPY package*.json ./
+RUN npm ci
+
+COPY tsconfig*.json ./
+COPY src ./src
+COPY spec ./spec
+COPY seed ./seed
+COPY ci-cd ./ci-cd
+RUN npm run build:dev
+
+EXPOSE 3000
+
+CMD ["npm", "run", "prod:serverless"]

package/templates/backend/docker/services/Dockerfile.graphql

@@ -0,0 +1,17 @@
+FROM node:22-alpine
+
+WORKDIR /app
+
+COPY package*.json ./
+RUN npm ci
+
+COPY tsconfig*.json ./
+COPY src ./src
+COPY spec ./spec
+COPY seed ./seed
+COPY ci-cd ./ci-cd
+RUN npm run build:dev
+
+EXPOSE 3000
+
+CMD ["npm", "run", "prod:fastify"]

package/templates/backend/docker/services/Dockerfile.grpc

@@ -0,0 +1,17 @@
+FROM node:22-alpine
+
+WORKDIR /app
+
+COPY package*.json ./
+RUN npm ci
+
+COPY tsconfig*.json ./
+COPY src ./src
+COPY spec ./spec
+COPY seed ./seed
+COPY ci-cd ./ci-cd
+RUN npm run build:dev
+
+EXPOSE 50051
+
+CMD ["npm", "run", "prod:fastify"]

package/templates/backend/docker/services/Dockerfile.rest

@@ -0,0 +1,17 @@
+FROM node:22-alpine
+
+WORKDIR /app
+
+COPY package*.json ./
+RUN npm ci
+
+COPY tsconfig*.json ./
+COPY src ./src
+COPY spec ./spec
+COPY seed ./seed
+COPY ci-cd ./ci-cd
+RUN npm run build:dev
+
+EXPOSE 3000
+
+CMD ["npm", "run", "prod:fastify"]

package/templates/backend/docker/services/Dockerfile.websocket

@@ -0,0 +1,17 @@
+FROM node:22-alpine
+
+WORKDIR /app
+
+COPY package*.json ./
+RUN npm ci
+
+COPY tsconfig*.json ./
+COPY src ./src
+COPY spec ./spec
+COPY seed ./seed
+COPY ci-cd ./ci-cd
+RUN npm run build:dev
+
+EXPOSE 3000
+
+CMD ["npm", "run", "prod:fastify"]

package/templates/backend/docker-compose-aurora.yml

@@ -0,0 +1,20 @@
+services:
+  aurora:
+    image: postgres:16
+    container_name: aaa-aurora-compatible
+    environment:
+      POSTGRES_USER: aaa
+      POSTGRES_PASSWORD: '${JUMENTIX_POSTGRES_PASSWORD:-${AAA_POSTGRES_PASSWORD:-change_me_postgres_password}}'
+      POSTGRES_DB: aaa
+    ports:
+      - '5433:5432'
+    healthcheck:
+      test: ['CMD-SHELL', 'pg_isready -U "$$POSTGRES_USER" -d "$$POSTGRES_DB"']
+      interval: 3s
+      timeout: 5s
+      retries: 20
+    volumes:
+      - aurora_data:/var/lib/postgresql/data
+
+volumes:
+  aurora_data:

package/templates/backend/docker-compose-cassandra.yml

@@ -0,0 +1,22 @@
+services:
+  cassandra:
+    image: cassandra:5.0
+    container_name: aaa-cassandra
+    ports:
+      - '9042:9042'
+    volumes:
+      - cassandra_data:/var/lib/cassandra
+    # `up -d` returns when the container starts; Cassandra needs roughly a
+    # minute more before it accepts CQL. Without this the suite connects into
+    # that window and fails for a reason that looks like a broken adapter
+    # (JUM-602, same shape as the RabbitMQ race in JUM-600).
+    healthcheck:
+      test: ['CMD-SHELL', 'cqlsh -e "describe keyspaces" || exit 1']
+      interval: 5s
+      timeout: 10s
+      retries: 30
+      start_period: 30s
+
+volumes:
+  cassandra_data:
+

package/templates/backend/docker-compose-dynamodb.yml

@@ -0,0 +1,18 @@
+services:
+  dynamodb:
+    image: amazon/dynamodb-local:latest
+    container_name: aaa-dynamodb-local
+    command: '-jar DynamoDBLocal.jar -sharedDb'
+    ports:
+      - '8000:8000'
+    healthcheck:
+      test: ['CMD-SHELL', 'curl -s -o /dev/null http://127.0.0.1:8000 || exit 1']
+      interval: 3s
+      timeout: 5s
+      retries: 20
+    volumes:
+      - dynamodb_data:/home/dynamodblocal/data
+
+volumes:
+  dynamodb_data:
+

package/templates/backend/docker-compose-firebase.yml

@@ -0,0 +1,34 @@
+services:
+  firebase-emulator:
+    image: andreysenov/firebase-tools:latest
+    container_name: aaa-firebase-emulator
+    # `--host` is not a flag the firebase CLI accepts, and it never was here:
+    # the container exited 1 on every run with "unknown option '--host'", so
+    # the Firebase smoke has never met an emulator (JUM-620, same class as the
+    # MSSQL password in JUM-598). The host belongs in a config file, which is
+    # written inline so nothing has to be mounted.
+    command: >
+      sh -c "printf '%s' '{\"emulators\":{\"firestore\":{\"host\":\"0.0.0.0\",\"port\":8080}}}'
+      > /home/node/firebase.json &&
+      firebase setup:emulators:firestore &&
+      firebase emulators:start --project demo-project --only firestore
+      --config /home/node/firebase.json"
+    ports:
+      - '8080:8080'
+      - '4000:4000'
+    healthcheck:
+      test:
+        - CMD-SHELL
+        - >-
+          node -e "require('http').get('http://127.0.0.1:8080',r=>process.exit(0))
+          .on('error',()=>process.exit(1))"
+      interval: 5s
+      timeout: 5s
+      retries: 30
+      start_period: 20s
+    volumes:
+      - firebase_data:/home/node/.cache
+
+volumes:
+  firebase_data:
+

package/templates/backend/docker-compose-messaging.yml

@@ -0,0 +1,35 @@
+# Healthchecks exist so `docker compose up --wait` has something to wait for
+# (JUM-600). `up -d` returns when a container has *started*, and RabbitMQ takes
+# roughly fifteen seconds after that before it accepts an AMQP connection. The
+# broker suite connected into that window and failed with "Socket closed
+# abruptly during opening handshake" — a readiness race that reads exactly like
+# a broken adapter.
+services:
+  redis:
+    image: redis:7.2-alpine
+    container_name: aaa-redis
+    restart: unless-stopped
+    ports:
+      - '6379:6379'
+    healthcheck:
+      test: ['CMD', 'redis-cli', 'ping']
+      interval: 2s
+      timeout: 3s
+      retries: 15
+
+  rabbitmq:
+    image: rabbitmq:3.13-management-alpine
+    container_name: aaa-rabbitmq
+    restart: unless-stopped
+    ports:
+      - '5672:5672'
+      - '15672:15672'
+    healthcheck:
+      # `check_port_connectivity` is what the suite actually needs: the AMQP
+      # listener accepting connections. A plain `ping` returns healthy while
+      # the listener is still binding.
+      test: ['CMD', 'rabbitmq-diagnostics', 'check_port_connectivity']
+      interval: 3s
+      timeout: 10s
+      retries: 20
+      start_period: 10s

package/templates/backend/docker-compose-mongodb.yml

@@ -0,0 +1,16 @@
+services:
+  mongodb:
+    image: mongo:7
+    container_name: aaa-mongodb
+    ports:
+      - '27027:27017'
+    volumes:
+      - mongodb_data:/data/db
+    healthcheck:
+      test: ['CMD', 'mongosh', '--quiet', '--eval', "db.adminCommand('ping')"]
+      interval: 3s
+      timeout: 5s
+      retries: 20
+
+volumes:
+  mongodb_data:

package/templates/backend/docker-compose-mssql.yml

@@ -0,0 +1,26 @@
+services:
+  mssql:
+    image: mcr.microsoft.com/mssql/server:2022-latest
+    container_name: aaa-mssql
+    environment:
+      ACCEPT_EULA: 'Y'
+      # SQL Server rejects a password that is not complex enough and the
+      # container then exits, so this default carries an uppercase letter, a
+      # digit and a symbol. With the old one the container never started, and
+      # the MSSQL smoke test had therefore never run at all.
+      MSSQL_SA_PASSWORD: '${JUMENTIX_MSSQL_SA_PASSWORD:-${AAA_MSSQL_SA_PASSWORD:-Change_me_mssql_password_1}}' 
+    ports:
+      - '1433:1433'
+    healthcheck:
+      test:
+        - CMD-SHELL
+        - '/opt/mssql-tools18/bin/sqlcmd -S localhost -U sa -P "$$MSSQL_SA_PASSWORD" -C -Q "SELECT 1" || exit 1'
+      interval: 5s
+      timeout: 10s
+      retries: 30
+      start_period: 20s
+    volumes:
+      - mssql_data:/var/opt/mssql
+
+volumes:
+  mssql_data:

package/templates/backend/docker-compose-mysql.yml

@@ -0,0 +1,24 @@
+services:
+  mysql:
+    image: mysql:8.4
+    container_name: aaa-mysql
+    environment:
+      MYSQL_ROOT_PASSWORD: '${JUMENTIX_MYSQL_ROOT_PASSWORD:-${AAA_MYSQL_ROOT_PASSWORD:-change_me_mysql_root_password}}'
+      MYSQL_DATABASE: aaa
+      MYSQL_USER: aaa
+      MYSQL_PASSWORD: '${JUMENTIX_MYSQL_PASSWORD:-${AAA_MYSQL_PASSWORD:-change_me_mysql_password}}'
+    ports:
+      - '3306:3306'
+    healthcheck:
+      test:
+        - CMD-SHELL
+        - 'mysqladmin ping -h 127.0.0.1 -u root -p"$$MYSQL_ROOT_PASSWORD" --silent'
+      interval: 3s
+      timeout: 5s
+      retries: 30
+      start_period: 20s
+    volumes:
+      - mysql_data:/var/lib/mysql
+
+volumes:
+  mysql_data:

package/templates/backend/docker-compose-oracle.yml

@@ -0,0 +1,21 @@
+services:
+  oracle:
+    image: gvenzl/oracle-free:23-slim
+    container_name: aaa-oracle
+    environment:
+      ORACLE_PASSWORD: '${JUMENTIX_ORACLE_PASSWORD:-${AAA_ORACLE_PASSWORD:-change_me_oracle_password}}'
+      APP_USER: aaa
+      APP_USER_PASSWORD: '${JUMENTIX_ORACLE_APP_USER_PASSWORD:-${AAA_ORACLE_APP_USER_PASSWORD:-change_me_oracle_app_password}}'
+    ports:
+      - '1521:1521'
+    healthcheck:
+      test: ['CMD-SHELL', 'healthcheck.sh']
+      interval: 10s
+      timeout: 10s
+      retries: 40
+      start_period: 60s
+    volumes:
+      - oracle_data:/opt/oracle/oradata
+
+volumes:
+  oracle_data:

package/templates/backend/docker-compose-postgresql.yml

@@ -0,0 +1,20 @@
+services:
+  postgresql:
+    image: postgres:16
+    container_name: aaa-postgresql
+    environment:
+      POSTGRES_USER: aaa
+      POSTGRES_PASSWORD: '${JUMENTIX_POSTGRES_PASSWORD:-${AAA_POSTGRES_PASSWORD:-change_me_postgres_password}}'
+      POSTGRES_DB: aaa
+    ports:
+      - '5432:5432'
+    healthcheck:
+      test: ['CMD-SHELL', 'pg_isready -U "$$POSTGRES_USER" -d "$$POSTGRES_DB"']
+      interval: 3s
+      timeout: 5s
+      retries: 20
+    volumes:
+      - postgresql_data:/var/lib/postgresql/data
+
+volumes:
+  postgresql_data:

package/templates/backend/docker-compose-rds.yml

@@ -0,0 +1,20 @@
+services:
+  rds:
+    image: postgres:16
+    container_name: aaa-rds-compatible
+    environment:
+      POSTGRES_USER: aaa
+      POSTGRES_PASSWORD: '${JUMENTIX_POSTGRES_PASSWORD:-${AAA_POSTGRES_PASSWORD:-change_me_postgres_password}}'
+      POSTGRES_DB: aaa
+    ports:
+      - '5434:5432'
+    healthcheck:
+      test: ['CMD-SHELL', 'pg_isready -U "$$POSTGRES_USER" -d "$$POSTGRES_DB"']
+      interval: 3s
+      timeout: 5s
+      retries: 20
+    volumes:
+      - rds_data:/var/lib/postgresql/data
+
+volumes:
+  rds_data:

package/templates/backend/docker-compose-redis.yml

@@ -0,0 +1,30 @@
+services:
+  redis-server:
+    image: redis/redis-stack-server:latest
+    restart: always
+    ports:
+      - '6379:6379'
+    command: redis-server --save 20 1 --loglevel warning --requirepass eYVX7EwVmmxKPCDmwMtyKVge8oLd2t81
+    # So `docker compose up --wait` has something to wait for (JUM-600). The
+    # password is required here: an unauthenticated PING answers NOAUTH, which
+    # is a live server refusing the check rather than a healthy one.
+    healthcheck:
+      test:
+        - CMD
+        - redis-cli
+        - '-a'
+        - eYVX7EwVmmxKPCDmwMtyKVge8oLd2t81
+        - ping
+      interval: 2s
+      timeout: 3s
+      retries: 15
+    networks:
+      - app-network
+    volumes: 
+      - redis-server:/data
+volumes:
+  redis-server:
+    driver: local
+networks:
+    app-network:
+      driver: bridge