@semacode/cli 2.2.0 → 2.3.1

package/docs/README.md

@@ -1,28 +1,34 @@
-# Sema Documentation
-
-These docs describe the public Codex-native local CLI distribution of Sema.
-
-Sema is local-first: Codex runs the CLI inside a project folder, reads `.sema`
-contracts, checks drift, maps impact, and closes changes with documentation
-evidence. `AGENTS.md` is the official Codex entrypoint. Public docs are written
-in English.
-
-Sema is an independent product and is not affiliated with or endorsed by
-OpenAI. Codex-native describes Sema's product direction, not an official OpenAI
-program or submission.
-
-Start here:
-
-- [CLI](./cli.md)
-- [Commands](./commands.md)
-- [Syntax](./syntax.md)
-- [Profiles](./profiles.md)
-- [AI-native Content Pipeline](./pipeline-conteudo.md) — signed-policy,
-  multi-channel and multi-format orchestration for external AI runners, with
-  canonical ledger replay and no native human-review path.
-- [Documentation Governance](./documentation.md)
-- [Repository Boundary](./repositories.md)
-- [Security](./security.md)
-- [Codex Integration](./ai-integration.md)
-
-Official support: [suporte@otimitare.online](mailto:suporte@otimitare.online)
+# Sema Documentation
+
+These docs describe the public Codex-native local CLI distribution of Sema.
+
+Sema is local-first: Codex runs the CLI inside a project folder, reads `.sema`
+contracts, checks drift, maps impact, and closes changes with documentation
+evidence. `AGENTS.md` is the official Codex entrypoint. Public docs are written
+in English.
+
+Sema is an independent product and is not affiliated with or endorsed by
+OpenAI. Codex-native describes Sema's product direction, not an official OpenAI
+program or submission.
+
+Start here:
+
+- [CLI](./cli.md)
+- [Commands](./commands.md)
+- [Syntax](./syntax.md)
+- [Profiles](./profiles.md)
+- [Capability Discovery](./descoberta-capacidades.md) — one explainable catalog
+  for governance flows, profiles, specialized workflows, pipelines, generators,
+  capability tokens, and adapters.
+- [AI-native Interactive Systems](./sistemas-interativos.md) — declarative
+  control plane for games, simulations, and hybrids across 3D, 2D, retro,
+  text, XR, and headless execution.
+- [AI-native Content Pipeline](./pipeline-conteudo.md) — signed-policy,
+  multi-channel and multi-format orchestration for external AI runners, with
+  canonical ledger replay and no native human-review path.
+- [Documentation Governance](./documentation.md)
+- [Repository Boundary](./repositories.md)
+- [Security](./security.md)
+- [Codex Integration](./ai-integration.md)
+
+Official support: [suporte@otimitare.online](mailto:suporte@otimitare.online)

package/docs/ai-onboarding.md

@@ -1,62 +1,62 @@
-# Codex Onboarding
-
-The official Sema skill is required for Codex to recognize and initialize Sema
-before a project has its own protocol:
-
-```bash
-codex plugin marketplace add gerlanss/Sema
-codex plugin add sema@sema
-```
-
-Open a new Codex task in the target repository after installation. Codex loads
-the plugin/skill catalog at task start, so `$sema` is not added retroactively to
-an already-open task. Invoke `$sema` in the new task; it bootstraps the project,
-reads the generated `AGENTS.md`, and later tasks load that protocol
-automatically.
-
-`AGENTS.md` is the official Sema entrypoint for Codex. It gives Codex the durable
-repository rule that contracts come first and the local CLI is the source of
-truth. Once the file exists, the skill delegates to it instead of carrying a
-second copy of the governed workflow.
-
-Create or refresh the entrypoint with:
-
-```bash
-sema sync-codex --json
-```
-
-## Minimal Prompt
-
-```text
-This workspace is governed by Sema. Before editing code, contracts, docs,
-workflows, profiles, or release scripts, run:
-
-1. sema --version
-2. sema resumo
-3. sema docs-impacto --intencao "<change>" --json
-4. sema inspecionar on the applicable .sema contract
-5. sema drift before editing existing code
-6. sema impacto before changing behavior
-7. sema finalizar-mudanca before closing
-
-If the CLI is unavailable, stop and install or repair @semacode/cli. There is
-no separate Sema login, license activation, or authorization gate. Do not
-replace Sema with manual search or guessed contracts.
-```
-
-## What Codex Should Not Do
-
-- Do not invent `.sema` contracts.
-- Do not implement code without an applicable contract.
-- Do not ignore severity 4+ warnings.
-- Do not publish private or sensitive operational material.
-- Do not replace the local CLI when the local workspace is available.
-
-Other AI clients can invoke the public CLI manually, but Sema does not ship or
-manage an official repository entrypoint for them. The supported product path
-is Codex plus `AGENTS.md`.
-
-Sema is an independent product and is not affiliated with or endorsed by
-OpenAI.
-
-Support: suporte@otimitare.online
+# Codex Onboarding
+
+The official Sema skill is required for Codex to recognize and initialize Sema
+before a project has its own protocol:
+
+```bash
+codex plugin marketplace add gerlanss/Sema
+codex plugin add sema@sema
+```
+
+Open a new Codex task in the target repository after installation. Codex loads
+the plugin/skill catalog at task start, so `$sema` is not added retroactively to
+an already-open task. Invoke `$sema` in the new task; it bootstraps the project,
+reads the generated `AGENTS.md`, and later tasks load that protocol
+automatically.
+
+`AGENTS.md` is the official Sema entrypoint for Codex. It gives Codex the durable
+repository rule that contracts come first and the local CLI is the source of
+truth. Once the file exists, the skill delegates to it instead of carrying a
+second copy of the governed workflow.
+
+Create or refresh the entrypoint with:
+
+```bash
+sema sync-codex --json
+```
+
+## Minimal Prompt
+
+```text
+This workspace is governed by Sema. Before editing code, contracts, docs,
+workflows, profiles, or release scripts, run:
+
+1. sema --version
+2. sema resumo
+3. sema docs-impacto --intencao "<change>" --json
+4. sema inspecionar on the applicable .sema contract
+5. sema drift before editing existing code
+6. sema impacto before changing behavior
+7. sema finalizar-mudanca before closing
+
+If the CLI is unavailable, stop and install or repair @semacode/cli. There is
+no separate Sema login, license activation, or authorization gate. Do not
+replace Sema with manual search or guessed contracts.
+```
+
+## What Codex Should Not Do
+
+- Do not invent `.sema` contracts.
+- Do not implement code without an applicable contract.
+- Do not ignore severity 4+ warnings.
+- Do not publish private or sensitive operational material.
+- Do not replace the local CLI when the local workspace is available.
+
+Other AI clients can invoke the public CLI manually, but Sema does not ship or
+manage an official repository entrypoint for them. The supported product path
+is Codex plus `AGENTS.md`.
+
+Sema is an independent product and is not affiliated with or endorsed by
+OpenAI.
+
+Support: suporte@otimitare.online

package/docs/ai-workflow.md

@@ -9,10 +9,11 @@ This is the minimum workflow for Codex in a local workspace.
 4. Run `sema docs-impacto --intencao "<change>" --json`.
 5. Read every required document returned by the command.
 6. Read `docs/commands.md` before selecting a command or interpreting `--saida`.
-7. Use `exemplos/` and `docs/syntax.md` before creating or editing a contract.
-8. Run `sema drift` and `sema impacto` before editing existing code.
-9. Run `sema formatar` and `sema validar` after changing a `.sema` contract.
-10. Run `sema finalizar-mudanca` with the documents read before closure.
+7. If the right capability is unclear, run `sema descobrir recomendar --intencao "<goal>" --json`; do not auto-run ambiguous recommendations.
+8. Use `exemplos/` and `docs/syntax.md` before creating or editing a contract.
+9. Run `sema drift` and `sema impacto` before editing existing code.
+10. Run `sema formatar` and `sema validar` after changing a `.sema` contract.
+11. Run `sema finalizar-mudanca` with the documents read before closure.
 
 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`.
 
@@ -20,6 +21,10 @@ Closing rule: `sema drift --json` must return `sucesso:true`. If it reports `suc
 
 UI rule: if the task involves an interface, minimum evidence includes desktop and mobile. On a narrow viewport such as 390px, `document.documentElement.scrollWidth <= document.documentElement.clientWidth` must pass; horizontal scroll blocks closure.
 
+Focused inspection rule: `sema inspecionar <contrato.sema>` and `sema resumo <contrato.sema> --micro` default to `--drift none`. They load the target plus its transitive `use` closure and must state that live code was not verified. Use `--drift cache`, `--drift fresh`, or `--com-drift` only when implementation evidence is required.
+
+Drift scope rule: a file/module run plans its physical file set before cataloging and never falls back to a whole-project walk when no safe anchor exists. `--cache auto` reuses validated catalog, file, and semantic-group entries; `--cache refresh` recalculates them; `--cache off` disables persistent cache I/O. Inspect `escopo_aplicado.catalogo`, `escopo_aplicado.cache.incremental`, and `escopo_aplicado.cache.fasesMs` for the work actually performed.
+
 ## Codex Context Capacity
 
 - Small context: `SEMA_SMALL_MODEL.md`, `SEMA_BRIEF.micro.txt`, `AGENT_CONTEXT_PACK.json`, `SEMA_INDEX.json`.

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

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

@@ -22,17 +22,25 @@ Then read every required doc returned by `docs-impacto`.
 - `sema inspecionar <arquivo-ou-pasta> --json`: shows modules, tasks, routes, entities, links, and expected files.
 - `sema ast <arquivo.sema> --json`: shows AST for syntax debugging.
 - `sema ir <arquivo.sema> --json`: shows the IR used by gates and generators.
+- `sema descobrir catalogo --json`: lists governance flows, profiles, specialized workflows, pipelines, generators, capability tokens, and adapters from their canonical registries.
+- `sema descobrir recomendar --intencao "<goal>" --json`: ranks compatible capabilities deterministically without executing the selected command.
+- `sema descobrir explicar <id> --json`: explains inputs, boundaries, reasons, and the command template for one capability.
+- `sema pipeline listar|descrever <id> --json` and `sema capabilities --json`: compact projections of the same discovery catalog.
 
 ## Change and Closure
 
 - `sema docs-impacto --intencao "<acao>" --json`: discovers required docs and documentary blockers.
-- `sema drift <arquivo-ou-pasta> --escopo modulo --json`: compares contract and implementation.
+- `sema inspecionar <arquivo-ou-pasta> [--drift none|cache|fresh] [--com-drift] --json`: inspects contracts; the default is contract-only `none` and leaves code scores absent.
+- `sema resumo <arquivo-ou-pasta> --micro [--drift none|cache|fresh] --json`: produces a small contract summary; the default is contract-only `none` and explicitly says implementation was not verified.
+- `sema drift <arquivo-ou-pasta> --escopo modulo [--cache auto|refresh|off] --json`: compares contract and implementation after planning the physical scope.
 - `sema impacto <arquivo-ou-pasta> --alvo <token> --mudanca "<descricao>" --json`: maps impact before changing behavior.
 - `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: treat drift JSON as the source of truth. `sucesso:false`, `vinculos_quebrados`, `rotas_divergentes`, or broken impls mean the change is not complete yet. Do not report "clean drift" without green JSON.
 
+Focused drift does not fall back to a global scan when it cannot prove a safe file anchor. With `--cache auto`, unchanged catalog snapshots, file metadata/content, dependency extraction, and semantic groups are reused only after schema, digest, identity, runtime-shape, and filesystem validation. The JSON fields `escopo_aplicado.catalogo`, `escopo_aplicado.cache.incremental`, and `escopo_aplicado.cache.fasesMs` expose visits, reads, hits, misses, extractions, writes, and phase timing.
+
 ## Sema Code
 
 - `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.
@@ -67,10 +75,47 @@ Ready UI rule: if the task generates an app, site, dashboard, form, or static HT
 ## 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.
+- `sema profile validar <software|workflow|ops|game|simulation|legal|research|redacao|propostas|conversas> <arquivo> --json`: validates an artifact by profile.
 - `sema profile capabilities --json`: lists profiles/capabilities.
 - `sema rule-packs --profile <profile> --json`: lists rule packs.
 
+`author` is a specialized `sema author` workflow, not a `profile validar` alias. Discovery exposes that distinction explicitly.
+
+## AI-native Content Pipeline
+
+- `sema conteudo capabilities --json`: lists generic producer, evaluator, and adapter capabilities without fixing a platform.
+- `sema conteudo validar <definition.json> --json`: validates the content DAG, gates, and open adapters.
+- `sema conteudo planejar <definition.json> --alvos-arquivo <targets.json> --json`: creates a declarative multi-target plan for an external runner.
+- `sema conteudo validar-envelope --envelope-arquivo <envelope.json> --confianca-arquivo <trust.json> --trust-root-digest <sha256:...> --revocation-digest <sha256:...> --payload-type <type> --json`: verifies Ed25519 identity, authorization, freshness, scope, and the separately pinned trust root and current revocation overlay.
+- `sema conteudo registrar <ledger.ndjson> --envelope-arquivo <envelope.json> --politica-arquivo <policy-envelope.json> --confianca-arquivo <trust.json> --trust-root-digest <sha256:...> --revocation-digest <sha256:...> --ledger-id <id> --expected-head <sha256:...> --json`: appends a verified envelope under the signed run policy to the local replay ledger at an externally retained head.
+- `sema conteudo status <definition.json> --politica-arquivo <policy-envelope.json> --confianca-arquivo <trust.json> --trust-root-digest <sha256:...> --revocation-digest <sha256:...> --ledger-arquivo <ledger.ndjson> --expected-head <sha256:...> --json`: verifies the signed policy and derives verdicts, operational conditions, completion, and next actions from canonical events.
+- `sema conteudo projetar <definition.json> --politica-arquivo <policy-envelope.json> --confianca-arquivo <trust.json> --trust-root-digest <sha256:...> --revocation-digest <sha256:...> --ledger-arquivo <ledger.ndjson> --expected-head <sha256:...> --saida <manifest.json> --json`: regenerates a non-authoritative manifest bound to the ledger head.
+
+The content command never runs producers, evaluators, creative tools, or publication adapters; those belong to an external runner. It has no native human-review transition. A signed policy binds the run, definition, ledger, trust root, gates, complete target set, and authorization window. Stages select `adapterPolicy` as `NONE`, `CONSTRAINTS`, or `CONFIRMATION`; definition v1 accepts one output per stage. Constraint results must come from independent signed observations, including independently observed media type, not artifact metadata or executor claims.
+
+Target metadata is an exact scalar allowlist from `requiredMetadata + optionalMetadata`; `accountScope` is a credential-free `account:<alias>` reference, and artifact metadata is prohibited in v1. Deterministic evidence and AI opinions have separate quorum fields. Evidence requires an exact attestation capability plus signed adapter binding where applicable.
+
+Verdicts remain separate from operational conditions, and a generated manifest cannot alter canonical state. Append freshness uses the platform clock rather than caller-provided time, and an authority in the current revocation overlay cannot sign an accepted policy.
+
+Local NDJSON plus a hash chain is portable replay evidence, not a strong append-only trust boundary. Retain the expected head, canonical trust-root digest, and current revocation digest externally, or use protected storage for high assurance. A workspace-local trust file additionally requires `--development-local-trust`; that flag does not disable digest pinning.
+
+## AI-native Interactive Systems
+
+- `sema interativo capabilities --json`: lists the canonical interactive capability vocabulary.
+- `sema interativo schema --json`: exposes stable definition, extension-command, and data-schema shapes for AI clients.
+- `sema interativo pipelines --json`: lists reusable game, simulation, and hybrid pipelines.
+- `sema interativo adapters [--spatial-model <NON_SPATIAL|TWO_D|TWO_POINT_FIVE_D|THREE_D>] [--render-mode <HEADLESS|TEXT|VISUAL|XR>] --json`: lists compatible external adapter descriptors.
+- `sema interativo validar <definition.json> --json`: validates independent kind, spatial model, render mode, visual profile, fidelity, control, time, world, budget, pipeline, and acceptance axes.
+- `sema interativo planejar <definition.json> --json`: expands compatible stages and required evidence without running an engine.
+- `sema interativo validar-evidencias|status <definition.json> [--plano-arquivo <plan.json>] --bundle-arquivo <bundle.json> --json`: validates a portable evidence bundle or derives non-authoritative status; `--evidencias-arquivo` is an alias and an omitted plan is recomputed deterministically.
+- `sema interativo validar-protocolo <adapter-run.json> --json`: checks DETECT/PROBE/SNAPSHOT/PLAN/APPLY/VALIDATE/EVIDENCE/ROLLBACK ordering and stable target binding.
+- Experience IR: `validar-ir`, `indexar-ir`, `consultar-ir`, `chunk-ir`, and `descrever-ir`.
+- Operational state: `validar-engine-snapshot`, `diff-engine-snapshots`, `validar-asset-provenance`, `validar-editor-state`, `planejar-jobs`, `validar-acceptance`, `operar-acceptance`, and `validar-multimodal`.
+- Temporal, autonomy, and testing: `validar-temporal`, `validar-evidencia-temporal`, `validar-autonomia`, `validar-playtest-fuzz`, and `validar-multiplayer`.
+- Portability and workers: `analisar-portabilidade` and `validar-workers`.
+
+Spatial model and render mode are orthogonal: `THREE_D + HEADLESS` is valid, while XR requires `THREE_D`. `PIXEL_8_BIT` and `PIXEL_16_BIT` are independent visual profiles available to games and simulations. Every command above is local and read-only; external runners own engine/editor execution, authorization, mutation, rollback, migration, rendering, playtest, and worker scheduling. Full local coverage is `STRUCTURALLY_COMPLETE`, never authoritative completion.
+
 ## Operational
 
 - `sema doctor`: diagnoses local installation.

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,41 +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 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.
+# 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.