@semacode/cli 1.5.55 → 2.0.0

package/docs/cli.md

@@ -1,8 +1,10 @@
 # Sema CLI
 
-Sema is now a local CLI distribution. The public package reads the workspace on
-the user's machine, validates `.sema` contracts, checks drift, maps impact, and
-generates code without requiring external service credentials.
+Sema is a Codex-native local CLI distribution. The public package reads the
+workspace on the user's machine, validates `.sema` contracts, checks drift,
+maps impact, and generates code without login, user authorization, license
+activation, tokens, credits, billing services, a control panel, or external
+service credentials.
 
 Support: suporte@otimitare.online
 
@@ -21,14 +23,25 @@ npm run build
 node pacotes/cli/dist/index.js --help
 ```
 
+## Codex Setup
+
+`AGENTS.md` is the official Sema entrypoint for Codex. Create or refresh it from
+the local CLI:
+
+```bash
+sema sync-codex --json
+```
+
+Codex automatically loads `AGENTS.md` as repository guidance. Sema is an
+independent product and is not affiliated with or endorsed by OpenAI.
+
 ## Required Local Flow
 
-Agents and humans should use the same local sequence before changing governed
+Codex and humans should use the same local sequence before changing governed
 code, contracts, workflows, release scripts, or operational docs:
 
 ```bash
 sema --version
-sema preflight resumo --json
 sema resumo
 sema docs-impacto --intencao "describe the change" --json
 sema inspecionar contratos/example.sema --json
@@ -36,9 +49,8 @@ sema drift contratos/example.sema --escopo modulo --json
 sema impacto contratos/example.sema --alvo sema.example.target --mudanca "describe the change" --json
 ```
 
-Continue only when `preflight` returns `decisao: "use_cli_local"`. The public
-CLI preflight is an offline local gate; it does not check credits, install
-keys, or call an external control surface.
+Commands run directly against the local workspace. If `sema --version` fails,
+install or repair the npm package; there is no separate authorization gate.
 
 ## Core Commands
 
@@ -52,6 +64,7 @@ keys, or call an external control surface.
 - `sema compilar`: generate code from contracts.
 - `sema verificar`: run the final local verification bundle.
 - `sema contexto-ia`: build local AI context from a contract.
+- `sema sync-codex`: create or refresh the official `AGENTS.md` entrypoint.
 
 ## Public Boundary
 

package/docs/commands.md

@@ -1,13 +1,12 @@
 <!-- sema:agent-entrypoint:start -->
 # Sema Command Catalog
 
-Use this file when an AI agent does not know which command to run. A Sema command is an operational gate; do not replace it with a Markdown report.
+Use this file when Codex does not know which command to run. A Sema command is an operational gate; do not replace it with a Markdown report.
 
 ## Minimum Local Flow
 
 ```bash
 sema --version
-sema preflight resumo --json
 sema resumo
 sema docs-impacto --intencao "<acao>" --json
 ```
@@ -16,7 +15,7 @@ Then read every required doc returned by `docs-impacto`.
 
 ## Contract and Discovery
 
-- `sema iniciar --template <template>`: creates a new Sema project with a contract, docs, examples, and AI kit.
+- `sema iniciar --template <template> [--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.
@@ -49,23 +48,23 @@ 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`, `php`.
+- Origins for `use` and `impl`: `ts/typescript`, `js/javascript`, `py/python`, `dart`, `lua`, `cs/dotnet`, `java`, `go`, `rust`, `cpp`.
 - 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`.
 
 `sema compilar --alvo javascript` is a generation target. `impl { js: ... }` is the live-code origin. Do not swap one for the other.
 
-## AI and Context
+## Codex and Context
 
-- `sema ajuda-ia`: short guidance for agents.
+- `sema ajuda-ia`: short guidance for Codex.
 - `sema starter-ia`: operational starter.
 - `sema contexto-ia <arquivo.sema> --saida <dir> --json`: AI context package.
 - `sema prompt-curto <arquivo-ou-pasta> --json`: compact prompt.
-- `sema sync-ai-entrypoints --json`: synchronizes AGENTS, boot, pack, and local docs.
+- `sema sync-codex --json`: synchronizes the official Codex entrypoint and local support docs.
 - `sema instalar-exemplos --json`: installs official examples in the workspace.
 - `sema exemplos-prompt-ia`: shows prompt examples, not `.sema` examples.
 
-## Profiles e Author
+## Profiles and Author
 
 - `sema author iniciar|validar|briefing|revisar-cliches|validar-narrativa|validar-proibicoes`: governs authorial writing.
 - `sema profile validar <software|workflow|ops|game|legal|research|redacao|propostas|conversas> <arquivo> --json`: validates an artifact by profile.
@@ -81,10 +80,10 @@ Ready UI rule: if the task generates an app, site, dashboard, form, or static HT
 - Do not use an external workspace source to inspect a local workspace when `sema --version` works.
 - Do not search the entire disk for `.sema` syntax; use `exemplos/`, `docs/syntax.md`, and this catalog.
 - Do not stop after `sema compilar` if the contract target files still do not exist.
-- Do not replace `sema compilar` with `sema testar` when Guard asks for Sema Code.
+- 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 `sema drift --json` returned `sucesso:false`, broken link, divergent route, or broken impl.
 - Do not declare a UI responsive without mobile/desktop proof; horizontal scroll at 390px blocks closure.
 
-Governed code policy: Arquivos de codigo gerados ou governados pela Sema devem manter cabecalho curto com modulo de origem, contrato .sema aplicavel e descricao humana. Validacao inline prova apenas o payload enviado; o arquivo fisico ainda precisa de SEMA-GOVERNED para orientar a proxima IA. Codigo governado avisa acima de 1000 linhas e bloqueia acima de 2000. Contrato .sema avisa acima de 300 linhas e bloqueia criacao, edicao, drift, finalizacao, geracao e snapshot acima de 500. O split de .sema deve ser por dominio/capacidade, nunca parte_1/parte_2; varios contratos podem governar o mesmo arquivo de codigo via vinculos. Sema Codigo deve preservar essa rastreabilidade em cabecalhos e saidas geradas. Documentacao Markdown nao entra nesse limite de codigo; continua governada por docs-impacto, limite de bytes e verificacao de segredos. Payload inline acima de 262144 caracteres nao e caso de aumentar timeout: divida por responsabilidade ou use anexo/caminho de servidor autorizado.
+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.
 <!-- sema:agent-entrypoint:end -->

package/docs/deploy.md

@@ -1,13 +1,36 @@
 # Deployment Boundary
 
-The public Sema repository only documents public local CLI release checks.
+The public Sema repository documents two coordinated release surfaces: the
+local npm CLI and the Codex bootstrap skill. The skill remains a separate,
+explicit Codex installation and is never injected by npm lifecycle scripts.
 
-Public release work should focus on the local CLI package:
+Run the complete public gate:
 
 ```bash
 npm run build
-npm run cli:empacotar-publica
-node scripts/testar-pacote-cli-publico.mjs
+npm run status:check
+npm run repo:verificar-publico
+npm run plugin:testar-codex
+npm test
+npm run release:verificar-drift
+npm run release:preparar-publica
+npm run release:publicar-npm-dry-run
 ```
 
+The plugin smoke installs the repo marketplace into an isolated `CODEX_HOME`,
+installs `sema@sema`, compares the cached skill with the versioned source, and
+proves no Sema MCP server was registered. Plugin and CLI versions must match
+before the commit is pushed. The release command itself runs the full test suite
+and project-wide Sema drift gate; these are not optional manual preliminaries.
+
+Push the commit containing `.agents/plugins/marketplace.json` and
+`plugins/sema/` before telling users to install from `gerlanss/Sema`. Publish
+the npm package only after the tarball smoke passes. After npm publication, run
+`npm run release:verificar-distribuicao` to verify the registry and live GitHub
+state. That final verifier also requires the remote GitHub HEAD to match the
+local commit, installs `sema@sema` from `gerlanss/Sema` in an isolated
+`CODEX_HOME`, compares the remote skill with the versioned source, and proves
+that the remote plugin registers no Sema MCP. The current contract does not
+permit creating a GitHub Release or release asset.
+
 Do not publish private or sensitive operational material in this repository.

package/docs/documentation.md

@@ -1,6 +1,6 @@
 # Documentation Governance
 
-Documentation is part of every governed change. An agent must use
+Documentation is part of every governed change. Codex must use
 `sema docs-impacto` before editing contracts, code, operational docs, workflows,
 profiles, generated artifacts, or release material.
 
@@ -16,7 +16,7 @@ The result lists:
 
 - `leituraObrigatoria`: files that must be read before the change;
 - `docsAusentes`: missing docs that block the change;
-- `docsCriadas`: generated draft docs that must be completed by the agent;
+- `docsCriadas`: generated draft docs that must be completed by Codex;
 - `bloqueios`: blocking diagnostics.
 
 Before closing the change, prove the required docs were read:

package/docs/env.md

@@ -1,6 +1,8 @@
 # Environment
 
-The public Sema CLI should work without private service credentials.
+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:
 

package/docs/getting-started.md

@@ -4,11 +4,30 @@ Sema is installed and used as a local CLI.
 
 ```bash
 npm install -g @semacode/cli
+codex plugin marketplace add gerlanss/Sema
+codex plugin add sema@sema
+```
+
+Open a new Codex task in the target repository so the newly installed `$sema`
+skill is loaded, then ask it to initialize Sema. Existing tasks do not refresh
+their skill catalog. After bootstrap, `AGENTS.md` becomes the automatic protocol
+for subsequent tasks.
+
+Then verify the local engine:
+
+```bash
 sema --version
-sema preflight resumo --json
+sema resumo
 ```
 
-Proceed only when `preflight` returns `decisao: "use_cli_local"`.
+The CLI is ready when `sema --version` succeeds. No Sema login, user
+authorization, activation key, product-license check, token, credits, billing
+service, or control panel is involved.
+
+The Codex skill is required for first contact with a project that does not yet
+have Sema. It only bootstraps the local CLI and generates the repository's
+`AGENTS.md`; that file becomes the automatic workspace protocol afterward.
+Plugin installation is explicit and does not happen from npm lifecycle scripts.
 
 ## First Project
 
@@ -18,6 +37,10 @@ sema validar contratos/*.sema --json
 sema resumo
 ```
 
+`sema iniciar` preserves existing project files and refuses symlink or junction
+escapes. The bootstrap skill never uses `--force`; explicit overwrite remains a
+human decision.
+
 ## Existing Project
 
 ```bash
@@ -28,6 +51,7 @@ 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.
+The public CLI does not require private service credentials or an external
+request before local commands run.
 
 Support: suporte@otimitare.online

package/docs/repositories.md

@@ -1,7 +1,8 @@
 # Repository Boundary
 
-The public Sema repository should contain only the local CLI, runtime packages,
-examples, tests that run locally, and English documentation.
+The public Sema repository should contain only the Codex-native local CLI, the
+first-contact Codex skill, runtime packages, examples, tests that run locally,
+and English documentation.
 
 ## Public
 
@@ -12,12 +13,27 @@ examples, tests that run locally, and English documentation.
 - examples
 - English docs
 - local package scripts
+- `AGENTS.md` as the official Codex entrypoint
+- the official Sema skill as a thin bootstrap before `AGENTS.md` exists
+- the repo marketplace that installs that skill explicitly
 
 ## Not Public
 
 - private or sensitive operational material
 - real credentials, environment files, or secret inventories
 - private project data or generated private artifacts
+- runtime authorization, activation, billing, credit, token, or panel gates
+- product-specific entrypoint files for AI clients other than Codex
+- MCP servers, remote workspace bridges, or duplicated governance inside the
+  bootstrap skill
+
+The CLI must run directly against the local workspace without login, user
+authorization, a product-license check, activation key, credits, token, billing
+service, or control panel.
+
+Sema is an independent product and is not affiliated with or endorsed by
+OpenAI. Codex-native is Sema's official product direction, not an official
+OpenAI program or submission.
 
 ## Commercial Use
 

package/docs/rollback.md

@@ -1,13 +1,31 @@
 # Rollback Boundary
 
-Public Sema rollback guidance is limited to local files and npm package
-artifacts.
+Public rollback covers both the npm CLI and the separately installed Codex
+bootstrap skill.
 
-For public package work:
+For a failed pre-publication candidate:
 
 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`.
+2. Revert the plugin source, marketplace manifest, CLI source, and versions to
+   the last known-good commit.
+3. Re-run `npm run release:preparar-publica`.
+
+If a bad commit was already pushed, revert it with a normal Git revert and push
+the corrective commit. Refresh the marketplace and reinstall the skill:
+
+```bash
+codex plugin marketplace upgrade sema
+codex plugin remove sema@sema
+codex plugin add sema@sema
+```
+
+Open a new Codex task before validating the reinstalled skill. Already-open
+tasks keep the plugin/skill catalog they started with.
+
+If a bad npm version was published, do not overwrite it. Publish a corrected
+version and direct users to that version. Verify the final registry/GitHub state
+with `npm run release:verificar-distribuicao`. Do not create a GitHub Release or
+asset as a rollback shortcut while the release contract blocks that surface.
 
 Do not publish private or sensitive operational rollback material in this
 repository.

package/docs/security.md

@@ -3,6 +3,14 @@
 The public Sema repository must not contain private or sensitive operational
 material.
 
+Local Sema execution does not need a credential, login, activation key, license
+token, billing token, or control-panel session. Do not introduce one as a
+condition for reading or governing a local workspace.
+
+The official Codex bootstrap skill contains instructions only. It must not
+bundle an MCP server, app connector, remote workspace bridge, credential flow,
+or a second copy of the repository governance that belongs in `AGENTS.md`.
+
 Do not publish:
 
 - real credentials or secret material;

package/docs/syntax.md

@@ -1,5 +1,5 @@
 <!-- sema:agent-entrypoint:start -->
-# Sema Syntax for AI Agents
+# Sema Syntax for Codex
 
 Use this file as a compact reference before creating or fixing `.sema` contracts.
 
@@ -74,7 +74,6 @@ Use these origins before inventing a new one:
 - `go`
 - `rust`
 - `cpp`
-- `php`
 
 Examples:
 
@@ -105,7 +104,7 @@ impl {
 
 ## JavaScript Is Supported
 
-The CLI supports JavaScript and PHP generation:
+The CLI supports JavaScript generation:
 
 ```bash
 sema compilar contratos/orders.sema --alvo javascript --saida ./generated/javascript
@@ -115,15 +114,15 @@ The project can also generate TypeScript, Python, PHP, Dart, Lua, HTML, and CSS
 
 ## 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.
+- `AGENTS.md`: official Codex repository rules, loaded automatically.
+- `SEMA_BOOT.md`: first Sema read for Codex.
+- `SEMA_SMALL_MODEL.md`: compact guidance for a small context budget.
+- `AGENT_CONTEXT_PACK.json`: structured Codex 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.
+If Codex 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.
+Platform policy: Sema governs project contracts, scope, drift, evidence, and quality. It never bypasses platform policies, permissions, security controls, terms, or laws.
 <!-- sema:agent-entrypoint:end -->

package/docs/testing.md

@@ -6,12 +6,23 @@ Recommended checks:
 
 ```bash
 npm run build
+npm run status:check
+npm run repo:verificar-publico
+npm run plugin:testar-codex
 node pacotes/cli/dist/index.js --help
-node pacotes/cli/dist/index.js preflight resumo --json
+node pacotes/cli/dist/index.js --version
+node pacotes/cli/dist/index.js resumo exemplos/calculadora.sema --micro --json
 node pacotes/cli/dist/index.js validar exemplos/calculadora.sema --json
-npm run cli:empacotar-publica
-node scripts/testar-pacote-cli-publico.mjs
+npm run release:preparar-publica
+npm run release:verificar-drift
 ```
 
 Do not require private or sensitive operational material for public test
-evidence.
+evidence. The public-package smoke must also reject the removed authorization
+command, legacy gate markers, any stale billing artifact, secrets, and broken
+encoding in every published document. The plugin smoke must validate the repo
+marketplace, manifest version, installed skill copy, and absence of Sema MCP.
+After push and npm publication, `npm run release:verificar-distribuicao` must
+repeat that installation from the remote `gerlanss/Sema` marketplace and prove
+that GitHub HEAD, the installed skill, and npm 2.0.0 all describe the same
+release.

package/docs/vocabulary.md

@@ -10,7 +10,8 @@ identifiers.
 - impact map
 - governed code
 - traceability
-- preflight
+- Codex-native
+- local runtime
 - finalization
 - evidence
 - local CLI

package/package.json

@@ -1,18 +1,26 @@
 {
   "name": "@semacode/cli",
-  "version": "1.5.55",
-  "description": "Local semantic governance CLI for AI agents: contracts, drift, impact, documentation gates, and code generation.",
+  "version": "2.0.0",
+  "description": "Codex-native local semantic governance CLI for contracts, drift, impact, documentation gates, and code generation.",
   "type": "module",
   "icon": "logo.png",
   "license": "SEE LICENSE IN LICENSE",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/gerlanss/Sema.git"
+  },
   "homepage": "https://otimitare.online",
   "bugs": {
-    "url": "https://otimitare.online",
+    "url": "https://github.com/gerlanss/Sema/issues",
     "email": "suporte@otimitare.online"
   },
   "keywords": [
     "sema",
     "ai",
+    "codex",
+    "ai-agents",
+    "semantic-governance",
+    "local-first",
     "contracts",
     "governance",
     "backend",
@@ -39,16 +47,16 @@
     "LICENSE"
   ],
   "dependencies": {
-    "@sema/nucleo": "1.5.55",
-    "@sema/gerador-dart": "1.5.55",
-    "@sema/gerador-lua": "1.5.55",
-    "@sema/gerador-python": "1.5.55",
-    "@sema/gerador-typescript": "1.5.55",
-    "@sema/gerador-javascript": "1.5.55",
-    "@sema/gerador-html": "1.5.55",
-    "@sema/gerador-css": "1.5.55",
+    "@sema/nucleo": "1.5.53",
+    "@sema/gerador-dart": "1.5.53",
+    "@sema/gerador-lua": "1.5.53",
+    "@sema/gerador-python": "1.5.53",
+    "@sema/gerador-typescript": "1.5.53",
+    "@sema/gerador-javascript": "1.5.53",
+    "@sema/gerador-html": "1.5.53",
+    "@sema/gerador-css": "1.5.53",
     "@sema/gerador-php": "1.5.55",
-    "@sema/padroes": "1.5.55",
+    "@sema/padroes": "1.5.53",
     "typescript": "^5.8.3"
   },
   "bundledDependencies": [

package/dist/billing/index.d.ts

@@ -1,17 +0,0 @@
-export interface PreflightCliOutput {
-    comando: "preflight";
-    surface: "local_cli";
-    autorizado: boolean;
-    decisao: "use_cli_local" | "blocked";
-    filesystem: "local_available";
-    origemCobranca: "local_only";
-    operationCode: string;
-    toolName: string;
-    erro?: string;
-}
-export declare function executarPreflightCli(params: {
-    comandoCli: string;
-    args?: string[];
-    projectId?: string | null;
-}): Promise<PreflightCliOutput>;
-export declare function comandoPreflightCli(args: string[], json: boolean): Promise<number>;

package/dist/billing/index.js

@@ -1,74 +0,0 @@
-// SEMA-GOVERNED: sema.governanca_ia_contexto
-// Descricao: preflight local-only da CLI publica.
-import { obterOpcao, obterPosicionais, possuiFlag } from "../cliArgs.js";
-const OPERATION_CODE_BY_CLI_COMMAND = {
-    resumo: "tool.sema_resumo",
-    validar: "tool.sema_validar",
-    ir: "tool.sema_ir",
-    inspecionar: "tool.sema_inspecionar",
-    drift: "drift.module",
-    impacto: "default.operation",
-    verificar: "verify.full",
-};
-function normalizarComandoCli(comandoCli) {
-    return comandoCli.trim().replace(/^sema\s+/i, "").split(/\s+/)[0]?.toLowerCase() || "default";
-}
-function resolverOperationCodeCli(comandoCli, args) {
-    const explicito = obterOpcao(args, "--operation-code");
-    if (explicito)
-        return explicito;
-    const comando = normalizarComandoCli(comandoCli);
-    if (comando === "drift" && obterOpcao(args, "--escopo") === "projeto") {
-        return "drift.project";
-    }
-    return OPERATION_CODE_BY_CLI_COMMAND[comando] ?? "default.operation";
-}
-function resolverToolNameCli(comandoCli) {
-    return `sema_cli_${normalizarComandoCli(comandoCli).replace(/[^a-z0-9_]+/g, "_")}`;
-}
-export async function executarPreflightCli(params) {
-    const args = params.args ?? [];
-    const comandoCli = params.comandoCli || "default";
-    const operationCode = resolverOperationCodeCli(comandoCli, args);
-    const toolName = resolverToolNameCli(comandoCli);
-    void params.projectId;
-    return {
-        comando: "preflight",
-        surface: "local_cli",
-        autorizado: true,
-        decisao: "use_cli_local",
-        filesystem: "local_available",
-        origemCobranca: "local_only",
-        operationCode,
-        toolName,
-    };
-}
-export async function comandoPreflightCli(args, json) {
-    if (possuiFlag(args, "--help") || possuiFlag(args, "-h")) {
-        console.log([
-            "Usage: sema preflight [command] [--operation-code <code>] [--json]",
-            "",
-            "Checks the local CLI surface. Public Sema is local-only and does not call external services.",
-            "If this command returns decisao=use_cli_local, continue with local CLI commands.",
-        ].join("\n"));
-        return 0;
-    }
-    const posicionais = obterPosicionais(args);
-    const comandoCli = obterOpcao(args, "--comando") ?? posicionais[0] ?? "resumo";
-    const resultado = await executarPreflightCli({
-        comandoCli,
-        args,
-        projectId: obterOpcao(args, "--project-id") ?? null,
-    });
-    if (json) {
-        console.log(JSON.stringify(resultado, null, 2));
-    }
-    else if (resultado.autorizado) {
-        console.log(`Sema CLI authorized: ${resultado.operationCode}. Decision: ${resultado.decisao}.`);
-    }
-    else {
-        console.error(`Sema CLI blocked: ${resultado.erro}`);
-    }
-    return resultado.autorizado ? 0 : 1;
-}
-//# sourceMappingURL=index.js.map