@zaip-ai/cli 3.7.0 → 3.8.0

package/templates/.agents/runtime/checksums.sha256

@@ -1,11 +1,11 @@
 b146bd0c7c60b1ab43c4f71e0b1d2262c6df6da6f7053a0425f834ccb77a6b48  LICENSE
 bc02cba77e8d51e5c580f43668863dc868eda66f1ff663bfaa49fcf3ca16320e  THIRD_PARTY_NOTICES.md
-84746b20a3a72f6ff85a629706e50507c1bd200907456b76dd808a2a5ca0efba  VERSION
-5c911d434505e839d55d273fc275e0725dde425e2b4e91219d3cd28e3883c56b  bin/zaip.mjs
-38a97d3f4f2d30deb9bfe0308a62670c9302d6b6fba1b1173bc0c2d30cf12f0b  manifest.json
+88206afd2d9b56ca71466c85d1ed1421b1db0e78fa00072697918fb8a9ac54ef  VERSION
+b9d0c02583775ea664f7bb92d73c4c901194d4a9bbd3a49993b4891ed241b6ef  bin/zaip.mjs
+d6ef4cfccc2b5d66289f37da8e3f8c726d2c6f5fe8f93e65b0e1f7df7c9b450d  manifest.json
 7f89219d7c567c82a51679ad136d84364bded7ac659492537e125d33b1d58a7a  migrations/001-layout-v1.json
 5f8c48b286d0b44d8fbb57a9a5d009a8a500439aa3148d750b8f193f72995c9f  migrations/002-layout-v2.json
 33c98d5dc506bba4b8b3ca612706d9eb05ef13d9e03c33a4f9e65ca7804be9d1  pnpm-lock.sha256
-4ce32e7d7ecc19a30965b99d5242762015639d5890a647e4fbeda64c71d24b90  provenance.json
-77bb58427ab6dbb4cb721e834218b058a266ea94ae91ebc8853ce7e30418009b  sbom.cdx.json
+15a8ac0676b794bf453eb54f027b30c0ca7cc5e7e572c591a5d76dee6efd1ed3  provenance.json
+017f220c51e33ecccbcbeb58a5673b990b67c37b44a5e6761f02be8c9219a761  sbom.cdx.json
 b3ffedf9e146be802a15b4009f33e031dec3071ca1525e12c67606fd964a3067  schemas/contracts.schema.json

package/templates/.agents/runtime/manifest.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 2,
   "name": "zaip-aios",
-  "version": "3.7.0",
+  "version": "3.8.0",
   "node": ">=22",
   "files": [
     "LICENSE",

package/templates/.agents/runtime/provenance.json

@@ -2,10 +2,10 @@
   "schema_version": 1,
   "statement_type": "self_reported_build_integrity",
   "authenticity": "unverified",
-  "version": "3.7.0",
+  "version": "3.8.0",
   "source_origin": "zaip-aios:local-build",
   "lockfile_sha256": "03d08e5bbb198d74014ea4a806fcdeb350db23ec2bf0c2886a2265066555d418",
-  "sbom_sha256": "77bb58427ab6dbb4cb721e834218b058a266ea94ae91ebc8853ce7e30418009b",
-  "runtime_sha256": "ab3104b23c8a07bfe1c1991ba7f12d40300248c54453ef4c88c71e033842b69a",
-  "statement_sha256": "02dc17045e38d3e808a848926a7d8074cccd812e2db0f376505b59d849de0d0b"
+  "sbom_sha256": "017f220c51e33ecccbcbeb58a5673b990b67c37b44a5e6761f02be8c9219a761",
+  "runtime_sha256": "ce933ca820e864c27fb8fc33c873ef94504cf2015e14cdd8709b6b9e72370bb9",
+  "statement_sha256": "a6b24e3dacdca76511477e9f77a8d83281159cf73d96257b962c6677009f80dd"
 }

package/templates/.agents/runtime/sbom.cdx.json

@@ -6,7 +6,7 @@
     "component": {
       "type": "application",
       "name": "zaip-aios",
-      "version": "3.7.0"
+      "version": "3.8.0"
     }
   },
   "components": [

package/templates/.agents/skills/zaip-skill-adapters/SKILL.md

@@ -7,7 +7,7 @@ description: Generate and verify Codex and Claude guidance adapters from canonic
 
 Um `.codex/config.toml` existente sem cabeçalho `zaip-managed` é um overlay local: `adapters build` deve preservá-lo e `adapters check` não deve reportá-lo como drift. Arquivos ausentes ou gerenciados continuam sujeitos à projeção canônica; nenhum outro adapter recebe essa exceção.
 
-1. Trate `.agents/config`, `rules/` e skills como fontes; `AGENTS.md`, `CLAUDE.md` e wrappers são projeções geradas mínimas. A propriedade de cada Rule é definida pela presença no `framework.lock.yaml`.
+1. Trate `.agents/config`, `rules/` e skills como fontes; `AGENTS.md` e wrappers são projeções geradas mínimas. A propriedade de cada Rule é definida pela presença no `framework.lock.yaml`.
 2. Oriente o agente a começar por `project.yaml` e Rules críticas, depois carregar trabalho, Requirements e skills relevantes sob demanda.
 3. Não instrua a carregar todo o histórico, Runs JSONL ou raízes V1 por padrão.
 4. Gere com cabeçalho managed, versão, checksum e allowlist determinísticos; execute `adapters build` e depois `adapters check`.

package/templates/.agents/skills/zaip-skill-github-deploy/SKILL.md

@@ -1,17 +1,17 @@
 ---
 name: zaip-skill-github-deploy
-description: Use only when the user explicitly asks in the current turn to deploy, push, publish, or make a GitHub publication with folder-scoped SSH; it is Git-only and never grants publication automatically.
+description: Use only when the user explicitly asks to deploy, push or publish to GitHub; in the zaip-aios builder, a full deploy includes a GitHub Release and npm publication through GitHub Actions.
 ---
 
 # Deploy and repair GitHub publication
 
-Treat deploy as Git-only publication. An explicit current-turn request to `deploy`, `push`, `publicar`, `publicação` or GitHub publication selects this skill. It never authorizes provider deployment.
+An explicit current-turn request to `deploy`, `push`, `publicar`, `publicação` or GitHub publication selects this skill; discussing or editing deployment does not authorize publication. In the `zaip-ai/zaip-aios` builder, “faça deploy” means the guarded push, GitHub Release and observation of the GitHub Actions npm publication. Consumer repositories follow their own GitHub-only policy. Neither route authorizes a hosting-provider deployment.
 
 Read [the deployment workflow](references/deployment-workflow.md) for the detailed operational contract before publication. The steps below retain its authority, identity and completion boundaries.
 
 ## Authorization and scope
 
-- The exact command “faça deploy” authorizes commits covering all versionable pending changes in the selected worktree, followed by push and Release, after secret, size and ignore checks. The selected worktree is the complete publication scope; other worktrees remain outside it.
+- The exact command “faça deploy” authorizes commits covering all versionable pending changes in the selected worktree, followed by push and Release, after secret, size and ignore checks. In the verified framework source, publishing that Release triggers the npm workflow; follow it to terminal status and verify the registry. The selected worktree is the complete publication scope; other worktrees remain outside it. An explicit push-only request stops after the verified push and does not create a Release or publish npm.
 - Resolve dirty state, untracked files, generated projections, branch divergence and repairable local/remote failures automatically within that scope. Limit repairs to the evidenced cause, with up to five repair cycles; stop when the same root cause remains after two repairs.
 - Treat the selected worktree's local branch, recovery branch or detached state as the source candidate only. The configured deploy branch is the remote target; a mismatch between source and target is not a blocker and never requires checking out the target locally.
 - Stop only for an unresolved index conflict after bounded repair, secrets, files at or above GitHub's 100 MB limit, unavailable authentication/authority, external outage, destructive requirement, or ambiguous scope expansion.
@@ -43,7 +43,7 @@ Every product commit requires causal Task/Change/Execution records and matching
 
 1. Compose `$zaip-skill-release-qualification` and follow [local preparation](../zaip-skill-release-qualification/references/local-preparation.md). Synchronize and commit before preparing the clean exact SHA. Failed or stale evidence is not qualification.
 2. Resolve the previous Release, next canonical version and package identity using [release identity](references/release-identity.md). For the framework, `vN.N` maps to package `N.N.0`; only GitHub Actions publishes `@zaip-ai/cli` to npm.
-3. For `zaip-ai/zaip-aios`, use `scripts/local-release-deploy.mjs`. It prepares/verifies, pushes the exact SHA to configured `main`, uploads verified assets to a draft, then publishes the Release. Enable the thin publisher only after explicit rollout authority, public trust enrollment and signed local qualification. It validates published assets and runs one read-only installation smoke before npm; no private-draft pilot or write token is needed. GitHub Release publication and npm completion remain separate.
+3. For the verified `zaip-ai/zaip-aios` source, use `scripts/local-release-deploy.mjs`. It prepares/verifies, pushes the exact SHA to configured `main`, uploads verified assets to a draft, then publishes the Release. The `publish-cli.yml` workflow is triggered by `release: published` and alone performs npm publication. Enable the thin publisher only after explicit rollout authority, public trust enrollment and signed local qualification. It validates published assets and runs one read-only installation smoke before npm; no private-draft pilot or local npm write token is needed. Inspect the configured signing key, trust store, policy and protected workflow settings before reporting a missing credential; do not confuse the release-signing private key with the Git SSH key or npm token in a local `.env`, and never rotate trust or bypass a gate without separate authorization. The user authorized routine per-version updates of **only** `ZAIP_LOCAL_RELEASE_POLICY_B64` for this builder on 2026-09-23. Prepare a reviewed version-matched policy, qualify the exact SHA, enroll those exact public policy bytes and verify readback before publishing the Release; do not ask again merely because the previous version is still enrolled. This standing authorization never covers trust-key rotation, other protected variables, or weaker gates. GitHub Release publication and npm completion remain separate.
 4. Consumers use `scripts/consumer-release-preparation.mjs guarded-push` with their own policy and explicit branch, SHA and trusted receipt. They have no framework npm/TGZ requirement. See the preparation guide for bootstrap and guarded commands.
 5. Immediately before delivery, reread the configured target; if changed, restart preparation. Helpers bind the exact candidate to `HEAD:refs/heads/<configured branch>` (or its equivalent immutable-SHA refspec) independently of the local source branch; do not bypass them with a manual push.
 6. After qualification, a missing Release is normal. Unless explicitly push-only, automatically create the draft for that SHA or resume a verified draft for the same SHA. Verify an already-published exact Release as a no-op; an API/authentication error never proves absence. Refuse conflicting tags/assets without overwrite.
@@ -66,7 +66,7 @@ publication separately; neither preparation nor this policy grants publication a
 - After push, compare the local SHA with the configured remote ref. If the push result is uncertain, read remote state first; only one documented transient transport retry is allowed per cycle.
 - Observe required GitHub checks for that exact SHA, waiting up to 20 minutes with concise progress at least once per minute. Read the exact failed step before repairing. Never repeat an unchanged failing command or disable a gate for green status.
 - Reconcile recoverable prerequisites and continue through the same bounded repair policy; do not stop merely because a Release or generated file was absent.
-- Success requires matching local/remote hashes, successful required observable checks, verified Release identity/body and a clean intended worktree. Distinguish GitHub publication, npm availability and formal lifecycle closure. If checks cannot be observed, report CI as unconfirmed.
+- Full framework deploy success requires matching local/remote hashes, successful required checks, verified Release identity/body, a clean intended worktree, terminal success of the exact `publish-cli.yml` run, and registry confirmation of `@zaip-ai/cli@N.N.0` with the intended dist-tag and artifact integrity. The local `.env` does not automatically provide GitHub Actions credentials; use only the workflow's configured secret/environment. If npm fails or cannot be observed, report the GitHub Release as published but the deploy as partial or blocked, with the exact failed/pending gate. Consumer deploys have no framework npm gate. Formal lifecycle closure remains separate.
 - Retain terminal evidence and close every owned Task/Change/Execution correctly through the finalizer. Never finish with an owned Task executing/verifying; use completed, blocked, cancelled or failed according to observed outcome.
 
 Database request-branch PRs retain their separate policy. This Git-only skill never applies SQL, provisions paid resources or publishes database production. Read-only identities cannot substitute for deploy credentials.

package/templates/.agents/skills/zaip-skill-github-deploy/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "ZAIP GitHub Deploy"
-  short_description: "Publicacao GitHub explicita, Git-only e verificavel"
-  default_prompt: "Use $zaip-skill-github-deploy para pedidos explicitos de deploy, push, publicar ou publicacao GitHub; quando o usuario disser 'faca deploy', trate o worktree selecionado inteiro como escopo autorizado, incluindo arquivos novos, apos os gates de segredos, tamanho, conflitos e SSH; trate a branch local ou detached como origem e a branch configurada como alvo remoto, publicando por refspec explicito via SSH da pasta sem force push nem reescrita de historico."
+  short_description: "Deploy GitHub; npm via Actions no builder ZAIP"
+  default_prompt: "Use $zaip-skill-github-deploy para o pedido explicito 'faca deploy': no builder zaip-aios, publique a Release pelo fluxo protegido e confirme o workflow npm e o registro; em consumidores, siga a politica GitHub-only, respeitando pedidos push-only."
 policy:
   allow_implicit_invocation: true

package/templates/.agents/skills/zaip-skill-github-deploy/references/deployment-workflow.md

@@ -3,7 +3,7 @@
 
 The exact command “faça deploy” authorizes publication of everything versionable in the selected worktree, including tracked and untracked files, after the safety gates below. It does not authorize provider deployment.
 
-Treat deploy as Git-only publication. An explicit current-turn request to `deploy`, `push`, `publicar`, `publicação` or GitHub publication selects this skill; it authorizes only the bounded Git publication described below, never a provider deployment or automatic publication.
+An explicit current-turn request to `deploy`, `push`, `publicar`, `publicação` or GitHub publication selects this skill. For the verified `zaip-ai/zaip-aios` source, a default “faça deploy” includes the guarded Git push, GitHub Release and terminal observation of the npm workflow it triggers. Consumer repositories remain GitHub-only. Discussing or editing deployment does not authorize publication, and neither route authorizes provider deployment.
 
 ## Authorization
 
@@ -11,7 +11,7 @@ Treat deploy as Git-only publication. An explicit current-turn request to `deplo
 - The request authorizes the initial publication, automatic reconciliation needed to publish the selected branch, commits covering all versionable pending changes in the selected worktree, and up to five repair cycles needed to make required local and remote GitHub checks pass. Do not stop merely because the worktree is dirty, history is behind/diverged, generated files are pending, or a local gate has a repairable failure.
 - Limit repairs to the intended repository state and the evidenced failure. Do not add unrelated features or broaden product scope.
 - Never force push, rewrite history, replace remotes, change credentials or Git/SSH configuration, bypass checks, or deploy to another service.
-- Do not create lifecycle artifacts for an explicit Git-only publication request. The deploy authorization permits staging every inventoried versionable path in the selected worktree after secret, size, and ignore checks; it never authorizes changes outside that worktree.
+- Do not create lifecycle artifacts merely to publish already-existing commits. The deploy authorization permits staging every inventoried versionable path in the selected worktree after secret, size, and ignore checks; it never authorizes changes outside that worktree.
 - Every product commit needs its evidenced Task and canonical Task title, including Task-first. If ownership is missing, materialize the authorized work before editing/committing; never borrow the latest global Task. Only records/local-only snapshots are exempt. Omit nonexistent PRD/SPEC lineage. Explicit deploy authorizes reviewed path staging, never force, destructive reset, history rewrite, or credential changes.
 
 ## Mandatory authorization record
@@ -99,6 +99,8 @@ Every authorized deploy must first compose `$zaip-skill-release-qualification` a
 
 For `zaip-ai/zaip-aios` framework releases, use `scripts/local-release-deploy.mjs`: it prepares and verifies the candidate, pushes the exact SHA to `main`, uploads the verified assets to a draft release, and publishes that release. npm publication remains exclusively in GitHub Actions. Run the folder-scoped SSH preflight with the explicitly configured frontend scope before this entrypoint.
 
+Before classifying a missing signer as a blocker, inspect the configured external signing-key path, trust store, policy and protected GitHub release variables without exposing secret contents. The private Ed25519 release key is distinct from the Git SSH key and a local `.env` npm token; the latter does not automatically reach Actions. If a required key or protected setting truly is absent, stop with its exact name and recovery action. Do not generate a replacement, rotate public trust or publish locally without separate authority. The user's 2026-09-23 standing authorization permits routine version-specific updates of **only** `ZAIP_LOCAL_RELEASE_POLICY_B64` in the verified `zaip-ai/zaip-aios` repository. When the enrolled policy names an older release, prepare a reviewed policy for the exact new version and fixed qualification profile; preserve repository, branch, channel, publication mode, non-force/non-replacement controls and trusted key. After successful signed local qualification and before Release publication, set that one variable to the exact UTF-8 policy bytes encoded in base64 and read it back byte-for-byte. A missing key, changed trust, weaker policy, failed readback or insufficient GitHub permission remains a blocker, not a reason to ask again for the already-authorized routine version update.
+
 After exact-candidate qualification, a missing GitHub Release is normal. Unless the request is explicitly push-only, use the configured entrypoint to create a draft for that SHA or resume a verified draft for the same SHA; do not recreate an existing Release. A published Release for the exact SHA is verified as a no-op, or its failed checks are repaired within the bounded cycle. An authentication or API error does not prove that a Release is absent.
 
 For a consumer repository, bootstrap its own Ed25519 trust store and define `configured_branch`, GitHub version `vN.N`, and `required_commands` in its project policy. `prepare` runs only those policy commands and signs a receipt after the Git identity is unchanged before and after them. `verify` checks the configured branch, exact SHA/tree, policy digest and trusted key. `guarded-push` runs prepare and verify before its explicit push command; a failed required command, dirty checkout, changed SHA/policy, or unavailable key prevents that command from running. This consumer flow is GitHub-only: it has no npm channel, package manifest version, or TGZ contract.
@@ -134,4 +136,4 @@ Unless the request is push-only, resolve the release identity before mutation us
 
 ## Success condition
 
-Finish only when the local and remote hashes match, every required observable check is successful, and the intended worktree is clean. Otherwise report the exact terminal blocker and the repair cycles consumed.
+For a full framework deploy, finish only when the local and remote hashes match, the intended worktree is clean, the exact Release identity/assets/body are verified, the associated `publish-cli.yml` run reaches success, and the npm registry confirms the intended `@zaip-ai/cli@N.N.0` version, dist-tag and artifact integrity. The workflow uses its configured GitHub credential/environment; a local `.env` does not publish the package. A published Release with failed or unobserved npm is partial, never a completed deploy. For a consumer or an explicit push-only request, apply only its authorized GitHub scope. Otherwise report the exact terminal blocker and repair cycles consumed.

package/templates/.agents/skills/zaip-skill-github-deploy/scripts/github-deploy-contract.test.mjs

@@ -20,6 +20,13 @@ const managedDeployFiles = [
 
 test("framework lock matches the deploy guidance and executable contract", async () => {
   const lock = await readFile(resolve(root, "config", "framework.lock.yaml"), "utf8");
+  const installerPlaceholder = "# Generated transactionally by @zaip-ai/cli during installation.\n";
+  if (lock === installerPlaceholder) {
+    // The npm template deliberately ships no repository-specific hashes. The
+    // installer creates the complete lock only after projecting the selected
+    // profile into the consumer workspace.
+    return;
+  }
   for (const path of managedDeployFiles) {
     const digest = createHash("sha256")
       .update(await readFile(resolve(root, path)))
@@ -35,24 +42,40 @@ test("explicit Git publication verbs select the guarded deploy skill", async ()
     readFile(resolve(root, "rules", "core.md"), "utf8"),
   ]);
   assert.match(skill, /explicit current-turn request to `deploy`, `push`, `publicar`/);
-  assert.match(skill, /never grants publication automatically/);
+  assert.match(skill, /discussing or editing deployment does not authorize publication/);
   assert.doesNotMatch(skill, /standing automatic deployment|activate it automatically/);
   assert.match(openai, /\$zaip-skill-github-deploy/);
   assert.match(openai, /fa.a deploy/);
   assert.match(core, /seleciona/);
 });
 
-test("deploy guidance preserves the canonical Task subject and Git-only boundary", async () => {
+test("deploy guidance preserves canonical Task identity and builder-versus-consumer boundary", async () => {
   const [skill, workflow] = await Promise.all([
     readFile(resolve(skillRoot, "SKILL.md"), "utf8"),
     readFile(resolve(root, "rules", "workflow.md"), "utf8"),
   ]);
   assert.ok(skill.includes("[CODEX|CLAUDE] [P:XXXX] [S:XXXX] [T:XXXX] <Task title>"));
   assert.match(skill, /exclusively `CODEX` or `CLAUDE`; `AUTO` is not part/);
-  assert.match(skill, /Git-only publication/);
+  assert.match(skill, /Consumer repositories follow their own GitHub-only policy/);
+  assert.match(skill, /“faça deploy” means the guarded push, GitHub Release and observation of the GitHub Actions npm publication/);
   assert.match(workflow, /commitar o diff evidenciado com pathspecs explícitos/);
 });
 
+test("framework deploy follows Release-triggered npm publication without claiming partial success", async () => {
+  const [skill, workflow, publishWorkflow] = await Promise.all([
+    readFile(resolve(skillRoot, "SKILL.md"), "utf8"),
+    readFile(resolve(skillRoot, "references", "deployment-workflow.md"), "utf8"),
+    readFile(resolve(root, "..", ".github", "workflows", "publish-cli.yml"), "utf8"),
+  ]);
+  assert.match(publishWorkflow, /release:\s*\n\s*types: \[published\]/);
+  assert.match(publishWorkflow, /npm publish /);
+  assert.match(skill, /publish-cli\.yml.*registry confirmation/s);
+  assert.match(skill, /npm fails or cannot be observed.*partial or blocked/);
+  assert.match(skill, /explicit push-only request.*does not create a Release or publish npm/);
+  assert.match(workflow, /private Ed25519 release key is distinct from the Git SSH key and a local `\.env` npm token/);
+  assert.match(workflow, /A published Release with failed or unobserved npm is partial/);
+});
+
 test("faça deploy authorizes the complete selected worktree with safety gates", async () => {
   const skill = await readFile(resolve(skillRoot, "SKILL.md"), "utf8");
   assert.match(skill, /commits covering all versionable pending changes/);
@@ -73,8 +96,8 @@ test("deploy permission and reconciliation remain explicit and recoverable", asy
   assert.match(skill, /Restore with `git stash apply`/);
   assert.match(skill, /local branch, recovery branch or detached state as the source candidate/);
   assert.match(skill, /configured deploy branch is the remote target/);
-  assert.match(openai, /worktree selecionado inteiro como escopo autorizado/);
-  assert.match(openai, /branch local ou detached como origem/);
+  assert.match(openai, /\$zaip-skill-github-deploy/);
+  assert.match(openai, /builder zaip-aios.*Release.*workflow npm/);
 });
 
 test("workflow retains the explicit publication routing contract", async () => {

package/templates/.agents/skills/zaip-skill-release-qualification/references/local-preparation.md

@@ -17,7 +17,13 @@ node scripts/local-release-preparation.mjs prepare --repository <absolute-reposi
 ```
 
 The framework policy is an administrator-reviewed file whose bytes must match the protected
-GitHub policy. Gates are fixed in the versioned helper, not supplied by the caller. Preparation
+GitHub policy before Release publication. The user's 2026-09-23 authorization permits the
+builder deploy to update only `ZAIP_LOCAL_RELEASE_POLICY_B64` for each exact new version after
+successful signed local qualification, with byte-for-byte readback and no key/trust rotation.
+The policy must name the exact repository, `main`, channel, `N.N`/`N.N.0` versions, selected
+fixed qualification profile, `github-actions-only`, `signed-release-linux-smoke`, and disabled
+force/replacement/pilot flags. Do not reuse an older version's policy unchanged or ask again
+solely because its version is stale. Gates are fixed in the versioned helper, not supplied by the caller. Preparation
 fails at the first failed gate. The default `essential-v3` profile validates source size, locks,
 build/type integrity, package/SBOM/TGZ binding, dependency audit and one clean installed-consumer
 doctor/SQLite/API smoke. It does not run browser navigation across every dashboard tab or XLSX

package/templates/.agents/zaip-aios/VERSION

@@ -1 +1 @@
-3.7
+3.8

package/templates/.agents/zaip-aios/guides/18-catalogo-de-agentes.md

@@ -68,7 +68,7 @@ O dispatch autônomo passa os `Task.write_scopes` a essa seleção **por Task**
 
 O `budget.soft_cycles` também acompanha o agente selecionado por Task e governa seu checkpoint suave. Tokens continuam observados para telemetria e custo, mas não interrompem nem exigem checkpoint. Para comparar agentes, use `zaip run aggregate --agent agent-ID`; o resultado inclui duração coberta, ciclos de uso observados, tokens, custo, cobertura e Runs de rework.
 
-Nanda (`agent-reviewer`) usa `gpt-5.6-terra` com esforço `medium` e `soft_cycles: 12`, proporcional à revisão standard. Ana (`agent-auditor`) permanece `gpt-5.6-sol`/`high` para auditoria crítica ou explicitamente auditável; Luiz (`agent-security-auditor`) permanece `gpt-5.6-sol`/`high` para auditoria de segurança explícita.
+Nanda (`agent-reviewer`) usa `gpt-6-sol` com esforço `medium` e `soft_cycles: 12`, proporcional à revisão standard. Ana (`agent-auditor`) usa `gpt-6-sol`/`high` para auditoria crítica ou explicitamente auditável; Luiz (`agent-security-auditor`) usa `gpt-6-sol`/`high` para auditoria de segurança explícita.
 
 ## Dashboard e segurança operacional
 

package/templates/.agents/zaip-aios/guides/20-instalacao-detalhada.md

@@ -119,7 +119,7 @@ O setup identifica a propriedade pelo `framework.lock.yaml`: Rules presentes no
 framework; as demais são locais ao projeto e são preservadas em instalações e upgrades. Conflitos
 de ID ou contradições bloqueiam a operação; não existe override silencioso.
 
-Também gera adapters mínimos, como `AGENTS.md` e `CLAUDE.md`, sem sobrescrever conteúdo do usuário silenciosamente.
+Também gera adapters mínimos, como `AGENTS.md` e os wrappers de skills dos clientes, sem sobrescrever conteúdo do usuário silenciosamente.
 
 ## Migrar estado V1
 

package/templates/.agents/zaip-aios/guides/23-orquestracao-de-modelos.md

@@ -62,7 +62,7 @@ partir do terceiro, quando a rota válida o selecionar; não se torna reviewer
 ou finalizer. A exceção de execução não acrescenta tentativas nem amplia
 write scopes.
 
-O primeiro replanejamento usa `gpt-5.6-sol`; os seguintes permitidos usam
+O primeiro replanejamento usa `gpt-6-sol`; os seguintes permitidos usam
 `gpt-6-astra`. Executor e replanejador são invocações diferentes. Planejar
 com Astra não obriga a executar com Astra no segundo bloco.
 
@@ -93,9 +93,8 @@ não crie outra Task ou apague `.local` para renovar a quota.
 
 | Modelo | Papel dentro da política ZAIP |
 | --- | --- |
-| `gpt-5.6-luna` | Execução clara e delimitada, conforme catálogo e capacidade |
-| `gpt-5.6-terra` | Implementação, testes e integração cotidianos |
-| `gpt-5.6-sol` | Planejamento difícil, revisão especializada e primeiro replanejamento |
+| `gpt-6-luna` | Execução clara e delimitada, conforme catálogo e capacidade |
+| `gpt-6-sol` | Implementação, testes, integração, planejamento difícil, revisão especializada e primeiro replanejamento |
 | `gpt-6-astra` | Replanejamentos e exceção de execução permitidos pelo preset |
 
 Esses são papéis configurados pelo ZAIP, não alegações de benchmark dos

package/templates/.agents/zaip-aios/guides/24-calculo-de-custos-openai.md

@@ -42,20 +42,20 @@ BRL_total = USD_total × cotação_USD_BRL
 
 A conversão para BRL é a última etapa. Quando a moeda exibida é USD, não há conversão.
 
-## Exemplo didático — GPT-5.6 Sol, Standard
+## Exemplo didático — GPT-6 Sol, Standard
 
-No snapshot local consultado durante a redação, `gpt-5.6-sol` contém input US$5, cache US$0,50 e output US$30 por 1M. Esses números ilustram a fórmula; confira o catálogo e a fonte registrada antes de usar valores em uma decisão atual. Para 1.000.000 input, 800.000 cache, 100.000 output e 70.000 reasoning:
+No catálogo consultado em 2026-09-22, `gpt-6-sol` contém input US$2, cache US$0,20 e output US$10 por 1M. Esses números ilustram a fórmula; confira o catálogo e a fonte registrada antes de usar valores em uma decisão atual. Para 1.000.000 input, 800.000 cache, 100.000 output e 70.000 reasoning:
 
 ```text
 input sem cache = 1.000.000 - 800.000 = 200.000
-input = 0,2 × 5,00 = US$ 1,00
-cache = 0,8 × 0,50 = US$ 0,40
-output = 0,1 × 30,00 = US$ 3,00
+input = 0,2 × 2,00 = US$ 0,40
+cache = 0,8 × 0,20 = US$ 0,16
+output = 0,1 × 10,00 = US$ 1,00
 reasoning = US$ 0,00 adicional (já está nos 100.000 output)
-total = US$ 4,40
+total = US$ 1,56
 ```
 
-Com uma cotação **hipotética** USD/BRL de 5,45: `4,40 × 5,45 = R$ 23,98`.
+Com uma cotação **hipotética** USD/BRL de 5,45: `1,56 × 5,45 = R$ 8,50` (arredondado).
 
 ## Service tier, contexto e dados incompletos