@semacode/cli 3.12.2 → 4.0.0

package/dist/sync/index.js

@@ -46,25 +46,25 @@ export async function gerarSchemaPrisma(pastaContratos, saidaSchema, datasourceP
     for (const contrato of contratos) {
         const nomeModel = path.basename(contrato, '.sema').replace(/\./g, '_');
         // Schema simplificado - em producao, fazer parsing real do contrato
-        models += `\nmodel ${nomeModel.charAt(0).toUpperCase() + nomeModel.slice(1)} {
-  id        String   @id @default(uuid())
-  criadoEm  DateTime @default(now())
-  // Gerado a partir de: ${contrato}
-  // TODO: Adicionar campos do contrato Sema
+        models += `\nmodel ${nomeModel.charAt(0).toUpperCase() + nomeModel.slice(1)} {
+  id        String   @id @default(uuid())
+  criadoEm  DateTime @default(now())
+  // Gerado a partir de: ${contrato}
+  // TODO: Adicionar campos do contrato Sema
 }\n`;
         modelCount++;
     }
-    const schema = `// Gerado automaticamente pelo Sema
-// Fonte: ${pastaContratos}
-
-generator client {
-  provider = "prisma-client-js"
-}
-
-datasource db {
-  provider = "${datasourceProvider}"
-  url      = env("SEMA_PRISMA_URL")
-}
+    const schema = `// Gerado automaticamente pelo Sema
+// Fonte: ${pastaContratos}
+
+generator client {
+  provider = "prisma-client-js"
+}
+
+datasource db {
+  provider = "${datasourceProvider}"
+  url      = env("SEMA_PRISMA_URL")
+}
 ${models}`;
     // Salvar
     fs.writeFileSync(saidaSchema, schema, 'utf-8');
@@ -90,25 +90,25 @@ export async function importarSchemaPrisma(caminhoSchema, pastaSaida, nomeModulo
         const nomeContrato = `${nomeModel.toLowerCase()}.sema`;
         const caminhoContrato = path.join(pastaSaida, nomeContrato);
         // Gerar contrato basico
-        const conteudo = `module ${nomeModulo}.${nomeModel.toLowerCase()} {
-  entity ${nomeModel} {
-    fields {
-      id: Id
-      // TODO: Mapear campos do schema Prisma
-    }
-  }
-
-  task criar_${nomeModel.toLowerCase()} {
-    input {
-      // TODO: Definir inputs
-    }
-    output {
-      ${nomeModel.toLowerCase()}: ${nomeModel}
-    }
-    effects {
-      persistencia ${nomeModel}
-    }
-  }
+        const conteudo = `module ${nomeModulo}.${nomeModel.toLowerCase()} {
+  entity ${nomeModel} {
+    fields {
+      id: Id
+      // TODO: Mapear campos do schema Prisma
+    }
+  }
+
+  task criar_${nomeModel.toLowerCase()} {
+    input {
+      // TODO: Definir inputs
+    }
+    output {
+      ${nomeModel.toLowerCase()}: ${nomeModel}
+    }
+    effects {
+      persistencia ${nomeModel}
+    }
+  }
 }`;
         fs.writeFileSync(caminhoContrato, conteudo, 'utf-8');
         contratos.push(caminhoContrato);

package/docs/ai-workflow.md

@@ -18,7 +18,7 @@ This is the minimum workflow for Codex in a local workspace.
 
 Contract edit rule: `.sema` has its own size budget. Above 300 lines, plan a split by domain/capability; above 500, do not create or edit before splitting. Do not use parte_1/parte_2 and do not force a 1:1 contract-to-file relationship; several contracts can govern the same file through `vinculos`.
 
-Closing rule: the `payload` of `sema drift --cache fresh --json` must return `sucesso:true`. If it reports `sucesso:false`, `vinculos_quebrados`, `rotas_divergentes`, or `impls_quebrados`, the task is still blocked. Passing unit tests or a cache hit do not replace fresh green drift. In 3.0.0, `ok` describes the CLI result path and never replaces a command-specific domain verdict.
+Closing rule: the `payload` of `sema drift --cache fresh --json` must return `sucesso:true`. If it reports `sucesso:false`, `vinculos_quebrados`, `rotas_divergentes`, or `impls_quebrados`, the task is still blocked. Passing unit tests or a cache hit do not replace fresh green drift. `vinculos_fora_do_escopo` is informational: the file exists in the workspace outside the configured `diretoriosCodigo`, and each entry carries a `diretorioSugerido` to add to `sema.config.json`; it does not block closure. In 3.0.0, `ok` describes the CLI result path and never replaces a command-specific domain verdict.
 
 Focused drift rule: file and module scopes plan their physical file set before cataloging. They never fall back to a whole-project walk when no safe anchor exists. All indexers and semantic-budget checks reuse the same in-memory source read; a global walk is reserved for explicit `--escopo projeto`. Code discovery is deferred until that plan exists, homonymous candidates fail as ambiguous, and configured contract origins or code roots resolving outside the workspace are rejected before enumeration. `inspecionar`, `impacto`, and `renomear-semantico` preserve the same directed boundary. Missing unambiguous local dependencies make coverage partial and block success. In Python, an unresolved `name` from `from module import name` is not itself a missing file after `module` resolves: it may be an exported symbol, while a real child module is still included whenever its file exists.
 

package/docs/auth.md

@@ -1,26 +1,26 @@
-# Local Runtime Boundary
-
-The public Sema CLI executes directly against the local workspace. It does not
-require a Sema login, user authentication, product authorization, license
-activation, install key, token, credits, billing service, control panel, or an
-external request.
-
-Use local commands:
-
-```bash
-sema --version
-sema resumo
-sema validar contratos/example.sema --json
-```
-
-The repository license governs use and redistribution. It is not checked as a
-runtime activation mechanism.
-
-An `authz` block inside a `.sema` contract describes authorization in the
-application being governed. It does not authenticate a person before the Sema
-CLI can run.
-
-Do not put private or sensitive operational material in this repository.
-
-Application-specific authentication belongs in the application repository that
-owns it.
+# Local Runtime Boundary
+
+The public Sema CLI executes directly against the local workspace. It does not
+require a Sema login, user authentication, product authorization, license
+activation, install key, token, credits, billing service, control panel, or an
+external request.
+
+Use local commands:
+
+```bash
+sema --version
+sema resumo
+sema validar contratos/example.sema --json
+```
+
+The repository license governs use and redistribution. It is not checked as a
+runtime activation mechanism.
+
+An `authz` block inside a `.sema` contract describes authorization in the
+application being governed. It does not authenticate a person before the Sema
+CLI can run.
+
+Do not put private or sensitive operational material in this repository.
+
+Application-specific authentication belongs in the application repository that
+owns it.

package/docs/commands.md

@@ -31,7 +31,7 @@ Then read every required doc returned by `docs-impacto`.
 
 ## Contract and Discovery
 
-- `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 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. Inside a subfolder of an already governed workspace, the subfolder is registered under `diretoriosCodigo` of the ancestral `sema.config.json` (safe write, deduplicated) instead of creating a local config; if the parent config cannot be written, the scaffold proceeds and prints the exact line to add.
 - `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.
@@ -51,7 +51,7 @@ Then read every required doc returned by `docs-impacto`.
 - `sema verificar <arquivo-ou-pasta> --json`: runs aggregated final verification.
 - `sema finalizar-mudanca --intencao "<acao>" --doc-lida <arquivo> --json`: proves documentation reading before closure.
 
-Honest closure: unwrap drift JSON and treat its command payload as the source of truth. `payload.sucesso:false`, non-empty `payload.vinculos_quebrados`, non-empty `payload.rotas_divergentes`, or non-empty `payload.impls_quebrados` mean the change is not complete yet. Do not report "clean drift" without a green payload.
+Honest closure: unwrap drift JSON and treat its command payload as the source of truth. `payload.sucesso:false`, non-empty `payload.vinculos_quebrados`, non-empty `payload.rotas_divergentes`, or non-empty `payload.impls_quebrados` mean the change is not complete yet. Do not report "clean drift" without a green payload. `payload.vinculos_fora_do_escopo` is informational: the file exists in the workspace outside `diretoriosCodigo`, and each entry carries a `diretorioSugerido` for `sema.config.json`.
 
 Focused drift exposes its planned, declared, inferred, and missing files plus catalog visit/read metrics in `escopo_aplicado`. A missing declared file or a missing unambiguous code-referenced dependency is a blocker reported as `vinculo_quebrado`; a missing inferred candidate derived from an `impl` symbol is informational under `arquivosAusentesInferidos` and never blocks an implementation that resolved. For Python `from module import name`, Sema still includes `name` when it resolves as a real submodule, but never reports the absent submodule candidate as a broken link after the parent module resolved because `name` may be a function, class, or variable. File and module scopes fail closed without a safe anchor, with homonymous implementation candidates, or with missing local dependencies; only `--escopo projeto` may walk every configured code root. Logical roots such as `src` are probed deterministically without a discovery walk. Configured contract origins and code roots are confined before enumeration, and `inspecionar`, `impacto`, and `renomear-semantico` reuse the same directed boundary without reopening arbitrary external paths.
 
@@ -156,7 +156,7 @@ Spatial model and render mode are orthogonal: `THREE_D + HEADLESS` is valid, whi
 - Do not stop after `sema compilar` if the contract target files still do not exist.
 - Do not replace `sema compilar` with `sema testar` when the contract requires generated code.
 - Do not create a Markdown report to pretend a gate ran.
-- Do not say drift passed when the unwrapped `sema drift --cache fresh --json` payload returned `sucesso:false`, a non-empty `vinculos_quebrados`, `rotas_divergentes`, or `impls_quebrados` list.
+- Do not say drift passed when the unwrapped `sema drift --cache fresh --json` payload returned `sucesso:false`, a non-empty `vinculos_quebrados`, `rotas_divergentes`, or `impls_quebrados` list. `vinculos_fora_do_escopo` entries are informational scope hints, not broken links.
 - Do not declare a UI responsive without mobile/desktop proof; horizontal scroll at 390px blocks closure.
 
 Governed code policy: keep the `SEMA-GOVERNED` marker, split large code by real responsibility, preserve contract links, and never treat a generated output directory as the final delivery.

package/docs/database.md

@@ -1,15 +1,15 @@
-# Database Boundary
-
-The public Sema CLI does not require a database.
-
-Sema reads contracts and source files from the local workspace. Any database used
-by an application governed by Sema belongs to that application, not to the public
-Sema CLI distribution.
-
-## Public Rule
-
-Do not ship private database material, real credentials, operational schemas, or
-project-specific data in the public Sema package.
-
-Application-specific database docs should live in the application repository
-that owns the database.
+# Database Boundary
+
+The public Sema CLI does not require a database.
+
+Sema reads contracts and source files from the local workspace. Any database used
+by an application governed by Sema belongs to that application, not to the public
+Sema CLI distribution.
+
+## Public Rule
+
+Do not ship private database material, real credentials, operational schemas, or
+project-specific data in the public Sema package.
+
+Application-specific database docs should live in the application repository
+that owns the database.

package/docs/env.md

@@ -1,16 +1,16 @@
-# Environment
-
-The public Sema CLI works without private service credentials. No environment
-variable unlocks local execution: there is no login, activation, product
-authorization, license-key, billing, credit, token, or panel gate.
-
-Allowed public examples may use placeholders:
-
-```bash
-EXAMPLE_API_KEY=replace-me
-```
-
-Do not publish private or sensitive operational material in public Sema docs.
-
-If an application governed by Sema needs environment variables, document them in
-that application repository.
+# Environment
+
+The public Sema CLI works without private service credentials. No environment
+variable unlocks local execution: there is no login, activation, product
+authorization, license-key, billing, credit, token, or panel gate.
+
+Allowed public examples may use placeholders:
+
+```bash
+EXAMPLE_API_KEY=replace-me
+```
+
+Do not publish private or sensitive operational material in public Sema docs.
+
+If an application governed by Sema needs environment variables, document them in
+that application repository.

package/docs/frontend.md

@@ -1,41 +1,41 @@
-# User Experience Quality
-
-When Sema governs a UI, dashboard, app, site, game, or terminal tool, the
-experience must be modern, contextual, and verified. This is a quality gate, not
-decoration.
-
-## Before Building
-
-Define:
-
-- audience and domain
-- primary workflow
-- density and information hierarchy
-- interaction states
-- responsive behavior
-- accessibility basics
-- evidence needed before closing
-
-## Browser Evidence
-
-For web UI, check desktop and mobile. On a narrow viewport such as 390px, this
-must be true:
-
-```js
-document.documentElement.scrollWidth <= document.documentElement.clientWidth
-```
-
-Fix overlapping text, broken wrapping, hidden controls, and incoherent layout
-before closing the change.
-
-## Terminal Evidence
-
-For CLI/TUI work, smoke-check:
-
-- `--help`
-- success output
-- error output
-- JSON output when supported
-
-The public Sema CLI itself must stay local-only and must not depend on private
-or sensitive operational material for these checks.
+# User Experience Quality
+
+When Sema governs a UI, dashboard, app, site, game, or terminal tool, the
+experience must be modern, contextual, and verified. This is a quality gate, not
+decoration.
+
+## Before Building
+
+Define:
+
+- audience and domain
+- primary workflow
+- density and information hierarchy
+- interaction states
+- responsive behavior
+- accessibility basics
+- evidence needed before closing
+
+## Browser Evidence
+
+For web UI, check desktop and mobile. On a narrow viewport such as 390px, this
+must be true:
+
+```js
+document.documentElement.scrollWidth <= document.documentElement.clientWidth
+```
+
+Fix overlapping text, broken wrapping, hidden controls, and incoherent layout
+before closing the change.
+
+## Terminal Evidence
+
+For CLI/TUI work, smoke-check:
+
+- `--help`
+- success output
+- error output
+- JSON output when supported
+
+The public Sema CLI itself must stay local-only and must not depend on private
+or sensitive operational material for these checks.

package/docs/i18n.md

@@ -1,15 +1,15 @@
-# Language And Identifiers
-
-Public Sema documentation is English.
-
-Do not translate commands, file paths, package names, endpoint paths, environment
-variable names, code symbols, DSL keywords, or brand names.
-
-Examples:
-
-- Keep `sema validar`, not an English paraphrase.
-- Keep `.sema`, `task`, `input`, `output`, `rules`, `effects`, and `guarantees`.
-- Keep package names such as `@semacode/cli`.
-
-Human-facing prose should be clear English. Contract DSL can keep its own
-keywords and domain identifiers.
+# Language And Identifiers
+
+Public Sema documentation is English.
+
+Do not translate commands, file paths, package names, endpoint paths, environment
+variable names, code symbols, DSL keywords, or brand names.
+
+Examples:
+
+- Keep `sema validar`, not an English paraphrase.
+- Keep `.sema`, `task`, `input`, `output`, `rules`, `effects`, and `guarantees`.
+- Keep package names such as `@semacode/cli`.
+
+Human-facing prose should be clear English. Contract DSL can keep its own
+keywords and domain identifiers.

package/exemplos/agendamento.sema

@@ -102,4 +102,4 @@ module exemplos.agendamento {
       }
     }
   }
-}
+}

package/exemplos/assinatura.sema

@@ -130,4 +130,4 @@ module exemplos.assinatura {
       }
     }
   }
-}
+}

package/exemplos/auditoria.sema

@@ -86,4 +86,4 @@ module exemplos.auditoria {
       }
     }
   }
-}
+}

package/exemplos/autenticacao.sema

@@ -122,4 +122,4 @@ module exemplos.autenticacao {
       }
     }
   }
-}
+}

package/exemplos/author_obra_comum.sema

@@ -291,4 +291,4 @@ module exemplos.author.obra_comum {
       auditoria author_flow criticidade = media
     }
   }
-}
+}

package/exemplos/author_tema_sensivel.sema

@@ -261,4 +261,4 @@ module exemplos.author.tema_sensivel {
       auditoria author_flow_sensivel criticidade = alta
     }
   }
-}
+}

package/exemplos/automacao.sema

@@ -104,4 +104,4 @@ module exemplos.automacao {
     etapa auditar usa registrar_auditoria com protocolo = receber.protocolo depende_de receber
     etapa registrar_falha usa registrar_falha_onboarding com lead_id = lead_id depende_de receber
   }
-}
+}

package/exemplos/cadastro_usuario.sema

@@ -51,4 +51,4 @@ module exemplos.cadastro.usuario {
       }
     }
   }
-}
+}

package/exemplos/calculadora.sema

@@ -75,4 +75,4 @@ module exemplos.calculadora {
       }
     }
   }
-}
+}

package/exemplos/crud_simples.sema

@@ -86,4 +86,4 @@ module exemplos.crud.simples {
       produto: Produto
     }
   }
-}
+}

package/exemplos/estoque.sema

@@ -124,4 +124,4 @@ module exemplos.estoque {
       }
     }
   }
-}
+}

package/exemplos/exportacao.sema

@@ -91,4 +91,4 @@ module exemplos.exportacao {
       }
     }
   }
-}
+}

package/exemplos/fila.sema

@@ -127,4 +127,4 @@ module exemplos.fila {
       }
     }
   }
-}
+}

package/exemplos/integracao_externa.sema

@@ -91,4 +91,4 @@ module exemplos.integracao.externa {
       }
     }
   }
-}
+}

package/exemplos/multi_tenant.sema

@@ -137,4 +137,4 @@ module exemplos.multi.tenant {
       }
     }
   }
-}
+}

package/exemplos/notificacao.sema

@@ -146,4 +146,4 @@ module exemplos.notificacao {
     etapa registrar_falha_push usa registrar_falha_notificacao com canal = canal_push depende_de push
     etapa concluir usa confirmar_notificacao com destinatario_id = destinatario_id depende_de email
   }
-}
+}