@gradial/aci 0.1.52-rc.33 → 0.1.52-rc.34

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.1.52-rc.34
+
+### Changed
+
+- The `dam-delivery` agent skill now says a future `expiresAt` is admitted to
+  public delivery and can be set, moved, or cleared on a public version; only
+  a past expiry vetoes approval or is refused on a public version.
+
 ## 0.1.52-rc.33
 
 ### Migration required

package/README.md

@@ -1,6 +1,6 @@
 # Agentic Content Infrastructure SDK
 
-`@gradial/aci` `0.1.52-rc.33` is a pre-1.0 public-surface reset for the ACI
+`@gradial/aci` `0.1.52-rc.34` is a pre-1.0 public-surface reset for the ACI
 client SDK. Breaking changes from the old `0.1.x` accidental surface are
 intentional: the root import is framework-neutral, framework runtime behavior is
 behind explicit subpaths, and the first required customer path is React/Next.
@@ -8,7 +8,7 @@ behind explicit subpaths, and the first required customer path is React/Next.
 ## Install
 
 ```bash
-npm install @gradial/aci@0.1.52-rc.33 zod@^4
+npm install @gradial/aci@0.1.52-rc.34 zod@^4
 ```
 
 ## Root Import
@@ -137,13 +137,13 @@ host bundles select and serve immutable release artifacts.
 The first RC scaffold path is Next:
 
 ```bash
-npx @gradial/aci@0.1.52-rc.33 init my-site --template next-starter
+npx @gradial/aci@0.1.52-rc.34 init my-site --template next-starter
 ```
 
 List available templates:
 
 ```bash
-npx @gradial/aci@0.1.52-rc.33 init --list
+npx @gradial/aci@0.1.52-rc.34 init --list
 ```
 
 ## Personalization: The One-Tag Install

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gradial/aci",
-  "version": "0.1.52-rc.33",
+  "version": "0.1.52-rc.34",
   "repository": {
     "type": "git",
     "url": "https://github.com/gradial/bare-metal-go.git",
@@ -160,11 +160,11 @@
     "zod": "^4.0.0"
   },
   "optionalDependencies": {
-    "@gradial/aci-cli-darwin-arm64": "0.1.52-rc.33",
-    "@gradial/aci-cli-darwin-x64": "0.1.52-rc.33",
-    "@gradial/aci-cli-linux-arm64": "0.1.52-rc.33",
-    "@gradial/aci-cli-linux-x64": "0.1.52-rc.33",
-    "@gradial/aci-cli-win32-arm64": "0.1.52-rc.33",
-    "@gradial/aci-cli-win32-x64": "0.1.52-rc.33"
+    "@gradial/aci-cli-darwin-arm64": "0.1.52-rc.34",
+    "@gradial/aci-cli-darwin-x64": "0.1.52-rc.34",
+    "@gradial/aci-cli-linux-arm64": "0.1.52-rc.34",
+    "@gradial/aci-cli-linux-x64": "0.1.52-rc.34",
+    "@gradial/aci-cli-win32-arm64": "0.1.52-rc.34",
+    "@gradial/aci-cli-win32-x64": "0.1.52-rc.34"
   }
 }

package/templates/common/.agents/skills/dam-delivery/SKILL.md

@@ -120,7 +120,7 @@ Read `effects` in the response to see what happened:
 | Effect | Meaning |
 | --- | --- |
 | `live_published` | the link now serves this version |
-| `public_admission_vetoed:<cause>` | the version is approved but **not public**: it carries an expiry date, an embargo still in force, a usage block, or a license that does not allow publication. The link keeps serving the previous public version, if there is one |
+| `public_admission_vetoed:<cause>` | the version is approved but **not public**: its expiry date has already passed, an embargo is still in force, a usage block, or a license that does not allow publication. A future expiry date does not veto; the link serves until that date. The link keeps serving the previous public version, if there is one |
 | `live_plane_unconfigured` | a local or dev stack with no delivery wired; nothing was made public |
 
 On the asset record (`GET /v1/dam/assets/{assetId}`), a public version
@@ -133,9 +133,11 @@ shows `deliveryTier: "public"` in its governance, and a refused one shows
   the previous public version, or stops serving if there is none) or
   `archive` the asset. Both use the same lifecycle endpoint.
 - **Governance that would have blocked the approval cannot be added while
-  a version is public.** A patch adding an expiry date, an embargo, a
+  a version is public.** A patch adding a past expiry date, an embargo, a
   usage block, or a license without publication is refused with a
-  conflict that tells you to demote first.
+  conflict that tells you to demote first. A future expiry date can be
+  set, moved, or cleared on a public version; the link stops serving the
+  version when that date arrives.
 - **Changes take up to five minutes to show everywhere.** Responses are
   `Cache-Control: public, max-age=300`, so a new version or a take-down
   can lag by that long in browsers and CDN caches. On AWS CloudFront,