@zaip-ai/cli 5.9.0 → 6.0.1

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

@@ -1,11 +1,11 @@
 b146bd0c7c60b1ab43c4f71e0b1d2262c6df6da6f7053a0425f834ccb77a6b48  LICENSE
 bc02cba77e8d51e5c580f43668863dc868eda66f1ff663bfaa49fcf3ca16320e  THIRD_PARTY_NOTICES.md
-a3cd6b827c4a4e7e7601c9aace0a77a7915cfa18b8b039139b1dcbb1c4b22c0d  VERSION
-f6fd9810de5e51675406cdf3bead03f615107d18194ee3a90778d5b40cdfc98b  bin/zaip.mjs
-92226ac363c4a076769fc7bfcb7dbf372bcbb6195085c8beaf2c9eb3faeb1215  manifest.json
+cf3701cb2416e87a99c0e77dbd0518fc4fc27e390f025c024e6ed1c389c928e0  VERSION
+ea96e255489fc59126568fbf2e36f88d46a56442514a43aba211f33ef37a1c5e  bin/zaip.mjs
+3b5cf6b8aeebc457cde6a5a3d889d042983272ad8695b4acb95c8be581ccdaac  manifest.json
 7f89219d7c567c82a51679ad136d84364bded7ac659492537e125d33b1d58a7a  migrations/001-layout-v1.json
 5f8c48b286d0b44d8fbb57a9a5d009a8a500439aa3148d750b8f193f72995c9f  migrations/002-layout-v2.json
 2bd34b2f5c253a2167d9addaf1994167308ac0bb4fec22a794c8a5b488205278  pnpm-lock.sha256
-74b9885a878a98e0eb27e570156e85ccb3ed9c417dd2faf26e72cb5dda992ae9  provenance.json
-d77347313b33644005a3f31d1324d8f1f1527c24b1686ec33325e4570bd1f31d  sbom.cdx.json
+9a3baaaa1db06fe6caa56dc3b3e9391625e08969f887fb3afcc38f7a69d8c6c9  provenance.json
+56beff20a7c2bd8e3e457f32cc50559528e1b4db38db44b7ef7f87e9ab07aba0  sbom.cdx.json
 b3ffedf9e146be802a15b4009f33e031dec3071ca1525e12c67606fd964a3067  schemas/contracts.schema.json

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

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 2,
   "name": "zaip-aios",
-  "version": "5.9.0",
+  "version": "6.0.1",
   "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": "5.9.0",
+  "version": "6.0.1",
   "source_origin": "zaip-aios:local-build",
   "lockfile_sha256": "b5e11351951654d41aa78dc858d43990a12964ba4051a070613ac8b11bc73a27",
-  "sbom_sha256": "d77347313b33644005a3f31d1324d8f1f1527c24b1686ec33325e4570bd1f31d",
-  "runtime_sha256": "75b82243c2590814de27485f7fe35cce33c36c7a57091863ecdb1f1571b27bb3",
-  "statement_sha256": "7f8943175b8194a9be1f6c230940523811dd8b09e636701f49d68f64049aad13"
+  "sbom_sha256": "56beff20a7c2bd8e3e457f32cc50559528e1b4db38db44b7ef7f87e9ab07aba0",
+  "runtime_sha256": "8781c0725c48b5a6d20f156fd23d03842ba161ada04e8080422442f1ec2f29e2",
+  "statement_sha256": "e8a81f1ce0a1d0140772a85671588ceab818c86d19422da4bf23fe4976df3918"
 }

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

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

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

@@ -41,6 +41,7 @@ Commit subjects retain `[CODEX|CLAUDE] [P:XXXX] [S:XXXX] [T:XXXX] <Task title>`
 - **Commits:** use `scripts/guarded-commits.mjs` with its reviewed CLI and valid scoped checks to push the exact SHA to the configured branch. Do not enter release qualification, change a version or create a Release merely for this mode. Installer/security work still runs checks directly required by its impact.
 - **Release:** read [release identity](references/release-identity.md), then compose `$zaip-skill-release-qualification` and [local preparation](../zaip-skill-release-qualification/references/local-preparation.md) for the actual distribution surface. Verified builder uses `scripts/local-release-deploy.mjs`; consumers create only their GitHub Release under their own checks, without builder npm, signing-key or protected-policy requirements.
 - Before release versioning, verify whether the candidate SHA is already published. The same published SHA is a no-op, never an empty new Release. Resume a verified draft or retry only observed incomplete delivery with the exact same SHA and identity. A changed candidate requires new identity/evidence.
+- An explicitly authorized corrective patch uses product `N.N`, package `N.N.P` with `P > 0`, and a new immutable tag `vN.N.P`. Preserve the original tag/package and the next open cycle. Require the signed patch policy, exact base publication, observed maintenance actor, reviewed paths and all candidate/artifact/remote checks. Record verified delivery in the separate patch ledger; never use ordinary cycle advance for a patch or infer patch authority from a retry.
 - Review detailed UTF-8 notes only for the Release, following [release notes](references/release-notes.md). Observe the complete previous-Release-to-candidate Git range as source/evidence, including changes beyond the current chat. Validate the inventory and compare the published body byte-for-byte; never use generated notes alone.
 
 Dense source/template/package/TGZ gates belong to builder release qualification. Generic commits use targeted validation, without an automatic full suite, test-count cap or Task wallclock limit. Apply the frozen autonomy profile: balanced permits 10 executions total and 3 replans; tests/tool calls are not executions and resumption does not reset the budget. Do not add an independent five-cycle limit.
@@ -51,13 +52,13 @@ For post-receipt rapid reuse in the verified builder, follow `docs/quality/v49-d
 
 Compare the exact pushed SHA with the configured remote ref. If a push result is uncertain, read remote state before retrying. Observe required checks for that SHA, inspect failed steps and repair their evidenced cause within the frozen profile; do not repeat unchanged failures or bypass a gate.
 
-Commits success requires the scoped exact-SHA push and its required checks. Consumer release success additionally requires the verified tag, SHA and reviewed body. Builder release success additionally requires its verified signed assets, terminal `publish-cli.yml` success and registry version, dist-tag and integrity for `@zaip-ai/cli@N.N.0`. A Release with failed or unobserved npm is partial. An unavailable check stays unconfirmed.
+Commits success requires the scoped exact-SHA push and its required checks. Consumer release success additionally requires the verified tag, SHA and reviewed body. Builder release success additionally requires its verified signed assets, terminal `publish-cli.yml` success and registry version, dist-tag and integrity for the signed target package (`@zaip-ai/cli@N.N.0` in standard mode, `@zaip-ai/cli@N.N.P` in patch mode). A Release with failed or unobserved npm is partial. An unavailable check stays unconfirmed.
 
 Give a brief chat result with the delivered mode, branch/SHA, Release link when applicable and any actual pending gate. Keep detailed change notes in the Release and sanitized evidence in the owned lifecycle. Formal closure belongs to the responsible orchestrator/finalizer. This GitHub workflow grants no provider deploy, database production, SQL application or host power action.
 
 ## Pre-main candidate and release-cycle audit
 
-For the verified framework builder, release delivery requires `.agents/config/release-cycle.json` frozen at the version being released, a clean candidate SHA, remote `main` as its ancestor, and no stale branch/worktree. Every owner SPEC DAG predecessor must be completed. The sole open exception is the critical release-only Task coordinator delegated from the owner SPEC/Execution/macro Run; its exact lineage, predecessor states and candidate records are authenticated at freeze, audit and advance. Other current-release Task/PRD/SPEC work blocks. `scripts/local-release-deploy.mjs` runs fixed local checks at the exact SHA without creating a remote candidate branch. It then pushes only `main` and waits for the exact successful `main` push run of `pre-main-candidate.yml` before publishing a Release. A critical framework commit follows the same branch-free sequence through `guarded-commits.mjs`. Failed local checks block the push; failed or unavailable remote CI blocks Release publication and requires repair on `main`.
+In standard mode, verified framework builder release delivery requires `.agents/config/release-cycle.json` frozen at the version being released, a clean candidate SHA, remote `main` as its ancestor, and no stale branch/worktree. Every owner SPEC DAG predecessor must be completed. The sole open exception is the critical release-only Task coordinator delegated from the owner SPEC/Execution/macro Run; its exact lineage, predecessor states and candidate records are authenticated at freeze, audit and advance. Other current-release Task/PRD/SPEC work blocks. `scripts/local-release-deploy.mjs` runs fixed local checks at the exact SHA without creating a remote candidate branch. It then pushes only `main` and waits for the exact successful `main` push run of `pre-main-candidate.yml` before publishing a Release. A critical framework commit follows the same branch-free sequence through `guarded-commits.mjs`. Failed local checks block the push; failed or unavailable remote CI blocks Release publication and requires repair on `main`.
 
 When the same authorized direct Task root implements the product repair and release, the explicit integrated coordinator mode in `$zaip-skill-release-qualification` can freeze while that Task and Run are active. It keeps the clean exact-SHA, only-main, no-other-work, independent validation and publication gates. Record this selection in the frozen cycle; it does not create a second Task or client turn.
 

package/templates/.agents/skills/zaip-skill-github-deploy/references/release-identity.md

@@ -37,7 +37,9 @@ Generic consumer deploy under auto selects commits. Only release mode enters thi
 
 Recognize framework source only through approved origin `zaip-ai/zaip-aios`, root package `@zaip-ai/aios` and public CLI package `@zaip-ai/cli`. Names or installed framework files do not prove builder identity; contradictory signals block classification.
 
-Select the next allowed `N.N` from observed release history, then update canonical root `package.json#version` to `N.N.0` and align the declared public/CLI manifests through the version tooling before committing and qualifying. The root manifest is the candidate's version source. Do not allocate an independent GitHub tag or replace version strings broadly. Retries retain the already-assigned version.
+For an ordinary release, select the next allowed `N.N` from observed release history, then update canonical root `package.json#version` to `N.N.0` and align the declared public/CLI manifests through the version tooling before committing and qualifying. The root manifest is the candidate's version source. Do not allocate an independent GitHub tag or replace version strings broadly. Retries retain the already-assigned version.
+
+For an explicitly authorized corrective patch, use product `N.N`, package `N.N.P` (`P > 0`) and tag `vN.N.P`. Apply this identity with the version updater's explicit patch option. The signed patch policy binds the mapping, immutable base tag/SHA, source base and reviewed file inventory. A changed package never reuses the original tag or npm version. The next ordinary open cycle stays unchanged; patch delivery has a separate verified ledger. Local manifests describe the candidate, not publication.
 
 Protected delivery uses `scripts/local-release-deploy.mjs`. First resolve mode in the Task's local area; only release mode may run signed `local-release-preparation.mjs prepare`. After that preparation successfully creates the receipt directory, save the actual UTF-8 human request at `<output-dir>/deploy-request.txt` and resolve its final-candidate contract to `<output-dir>/deploy-contract.json`. Do not pre-create the output directory just to write these files: preparation treats an existing directory as an immutable receipt cache. The resolver retains `--repository ROOT --request-file FILE --plan-file FILE`; the release helper reads only those fixed paths before reusing preparation or using publication credentials. Do not add request/plan CLI arguments or expand the installed hook allowlist. Resolve against the final committed candidate identity; stale contracts block delivery.
 

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

@@ -0,0 +1,25 @@
+import assert from "node:assert/strict";
+import { repositoryKind } from "./deploy-contract.mjs";
+export function assertPatchManifestVersions(builder) {
+  assert.equal(
+    repositoryKind({
+      ...builder,
+      rootVersion: "6.0.1",
+      cliVersion: "6.0.1",
+      workspaceVersion: "6.0.1",
+    }),
+    "builder",
+  );
+  for (const version of ["06.0.1", "6.0.01", "6.0.1-beta", "6.0"]) {
+    assert.throws(
+      () =>
+        repositoryKind({
+          ...builder,
+          rootVersion: version,
+          cliVersion: version,
+          workspaceVersion: version,
+        }),
+      /versions/,
+    );
+  }
+}

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

@@ -57,7 +57,7 @@ export function repositoryKind({
     "Conflicting builder identity; repository and package manifests must agree",
   );
   assert(
-    /^\d+\.\d+\.0$/.test(rootVersion ?? "") &&
+    /^(?:0|[1-9]\d*)\.(?:0|[1-9]\d*)\.(?:0|[1-9]\d*)$/.test(rootVersion ?? "") &&
       rootVersion === cliVersion &&
       rootVersion === workspaceVersion,
     "Builder manifest versions must agree",
@@ -105,7 +105,7 @@ export function requestedDeployment(request) {
       .split(/\r?\n|(?<=[.!])\s+/)
       .map(normalize)
       .some((line) =>
-        /^(?:(?:(?:faca|realize|execute)\s+(?:as mudancas necessarias|os ajustes necessarios|as melhorias|todos os testes)(?:\s+e\s+(?:todos os testes|as validacoes|os testes))?|pode (?:implementar|executar))\s+e\s+|depois\s+|apos\s+os\s+ajustes\s+e\s+(?:os\s+)?testes\s+)(?:publique|publica|publicar)\s+(?:(?:em|como)\s+)?(?:uma\s+|a\s+)?(?:nova|proxima)\s+versao[.!]?$/.test(
+        /^(?:(?:(?:faca|realize|execute)\s+(?:as mudancas necessarias|(?:todos os |os )(?:ajustes|ajuates)(?: necessarios)?|as melhorias|todos os testes)(?:\s+e\s+(?:todos os testes|as validacoes|os testes))?|pode (?:implementar|executar))\s+e\s+|depois\s+|apos\s+os\s+ajustes\s+e\s+(?:os\s+)?testes\s+)(?:publique|publica|publicar)\s+(?:(?:em|como)\s+)?(?:uma\s+|a\s+)?(?:(?:nova|proxima)\s+versao|v(?:0|[1-9]\d*)\.(?:0|[1-9]\d*))(?:\s+com\s+uma\s+versao\s+final\s+pronta\s+(?:para|pra)\s+producao)?[.!]?$/.test(
           line,
         ),
       );

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

@@ -11,6 +11,7 @@ import {
   resolveDeployment,
   verifyContract,
 } from "./deploy-contract.mjs";
+import { assertPatchManifestVersions } from "./deploy-contract-patch.test-support.mjs";
 import { criticalTaskInRange, guardedCommits } from "./guarded-commits.mjs";
 
 const builder = {
@@ -193,6 +194,7 @@ test("preferences are project-owned; one-shot overrides, scope and invalid confi
 });
 test("builder identity requires origin plus all three agreeing manifests", () => {
   assert.equal(repositoryKind(builder), "builder");
+  assertPatchManifestVersions(builder);
   assert.equal(repositoryKind(consumer), "consumer");
   for (const identity of [
     { ...builder, origin: consumer.origin },

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

@@ -12,6 +12,33 @@ const builder = {
 };
 const input = (request, identity) => ({ request, identity });
 
+test("explicit major after adjustments preserves literal authority and refuses human holds", () => {
+  const directive =
+    "Faça todos os ajuates e publique a v6.0 com uma versao final pronta pra produção";
+  const request = `Ainda tem nota baixa nos itens. Governança e fechamento, eficiência e recuperação\n\nPreciso melhorar para pelo.menos uma nota 8\n\n${directive}`;
+  const plan = resolveDeployment(input(request, builder));
+  assert.equal(plan.mode, "release");
+  assert.equal(plan.phase, "publish");
+  assert.equal(plan.scope, "current-work");
+  assert.equal(plan.version, "6.0");
+  assert.equal(plan.npm_publication, true);
+  assert.equal(
+    resolveDeployment(input(directive.replace("ajuates", "ajustes"), builder)).version,
+    "6.0",
+  );
+  for (const rejected of [
+    `${directive}?`,
+    `Ele disse: ${directive}`,
+    `"${directive}"`,
+    `${directive} se eu aprovar`,
+    `${directive}\nAguarde minha confirmação.`,
+    `Não publique a v6.0.\n${directive}`,
+    directive.replace("e publique", "e não publique"),
+    directive.replace("v6.0", "v6.0.1"),
+  ])
+    assert.equal(resolveDeployment(input(rejected, builder)).mode, "none", rejected);
+});
+
 test("execution and next-version publication remain bounded to a direct human request", () => {
   const directive = "Pode executar e publicar próxima versão";
   const plan = resolveDeployment(input(directive, builder));

package/templates/.agents/skills/zaip-skill-lifecycle-closure/references/post-publication-task-first.md

@@ -50,6 +50,18 @@ Quando existe um reparo de publicador posterior à tag, a fronteira exige invent
 
 ## Procedimento canônico
 
+Recibos v3 também congelam o status de Execution e SPEC. Uma Execution já
+`running` após interrupção pode ser a baseline exata; o consumo não incrementa
+novamente sua revisão. SPEC histórica `ready` é recusada ainda no preview:
+o fluxo de recuperação publicada exige `blocked` ou `active`, sem emitir um
+recibo impossível de consumir. Recibos antigos permanecem conservadores.
+
+Vários recibos da mesma manutenção podem ser consumidos no mesmo turno observado.
+O claim versionado conserva cada etapa e exige o predecessor e seu Gui concluídos
+antes da seguinte. Cada recibo/Decision continua autenticado separadamente. O
+predecessor imediato passa a ser a etapa anterior; a autoridade original continua
+sendo a manutenção. Não crie turnos artificiais para contornar exclusividade.
+
 1. Inspecione somente os IDs envolvidos, a revisão atual e as evidências originais.
    Confirme que os critérios de aceite históricos realmente foram satisfeitos.
    Publicação, teste técnico aprovado e `run.finished` não substituem esse aceite.

package/templates/.agents/skills/zaip-skill-release-qualification/SKILL.md

@@ -11,6 +11,8 @@ Use after `$zaip-skill-github-deploy` resolves release mode, or when local prepa
 
 Preparation, verification and dry-run do not publish. The request's resolved route supplies publication authority separately.
 
+An explicitly authorized patch uses `--mode patch --package-version N.N.P` with product `--version N.N`. Its signed policy and receipt bind both identities, the base publication, observed actor, cycle snapshot and reviewed paths. The patch audit preserves the next open cycle; it does not freeze or advance that ordinary cycle. All exact-candidate, artifact, signature, remote CI and npm checks still apply. Follow the [release identity contract](../zaip-skill-github-deploy/references/release-identity.md) and record verified patch delivery separately.
+
 For readiness grades, load `RULE-PRODUCTION-READINESS` and apply
 `technical-essential-v1` from `docs/quality/production-readiness.md`. Grade 9
 requires the six essential criteria; grade 10 adds reviewed concurrency,
@@ -29,6 +31,15 @@ Read [local preparation](references/local-preparation.md) for the selected surfa
 
 ## Builder release qualification
 
+An explicitly requested next major may replace an unpublished open minor using
+`task retarget-open-release TASK --run RUN --from N.N --to NEXT.0 --expected-revision REV`.
+Preview returns the exact payload for a confirmed human contract Decision scoped
+to the Change; apply with `--decision DEC-HUMAN-... --apply`. Finish active children
+first. This Task-first operation journals both preimages, preserves publication
+history and resumes interrupted writes without overwriting unrelated changes.
+The `planned-major-retarget` row is planning only; it never proves publication of
+the skipped minor. Freeze and all distribution gates still apply.
+
 Local builder preparation defaults to signed `essential-v3`: deterministic source/lock/parity, build/type integrity, dependency audit, prioritized installer/rollback/release regressions, package/SBOM/TGZ binding and one clean installed-consumer doctor/SQLite/API smoke.
 
 These dense distribution checks are release gates. Change validation outside release remains targeted, with installer/security checks selected when directly impacted. Do not automatically run the full suite for generic commits, impose a test-count ceiling or classify a Task by wallclock duration.

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

@@ -94,6 +94,20 @@ These commands exist only in the source repository `zaip-ai/zaip-aios`. Values i
 must be replaced with the authorized candidate and external paths. GitHub version `N.N` maps
 to tag `vN.N` and package version `N.N.0`.
 
+For an explicitly authorized corrective patch, use `--mode patch --version N.N
+--package-version N.N.P` on the patch-aware preparation, staging and deploy
+commands. The signed schema-2 policy and schema-3 receipt bind the immutable base
+publication, observed delivery actor, exact paths and unchanged open product
+cycle. The patch ledger replaces ordinary cycle advance for this route. See
+[the patch contract](../../zaip-skill-github-deploy/references/release-identity.md).
+
+If an unpublished patch candidate needs a corrected path inventory, `stage-policy`
+accepts `--recover-unpublished-from-sha256 <old-policy-sha256>`. Only
+`allowed_paths` may change. Recovery requires the unchanged remote base, absent
+tag and Release, authenticated GitHub access and a successful npm inventory
+without that version. It preserves a verified private backup and requires a new
+signed receipt; unavailable publication checks never count as absence.
+
 ```text
 node scripts/local-release-preparation.mjs keygen --output-dir <new-stable-private-key-directory>
 node scripts/local-release-preparation.mjs bootstrap --trust-store <new-stable-private-key-directory>/trust --public-key <new-stable-private-key-directory>/release-public.pem --key-id <new-key-id> --channels latest

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

@@ -1 +1 @@
-5.9
+6.0