@semacode/cli 3.11.0 → 3.12.0

package/dist/agentEntryPoints.js

@@ -567,18 +567,19 @@ module app.example {
 
 ## Canonical \`use\` and \`impl\` Origins
 
-Use these origins before inventing a new one:
+Use these origins before inventing a new one (aliases after \`ou\`):
 
 - \`ts\` ou \`typescript\`
 - \`js\` ou \`javascript\`
 - \`py\` ou \`python\`
 - \`dart\`
 - \`lua\`
-- \`cs\` ou \`dotnet\`
+- \`cs\`, \`csharp\` ou \`dotnet\`
 - \`java\`
-- \`go\`
-- \`rust\`
-- \`cpp\`
+- \`go\` ou \`golang\`
+- \`rust\` ou \`rs\`
+- \`cpp\`, \`cxx\`, \`cc\` ou \`c++\`
+- \`php\`
 
 Examples:
 
@@ -590,11 +591,19 @@ impl {
 }
 \`\`\`
 
+\`\`\`sema
+use php app.legacy.pedidos
+
+impl {
+  php: pedidos.criarPedido
+}
+\`\`\`
+
 \`sema compilar --alvo javascript\` defines a generation target. \`impl { js: ... }\` defines the live-code origin linked to the contract. They are different layers and both are valid.
 
 ## Layered \`impl\` Roles
 
-Layered code (route + service + persistence in the same language) can declare one \`impl\` per role. Append a supported role to the origin: \`rota\`, \`servico\`, \`persistencia\` or \`repositorio\`.
+Layered code (route + service + persistence in the same language) can declare one \`impl\` per role. Append a supported role to any origin: \`rota\`, \`servico\`, \`persistencia\` or \`repositorio\`.
 
 \`\`\`sema
 impl {
@@ -604,6 +613,16 @@ impl {
 }
 \`\`\`
 
+The role suffix combines with every origin, not only TypeScript:
+
+\`\`\`sema
+impl {
+  php_rota: pedidos.rota.criarPedido
+  php_servico: pedidos.servico.criarPedido
+  php_persistencia: pedidos.repositorio.criar
+}
+\`\`\`
+
 Each origin-plus-role pair must appear at most once; the bare origin (for example \`ts\`) stays valid for single-layer tasks, and drift resolves every role independently.
 
 ## Small Canonical Lists
@@ -709,6 +728,7 @@ Use this file when Codex does not know which command to run. A Sema command is a
 
 \`\`\`bash
 sema --version
+sema sessao "<intencao>" --json
 sema resumo --drift none
 sema docs-impacto --intencao "<acao>" --json
 \`\`\`
@@ -717,6 +737,10 @@ If \`sema\` is absent from \`PATH\`, use \`$HOME/.sema/bin/sema\` on macOS/Linux
 
 Then read every required doc returned by \`docs-impacto\`.
 
+## Session Opening
+
+- \`sema sessao "<intencao>" --json\`: opens a governed session with one compact envelope. It returns workspace identity (\`baseProjeto\`, \`hashContratos\`, CLI version), artifact freshness (\`frescor.fresco\` plus the exact recovery command when stale), the project's contract count and modules, the declared intent's categories with blocking and recommended docs, the four gate commands for the full loop, and concrete next steps. Treat \`frescor.fresco:false\` as a pre-action blocker: run the suggested \`sema sync-codex --json\` before editing, because gates protect the consistency that stale artifacts break.
+
 ## Public JSON output
 
 \`sema --version\` stays plain exact SemVer text. With \`--json\`, help and command-control failures use exactly one six-field \`sema.cli.control/v1\` document on stdout with empty stderr. Every syntactically valid command uses exactly one eight-field \`sema.cli.result/v1\` document containing only \`schemaVersion\`, \`ok\`, \`kind\`, \`command\`, \`code\`, \`message\`, \`exitCode\`, and \`payload\`. The command-specific result is nested under \`payload\`, never \`data\`; envelope \`ok\` does not replace domain fields inside that payload. Valid structured domain failures use \`DOMAIN_ERROR\`, while uncaught runtime exceptions remain redacted \`FATAL_ERROR\` control failures.
@@ -728,7 +752,7 @@ Then read every required doc returned by \`docs-impacto\`.
 
 ## Contract and Discovery
 
-- \`sema iniciar --template <template> [--force]\`: creates a new Sema project and preserves existing files by default; \`--force\` is the only explicit overwrite path.
+- \`sema iniciar --template <base|nestjs|fastapi|nextjs-api|nextjs-consumer|react-vite-consumer|angular-consumer|flutter-consumer|node-firebase-worker|aspnet-api|springboot-api|go-http-api|rust-axum-api|cpp-service-bridge> [--force]\`: creates a new Sema project and preserves existing files by default; \`--force\` is the only explicit overwrite path.
 - \`sema validar <arquivo-ou-pasta> --json\`: validates \`.sema\` contracts.
 - \`sema diagnosticos <arquivo.sema> --json\`: details errors and warnings.
 - \`sema formatar <arquivo-ou-pasta>\`: formats contracts.
@@ -764,9 +788,9 @@ A cache hit is acceleration, not final evidence; closure still requires fresh dr
 
 ## Sema Code
 
-- \`sema compilar <arquivo-ou-pasta> --alvo <typescript|python|php|dart|lua|javascript|html|css|dotnet|cpp> --saida <diretorio>\`: generates starter/support artifacts from the contract.
+- \`sema compilar <arquivo-ou-pasta> --alvo <typescript|python|php|dart|lua|javascript|html|css|dotnet|cpp> --saida <diretorio> [--estrutura <flat|modulos|backend>] [--framework <base|nestjs|fastapi>]\`: generates starter/support artifacts from the contract.
 - \`sema testar <arquivo.sema> --alvo <alvo> --saida <diretorio-temporario>\`: generates and runs local tests when the target supports it.
-- \`sema importar <fonte> <diretorio> --saida <diretorio> --json\`: imports a legacy project into initial contracts.
+- \`sema importar <nestjs|express|fastify|koa|fastapi|flask|nextjs|nextjs-consumer|react-vite-consumer|angular-consumer|flutter-consumer|sveltekit-consumer|nuxt-consumer|firebase|typescript|python|dart|dotnet|java|go|rust|cpp|php> <diretorio> --saida <diretorio> --json\`: imports a legacy project into initial contracts; only these sources have a real importer.
 - \`sema renomear-semantico <arquivo-ou-pasta> --de <nome> --para <nome> --json\`: helps rename symbols semantically.
 
 Rule for \`--saida\`: the folder passed to \`sema compilar --saida\` is generated output. It is not the final delivery by itself. The final delivery is the target files/links declared by the contract. If the contract asks for \`index.html\`, \`css/styles.css\`, and \`js/app.js\`, creating only \`saida/expense_control.ts\` does not complete the task.
@@ -777,7 +801,10 @@ Ready UI rule: if the task generates an app, site, dashboard, form, or static HT
 
 ## Canonical Syntax Lists
 
-- Origins for \`use\` and \`impl\`: \`ts/typescript\`, \`js/javascript\`, \`py/python\`, \`dart\`, \`lua\`, \`cs/dotnet\`, \`java\`, \`go\`, \`rust\`, \`cpp\`.
+- Origins for \`use\` and \`impl\` (11, aliases after \`/\`): \`ts/typescript\`, \`js/javascript\`, \`py/python\`, \`dart\`, \`lua\`, \`cs/csharp/dotnet\`, \`java\`, \`go/golang\`, \`rust/rs\`, \`cpp/cxx/cc/c++\`, \`php\`.
+- Layered \`impl\` roles: append \`_rota\`, \`_servico\`, \`_persistencia\` or \`_repositorio\` to any origin (\`ts_rota\`, \`php_servico\`, \`cs_persistencia\`, \`py_repositorio\`).
+- Generation targets (10): \`typescript\`, \`javascript/js\`, \`python\`, \`php\`, \`dart\`, \`lua\`, \`html\`, \`css\`, \`dotnet/cs/csharp\`, \`cpp/c++/cxx/cc\`.
+- \`sema iniciar --template\` (14): \`base\`, \`nestjs\`, \`fastapi\`, \`nextjs-api\`, \`nextjs-consumer\`, \`react-vite-consumer\`, \`angular-consumer\`, \`flutter-consumer\`, \`node-firebase-worker\`, \`aspnet-api\`, \`springboot-api\`, \`go-http-api\`, \`rust-axum-api\`, \`cpp-service-bridge\`.
 - Frequent \`effects\` categories: \`persistencia\`, \`consulta\`, \`evento\`, \`auditoria\`, \`db.write\`, \`queue.publish\`, \`fs.write\`, \`network.egress\`, \`secret.read\`, \`shell.exec\`.
 - Accepted \`audit.motivo\` values: \`obrigatorio\`, \`opcional\`, \`dispensado\`.
 

package/dist/cliGrammar.js

@@ -23,8 +23,8 @@ const TEMPLATES_INIT = new Set([
 ]);
 const FONTES_IMPORTACAO = new Set([
     "nestjs", "express", "fastify", "koa", "fastapi", "flask", "nextjs", "nextjs-consumer", "react-vite-consumer",
-    "angular-consumer", "flutter-consumer", "sveltekit-consumer", "nuxt-consumer", "firebase", "typescript", "javascript",
-    "python", "dart", "lua", "dotnet", "java", "go", "rust", "cpp", "php",
+    "angular-consumer", "flutter-consumer", "sveltekit-consumer", "nuxt-consumer", "firebase", "typescript",
+    "python", "dart", "dotnet", "java", "go", "rust", "cpp", "php",
 ]);
 const ALVOS_GERACAO = new Set([
     "typescript", "python", "dart", "lua", "javascript", "js", "html", "css", "php",

package/dist/cliHelpTexto.js

@@ -25,7 +25,7 @@ export function criarAjudaRaiz(versao) {
         "",
         renderizarSecaoAscii("Fluxos rápidos", [
             "[1] Projeto novo / produção inicial",
-            "sema iniciar --template <base|nestjs|fastapi|nextjs-api|nextjs-consumer|react-vite-consumer|angular-consumer|flutter-consumer> [--force] [--com-exemplos]",
+            "sema iniciar --template <base|nestjs|fastapi|nextjs-api|nextjs-consumer|react-vite-consumer|angular-consumer|flutter-consumer|node-firebase-worker|aspnet-api|springboot-api|go-http-api|rust-axum-api|cpp-service-bridge> [--force] [--com-exemplos]",
             "Arquivos existentes são preservados; use --force somente para sobrescrita explícita. O starter de exemplos vem por padrão; --com-exemplos instala o pacote completo.",
             "sema validar contratos/<modulo>.sema --json",
             "sema compilar <arquivo-ou-pasta> --alvo <typescript|python|php|dart|lua|javascript|html|css|dotnet|cpp> --saida <diretorio>",

package/docs/commands.md

@@ -7,6 +7,7 @@ Use this file when Codex does not know which command to run. A Sema command is a
 
 ```bash
 sema --version
+sema sessao "<intencao>" --json
 sema resumo --drift none
 sema docs-impacto --intencao "<acao>" --json
 ```
@@ -15,6 +16,10 @@ If `sema` is absent from `PATH`, use `$HOME/.sema/bin/sema` on macOS/Linux. On W
 
 Then read every required doc returned by `docs-impacto`.
 
+## Session Opening
+
+- `sema sessao "<intencao>" --json`: opens a governed session with one compact envelope. It returns workspace identity (`baseProjeto`, `hashContratos`, CLI version), artifact freshness (`frescor.fresco` plus the exact recovery command when stale), the project's contract count and modules, the declared intent's categories with blocking and recommended docs, the four gate commands for the full loop, and concrete next steps. Treat `frescor.fresco:false` as a pre-action blocker: run the suggested `sema sync-codex --json` before editing, because gates protect the consistency that stale artifacts break.
+
 ## Public JSON output
 
 `sema --version` stays plain exact SemVer text. With `--json`, help and command-control failures use exactly one six-field `sema.cli.control/v1` document on stdout with empty stderr. Every syntactically valid command uses exactly one eight-field `sema.cli.result/v1` document containing only `schemaVersion`, `ok`, `kind`, `command`, `code`, `message`, `exitCode`, and `payload`. The command-specific result is nested under `payload`, never `data`; envelope `ok` does not replace domain fields inside that payload. Valid structured domain failures use `DOMAIN_ERROR`, while uncaught runtime exceptions remain redacted `FATAL_ERROR` control failures.
@@ -26,7 +31,7 @@ Then read every required doc returned by `docs-impacto`.
 
 ## Contract and Discovery
 
-- `sema iniciar --template <template> [--force]`: creates a new Sema project and preserves existing files by default; `--force` is the only explicit overwrite path.
+- `sema iniciar --template <base|nestjs|fastapi|nextjs-api|nextjs-consumer|react-vite-consumer|angular-consumer|flutter-consumer|node-firebase-worker|aspnet-api|springboot-api|go-http-api|rust-axum-api|cpp-service-bridge> [--force]`: creates a new Sema project and preserves existing files by default; `--force` is the only explicit overwrite path.
 - `sema validar <arquivo-ou-pasta> --json`: validates `.sema` contracts.
 - `sema diagnosticos <arquivo.sema> --json`: details errors and warnings.
 - `sema formatar <arquivo-ou-pasta>`: formats contracts.
@@ -62,9 +67,9 @@ A cache hit is acceleration, not final evidence; closure still requires fresh dr
 
 ## Sema Code
 
-- `sema compilar <arquivo-ou-pasta> --alvo <typescript|python|php|dart|lua|javascript|html|css|dotnet|cpp> --saida <diretorio>`: generates starter/support artifacts from the contract.
+- `sema compilar <arquivo-ou-pasta> --alvo <typescript|python|php|dart|lua|javascript|html|css|dotnet|cpp> --saida <diretorio> [--estrutura <flat|modulos|backend>] [--framework <base|nestjs|fastapi>]`: generates starter/support artifacts from the contract.
 - `sema testar <arquivo.sema> --alvo <alvo> --saida <diretorio-temporario>`: generates and runs local tests when the target supports it.
-- `sema importar <fonte> <diretorio> --saida <diretorio> --json`: imports a legacy project into initial contracts.
+- `sema importar <nestjs|express|fastify|koa|fastapi|flask|nextjs|nextjs-consumer|react-vite-consumer|angular-consumer|flutter-consumer|sveltekit-consumer|nuxt-consumer|firebase|typescript|python|dart|dotnet|java|go|rust|cpp|php> <diretorio> --saida <diretorio> --json`: imports a legacy project into initial contracts; only these sources have a real importer.
 - `sema renomear-semantico <arquivo-ou-pasta> --de <nome> --para <nome> --json`: helps rename symbols semantically.
 
 Rule for `--saida`: the folder passed to `sema compilar --saida` is generated output. It is not the final delivery by itself. The final delivery is the target files/links declared by the contract. If the contract asks for `index.html`, `css/styles.css`, and `js/app.js`, creating only `saida/expense_control.ts` does not complete the task.
@@ -75,7 +80,10 @@ Ready UI rule: if the task generates an app, site, dashboard, form, or static HT
 
 ## Canonical Syntax Lists
 
-- Origins for `use` and `impl`: `ts/typescript`, `js/javascript`, `py/python`, `dart`, `lua`, `cs/dotnet`, `java`, `go`, `rust`, `cpp`.
+- Origins for `use` and `impl` (11, aliases after `/`): `ts/typescript`, `js/javascript`, `py/python`, `dart`, `lua`, `cs/csharp/dotnet`, `java`, `go/golang`, `rust/rs`, `cpp/cxx/cc/c++`, `php`.
+- Layered `impl` roles: append `_rota`, `_servico`, `_persistencia` or `_repositorio` to any origin (`ts_rota`, `php_servico`, `cs_persistencia`, `py_repositorio`).
+- Generation targets (10): `typescript`, `javascript/js`, `python`, `php`, `dart`, `lua`, `html`, `css`, `dotnet/cs/csharp`, `cpp/c++/cxx/cc`.
+- `sema iniciar --template` (14): `base`, `nestjs`, `fastapi`, `nextjs-api`, `nextjs-consumer`, `react-vite-consumer`, `angular-consumer`, `flutter-consumer`, `node-firebase-worker`, `aspnet-api`, `springboot-api`, `go-http-api`, `rust-axum-api`, `cpp-service-bridge`.
 - Frequent `effects` categories: `persistencia`, `consulta`, `evento`, `auditoria`, `db.write`, `queue.publish`, `fs.write`, `network.egress`, `secret.read`, `shell.exec`.
 - Accepted `audit.motivo` values: `obrigatorio`, `opcional`, `dispensado`.
 

package/docs/syntax.md

@@ -62,18 +62,19 @@ module app.example {
 
 ## Canonical `use` and `impl` Origins
 
-Use these origins before inventing a new one:
+Use these origins before inventing a new one (aliases after `ou`):
 
 - `ts` ou `typescript`
 - `js` ou `javascript`
 - `py` ou `python`
 - `dart`
 - `lua`
-- `cs` ou `dotnet`
+- `cs`, `csharp` ou `dotnet`
 - `java`
-- `go`
-- `rust`
-- `cpp`
+- `go` ou `golang`
+- `rust` ou `rs`
+- `cpp`, `cxx`, `cc` ou `c++`
+- `php`
 
 Examples:
 
@@ -85,11 +86,19 @@ impl {
 }
 ```
 
+```sema
+use php app.legacy.pedidos
+
+impl {
+  php: pedidos.criarPedido
+}
+```
+
 `sema compilar --alvo javascript` defines a generation target. `impl { js: ... }` defines the live-code origin linked to the contract. They are different layers and both are valid.
 
 ## Layered `impl` Roles
 
-Layered code (route + service + persistence in the same language) can declare one `impl` per role. Append a supported role to the origin: `rota`, `servico`, `persistencia` or `repositorio`.
+Layered code (route + service + persistence in the same language) can declare one `impl` per role. Append a supported role to any origin: `rota`, `servico`, `persistencia` or `repositorio`.
 
 ```sema
 impl {
@@ -99,6 +108,16 @@ impl {
 }
 ```
 
+The role suffix combines with every origin, not only TypeScript:
+
+```sema
+impl {
+  php_rota: pedidos.rota.criarPedido
+  php_servico: pedidos.servico.criarPedido
+  php_persistencia: pedidos.repositorio.criar
+}
+```
+
 Each origin-plus-role pair must appear at most once; the bare origin (for example `ts`) stays valid for single-layer tasks, and drift resolves every role independently.
 
 ## Small Canonical Lists

package/exemplos/php_crud.sema

@@ -0,0 +1,170 @@
+module exemplos.php.crud {
+  entity Pedido {
+    fields {
+      id: Id
+      cliente: Texto
+      total: Numero
+      status: Texto
+    }
+  }
+
+  task criar_pedido {
+    input {
+      cliente: Texto required
+      total: Numero required
+    }
+    output {
+      pedido: Pedido
+    }
+    rules {
+      cliente deve_ser preenchido
+      total deve_ser positivo
+    }
+    effects {
+      persistencia Pedido
+      auditoria pedido_criado
+    }
+    guarantees {
+      pedido existe
+    }
+    impl {
+      php_rota: pedidos.rota.criarPedido
+      php_servico: pedidos.servico.criarPedido
+      php_persistencia: pedidos.repositorio.criar
+    }
+    vinculos {
+      arquivo: "src/Pedidos/Controller/PedidoController.php"
+      arquivo: "src/Pedidos/Service/PedidoService.php"
+      arquivo: "src/Pedidos/Repository/PedidoRepository.php"
+      simbolo: pedidos.rota.criarPedido
+    }
+    tests {
+      caso "cria pedido" {
+        given {
+          cliente: "Cliente Exemplo"
+          total: 150.0
+        }
+
+        expect {
+          sucesso: verdadeiro
+        }
+      }
+    }
+  }
+
+  task listar_pedidos {
+    input {
+      status: Texto
+    }
+    output {
+      pedidos: Lista
+    }
+    effects {
+      consulta Pedido
+    }
+    guarantees {
+      pedidos existe
+    }
+    impl {
+      php_rota: pedidos.rota.listarPedidos
+      php_servico: pedidos.servico.listarPedidos
+    }
+    vinculos {
+      arquivo: "src/Pedidos/Controller/PedidoController.php"
+      arquivo: "src/Pedidos/Service/PedidoService.php"
+      simbolo: pedidos.rota.listarPedidos
+    }
+    tests {
+      caso "lista pedidos por status" {
+        given {
+          status: "pago"
+        }
+
+        expect {
+          sucesso: verdadeiro
+        }
+      }
+    }
+  }
+
+  task cancelar_pedido {
+    input {
+      id: Id required
+    }
+    output {
+      cancelado: Booleano
+    }
+    rules {
+      id deve_ser valido
+    }
+    effects {
+      persistencia Pedido
+      auditoria pedido_cancelado
+    }
+    guarantees {
+      cancelado == verdadeiro
+    }
+    impl {
+      php_rota: pedidos.rota.cancelarPedido
+      php_servico: pedidos.servico.cancelarPedido
+      php_persistencia: pedidos.repositorio.atualizarStatus
+    }
+    vinculos {
+      arquivo: "src/Pedidos/Controller/PedidoController.php"
+      arquivo: "src/Pedidos/Service/PedidoService.php"
+      arquivo: "src/Pedidos/Repository/PedidoRepository.php"
+      simbolo: pedidos.rota.cancelarPedido
+    }
+    tests {
+      caso "cancela pedido por id" {
+        given {
+          id: "ped_1"
+        }
+
+        expect {
+          sucesso: verdadeiro
+        }
+      }
+    }
+  }
+
+  route pedidos_criar {
+    metodo: POST
+    caminho: /pedidos
+    task: criar_pedido
+    finalidade: cadastro_pedido
+    input {
+      cliente: Texto
+      total: Numero
+    }
+    output {
+      pedido: Pedido
+    }
+  }
+
+  route pedidos_listar {
+    metodo: GET
+    caminho: /pedidos
+    task: listar_pedidos
+    finalidade: consulta_pedidos
+    input {
+      status: Texto
+    }
+    output {
+      pedidos: Lista
+    }
+  }
+
+  route pedidos_cancelar {
+    metodo: PATCH
+    caminho: "/pedidos/{id}/cancelar"
+    task: cancelar_pedido
+    finalidade: cancelamento_pedido
+    input {
+      id: Id
+    }
+    output {
+      cancelado: Booleano
+    }
+  }
+}

package/node_modules/@sema/nucleo/dist/semantico/analisador.part01.js

@@ -279,7 +279,7 @@ export function validarImplementacoesTask(task, diagnosticos) {
     for (const campo of task.impl.campos) {
         const nome = normalizarNomeCampoImplementacao(campo.nome);
         if (!nome) {
-            diagnosticos.push(criarDiagnostico("SEM059", `Task "${task.nome}" declarou implementacao externa invalida em impl: "${campo.nome}".`, "erro", campo.intervalo, "Use ts, js, py, dart, lua, cs, java, go, rust, cpp ou php, opcionalmente com papel: ts_rota, ts_servico, ts_persistencia ou ts_repositorio."));
+            diagnosticos.push(criarDiagnostico("SEM059", `Task "${task.nome}" declarou implementacao externa invalida em impl: "${campo.nome}".`, "erro", campo.intervalo, "Use ts, js, py, dart, lua, cs, java, go, rust, cpp ou php, opcionalmente com papel de qualquer origem: <origem>_rota, <origem>_servico, <origem>_persistencia ou <origem>_repositorio (ex.: ts_rota, php_servico, cs_persistencia)."));
             continue;
         }
         const rotulo = nome.papel ? `${nome.origem}_${nome.papel}` : nome.origem;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@semacode/cli",
-  "version": "3.11.0",
+  "version": "3.12.0",
   "description": "Local-first semantic governance CLI for AI agents, proven with Claude, Codex, zCode (GLM) and Kimi: contracts, drift, impact, docs gates, and code generation.",
   "type": "module",
   "icon": "logo.png",