@semacode/cli 2.0.0 → 2.1.0

package/docs/cli.md

@@ -1,72 +1,79 @@
-# Sema CLI
-
-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
-
-## Install
-
-```bash
-npm install -g @semacode/cli
-sema --version
-```
-
-For development inside this repository:
-
-```bash
-npm install
-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
-
-Codex and humans should use the same local sequence before changing governed
-code, contracts, workflows, release scripts, or operational docs:
-
-```bash
-sema --version
-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
-```
-
-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
-
-- `sema iniciar`: create a governed starting point.
-- `sema validar`: validate `.sema` contracts.
-- `sema inspecionar`: inspect the applicable contract surface.
-- `sema drift`: compare contracts and implementation.
-- `sema impacto`: map the blast radius of a planned change.
-- `sema docs-impacto`: identify docs that must be read or updated.
-- `sema finalizar-mudanca`: close the governed change with evidence.
-- `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
-
-Do not publish private or sensitive operational material in public Sema
-artifacts.
+# Sema CLI
+
+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
+
+## Install
+
+```bash
+npm install -g @semacode/cli
+sema --version
+```
+
+For development inside this repository:
+
+```bash
+npm install
+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
+
+Codex and humans should use the same local sequence before changing governed
+code, contracts, workflows, release scripts, or operational docs:
+
+```bash
+sema --version
+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
+```
+
+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
+
+- `sema iniciar`: create a governed starting point.
+- `sema validar`: validate `.sema` contracts.
+- `sema inspecionar`: inspect the applicable contract surface.
+- `sema drift`: compare contracts and implementation.
+- `sema impacto`: map the blast radius of a planned change.
+- `sema docs-impacto`: identify docs that must be read or updated.
+- `sema finalizar-mudanca`: close the governed change with evidence.
+- `sema compilar`: generate code from contracts.
+- `sema testar`: generate, compile, and execute local contract tests, including `dotnet` and `cpp`.
+- `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.
+
+Generation targets are `typescript`, `python`, `php`, `dart`, `lua`,
+`javascript`, `html`, `css`, `dotnet`, and `cpp`. The aliases `cs` and
+`csharp` select `dotnet`; `c++`, `cxx`, and `cc` select `cpp`.
+Native targets are opt-in in `sema.config.json.alvos` for project-wide
+verification because they require local compiler toolchains.
+
+## Public Boundary
+
+Do not publish private or sensitive operational material in public Sema
+artifacts.

package/docs/commands.md

@@ -35,7 +35,7 @@ Honest closure: treat drift JSON as the source of truth. `sucesso:false`, `vincu
 
 ## Sema Code
 
-- `sema compilar <arquivo-ou-pasta> --alvo <typescript|python|php|dart|lua|javascript|html|css> --saida <diretorio>`: generates starter/support artifacts from the contract.
+- `sema compilar <arquivo-ou-pasta> --alvo <typescript|python|php|dart|lua|javascript|html|css|dotnet|cpp> --saida <diretorio>`: generates starter/support artifacts from the contract.
 - `sema testar <arquivo.sema> --alvo <alvo> --saida <diretorio-temporario>`: generates and runs local tests when the target supports it.
 - `sema importar <fonte> <diretorio> --saida <diretorio> --json`: imports a legacy project into initial contracts.
 - `sema renomear-semantico <arquivo-ou-pasta> --de <nome> --para <nome> --json`: helps rename symbols semantically.

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/deploy.md

@@ -1,36 +1,41 @@
-# Deployment Boundary
-
-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.
-
-Run the complete public gate:
-
-```bash
-npm run build
-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.
+# Deployment Boundary
+
+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.
+
+Run the complete public gate:
+
+```bash
+npm run build
+npm run codex:sync-entrypoint
+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
+```
+
+`release:preparar-publica` performs the Codex entrypoint sync before checking
+the public boundary, so a clean clone does not depend on ignored generated
+handshake files left by a previous local 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,39 +1,39 @@
-# Documentation Governance
-
-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.
-
-Public Sema documentation is English and local-only.
-
-## Required Flow
-
-```bash
-sema docs-impacto --intencao "describe the change" --json
-```
-
-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 Codex;
-- `bloqueios`: blocking diagnostics.
-
-Before closing the change, prove the required docs were read:
-
-```bash
-sema finalizar-mudanca \
-  --intencao "describe the change" \
-  --doc-lida README.md \
-  --doc-lida docs/documentation.md \
-  --json
-```
-
-## Public Docs Rules
-
-- Write public docs in English.
-- Keep commands, file paths, package names, environment variable names, and DSL
-  keywords literal.
-- Do not include private or sensitive operational material.
-- Prefer local CLI examples.
-- Point support requests to suporte@otimitare.online.
+# Documentation Governance
+
+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.
+
+Public Sema documentation is English and local-only.
+
+## Required Flow
+
+```bash
+sema docs-impacto --intencao "describe the change" --json
+```
+
+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 Codex;
+- `bloqueios`: blocking diagnostics.
+
+Before closing the change, prove the required docs were read:
+
+```bash
+sema finalizar-mudanca \
+  --intencao "describe the change" \
+  --doc-lida README.md \
+  --doc-lida docs/documentation.md \
+  --json
+```
+
+## Public Docs Rules
+
+- Write public docs in English.
+- Keep commands, file paths, package names, environment variable names, and DSL
+  keywords literal.
+- Do not include private or sensitive operational material.
+- Prefer local CLI examples.
+- Point support requests to suporte@otimitare.online.

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/getting-started.md

@@ -1,57 +1,57 @@
-# Installation And First Use
-
-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 resumo
-```
-
-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
-
-```bash
-sema iniciar --template base
-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
-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 or an external
-request before local commands run.
-
-Support: suporte@otimitare.online
+# Installation And First Use
+
+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 resumo
+```
+
+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
+
+```bash
+sema iniciar --template base
+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
+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 or an external
+request before local commands run.
+
+Support: suporte@otimitare.online

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.