@semacode/cli 3.8.1 → 3.8.3

package/docs/security.md

@@ -1,54 +1,54 @@
-# 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 bootstrap skill contains instructions only. The global npm
-postinstall may atomically update the managed launcher under `~/.sema/bin`, the
-canonical copy under `~/.agents/skills/sema`, and a Claude mirror under
-`~/.claude/skills/sema` when Claude is already detected. It must not scan the
-home recursively, overwrite an unowned destination, follow symlinks or
-junctions, write into a plugin cache, bundle an MCP server, add a credential
-flow, or duplicate the repository governance that belongs in `AGENTS.md`.
-
-Status output exposes symbolic paths such as `$HOME/.sema/bin/sema`,
-`$HOME/.sema/bin/sema.ps1`, `$HOME/.sema/bin/sema.cmd`, and
-`$HOME/.sema/bin/sema-managed.ps1`, never the real home, Node.js executable, or
-package path. On Windows, PowerShell resolves `sema.ps1` from `PATH`, `cmd.exe`
-resolves `sema.cmd`, and the fallback runs `sema-managed.ps1` through
-`%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe`. A managed receipt
-detects isolated corruption of the launchers and companion; it is integrity
-recovery, not authentication against a hostile process running as the same
-user. Private absolute paths are not published in JSON or logs.
-
-The public-package factory rejects pre-existing symlinks, junctions, and
-reparse points in source, stage, and output chains and revalidates filesystem
-identity around each path-based operation. This is fail-closed hardening, not a
-native sandbox: Node.js does not expose cross-platform `openat`/`linkat`-style
-operations anchored to directory handles, so a hostile process running as the
-same operating-system user can still race a parent-path swap. Do not present
-the private package stage as a security boundary against that attacker.
-
-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 bootstrap skill contains instructions only. The global npm
+postinstall may atomically update the managed launcher under `~/.sema/bin`, the
+canonical copy under `~/.agents/skills/sema`, and a Claude mirror under
+`~/.claude/skills/sema` when Claude is already detected. It must not scan the
+home recursively, overwrite an unowned destination, follow symlinks or
+junctions, write into a plugin cache, bundle an MCP server, add a credential
+flow, or duplicate the repository governance that belongs in `AGENTS.md`.
+
+Status output exposes symbolic paths such as `$HOME/.sema/bin/sema`,
+`$HOME/.sema/bin/sema.ps1`, `$HOME/.sema/bin/sema.cmd`, and
+`$HOME/.sema/bin/sema-managed.ps1`, never the real home, Node.js executable, or
+package path. On Windows, PowerShell resolves `sema.ps1` from `PATH`, `cmd.exe`
+resolves `sema.cmd`, and the fallback runs `sema-managed.ps1` through
+`%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe`. A managed receipt
+detects isolated corruption of the launchers and companion; it is integrity
+recovery, not authentication against a hostile process running as the same
+user. Private absolute paths are not published in JSON or logs.
+
+The public-package factory rejects pre-existing symlinks, junctions, and
+reparse points in source, stage, and output chains and revalidates filesystem
+identity around each path-based operation. This is fail-closed hardening, not a
+native sandbox: Node.js does not expose cross-platform `openat`/`linkat`-style
+operations anchored to directory handles, so a hostile process running as the
+same operating-system user can still race a parent-path swap. Do not present
+the private package stage as a security boundary against that attacker.
+
+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.com

package/docs/sistemas-interativos.md

@@ -330,33 +330,33 @@ only that local structural coverage is complete; it deliberately keeps
 editor was inspected, a plug-in existed, a worker accepted a job, a package
 launched, or an external observer attested the result.
 
-## Semantic responsibility split
-
-The operational surface is divided by responsibility while preserving
-`operations.ts` as the stable explicit export facade:
-
-- `operationPrimitives.ts` contains shared validation, canonicalization, digest,
-  and evidence primitives;
-- `engineObservation.ts` owns engine snapshots, semantic diffs, asset
-  provenance, and editor-state observation;
-- `jobOrchestration.ts` owns queues, locks, budgets, leases, checkpoints, and
-  recovery planning;
-- `acceptanceEvidence.ts` owns acceptance locks, invalidation, and multimodal
-  claim evidence.
-
-The contracts follow the same boundaries through
-`sistemas_interativos_operacao.sema`,
-`sistemas_interativos_observacao_engine.sema`,
-`sistemas_interativos_orquestracao_jobs.sema`, and
-`sistemas_interativos_acceptance_evidencias.sema`. The installed-package smoke
-also keeps one stable orchestrator and one isolated installation, delegating
-public-boundary security, Codex bootstrap, content-pipeline compatibility,
-interactive systems, and generated toolchains to named helpers under
-`scripts/cli-publico/`.
-
-This is a responsibility split, not a numbered-file workaround. Existing
-exports, schema versions, fixtures, digests, and fail-closed behavior remain
-backward compatible across the facades.
+## Semantic responsibility split
+
+The operational surface is divided by responsibility while preserving
+`operations.ts` as the stable explicit export facade:
+
+- `operationPrimitives.ts` contains shared validation, canonicalization, digest,
+  and evidence primitives;
+- `engineObservation.ts` owns engine snapshots, semantic diffs, asset
+  provenance, and editor-state observation;
+- `jobOrchestration.ts` owns queues, locks, budgets, leases, checkpoints, and
+  recovery planning;
+- `acceptanceEvidence.ts` owns acceptance locks, invalidation, and multimodal
+  claim evidence.
+
+The contracts follow the same boundaries through
+`sistemas_interativos_operacao.sema`,
+`sistemas_interativos_observacao_engine.sema`,
+`sistemas_interativos_orquestracao_jobs.sema`, and
+`sistemas_interativos_acceptance_evidencias.sema`. The installed-package smoke
+also keeps one stable orchestrator and one isolated installation, delegating
+public-boundary security, Codex bootstrap, content-pipeline compatibility,
+interactive systems, and generated toolchains to named helpers under
+`scripts/cli-publico/`.
+
+This is a responsibility split, not a numbered-file workaround. Existing
+exports, schema versions, fixtures, digests, and fail-closed behavior remain
+backward compatible across the facades.
 
 ## Fidelity rules
 

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.com
+
+OtimiTare website: https://otimitare.com
+
+Do not publish private or sensitive support routing material in the public Sema
+repository.

package/docs/testing.md

@@ -2,7 +2,7 @@
 
 Public Sema tests should run locally.
 
-Recommended checks:
+Recommended checks:
 
 ```bash
 npm run build
@@ -11,31 +11,31 @@ npm run repo:verificar-publico
 npm run plugin:testar-codex
 npm run cli:empacotar-publica
 npm run cli:testar-pacote-publico
-node pacotes/cli/dist/bin.js --help
-node pacotes/cli/dist/bin.js --version
-node pacotes/cli/dist/bin.js resumo exemplos/calculadora.sema --micro --json
-node pacotes/cli/dist/bin.js validar exemplos/calculadora.sema --json
-node pacotes/cli/dist/bin.js testar exemplos/calculadora.sema --alvo dotnet --saida .tmp/testing-dotnet
-node pacotes/cli/dist/bin.js testar exemplos/calculadora.sema --alvo cpp --saida .tmp/testing-cpp
+node pacotes/cli/dist/bin.js --help
+node pacotes/cli/dist/bin.js --version
+node pacotes/cli/dist/bin.js resumo exemplos/calculadora.sema --micro --json
+node pacotes/cli/dist/bin.js validar exemplos/calculadora.sema --json
+node pacotes/cli/dist/bin.js testar exemplos/calculadora.sema --alvo dotnet --saida .tmp/testing-dotnet
+node pacotes/cli/dist/bin.js testar exemplos/calculadora.sema --alvo cpp --saida .tmp/testing-cpp
 npm run release:preparar-publica
-npm run release:verificar-drift
-```
-
-`npm run cli:empacotar-publica` is the only supported package factory. It
-builds a private, per-run stage outside `pacotes/cli`, invokes npm there with
-lifecycle scripts disabled, validates the complete tarball, and publishes the
-final `.tgz` without replacing a different concurrent winner. Running `npm
-pack` directly in the source workspace must fail closed and leave the source
-tree byte-for-byte unchanged.
-
-Packaging regressions must prove rejection of pre-existing source or output
-junctions, zero external writes in those cases, cross-volume publication,
-cleanup after injected faults, concurrent no-replace publication, and a full
-stage sweep for source maps, credentials, environment files, and billing
-artifacts. Post-operation identity checks detect ordinary path swaps, but tests
-must not claim containment against a hostile same-user process racing path
-operations; that stronger guarantee requires native directory-handle-relative
-filesystem primitives that Node.js does not provide cross-platform.
+npm run release:verificar-drift
+```
+
+`npm run cli:empacotar-publica` is the only supported package factory. It
+builds a private, per-run stage outside `pacotes/cli`, invokes npm there with
+lifecycle scripts disabled, validates the complete tarball, and publishes the
+final `.tgz` without replacing a different concurrent winner. Running `npm
+pack` directly in the source workspace must fail closed and leave the source
+tree byte-for-byte unchanged.
+
+Packaging regressions must prove rejection of pre-existing source or output
+junctions, zero external writes in those cases, cross-volume publication,
+cleanup after injected faults, concurrent no-replace publication, and a full
+stage sweep for source maps, credentials, environment files, and billing
+artifacts. Post-operation identity checks detect ordinary path swaps, but tests
+must not claim containment against a hostile same-user process racing path
+operations; that stronger guarantee requires native directory-handle-relative
+filesystem primitives that Node.js does not provide cross-platform.
 
 Do not require private or sensitive operational material for public test
 evidence. The public-package smoke must also reject the removed authorization
@@ -47,104 +47,104 @@ repeat that installation from the remote `gerlanss/Sema` marketplace and prove
 that GitHub HEAD, the installed skill, and the manifest-declared npm version
 all describe the same release.
 
-The local public-package smoke installs the generated tarball in an isolated
-sandbox. It must import the root API without executing the CLI, materialize
-nested interactive examples, and execute discovery, interactive schema,
-definition validation, planning, and adapter-protocol validation through the
-installed binary. Its global-install phase uses an isolated home, prefix, npm
-cache, and user cache; it verifies the absolute launcher with Node.js/npm absent
-from `PATH`, exact skill digests, read-only status, idempotent repair, and zero
-changes to the real home or workspace. On Windows it must resolve `sema.ps1`
-from a restricted `PATH`, invoke `sema-managed.ps1` with the absolute system
-`powershell.exe`, and exercise `sema.cmd` with conventional `cmd.exe` arguments.
-Byte-exact arbitrary argv is proved through the PowerShell entrypoints. Passing this smoke proves
-the local tarball only; it does not mean that npm or a GitHub release was
-published.
-
-The same installed-package smoke must execute root help plus `iniciar --help`,
-`dev --help`, `formatar --help`, `sync-codex --help`, `skill sync --help`, short
-`-h`, and help after unknown arguments. Each text and `--json` invocation runs
-from an empty isolated workspace with an isolated HOME, user cache, plugin
-cache, and npm cache. A recursive content fingerprint before and after every
-invocation must remain identical, and every help path must finish within the
-smoke timeout with exit code `0` and empty stderr.
-
-The purity preload also fails on reads under the isolated workspace, HOME, or
-cache roots, subprocess creation, and network primitives. Module reads from the
-installed package itself remain allowed. The smoke invokes the real installed
-launcher with PATH emptied, so a passing direct `node dist/bin.js` probe alone
-is not accepted as launcher evidence.
-
-JSON help must be one parseable `sema.cli.control/v1` document containing
-exactly `schemaVersion`, `ok`, `kind`, `code`, `message`, and `exitCode`. The
-smoke must also prove a non-zero `UNKNOWN_COMMAND` control response whose
-process status equals `exitCode`, with no stack, absolute path, raw argv, or
-second JSON document. Every syntactically valid command using `--json` must be
-one parseable `sema.cli.result/v1` document containing exactly
-`schemaVersion`, `ok`, `kind`, `command`, `code`, `message`, `exitCode`, and
-`payload`. Smoke assertions must unwrap `payload` before checking
-command-specific fields, and recorded fixtures must contain that payload rather
-than either public CLI envelope. Coverage must include object, array, scalar,
-and `null` payloads, coherent `SUCCESS` and `DOMAIN_ERROR` results, process
-status equality, empty stderr, no `data` alias, and rejection of missing,
-extra, nested, or mismatched envelope fields. `--version` remains a plain exact
-SemVer text check.
-
-Focused distribution tests live in
-`testes/unidade/distribuicao-launcher-global.test.ts`,
-`testes/unidade/distribuicao-skill-global.test.ts`, and
-`testes/unidade/distribuicao-global.test.ts`. They must cover spaces, Unicode,
-argument forwarding, stale targets, ownership conflicts, symlink/junction
-escapes, atomic replacement, idempotent upgrades, the PowerShell fallback with
-an absolute system executable, a detected Claude mirror, and a local lifecycle
-no-op. No test may write to the real user home or a plugin cache.
-
-The public-package smoke has one orchestrator and named helpers under
-`scripts/cli-publico/`. All helpers share the same temporary sandbox and the
-same installed tarball; splitting the checks must never multiply installations
-or weaken the single `try/finally` cleanup boundary.
-
-Focused drift regressions live in
-`testes/unidade/drift-escopo-dependencias.test.ts`,
-`testes/unidade/drift-escopo-referencias.test.ts`,
-`testes/unidade/drift-catalogo.test.ts`,
-`testes/unidade/drift-leitura-compartilhada.test.ts`, and
-`testes/integracao/drift-escopo-io.test.ts`, plus the external-path attack
-regressions in `testes/integracao/drift-caminhos-externos.test.ts`. They must prove planning before
-cataloging, path confinement, dependency closure, one physical read and one AST
-per canonical file, no homonymous last-write-wins resolution, and no
-project-wide walk for `arquivo` or `modulo` scope. Project-loading regressions
-also prove deferred code discovery and rejection of external configured roots
-or contract origins before enumeration. In project scope, physical file
-bindings outside code roots must enter the safe catalog individually, including
-non-indexable assets, without causing a walk of their parent directories.
-Drift, impact, and semantic rename must not expose an external path or read its
-contents.
-Persistent-cache regressions live in
-`testes/unidade/drift-cache-modes.test.ts`,
-`testes/unidade/drift-cache-store.test.ts`,
-`testes/integracao/drift-cache-persistente.test.ts`, and
-`testes/integracao/drift-cli-modes.test.ts`. They must prove all three modes,
-query defaults, nullable non-evidence, zero cache I/O for `none`, storage outside
-the workspace, opaque paths, strong-content invalidation even with restored
-metadata, corruption recovery, immutable concurrent publication, and semantic
-equivalence between fresh and warm results. Shape-valid semantic tampering with
-only the envelope `payloadDigest` recalculated must fail the cross-index
-invariants, become a corrupt miss, recalculate, and match the fresh result. The
-payload must derive symbol, route, resource, and known-file aggregates from its
-canonical per-extractor indices instead of trusting redundant aggregate lists.
-A warm hit may skip AST/extractor work, but it never reuses the final score,
-links, diagnostics, or success decision. Junctions, symlinks, hardlinks, path
-traversal, drive-relative paths,
-intermediate-directory swaps, and cache unavailability must fail closed or
-degrade to an in-memory calculation without mutating the workspace.
-
-Cache digests are corruption checks, not authentication against a hostile
-process running as the same operating-system user. Tests must not present a
-warm cache hit as a protected trust boundary; final closure evidence uses
-`--cache fresh`.
-
-Native generator evidence is mandatory when changing C#/.NET or C++ support.
+The local public-package smoke installs the generated tarball in an isolated
+sandbox. It must import the root API without executing the CLI, materialize
+nested interactive examples, and execute discovery, interactive schema,
+definition validation, planning, and adapter-protocol validation through the
+installed binary. Its global-install phase uses an isolated home, prefix, npm
+cache, and user cache; it verifies the absolute launcher with Node.js/npm absent
+from `PATH`, exact skill digests, read-only status, idempotent repair, and zero
+changes to the real home or workspace. On Windows it must resolve `sema.ps1`
+from a restricted `PATH`, invoke `sema-managed.ps1` with the absolute system
+`powershell.exe`, and exercise `sema.cmd` with conventional `cmd.exe` arguments.
+Byte-exact arbitrary argv is proved through the PowerShell entrypoints. Passing this smoke proves
+the local tarball only; it does not mean that npm or a GitHub release was
+published.
+
+The same installed-package smoke must execute root help plus `iniciar --help`,
+`dev --help`, `formatar --help`, `sync-codex --help`, `skill sync --help`, short
+`-h`, and help after unknown arguments. Each text and `--json` invocation runs
+from an empty isolated workspace with an isolated HOME, user cache, plugin
+cache, and npm cache. A recursive content fingerprint before and after every
+invocation must remain identical, and every help path must finish within the
+smoke timeout with exit code `0` and empty stderr.
+
+The purity preload also fails on reads under the isolated workspace, HOME, or
+cache roots, subprocess creation, and network primitives. Module reads from the
+installed package itself remain allowed. The smoke invokes the real installed
+launcher with PATH emptied, so a passing direct `node dist/bin.js` probe alone
+is not accepted as launcher evidence.
+
+JSON help must be one parseable `sema.cli.control/v1` document containing
+exactly `schemaVersion`, `ok`, `kind`, `code`, `message`, and `exitCode`. The
+smoke must also prove a non-zero `UNKNOWN_COMMAND` control response whose
+process status equals `exitCode`, with no stack, absolute path, raw argv, or
+second JSON document. Every syntactically valid command using `--json` must be
+one parseable `sema.cli.result/v1` document containing exactly
+`schemaVersion`, `ok`, `kind`, `command`, `code`, `message`, `exitCode`, and
+`payload`. Smoke assertions must unwrap `payload` before checking
+command-specific fields, and recorded fixtures must contain that payload rather
+than either public CLI envelope. Coverage must include object, array, scalar,
+and `null` payloads, coherent `SUCCESS` and `DOMAIN_ERROR` results, process
+status equality, empty stderr, no `data` alias, and rejection of missing,
+extra, nested, or mismatched envelope fields. `--version` remains a plain exact
+SemVer text check.
+
+Focused distribution tests live in
+`testes/unidade/distribuicao-launcher-global.test.ts`,
+`testes/unidade/distribuicao-skill-global.test.ts`, and
+`testes/unidade/distribuicao-global.test.ts`. They must cover spaces, Unicode,
+argument forwarding, stale targets, ownership conflicts, symlink/junction
+escapes, atomic replacement, idempotent upgrades, the PowerShell fallback with
+an absolute system executable, a detected Claude mirror, and a local lifecycle
+no-op. No test may write to the real user home or a plugin cache.
+
+The public-package smoke has one orchestrator and named helpers under
+`scripts/cli-publico/`. All helpers share the same temporary sandbox and the
+same installed tarball; splitting the checks must never multiply installations
+or weaken the single `try/finally` cleanup boundary.
+
+Focused drift regressions live in
+`testes/unidade/drift-escopo-dependencias.test.ts`,
+`testes/unidade/drift-escopo-referencias.test.ts`,
+`testes/unidade/drift-catalogo.test.ts`,
+`testes/unidade/drift-leitura-compartilhada.test.ts`, and
+`testes/integracao/drift-escopo-io.test.ts`, plus the external-path attack
+regressions in `testes/integracao/drift-caminhos-externos.test.ts`. They must prove planning before
+cataloging, path confinement, dependency closure, one physical read and one AST
+per canonical file, no homonymous last-write-wins resolution, and no
+project-wide walk for `arquivo` or `modulo` scope. Project-loading regressions
+also prove deferred code discovery and rejection of external configured roots
+or contract origins before enumeration. In project scope, physical file
+bindings outside code roots must enter the safe catalog individually, including
+non-indexable assets, without causing a walk of their parent directories.
+Drift, impact, and semantic rename must not expose an external path or read its
+contents.
+Persistent-cache regressions live in
+`testes/unidade/drift-cache-modes.test.ts`,
+`testes/unidade/drift-cache-store.test.ts`,
+`testes/integracao/drift-cache-persistente.test.ts`, and
+`testes/integracao/drift-cli-modes.test.ts`. They must prove all three modes,
+query defaults, nullable non-evidence, zero cache I/O for `none`, storage outside
+the workspace, opaque paths, strong-content invalidation even with restored
+metadata, corruption recovery, immutable concurrent publication, and semantic
+equivalence between fresh and warm results. Shape-valid semantic tampering with
+only the envelope `payloadDigest` recalculated must fail the cross-index
+invariants, become a corrupt miss, recalculate, and match the fresh result. The
+payload must derive symbol, route, resource, and known-file aggregates from its
+canonical per-extractor indices instead of trusting redundant aggregate lists.
+A warm hit may skip AST/extractor work, but it never reuses the final score,
+links, diagnostics, or success decision. Junctions, symlinks, hardlinks, path
+traversal, drive-relative paths,
+intermediate-directory swaps, and cache unavailability must fail closed or
+degrade to an in-memory calculation without mutating the workspace.
+
+Cache digests are corruption checks, not authentication against a hostile
+process running as the same operating-system user. Tests must not present a
+warm cache hit as a protected trust boundary; final closure evidence uses
+`--cache fresh`.
+
+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
+- agent-native (Claude, Codex, zCode/GLM, Kimi)
+- 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.com for support references.