@semacode/cli 3.8.0 → 3.8.2

package/dist/initTemplatesBase.js

@@ -1,5 +1,5 @@
 // SEMA-GOVERNED: sema.produto.cli_init_templates, sema.produto.governanca_ia.drift.cache.modos
-// Descrição: contrato base e dispatcher dos templates Codex-native de inicialização.
+// Descrição: contrato base e dispatcher dos templates multi-agente de inicialização.
 import { arquivosInitTemplatesBackend } from "./initTemplatesBackend.js";
 import { arquivosInitTemplatesWeb } from "./initTemplatesWeb.js";
 import { arquivosInitTemplatesFlutter } from "./initTemplatesFlutter.js";
@@ -8,54 +8,54 @@ export function arquivosBaseIniciar() {
     return [
         {
             caminhoRelativo: "contratos/pedidos.sema",
-            conteudo: `module app.pedidos {
-  entity Pedido {
-    fields {
-      id: Id
-      status: Texto
-      total: Decimal
-    }
-  }
-
-  task criar_pedido {
-    input {
-      cliente_id: Id required
-      total: Decimal required
-    }
-    output {
-      pedido_id: Id
-      status: Texto
-    }
-    rules {
-      total > 0
-    }
-    effects {
-      persistencia Pedido criticidade=alta
-      auditoria pedidos
-    }
-    guarantees {
-      pedido_id existe
-      status existe
-    }
-    tests {
-      caso "pedido valido" {
-        given {
-          cliente_id: "cli-1"
-          total: 10
-        }
-        expect {
-          sucesso: verdadeiro
-        }
-      }
-    }
-  }
-
-  route criar_pedido_publico {
-    metodo: POST
-    caminho: /pedidos
-    task: criar_pedido
-  }
-}
+            conteudo: `module app.pedidos {
+  entity Pedido {
+    fields {
+      id: Id
+      status: Texto
+      total: Decimal
+    }
+  }
+
+  task criar_pedido {
+    input {
+      cliente_id: Id required
+      total: Decimal required
+    }
+    output {
+      pedido_id: Id
+      status: Texto
+    }
+    rules {
+      total > 0
+    }
+    effects {
+      persistencia Pedido criticidade=alta
+      auditoria pedidos
+    }
+    guarantees {
+      pedido_id existe
+      status existe
+    }
+    tests {
+      caso "pedido valido" {
+        given {
+          cliente_id: "cli-1"
+          total: 10
+        }
+        expect {
+          sucesso: verdadeiro
+        }
+      }
+    }
+  }
+
+  route criar_pedido_publico {
+    metodo: POST
+    caminho: /pedidos
+    task: criar_pedido
+  }
+}
 `,
         },
     ];
@@ -64,41 +64,41 @@ function arquivosApoioIaIniciar() {
     return [
         {
             caminhoRelativo: "README.md",
-            conteudo: `# Projeto Sema
-
-Este projeto foi inicializado com Sema.
-
-## Entrada oficial do Codex
-
-Antes de alterar codigo, contrato ou documentacao:
-
-1. leia \`AGENTS.md\`;
-2. rode \`sema --version\`; se o shell não localizar o comando, use \`$HOME/.sema/bin/sema\` no macOS/Linux; no Windows, PowerShell usa \`sema.ps1\` no PATH, cmd.exe usa \`sema.cmd\`, e o fallback absoluto é \`& "$env:SystemRoot\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File "$HOME\\.sema\\bin\\sema-managed.ps1" --version\`;
-3. rode \`sema resumo --drift none\` para contexto contratual; score, confiança e implementação ficam não avaliados;
-4. rode \`sema docs-impacto --intencao "<acao>" --json\`;
-5. leia \`docs/commands.md\` antes de escolher comando ou interpretar \`--saida\`;
-6. use \`sema descobrir recomendar --intencao "<objetivo>" --json\` quando não souber qual capacidade ou pipeline aplicar;
-7. use \`exemplos/\` e \`docs/syntax.md\` antes de criar ou corrigir \`.sema\`.
-
-Quando precisar comprovar o código vivo, rode \`sema drift <contrato.sema> --escopo modulo --cache fresh --json\`. Cache acelera navegação, mas não é prova final de fechamento.
-
-## Estrutura criada
-
-- \`contratos/\`: contratos semanticamente governados.
-- \`AGENTS.md\`: entrypoint oficial do Codex.
-- \`exemplos/\`: exemplos oficiais da DSL Sema.
-- \`docs/commands.md\`: catalogo de comandos, pipelines, gates e regra de \`--saida\`.
-- \`docs/syntax.md\`: referencia curta para escrever \`.sema\`.
-- \`docs/ai-workflow.md\`: fluxo minimo para agentes.
-- \`SEMA_BOOT.md\`, \`SEMA_SMALL_MODEL.md\`, \`AGENT_CONTEXT_PACK.json\` e \`SEMA_INDEX.json\`: contexto IA-first.
-
-## Geracao
-
-O template base ja declara alvo JavaScript. Exemplo:
-
-\`\`\`bash
-sema compilar contratos/pedidos.sema --alvo javascript --saida ./generated/javascript
-\`\`\`
+            conteudo: `# Projeto Sema
+
+Este projeto foi inicializado com Sema.
+
+## Entrada oficial do Codex
+
+Antes de alterar codigo, contrato ou documentacao:
+
+1. leia \`AGENTS.md\`;
+2. rode \`sema --version\`; se o shell não localizar o comando, use \`$HOME/.sema/bin/sema\` no macOS/Linux; no Windows, PowerShell usa \`sema.ps1\` no PATH, cmd.exe usa \`sema.cmd\`, e o fallback absoluto é \`& "$env:SystemRoot\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File "$HOME\\.sema\\bin\\sema-managed.ps1" --version\`;
+3. rode \`sema resumo --drift none\` para contexto contratual; score, confiança e implementação ficam não avaliados;
+4. rode \`sema docs-impacto --intencao "<acao>" --json\`;
+5. leia \`docs/commands.md\` antes de escolher comando ou interpretar \`--saida\`;
+6. use \`sema descobrir recomendar --intencao "<objetivo>" --json\` quando não souber qual capacidade ou pipeline aplicar;
+7. use \`exemplos/\` e \`docs/syntax.md\` antes de criar ou corrigir \`.sema\`.
+
+Quando precisar comprovar o código vivo, rode \`sema drift <contrato.sema> --escopo modulo --cache fresh --json\`. Cache acelera navegação, mas não é prova final de fechamento.
+
+## Estrutura criada
+
+- \`contratos/\`: contratos semanticamente governados.
+- \`AGENTS.md\`: entrypoint oficial do Codex.
+- \`exemplos/\`: exemplos oficiais da DSL Sema.
+- \`docs/commands.md\`: catalogo de comandos, pipelines, gates e regra de \`--saida\`.
+- \`docs/syntax.md\`: referencia curta para escrever \`.sema\`.
+- \`docs/ai-workflow.md\`: fluxo minimo para agentes.
+- \`SEMA_BOOT.md\`, \`SEMA_SMALL_MODEL.md\`, \`AGENT_CONTEXT_PACK.json\` e \`SEMA_INDEX.json\`: contexto IA-first.
+
+## Geracao
+
+O template base ja declara alvo JavaScript. Exemplo:
+
+\`\`\`bash
+sema compilar contratos/pedidos.sema --alvo javascript --saida ./generated/javascript
+\`\`\`
 `,
         },
     ];

package/dist/projetoOrigens.js

@@ -52,8 +52,14 @@ async function resolverDiretoriosConfiguradosConfinados(baseProjeto, baseConfigu
         let canonico = absoluto;
         try {
             const [real, informacao] = await Promise.all([realpath(absoluto), stat(absoluto)]);
-            if (!informacao.isDirectory()) {
-                throw new Error(`${identificadorSeguro} nao e diretorio`);
+            const ehContratoIndividual = campo === "origens"
+                && informacao.isFile()
+                && absoluto.toLowerCase().endsWith(".sema");
+            if (!informacao.isDirectory() && !ehContratoIndividual) {
+                const esperado = campo === "origens"
+                    ? "um diretorio de contratos (ex.: ./contratos) ou um arquivo .sema individual"
+                    : "um diretorio de codigo vivo";
+                throw new Error(`${identificadorSeguro} nao e ${esperado}. Corrija "${campo}" no sema.config.json; configuracoes geradas por versoes antigas da CLI podem listar arquivos direto.`);
             }
             if (!caminhoEstaDentro(baseReal, real)) {
                 throw new Error(`${identificadorSeguro} resolve fora da base do projeto`);

package/docs/README.md

@@ -1,25 +1,25 @@
 # Sema Documentation
 
-These docs describe the public Codex-native local CLI distribution of Sema.
+These docs describe the public local-first CLI distribution of Sema, proven with Claude, Codex, zCode (GLM) and Kimi.
 
-Sema is local-first: Codex runs the CLI inside a project folder, reads `.sema`
-contracts, checks drift, maps impact, and closes changes with documentation
-evidence. In 3.0.0, valid commands using `--json` return the exact
-`sema.cli.result/v1` envelope with command data nested under `payload`, while
-help and command-control failures keep the separate `sema.cli.control/v1`
-envelope. `AGENTS.md` is the official Codex entrypoint. Public docs are written
-in English.
+Sema is local-first: Codex runs the CLI inside a project folder, reads `.sema`
+contracts, checks drift, maps impact, and closes changes with documentation
+evidence. In 3.0.0, valid commands using `--json` return the exact
+`sema.cli.result/v1` envelope with command data nested under `payload`, while
+help and command-control failures keep the separate `sema.cli.control/v1`
+envelope. `AGENTS.md` is the official Codex entrypoint. Public docs are written
+in English.
 
 Sema is an independent product and is not affiliated with or endorsed by
-OpenAI. Codex-native describes Sema's product direction, not an official OpenAI
-program or submission.
+OpenAI. Proven compatibility with Claude, Codex, zCode (GLM) and Kimi describes
+Sema's product direction, not an official OpenAI program.
 
 Start here:
 
-- [CLI](./cli.md) — installation and the public JSON output contract
-- [Commands](./commands.md) — command catalog and envelope-consumption rules
-- [Drift Cache And Query Evidence](./drift-cache.md)
-- [Syntax](./syntax.md)
+- [CLI](./cli.md) — installation and the public JSON output contract
+- [Commands](./commands.md) — command catalog and envelope-consumption rules
+- [Drift Cache And Query Evidence](./drift-cache.md)
+- [Syntax](./syntax.md)
 - [Profiles](./profiles.md)
 - [Capability Discovery](./descoberta-capacidades.md) — one explainable catalog
   for governance flows, profiles, specialized workflows, pipelines, generators,
@@ -35,4 +35,4 @@ Start here:
 - [Security](./security.md)
 - [Codex Integration](./ai-integration.md)
 
-Official support: [suporte@otimitare.online](mailto:suporte@otimitare.online)
+Official support: [suporte@otimitare.com](mailto:suporte@otimitare.com)

package/docs/ai-onboarding.md

@@ -1,81 +1,81 @@
-# Codex Onboarding
-
-The official Sema skill lets Codex and compatible agents recognize and
-initialize Sema before a project has its own protocol:
-
-```bash
-npm install -g @semacode/cli
-sema skill status --json
-```
-
-The install maintains the canonical copy in `~/.agents/skills/sema` and a Claude
-mirror in `~/.claude/skills/sema` only when Claude is detected. Open a new task
-after installation or update because an already-open task does not reload its
-skill catalog. Invoking `$sema` for information does not initialize the
-workspace. Before implementation, the skill asks for explicit adoption
-authorization; installing or updating the global CLI authorizes distribution
-changes only. After authorized adoption, it reads the generated `AGENTS.md`,
-and later tasks load that protocol automatically.
-
-The optional Codex plugin remains available as a separate namespaced channel;
-the npm lifecycle never writes into its cache.
-
-`AGENTS.md` is the official Sema entrypoint for Codex. It gives Codex the durable
-repository rule that contracts come first and the local CLI is the source of
-truth. Once the file exists, the skill delegates to it instead of carrying a
-second copy of the governed workflow.
-
-Create or refresh the entrypoint with:
-
-```bash
-sema sync-codex --json
-```
-
-## Minimal Prompt
-
-```text
-This workspace is governed by Sema. Before editing code, contracts, docs,
-workflows, profiles, or release scripts, run:
-
-1. sema --version
-2. sema resumo --drift none
-3. sema docs-impacto --intencao "<change>" --json
-4. sema inspecionar <contract.sema> --drift none --json
-5. sema drift <contract.sema> --escopo modulo --cache fresh --json before
-   editing existing code
-6. sema impacto before changing behavior
-7. sema finalizar-mudanca before closing
-
-If `sema --version` is unavailable, try the managed absolute launcher at
-`~/.sema/bin/sema` on macOS/Linux. On Windows, PowerShell uses `sema.ps1` from
-`PATH`, `cmd.exe` uses `sema.cmd`, and the absolute PowerShell fallback is:
-& "$env:SystemRoot\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File "$HOME\.sema\bin\sema-managed.ps1" --version
-If that also fails, stop and install or repair @semacode/cli. There is no
-separate Sema login or license-activation gate. Distribution installation does
-not authorize workspace adoption. Do not replace Sema with manual search or
-guessed contracts.
-```
-
-Query commands default to `--drift none`, so their `analiseDrift` envelope marks
-the analysis as not executed and keeps drift-derived evidence `null`. Direct
-`sema drift` defaults to `--cache fresh`; `--cache none` still executes drift
-without persistent cache access. The cache is non-authoritative, lives outside
-the workspace, and safely falls back to recalculation when unavailable or
-corrupt. See [Drift Cache And Query Evidence](./drift-cache.md).
-
-## What Codex Should Not Do
-
-- Do not invent `.sema` contracts.
-- Do not implement code without an applicable contract.
-- Do not ignore severity 4+ warnings.
-- Do not publish private or sensitive operational material.
-- Do not replace the local CLI when the local workspace is available.
-
-Compatible AI clients can discover the same portable skill through the
-canonical global `.agents/skills` root. Sema does not create client-specific
-repository rules: `AGENTS.md` remains the only official workspace entrypoint.
-
-Sema is an independent product and is not affiliated with or endorsed by
-OpenAI.
-
-Support: suporte@otimitare.online
+# Codex Onboarding
+
+The official Sema skill lets Codex and compatible agents recognize and
+initialize Sema before a project has its own protocol:
+
+```bash
+npm install -g @semacode/cli
+sema skill status --json
+```
+
+The install maintains the canonical copy in `~/.agents/skills/sema` and a Claude
+mirror in `~/.claude/skills/sema` only when Claude is detected. Open a new task
+after installation or update because an already-open task does not reload its
+skill catalog. Invoking `$sema` for information does not initialize the
+workspace. Before implementation, the skill asks for explicit adoption
+authorization; installing or updating the global CLI authorizes distribution
+changes only. After authorized adoption, it reads the generated `AGENTS.md`,
+and later tasks load that protocol automatically.
+
+The optional Codex plugin remains available as a separate namespaced channel;
+the npm lifecycle never writes into its cache.
+
+`AGENTS.md` is the official Sema entrypoint for Codex. It gives Codex the durable
+repository rule that contracts come first and the local CLI is the source of
+truth. Once the file exists, the skill delegates to it instead of carrying a
+second copy of the governed workflow.
+
+Create or refresh the entrypoint with:
+
+```bash
+sema sync-codex --json
+```
+
+## Minimal Prompt
+
+```text
+This workspace is governed by Sema. Before editing code, contracts, docs,
+workflows, profiles, or release scripts, run:
+
+1. sema --version
+2. sema resumo --drift none
+3. sema docs-impacto --intencao "<change>" --json
+4. sema inspecionar <contract.sema> --drift none --json
+5. sema drift <contract.sema> --escopo modulo --cache fresh --json before
+   editing existing code
+6. sema impacto before changing behavior
+7. sema finalizar-mudanca before closing
+
+If `sema --version` is unavailable, try the managed absolute launcher at
+`~/.sema/bin/sema` on macOS/Linux. On Windows, PowerShell uses `sema.ps1` from
+`PATH`, `cmd.exe` uses `sema.cmd`, and the absolute PowerShell fallback is:
+& "$env:SystemRoot\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Bypass -File "$HOME\.sema\bin\sema-managed.ps1" --version
+If that also fails, stop and install or repair @semacode/cli. There is no
+separate Sema login or license-activation gate. Distribution installation does
+not authorize workspace adoption. Do not replace Sema with manual search or
+guessed contracts.
+```
+
+Query commands default to `--drift none`, so their `analiseDrift` envelope marks
+the analysis as not executed and keeps drift-derived evidence `null`. Direct
+`sema drift` defaults to `--cache fresh`; `--cache none` still executes drift
+without persistent cache access. The cache is non-authoritative, lives outside
+the workspace, and safely falls back to recalculation when unavailable or
+corrupt. See [Drift Cache And Query Evidence](./drift-cache.md).
+
+## What Codex Should Not Do
+
+- Do not invent `.sema` contracts.
+- Do not implement code without an applicable contract.
+- Do not ignore severity 4+ warnings.
+- Do not publish private or sensitive operational material.
+- Do not replace the local CLI when the local workspace is available.
+
+Compatible AI clients can discover the same portable skill through the
+canonical global `.agents/skills` root. Sema does not create client-specific
+repository rules: `AGENTS.md` remains the only official workspace entrypoint.
+
+Sema is an independent product and is not affiliated with or endorsed by
+OpenAI.
+
+Support: suporte@otimitare.com