@semacode/cli 1.5.48 → 1.5.53

package/docs/env.md

@@ -1,115 +1,14 @@
-# Env
-
-<!-- sema:i18n -->
-> EN: English first. The canonical operational body below may still be in Portuguese until full translation lands.
-> PT: Português depois, com acentos preservados.
-> ES: Español al final; não traduza comandos, rotas nem sómbolos `.sema` sem contrato.
-
-
-Ambiente necessário para publicar a Sema.
-
-## Ferramentas
-
-- Node.js LTS com `npm`.
-- Git com acesso ao repositório privado.
-- VS Code CLI (`code`) para instalar a VSIX localmente.
-- PowerShell no Windows.
-
-## Variaveis suportadas pelos instaladores
+# Environment
 
-- `SEMA_NPM_PACKAGE`: pacote da CLI. Padrão: `@semacode/cli`.
-- `SEMA_VERSION`: versão usada pelo `install-sema.sh`. Padrão: `latest`.
-- `SEMA_VSIX_PATH`: caminho privado/local para a VSIX quando usar `--with-vscode`.
-
-No PowerShell, o instalador recebe a versão por parametro:
-
-```powershell
-.\install-sema.ps1 -Version 1.5.48 -WithVSCode
-```
-
-No shell:
-
-```bash
-SEMA_VERSION=1.5.48 ./install-sema.sh --with-vscode
-```
-
-## Credenciais
-
-- NPM deve estar logado antes de publicar: `npm whoami`.
-- Nunca registre tokens em docs, logs ou release notes.
-
-## Registro NPM
-
-O pacote público é:
-
-- `@semacode/cli`
-
-Antes de publicar, confira:
-
-```bash
-npm view @semacode/cli version
-npm run release:verificar-versao
-```
-
-## Cliente MCP remoto
-
-Variaveis usadas por Codex, VS Code/forks e clientes que aceitam bearer:
-
-- `SEMA_MCP_AUTH_TOKEN`: chave comercial `sema_mcp_*` gerada no painel. E do cliente, nao do servidor.
-- `SEMA_MCP_ENDPOINT`: URL HTTPS `/mcp` usada por clientes que leem endpoint por variavel.
-
-No Windows, instale sem expor a chave em argumento:
-
-```powershell
-Get-Clipboard | sema mcp-instalar-chave --stdin --json
-```
-
-## Servidor MCP remoto privado
-
-Variaveis usadas pelo servidor MCP privado quando roda em modo HTTP:
-
-- `MCP_PORT`: porta HTTP. Quando ausente, o MCP roda em `stdio`.
-- `MCP_HOST`: host de bind. Padrão: `0.0.0.0`.
-- `SEMA_MCP_PUBLIC_BASE_URL`: URL pública HTTPS usada nos metadados OAuth do ChatGPT.
-- `SEMA_MCP_OAUTH_SECRET`: segredo usado para assinar access/refresh tokens OAuth.
-- `SEMA_MCP_OAUTH_PASSCODE`: fallback local/laboratorio; em MCP publico ou `production`, bloqueia o boot.
-- `SEMA_MCP_PROJECT_ROOTS`: raizes permitidas para projetos, separadas por `;`.
-- `SEMA_MCP_CORS_ORIGIN`: origem CORS permitida, lista separada por `;`. Nao use `*` em MCP publico ou `production`.
-- `SEMA_SUPABASE_URL`: URL do control plane Supabase usado para OAuth e billing.
-- `SEMA_SUPABASE_ANON_KEY` ou `SEMA_SUPABASE_PUBLISHABLE_KEY`: chave publica do Supabase para RPCs de OAuth/billing.
-- `SEMA_MCP_BILLING_DISABLED`: somente laboratorio local; em MCP publico ou `production`, bloqueia o boot.
-- `SEMA_MCP_MAX_CONTRACT_FILE_BYTES`: limite por contrato `.sema` enviado por snapshot ou conteudo inline. Padrao: `262144`.
-- `SEMA_MCP_MAX_CODE_FILE_BYTES`: limite por arquivo de codigo selecionado enviado por snapshot. Padrao: `262144`.
-- `SEMA_MCP_MAX_DOC_FILE_BYTES`: limite por arquivo de documentacao enviado por snapshot. Padrao: `262144`.
-- `SEMA_MCP_MAX_CODE_FILES`: limite de arquivos de codigo selecionado por snapshot. Padrao: `80`.
-- `SEMA_MCP_MAX_DOC_FILES`: limite de arquivos de documentacao por snapshot. Padrao: `80`.
-
-Exemplo operacional privado:
-
-```bash
-MCP_PORT=3333 \
-SEMA_MCP_PUBLIC_BASE_URL="https://sema.exemplo.com" \
-SEMA_MCP_OAUTH_SECRET="segredo-longo-para-oauth" \
-SEMA_SUPABASE_URL="https://projeto.supabase.co" \
-SEMA_SUPABASE_PUBLISHABLE_KEY="sb_publishable_..." \
-SEMA_MCP_PROJECT_ROOTS="/srv/sema/projetos" \
-SEMA_MCP_MAX_CONTRACT_FILE_BYTES=262144 \
-SEMA_MCP_MAX_CODE_FILE_BYTES=262144 \
-SEMA_MCP_MAX_DOC_FILE_BYTES=262144
-```
-
-Nunca publique `/mcp` ou `/sse` na internet sem billing habilitado, Supabase de billing configurado, chave comercial bearer por request ou OAuth com conta Sema, raiz restrita e HTTPS no proxy. Nunca registre chaves `sema_mcp_*`, OAuth secret ou passcode em docs publicas, logs, release notes ou screenshots.
-
-O limite de bytes e validado antes de gravar espelhos remotos ou executar contratos inline. Clientes MCP devem respeitar o limite anunciado no schema da ferramenta e dividir snapshots grandes em arquivos focados, sem enviar repositorio inteiro.
-
-## Distribuição
+The public Sema CLI should work without private service credentials.
 
-A Sema não tem repositório público de produto nem GitHub Release pública. O npm fica restrito ao instalador/cliente `@semacode/cli`.
-
-Depois de empacotar ou publicar o instalador, rode:
+Allowed public examples may use placeholders:
 
 ```bash
-node scripts/verificar-distribuicao-publica.mjs --json
+EXAMPLE_API_KEY=replace-me
 ```
 
-Esse check cruza manifestos, npm e CLI local, além de garantir que GitHub Release pública e assets abertos de produto continuam bloqueados.
+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

@@ -0,0 +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.

package/docs/getting-started.md

@@ -0,0 +1,33 @@
+# Installation And First Use
+
+Sema is installed and used as a local CLI.
+
+```bash
+npm install -g @semacode/cli
+sema --version
+sema preflight resumo --json
+```
+
+Proceed only when `preflight` returns `decisao: "use_cli_local"`.
+
+## First Project
+
+```bash
+sema iniciar --template base
+sema validar contratos/*.sema --json
+sema resumo
+```
+
+## Existing Project
+
+```bash
+sema resumo
+sema docs-impacto --intencao "describe the change" --json
+sema inspecionar contratos/example.sema --json
+sema drift contratos/example.sema --escopo modulo --json
+sema impacto contratos/example.sema --alvo sema.example.target --mudanca "describe the change" --json
+```
+
+The public CLI does not require private service credentials.
+
+Support: suporte@otimitare.online

package/docs/i18n.md

@@ -0,0 +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.

package/docs/profiles.md

@@ -0,0 +1,43 @@
+# Profiles
+
+Profiles are local validation layers for domains where syntax alone is not
+enough. They use the same `.sema` DSL and do not create a second language.
+
+## Principle
+
+A profile checks whether a contract is strong enough for a specific kind of
+work. It can require:
+
+- contract-first workflow;
+- domain core fields;
+- required rules, effects, guarantees, and tests;
+- explicit forbidden behavior;
+- evidence before closing the change.
+
+When a profile returns `bloqueado: true`, the artifact is not approved.
+
+## Commands
+
+```bash
+sema profile capabilities --json
+sema profile validar software contratos/example.sema --maturidade production --preset default --json
+sema rule-packs --profile software --json
+```
+
+## Built-In Profiles
+
+- `software`: code, APIs, modules, refactors, persistence, and generated output.
+- `workflow`: automations, queues, webhooks, scheduled jobs, and orchestration.
+- `ops`: deploy plans, rollback, incidents, runbooks, and operational evidence.
+- `legal`: terms, privacy, compliance, risk, and regulated language.
+- `research`: comparisons, uncertainty, evidence, citations, and decisions.
+- `game`: rules, loops, player states, scoring, and playability checks.
+- `author`: creative writing, narrative continuity, cliche review, and style
+  guardrails.
+- `proposal`: commercial proposals, scope clarity, deliverables, constraints,
+  and client-ready wording.
+- `sales`: customer conversation guardrails, escalation, pricing promises, and
+  channel changes.
+
+Profiles are local CLI checks. They do not create or require external service
+accounts.

package/docs/repositories.md

@@ -1,69 +1,27 @@
-# Repository Boundary
+# Repository Boundary
 
-<!-- sema:i18n -->
-> EN: English first.
-> PT: Português depois.
-> ES: Español al final.
+The public Sema repository should contain only the local CLI, runtime packages,
+examples, tests that run locally, and English documentation.
 
-## English
+## Public
 
-Sema is private by default and private end to end, with one npm installation channel for the governed client: `@semacode/cli`. There is no public product repository, no public MCP package surface, no public GitHub Release, and no active `public/` versus `private/` repository split.
-
-The active tree lives at the repository root: `contratos/`, `pacotes/`, `mcp/`, `site/`, `supabase/`, `deploy/`, `docs/`, `scripts/`, and `testes/`.
+- local CLI source
+- contract parser and validators
+- local drift and impact tooling
+- local code generators
+- examples
+- English docs
+- local package scripts
 
-The operating model is:
+## Not Public
 
-- The CLI is distributed through the npm installer/client `@semacode/cli`, then acts as the governed local executor for IDEs: it reads contracts, validates, checks drift, builds AI-first context, and runs `sema preflight resumo --json` against the SEMAS control plane before local action.
-- Local IDEs use the complete CLI and a local key. The agent must run `sema --version`; if missing, it asks the human to install from the Sema panel. Stop unless `decisao=use_cli_local`. Do not use remote MCP, `sema_sync`, `sema_contratos_sincronizar`, or `sema mcp-client` to read a local workspace.
-- The private MCP is the web/chat coordinator: it authenticates remote clients, selects the right server project or mirror, charges SEMAS, decides the required contract/profile flow, and returns the operational verdict.
-- Web chats remain supported because the private MCP keeps a CLI installed on the VPS and runs it against authorized mirrors under `/srv/sema/projetos/...`.
+- private or sensitive operational material
+- real credentials, environment files, or secret inventories
+- private project data or generated private artifacts
 
-Distribution outside the private boundary is allowed only for the governed CLI installer. If a script tries to publish the MCP server, product release assets, secrets, control-plane code, GitHub Release, or any public package outside `@semacode/cli`, it must fail before any artifact is created.
+## Commercial Use
 
-Use the private boundary check:
+The public Sema source may not be copied, rebranded, bundled, or replicated for
+commercial resale without written permission from OtimiTare.
 
-```bash
-npm run repo:verificar-privado
-```
-
-## Português
-
-O Sema é privado por padrao e privado de ponta a ponta, com um canal npm para o cliente governado: `@semacode/cli`. Não existe repositório público de produto, superfície MCP pública como pacote aberto, GitHub Release pública nem divisão ativa entre `public/` e `private/`.
-
-A árvore ativa vive na raiz do repositório: `contratos/`, `pacotes/`, `mcp/`, `site/`, `supabase/`, `deploy/`, `docs/`, `scripts/` e `testes/`.
-
-O modelo operacional é:
-
-- A CLI é distribuída pelo instalador/cliente npm `@semacode/cli` e depois atua como executor local governado para IDEs: lê contratos, valida, mede drift, monta contexto IA-first e roda `sema preflight resumo --json` contra o control plane de SEMAS antes de agir localmente.
-- IDEs locais usam a CLI completa e uma chave local. O agente deve rodar `sema --version`; se faltar, deve pedir ao humano para instalar pelo painel Sema. Pare se `decisao` não for `use_cli_local`. Não use MCP remoto, `sema_sync`, `sema_contratos_sincronizar` nem `sema mcp-client` para ler workspace local.
-- O MCP privado é o coordenador web/chat: autentica clientes remotos, escolhe o projeto ou espelho de servidor correto, cobra SEMAS, decide o fluxo de contrato/profile obrigatório e devolve o veredito operacional.
-- Chats web continuam suportados porque o MCP privado mantém uma CLI instalada na VPS e executa contra espelhos autorizados em `/srv/sema/projetos/...`.
-
-Distribuição fora da fronteira privada só é permitida para o instalador CLI governado. Se algum script tentar publicar o servidor MCP, assets de release de produto, segredos, control plane, GitHub Release ou qualquer pacote público fora de `@semacode/cli`, ele deve falhar antes de criar qualquer artefato.
-
-Use a checagem de fronteira privada:
-
-```bash
-npm run repo:verificar-privado
-```
-
-## Español
-
-Sema es privado de punta a punta, con un canal npm para el cliente gobernado: `@semacode/cli`. No existe repositorio público de producto, superficie MCP pública como paquete abierto, GitHub Release pública ni división activa entre `public/` y `private/`.
-
-El árbol activo vive en la raíz del repositorio: `contratos/`, `pacotes/`, `mcp/`, `site/`, `supabase/`, `deploy/`, `docs/`, `scripts/` y `testes/`.
-
-El modelo operativo es:
-
-- La CLI se distribuye por el instalador/cliente npm `@semacode/cli` y luego actúa como ejecutor local gobernado para IDEs: lee contratos, valida, mide drift, prepara contexto IA-first y ejecuta `sema preflight resumo --json` contra el control plane de SEMAS antes de actuar localmente.
-- Las IDEs locales usan la CLI completa y una clave local. El agente debe ejecutar `sema --version`; si falta, debe pedir al humano que instale desde el panel Sema. Para si `decisao` no es `use_cli_local`. No uses el MCP remoto, `sema_sync`, `sema_contratos_sincronizar` ni `sema mcp-client` para leer un workspace local.
-- El MCP privado es el coordinador web/chat: autentica clientes remotos, elige el proyecto o espejo de servidor correcto, cobra SEMAS, decide el flujo obligatorio de contrato/profile y devuelve el veredicto operativo.
-- Los chats web siguen soportados porque el MCP privado mantiene una CLI instalada en la VPS y la ejecuta contra espejos autorizados en `/srv/sema/projetos/...`.
-
-La distribución fuera de la frontera privada solo se permite para el instalador CLI gobernado. Si un script intenta publicar el servidor MCP, assets de release de producto, secretos, control plane, GitHub Release o cualquier paquete público fuera de `@semacode/cli`, debe fallar antes de crear cualquier artefacto.
-
-Usa la verificación de frontera privada:
-
-```bash
-npm run repo:verificar-privado
-```
+Support: suporte@otimitare.online

package/docs/rollback.md

@@ -1,24 +1,13 @@
-# Rollback Privado
+# Rollback Boundary
 
-<!-- sema:i18n -->
-> EN: English first.
-> PT: Português depois, com acentos preservados.
-> ES: Español al final.
+Public Sema rollback guidance is limited to local files and npm package
+artifacts.
 
-## English
+For public package work:
 
-Rollback is private and must preserve traceability. If the MCP runtime breaks, restore the previous package or dist files, restart `sema-mcp.service`, and verify `/healthz`.
+1. Keep the previous tarball until the new one passes smoke tests.
+2. Rebuild with `npm run cli:empacotar-publica`.
+3. Re-run `node scripts/testar-pacote-cli-publico.mjs`.
 
-Do not rewrite customer mirrors blindly. Project mirrors under `/srv/sema/projetos/...` must only be reverted when the failed change touched that mirror.
-
-## Português
-
-Rollback é privado e precisa preservar rastreabilidade. Se o runtime MCP quebrar, restaure o pacote ou os arquivos `dist` anteriores, reinicie `sema-mcp.service` e valide `/healthz`.
-
-Não reescreva espelhos de clientes às cegas. Espelhos de projeto em `/srv/sema/projetos/...` só devem ser revertidos quando a mudança com falha tiver tocado aquele espelho.
-
-## Español
-
-El rollback es privado y debe preservar trazabilidad. Si el runtime MCP falla, restaura el paquete o los archivos `dist` anteriores, reinicia `sema-mcp.service` y valida `/healthz`.
-
-No reescribas espejos de clientes a ciegas. Los espejos de proyecto en `/srv/sema/projetos/...` solo deben revertirse cuando el cambio fallido haya tocado ese espejo.
+Do not publish private or sensitive operational rollback material in this
+repository.

package/docs/security.md

@@ -0,0 +1,24 @@
+# Security
+
+The public Sema repository must not contain private or sensitive operational
+material.
+
+Do not publish:
+
+- real credentials or secret material;
+- private data or internal operational artifacts.
+
+Placeholder examples are allowed:
+
+```bash
+EXAMPLE_KEY=replace-me
+```
+
+If a real credential is exposed in code, docs, logs, screenshots, packages, or
+Git history:
+
+1. Rotate it immediately.
+2. Remove it from the affected artifact.
+3. Rebuild and rescan before publishing.
+
+Official support: suporte@otimitare.online

package/docs/support.md

@@ -0,0 +1,8 @@
+# Support
+
+Official Sema support email: suporte@otimitare.online
+
+OtimiTare website: https://otimitare.online
+
+Do not publish private or sensitive support routing material in the public Sema
+repository.

package/docs/syntax.md

@@ -0,0 +1,128 @@
+<!-- sema:agent-entrypoint:start -->
+# Sema Syntax for AI Agents
+
+Use this file as a compact reference before creating or fixing `.sema` contracts.
+
+## Golden Rule
+
+Contract comes before code. Before writing `.sema`, read the local examples in `exemplos/`.
+
+## Minimal Example
+
+```sema
+module app.example {
+  entity Item {
+    fields {
+      id: Id
+      name: Texto
+      active: Booleano
+    }
+  }
+
+  task create_item {
+    input {
+      name: Texto required
+    }
+    output {
+      item: Item
+    }
+    rules {
+      name deve_ser preenchido
+    }
+    effects {
+      persistencia Item
+      auditoria item_created
+    }
+    guarantees {
+      item existe
+    }
+    tests {
+      caso "creates valid item" {
+        given { name: "Item" }
+        expect { sucesso: verdadeiro }
+      }
+    }
+  }
+}
+```
+
+## Common Blocks
+
+- `docs`: module summary and notes.
+- `entity`: domain model.
+- `task`: governed operation.
+- `input` and `output`: input and output contracts.
+- `rules`: validations and business rules.
+- `effects`: persistence, reads, events, audit, and external calls.
+- `guarantees`: what the task must provide after success.
+- `error`: named errors and messages.
+- `tests`: minimal behavior examples.
+- `route`: public surface linked to a task.
+- `impl` and `vinculos`: links between the contract and real code.
+
+## Canonical `use` and `impl` Origins
+
+Use these origins before inventing a new one:
+
+- `ts` ou `typescript`
+- `js` ou `javascript`
+- `py` ou `python`
+- `dart`
+- `lua`
+- `cs` ou `dotnet`
+- `java`
+- `go`
+- `rust`
+- `cpp`
+
+Examples:
+
+```sema
+use javascript app.web.expenses
+
+impl {
+  js: src.app.saveExpense
+}
+```
+
+`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.
+
+## Small Canonical Lists
+
+- `effects`: `persistencia`, `consulta`, `evento`, `auditoria`, `db.write`, `queue.publish`, `fs.write`, `network.egress`, `secret.read`, `shell.exec`.
+- `audit.motivo`: `obrigatorio`, `opcional`, `dispensado`.
+
+## Contract Size
+
+- up to 300 lines: healthy
+- 301-500 lines: diagnostic warning, plan a split
+- above 500: blocks creation, edits, drift, finalization, generation, and snapshots
+- split by real domain/capability, such as `expenses_entry.sema`, `expenses_totals.sema`, `expenses_persistence.sema`
+- never use `parte_1`, `parte_2`, `part_3`, or equivalent names
+- do not remove `guarantees`, `tests`, `authz`, `dados`, or `vinculos` just to fit under the limit
+- multiple `.sema` contracts may govern the same code file through `vinculos`; this is expected
+
+## JavaScript Is Supported
+
+The CLI supports JavaScript generation:
+
+```bash
+sema compilar contratos/orders.sema --alvo javascript --saida ./generated/javascript
+```
+
+The project can also generate TypeScript, Python, Dart, Lua, HTML, and CSS when those targets are enabled in `sema.config.json`.
+
+## Support Files
+
+- `AGENTS.md`: required agent rules.
+- `SEMA_BOOT.md`: first read for every AI agent.
+- `SEMA_SMALL_MODEL.md`: short version for weaker agents.
+- `AGENT_CONTEXT_PACK.json`: structured agent context pack.
+- `SEMA_INDEX.json`: project index.
+- `docs/commands.md`: command catalog, gates, and `--saida` rule.
+- `exemplos/`: official DSL examples.
+
+If an AI agent does not know which shape to use, it must open `exemplos/calculadora.sema`, `exemplos/crud_simples.sema`, `exemplos/pagamento.sema`, or `exemplos/tratamento_erro.sema` before inventing syntax.
+
+Platform policy: O Sema governa contrato, escopo, drift, evidência e qualidade do projeto. Ele não pede, não autoriza e não contorna políticas da plataforma, termos de uso, permissões, segurança ou leis.
+<!-- sema:agent-entrypoint:end -->

package/docs/testing.md

@@ -0,0 +1,17 @@
+# Testing
+
+Public Sema tests should run locally.
+
+Recommended checks:
+
+```bash
+npm run build
+node pacotes/cli/dist/index.js --help
+node pacotes/cli/dist/index.js preflight resumo --json
+node pacotes/cli/dist/index.js validar exemplos/calculadora.sema --json
+npm run cli:empacotar-publica
+node scripts/testar-pacote-cli-publico.mjs
+```
+
+Do not require private or sensitive operational material for public test
+evidence.

package/docs/vocabulary.md

@@ -0,0 +1,28 @@
+# Sema Vocabulary
+
+Use consistent English prose in public docs while preserving technical
+identifiers.
+
+## Canonical Concepts
+
+- semantic contract
+- drift
+- impact map
+- governed code
+- traceability
+- preflight
+- finalization
+- evidence
+- local CLI
+
+## Do Not Translate
+
+- commands: `sema validar`, `sema drift`, `sema impacto`
+- files: `AGENTS.md`, `SEMA_BOOT.md`, `SEMA_INDEX.json`
+- DSL keywords: `task`, `input`, `output`, `rules`, `effects`, `guarantees`
+- package names: `@semacode/cli`
+- code symbols and environment variable names
+
+## Public Support
+
+Use suporte@otimitare.online for support references.

package/node_modules/@sema/gerador-css/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema/gerador-css",
-  "version": "1.5.48",
+  "version": "1.5.53",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts"

package/node_modules/@sema/gerador-dart/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema/gerador-dart",
-  "version": "1.5.48",
+  "version": "1.5.53",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts"

package/node_modules/@sema/gerador-html/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema/gerador-html",
-  "version": "1.5.48",
+  "version": "1.5.53",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts"

package/node_modules/@sema/gerador-javascript/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema/gerador-javascript",
-  "version": "1.5.48",
+  "version": "1.5.53",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts"

package/node_modules/@sema/gerador-lua/dist/index.js

@@ -181,6 +181,16 @@ function gerarPreparacaoSaida(task) {
             ajustes.push(`  saida["diacriticos_preservados"] = true`);
         }
     }
+    if (camposEntrada.has("drift")) {
+        precondicoes.push(`  local drift_texto = tostring(entrada["drift"] or ""):lower()`);
+        precondicoes.push(`  if drift_texto:find("sucesso:false", 1, true) or drift_texto:find("vinculos_quebrados", 1, true) or drift_texto:find("rotas_divergentes", 1, true) then return nil end`);
+    }
+    if (campoArtefatoI18n) {
+        precondicoes.push(`  local artefato_responsivo = tostring(entrada[${JSON.stringify(campoArtefatoI18n)}] or "")`);
+        precondicoes.push(`  local scroll_width = tonumber(artefato_responsivo:match("scrollWidth%s*(%d+)"))`);
+        precondicoes.push(`  local client_width = tonumber(artefato_responsivo:match("clientWidth%s*(%d+)"))`);
+        precondicoes.push(`  if scroll_width ~= nil and client_width ~= nil and scroll_width > client_width then return nil end`);
+    }
     for (const garantia of task.garantiasEstruturadas) {
         if (garantia.tipo === "pertencimento" && garantia.valores && camposSaida.has(garantia.alvo)) {
             ajustes.push(`  saida[${JSON.stringify(garantia.alvo)}] = ${formatarValorLua(garantia.valores[0] ?? "", camposSaida, "saida")}`);