Prepare authorized CellScript 0.30 release and website

Author: a19q3

BRANCHES.md

@@ -4,10 +4,11 @@
 
 The workspace and editor are prepared as 0.30.0 with the bounded
 `cellscript-source-semantics-2027-0.30-v1` identity. See the
-[release candidate notes](docs/releases/CELLSCRIPT_0_30_RELEASE_NOTES.md).
+[release notes](docs/releases/CELLSCRIPT_0_30_RELEASE_NOTES.md).
 Candidate `74cff5fd` and its website/editor gitlinks were pushed on 2026-09-19
-after the required gates passed. The no-TAC publication constraint still
-applies; no tag or public release is implied. See the
+after the required gates passed. On 2026-09-21 the maintainer authorized the
+0.30 release and website deployment, superseding the earlier no-TAC hold.
+The final source must pass a fresh full release gate before publication. See the
 [issue status audit](docs/releases/CELLSCRIPT_0_30_ISSUE_STATUS.md).
 
 `0.30` is the active capability-closure implementation branch, forked from
@@ -46,8 +47,8 @@ Playground parity are implemented, and the six-family temporal business corpus
 uses typed HeaderDep and Since operations. The repository-local candidate gates
 now pass, the maintainer has waived the independent review requirement, and
 issue #12 is closed. The selected Pudge deployment is recorded separately;
-publication and the stable tag remain open under issue #27 because they must
-not trigger TAC.
+publication and the stable tag remain tracked under issue #27 until the
+authorized release has been published and verified.
 
 The issue #18 package-compiler prerequisite is implemented through enforced
 `[package].cellscript_version` SemVer ranges, aggregated root/transitive

CHANGELOG.md

@@ -2,9 +2,9 @@
 
 ## 0.30.0 - Capability closure
 
-Release candidate prepared for publication; no stable tag or public release is
-created by this record. See [the 0.30 release notes](docs/releases/CELLSCRIPT_0_30_RELEASE_NOTES.md)
-for the accepted compatibility boundary and publication constraints.
+Publication and the website update were authorized on 2026-09-21, subject to a
+fresh full release gate. See [the 0.30 release notes](docs/releases/CELLSCRIPT_0_30_RELEASE_NOTES.md)
+for the accepted compatibility boundary and publication channels.
 
 The entries below retain the evidence state at each implementation step. The
 release notes and capability ledger record the current acceptance state.

README.md

@@ -4,7 +4,7 @@
 </p>
 
 [![CellScript CI](https://github.com/CellScript-Labs/CellScript/actions/workflows/ci.yml/badge.svg)](https://github.com/CellScript-Labs/CellScript/actions/workflows/ci.yml)
-[![Release: v0.24.0](https://img.shields.io/badge/release-v0.24.0-2f6f4e.svg)](https://github.com/CellScript-Labs/CellScript/releases/tag/v0.24.0)
+[![Release: v0.30.0](https://img.shields.io/badge/release-v0.30.0-2f6f4e.svg)](https://github.com/CellScript-Labs/CellScript/releases/tag/v0.30.0)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE-MIT)
 [![Rust 1.97.1](https://img.shields.io/badge/rust-1.97.1-orange.svg)](Cargo.toml)
 [![Targets: CKB](https://img.shields.io/badge/targets-CKB-2f6f4e.svg)](#target-profiles)
@@ -20,10 +20,10 @@ artifacts, together with typed metadata for auditing, policy checks, schema
 binding, and scheduler-aware execution.
 
 The current stable release is
-[CellScript v0.24.0](https://github.com/CellScript-Labs/CellScript/releases/tag/v0.24.0).
-The [0.24 release notes](docs/releases/CELLSCRIPT_0_24_RELEASE_NOTES.md)
-describe its verified-artifact, executable-test, integration, and explicitly
-deferred ecosystem boundaries.
+[CellScript v0.30.0](https://github.com/CellScript-Labs/CellScript/releases/tag/v0.30.0).
+The [0.30 release notes](docs/releases/CELLSCRIPT_0_30_RELEASE_NOTES.md)
+describe its bounded Cell lifecycles, multi-Script composition, typed CKB views,
+lock-authoritative packages, cost measurements, and evidence limits.
 
 In this README, metadata means machine-readable semantic facts emitted by the
 compiler: schema layout, Cell effects, access summaries, source hashes,
@@ -117,15 +117,15 @@ curl -fsSL https://raw.githubusercontent.com/CellScript-Labs/CellScript/main/scr
 Or pin a specific version:
 
 ```bash
-CELLSCRIPT_VERSION=0.24.0 curl -fsSL https://raw.githubusercontent.com/CellScript-Labs/CellScript/main/scripts/install.sh | sh
+CELLSCRIPT_VERSION=0.30.0 curl -fsSL https://raw.githubusercontent.com/CellScript-Labs/CellScript/main/scripts/install.sh | sh
 ```
 
 The release page publishes `SHA256SUMS` alongside all four platform archives.
 
 Build the exact published source instead:
 
 ```bash
-git clone --branch v0.24.0 --depth 1 https://github.com/CellScript-Labs/CellScript.git
+git clone --branch v0.30.0 --depth 1 https://github.com/CellScript-Labs/CellScript.git
 cd CellScript
 cargo install --locked --path .
 ```
@@ -551,7 +551,7 @@ or CellFabric intent engine.
 - [0.22 release notes](docs/releases/CELLSCRIPT_0_22_RELEASE_NOTES.md)
 - [0.23 release notes](docs/releases/CELLSCRIPT_0_23_RELEASE_NOTES.md)
 - [0.24 release notes](docs/releases/CELLSCRIPT_0_24_RELEASE_NOTES.md)
-- [0.30 release candidate notes](docs/releases/CELLSCRIPT_0_30_RELEASE_NOTES.md)
+- [0.30 release notes](docs/releases/CELLSCRIPT_0_30_RELEASE_NOTES.md)
 - [0.22 bounded Fiber interoperability guide](examples/fiber/README.md)
 - [Agentic Loops and cellscript-mcp tutorial](docs/wiki/Tutorial-13-Agentic-Loops-and-cellscript-mcp.md)
 - [LS-IDL for CKB Lock Scripts tutorial](docs/wiki/Tutorial-15-LS-IDL-for-CKB-Lock-Scripts.md)

docs/CELLSCRIPT_0_30_CAPABILITY_LEDGER.md

@@ -1,7 +1,8 @@
 # CellScript 0.30 Capability Ledger
 
-**Status:** accepted bounded capability contract for the 0.30.0 release
-candidate; public publication is withheld under the no-TAC constraint.
+**Status:** accepted bounded capability contract for the 0.30.0 release.
+The maintainer authorized publication and the website update on 2026-09-21;
+the final source still requires a fresh full release gate.
 
 This document separates two different completeness claims:
 
@@ -78,8 +79,8 @@ The machine ledger is the detailed source of truth. At this candidate point:
   Its `stable` eligibility and `split-and-close` recommendation mean the bounded
   capability is eligible for release; they do not claim the packages are already
   published or close the GitHub issue. Selected-network evidence is complete,
-  but no tag or release workflow may be created while the maintainer's no-TAC
-  constraint remains in force. The maintainer has explicitly waived
+  and publication was authorized on 2026-09-21 after the earlier no-TAC hold.
+  Each publication channel must still be verified. The maintainer has explicitly waived
   independent review for this release line. The previously
   unreachable gitlinks were re-accepted on 2026-09-11 at retrievable release
   evidence commits: VS Code `4df04807`, website `320d54e`, NovaSeal
@@ -106,8 +107,8 @@ The [dated issue audit](releases/CELLSCRIPT_0_30_ISSUE_STATUS.md) records all
 24 issue dispositions and the remaining publication boundary.
 
 This list is a dependency and closure map, not a delivery date or release
-promise. The `0.30` branch remains unpublished until the separate publication
-action is authorized and verified. Final candidate replay must pass on clean source.
+promise. Publication is authorized but must be verified separately from the
+capability evidence. Final candidate replay must pass on clean source.
 
 ## Strategy wording
 
@@ -138,4 +139,4 @@ validation additionally requires an `accepted` ledger, all release requirements
 passed, and every required capability stable and no longer marked `keep-open`.
 An assigned reviewer is required unless independent review is explicitly waived.
 Both release modes run this stricter check before CI. Eligibility is a
-pre-publication contract; it never authorizes a tag or overrides no-TAC.
+pre-publication contract; it does not itself authorize a tag or deployment.

docs/releases/CELLSCRIPT_0_30_RELEASE_NOTES.md

@@ -1,9 +1,10 @@
 # CellScript 0.30.0 Release Notes
 
-**Status:** release candidate; publication is withheld under the maintainer's
-no-TAC constraint. A prepared version, accepted capability record, or local
-release gate does not mean a tag, GitHub Release, package, or extension has been
-published.
+**Publication decision (2026-09-21):** the maintainer authorized the 0.30.0
+release and the cellscript.dev update, superseding the earlier no-TAC hold.
+Publication requires a fresh full release gate on the final clean source.
+GitHub assets and the website are released together; crates.io and extension
+marketplace publication retain their own independently verified status.
 
 ## Highlights
 
@@ -89,10 +90,11 @@ Both release modes require a clean checkout and invoke
 ledgers, incomplete required capabilities, stale evidence, and pending release
 layers fail closed. `release-quick` remains compile-only preflight.
 
-Public publication remains a separate operation. Do not create or push a release
-tag or dispatch GitHub release automation while the no-TAC constraint remains
-in force. The current GitHub release workflow is triggered
-by `v*` tags or manual dispatch, so it cannot be used under that constraint.
+The GitHub release workflow is triggered by `v*` tags or manual dispatch. Its
+full release gate must pass before binary builds and public publication. Deploy
+the website only after its matching release assets are available, and retain
+the previous site directory for rollback. A local gate result alone does not
+establish publication on any channel.
 
 ## Detailed contracts
 

tests/fixtures/business_corpus.json

@@ -45,7 +45,7 @@
     "transaction_fixture": "tests/fixtures/capability_anchor_cases.json"
   },
   "capability_ledger": "tests/fixtures/capability_ledger.json",
-  "capability_ledger_sha256": "0x4f3e2b920824e33fa2b92837da771af98ba0eaf7dbb252e791b6f0107cf2b3a9",
+  "capability_ledger_sha256": "0xd464e7b4ba8474203dca8b375da07d63d7a11ed815c83b4acb38ed0464051e6f",
   "claim": "Application-layer capability comparable to hand-written Rust CKB Scripts for this exact bounded eight-family portfolio; unrestricted Rust parity is excluded.",
   "cryptographic_capability_matrix": "tests/fixtures/cryptographic_capability_matrix.json",
   "evidence_files": [

tests/fixtures/capability_ledger.json

@@ -509,7 +509,7 @@
         "Version bumps, publication, or deployment before every required identity and gate agrees"
       ],
       "remaining_work": [
-        "Public publication remains withheld under the maintainer's no-TAC constraint; #27 stays open until the publication action is authorized and verified."
+        "The maintainer authorized the 0.30 release and website update on 2026-09-21; #27 stays open until the final clean-source release gate and each selected publication channel are verified."
       ]
     }
   ],