@semacode/cli 2.0.1 → 2.1.0

package/docs/profiles.md

@@ -1,43 +1,45 @@
-# 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.
+# 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.
+- `redacao`: editorial and creative writing, narrative structure, voice,
+  clarity, and publication-ready evidence.
+- `propostas`: commercial proposals, scope clarity, deliverables, constraints,
+  and client-ready wording.
+- `conversas`: 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,43 +1,43 @@
-# Repository Boundary
-
-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
-
-- local CLI source
-- contract parser and validators
-- local drift and impact tooling
-- local code generators
-- 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
-
-The public Sema source may not be copied, rebranded, bundled, or replicated for
-commercial resale without written permission from OtimiTare.
-
-Support: suporte@otimitare.online
+# Repository Boundary
+
+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
+
+- local CLI source
+- contract parser and validators
+- local drift and impact tooling
+- local code generators
+- 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
+
+The public Sema source may not be copied, rebranded, bundled, or replicated for
+commercial resale without written permission from OtimiTare.
+
+Support: suporte@otimitare.online

package/docs/rollback.md

@@ -1,31 +1,31 @@
-# Rollback Boundary
-
-Public rollback covers both the npm CLI and the separately installed Codex
-bootstrap skill.
-
-For a failed pre-publication candidate:
-
-1. Keep the previous tarball until the new one passes smoke tests.
-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.
+# Rollback Boundary
+
+Public rollback covers both the npm CLI and the separately installed Codex
+bootstrap skill.
+
+For a failed pre-publication candidate:
+
+1. Keep the previous tarball until the new one passes smoke tests.
+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

@@ -1,32 +1,32 @@
-# Security
-
-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;
-- 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
+# Security
+
+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;
+- 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

@@ -1,8 +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.
+# 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

@@ -110,7 +110,7 @@ The CLI supports JavaScript generation:
 sema compilar contratos/orders.sema --alvo javascript --saida ./generated/javascript
 ```
 
-The project can also generate TypeScript, Python, PHP, Dart, Lua, HTML, and CSS when those targets are enabled in `sema.config.json`.
+The project can also generate TypeScript, Python, PHP, Dart, Lua, HTML, CSS, C#/.NET (`dotnet`), and C++ (`cpp`) when those targets are enabled in `sema.config.json`.
 
 ## Support Files
 

package/docs/testing.md

@@ -1,28 +1,35 @@
-# Testing
-
-Public Sema tests should run locally.
-
-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 --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 release:preparar-publica
-npm run release:verificar-drift
-```
-
-Do not require private or sensitive operational material for public test
-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.1 all describe the same
-release.
+# Testing
+
+Public Sema tests should run locally.
+
+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 --version
+node pacotes/cli/dist/index.js resumo exemplos/calculadora.sema --micro --json
+node pacotes/cli/dist/index.js validar exemplos/calculadora.sema --json
+node pacotes/cli/dist/index.js testar exemplos/calculadora.sema --alvo dotnet --saida .tmp/testing-dotnet
+node pacotes/cli/dist/index.js testar exemplos/calculadora.sema --alvo cpp --saida .tmp/testing-cpp
+npm run release:preparar-publica
+npm run release:verificar-drift
+```
+
+Do not require private or sensitive operational material for public test
+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.1.0 all describe the same
+release.
+
+Native generator evidence is mandatory when changing C#/.NET or C++ support.
+The `dotnet` smoke must compile and execute through the local .NET SDK. The
+`cpp` smoke must compile and execute through GCC, Clang, or MSVC; checking only
+for generated files is not sufficient.

package/docs/vocabulary.md

@@ -1,29 +1,29 @@
-# Sema Vocabulary
-
-Use consistent English prose in public docs while preserving technical
-identifiers.
-
-## Canonical Concepts
-
-- semantic contract
-- drift
-- impact map
-- governed code
-- traceability
-- Codex-native
-- local runtime
-- 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.
+# Sema Vocabulary
+
+Use consistent English prose in public docs while preserving technical
+identifiers.
+
+## Canonical Concepts
+
+- semantic contract
+- drift
+- impact map
+- governed code
+- traceability
+- Codex-native
+- local runtime
+- 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/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
   }
-}
+}