Remove legacy lifecycle syntax

Author: a19q3

README.md

@@ -27,7 +27,7 @@ verifier obligations, runtime requirements, and target-profile policy flags.
 
 The language is intentionally narrow: it is not a new VM, and it is not an
 account-storage contract language. CellScript gives protocol authors a typed
-way to describe assets, shared Cell state, receipts, lifecycle transitions,
+way to describe assets, shared Cell state, receipts, explicit state transitions,
 locks, and transaction-shaped effects — while still mapping directly to the
 Cell model used by CKB.
 
@@ -169,7 +169,8 @@ CellScript programs are written in terms of Cell lifecycle operations:
 - **Capability gates** — `has store, transfer, destroy` makes asset permissions
   explicit instead of implicit.
 - **Declarative state machines** — state remains explicit schema data, while
-  `state_machine Type.field { A -> B by action; }` declares allowed edges and
+  `state_machine Name for Type.field { A -> B by action; }` or compact
+  `state Type.field { A -> B; }` declares allowed edges, and
   `action ... moves input.field A -> B` binds an action to the edge it proves.
 - **Effect inference** — `action` bodies are classified as `Pure`, `ReadOnly`,
   `Mutating`, `Creating`, or `Destroying` based on their Cell operations.
@@ -292,10 +293,10 @@ action burn(token: Token) {
 | Example | What it shows |
 |---|---|
 | `examples/token.cell` | Mint, transfer, burn, guarded same-symbol merge |
-| `examples/timelock.cell` | Time-gated state transitions, delayed claim paths |
+| `examples/timelock.cell` | Time-gated release checks, delayed claim paths |
 | `examples/multisig.cell` | Authorization thresholds, signature-oriented locks |
 | `examples/nft.cell` | Unique assets, metadata, ownership transfer |
-| `examples/vesting.cell` | Receipt-style grants and claim lifecycle |
+| `examples/vesting.cell` | Receipt-style grants and explicit claim state transitions |
 | `examples/amm_pool.cell` | Shared pool state, swap/liquidity effects |
 | `examples/launch.cell` | Launch/pool composition patterns |
 
@@ -317,7 +318,7 @@ chain-specific VM:
 |---|---|---|---|---|
 | Execution target | RISC-V ELF / asm on ckb-vm | EVM bytecode | Move bytecode | FuelVM bytecode |
 | State model | Typed Cells, explicit inputs/deps/outputs | Account storage slots | Resources in global storage | UTXO + native assets |
-| Asset model | Native `resource`, lifecycle, receipts, shared Cells | Manual token contracts | Native resources | Native assets |
+| Asset model | Native `resource`, state transitions, receipts, shared Cells | Manual token contracts | Native resources | Native assets |
 | Linear ownership | Compiler-enforced | No | Yes (abilities) | No general user-defined |
 | Shared state | Explicit `shared` Cells | Implicit contract storage | Shared objects (some chains) | No shared Cell analogue |
 | Reentrancy | No callback-style reentrancy | Common risk surface | Lower by design | Lower predicate risk |
@@ -337,7 +338,7 @@ CellScript includes production-style local language tooling for early users:
 - **In-process LSP** — diagnostics, completions, hover, go-to-definition,
   references, rename, formatting, and metadata-oriented code actions. The
   compiler crate exposes an `LspServer`; `cellc --lsp` provides a full
-  `tower-lsp` JSON-RPC transport over stdio. Completions include lifecycle
+  `tower-lsp` JSON-RPC transport over stdio. Completions include state-machine
   states after `Type::`.
 - **VS Code extension** — syntax highlighting, snippets, on-save diagnostics,
   compiler-backed formatting, scratch compilation, metadata/constraints/production
@@ -376,7 +377,7 @@ crate (`cellscript`) with its own `mod.rs` entry point under `src/`.
 graph LR
     Source["Source (.cell)"] --> Lexer
     Lexer --> Parser
-    Parser --> TypeCheck["Type Checker\n+ Lifecycle"]
+    Parser --> TypeCheck["Type Checker\n+ State Checks"]
     TypeCheck --> IRLower["IR Lowering\n+ Optimize"]
     IRLower --> Codegen["Codegen (RISC-V)"]
     IRLower --> Metadata["Metadata (JSON)"]
@@ -402,9 +403,9 @@ action `moves` clauses, and all statement/expression forms.
   or settled before the action body exits. Also validates shared-state
   mutability rules, capability gates, effect classification (`Pure` /
   `ReadOnly` / `Mutating` / `Creating` / `Destroying`), and call signatures.
-- *Lifecycle checking* — validates explicit state fields, `state_machine`
-  transition graphs, action `moves` clauses, legal state transitions, and static
-  create-site checks.
+- *State transition checking* — validates explicit state fields,
+  `state_machine` transition graphs, action `moves` clauses, legal state
+  transitions, and static create-site checks.
 
 **4. IR lowering** (`ir/` + `optimize/` + `resolve/`)
 - *`resolve/`* — builds per-module symbol tables and resolves `use` imports
@@ -482,7 +483,7 @@ treated as deployable.
 ```mermaid
 flowchart TB
     Source[".cell source + Cell.toml\n--target-profile ckb"] --> Frontend["Lexer + parser\nstable source spans"]
-    Frontend --> Semantics["Type + lifecycle checks\nlinear resources, lock-only require,\nprotected/witness/lock_args classification"]
+    Frontend --> Semantics["Type + state checks\nlinear resources, lock-only require,\nprotected/witness/lock_args classification"]
     Semantics --> Policy["CKB policy gate\nfail closed on unsupported runtime or state shapes"]
 
     subgraph Rules["CKB profile rules"]
@@ -509,7 +510,7 @@ flowchart TB
 
 This separates three boundaries:
 
-- **compiler boundary** — parse, type/lifecycle checks, CKB policy rejection, IR,
+- **compiler boundary** — parse, type/state checks, CKB policy rejection, IR,
   codegen, and metadata;
 - **artifact boundary** — `cellc verify-artifact` proves the artifact, sidecar,
   source hash, target profile, and selected policy flags agree;

README_CH.md

@@ -224,7 +224,7 @@ action burn(token: Token) {
 | `examples/timelock.cell` | 时间门控状态转换、延迟 claim 路径 |
 | `examples/multisig.cell` | 授权阈值、签名导向的 lock 逻辑 |
 | `examples/nft.cell` | 唯一资产、metadata、所有权转移 |
-| `examples/vesting.cell` | Receipt-style grants 和 claim lifecycle |
+| `examples/vesting.cell` | Receipt-style grants 和显式 claim 状态转换 |
 | `examples/amm_pool.cell` | Shared pool state、swap/liquidity effects |
 | `examples/launch.cell` | Launch/pool composition patterns |
 
@@ -299,7 +299,7 @@ CellScript 是一个多遍编译器，把 `.cell` 源码通过五个定义明确
 graph LR
     Source["Source (.cell)"] --> Lexer
     Lexer --> Parser
-    Parser --> TypeCheck["Type Checker\n+ Lifecycle"]
+    Parser --> TypeCheck["Type Checker\n+ State Checks"]
     TypeCheck --> IRLower["IR Lowering\n+ Optimize"]
     IRLower --> Codegen["Codegen (RISC-V)"]
     IRLower --> Metadata["Metadata (JSON)"]
@@ -323,7 +323,7 @@ graph LR
   体退出前必须被 consume、transfer、destroy、claim 或 settle。同时验证
   shared-state 可变性规则、capability gates、effect 分类（`Pure` /
   `ReadOnly` / `Mutating` / `Creating` / `Destroying`）和调用签名。
-- *生命周期检查* — 验证显式 state 字段、`state_machine` 转换图、action
+- *状态转换检查* — 验证显式 state 字段、`state_machine` 转换图、action
   `moves` 子句、合法状态转换和静态 create-site 检查。
 
 **4. IR 降低**（`ir/` + `optimize/` + `resolve/`）
@@ -397,7 +397,7 @@ CKB 假设暴露出来。
 ```mermaid
 flowchart TB
     Source[".cell source + Cell.toml\n--target-profile ckb"] --> Frontend["Lexer + parser\n稳定 source span"]
-    Frontend --> Semantics["Type + lifecycle checks\n线性资源、lock-only require、\nprotected/witness/lock_args 分类"]
+    Frontend --> Semantics["Type + state checks\n线性资源、lock-only require、\nprotected/witness/lock_args 分类"]
     Semantics --> Policy["CKB policy gate\n对不支持的 runtime 或状态形状 fail closed"]
 
     subgraph Rules["CKB profile rules"]
@@ -424,7 +424,7 @@ flowchart TB
 
 这里分成三条边界：
 
-- **编译器边界** — parse、type/lifecycle checks、CKB policy rejection、IR、
+- **编译器边界** — parse、type/state checks、CKB policy rejection、IR、
   codegen 和 metadata；
 - **artifact 边界** — `cellc verify-artifact` 证明 artifact、sidecar、源码
   hash、target profile 和选定 policy flags 一致；

docs/CELLSCRIPT_0_13_RELEASE_NOTES_DRAFT.md

@@ -198,20 +198,26 @@ New in 0.13:
   local witness buffer before decoding dynamic payload lengths, and reject
   trailing payload bytes after all static or dynamic witness arguments are
   consumed.
-- Lifecycle receipts now fail compilation unless they declare a scalar unsigned
-  `state` field, matching the runtime verifier's lifecycle state contract.
-- Lifecycle state storage remains explicit cell data: the compiler does not
+- Legacy `#[lifecycle(...)]` receipt syntax has been removed. State remains
+  explicit schema data, and transition policy is declared with `state` /
+  `state_machine` plus action-level `moves`.
+- State-machine storage remains explicit cell data: the compiler does not
   inject hidden state fields or mutate Molecule layout. `create` initializers
-  may now use declared lifecycle state names such as `state: Created`, while
+  may now use declared state names such as `state: Created`, while
   guards and computed expressions can use qualified names such as
   `Ticket::Active` instead of numeric state indexes. The LSP now completes
-  those qualified lifecycle states after `Type::`.
+  those qualified state-machine states after `Type::`.
 - Declarative state machines can now be expressed without hidden layout changes:
   `state_machine Name for Type.field { A -> B by action; }` and compact
   `state Type.field { A -> B; }` declare the graph, while action signatures can
   bind the edge they prove with `moves input.field A -> B`. The type checker,
-  lifecycle static checks, IR metadata, runtime verifier, formatter, docs
+  state static checks, IR metadata, runtime verifier, formatter, docs
   generator, and LSP all carry the explicit state field name.
+- State-machine checking no longer treats enum or declaration order as a hidden
+  linear state sequence: initial creates may use any declared state, and declared
+  edges may return to the first state. `moves` and `by action` edges now fail at
+  compile time unless the action consumes the corresponding owned input and
+  creates exactly one replacement output.
 - Mutate preserved-field verification now fails closed when not every preserved
   field is verifier-addressable; metadata no longer classifies oversized
   data-except fallback paths as checked-runtime.

docs/CELLSCRIPT_EXAMPLE_BUSINESS_FLOWS.md

@@ -127,7 +127,7 @@ are no lock entries in this example.
 
 ## `multisig.cell`
 
-Business purpose: threshold wallet creation, proposal lifecycle, signature
+Business purpose: threshold wallet creation, proposal records, signature
 collection, execution, cancellation, and signer/threshold governance proposals.
 
 ```mermaid

docs/CELLSCRIPT_RUNTIME_ERROR_CODES.md

@@ -26,9 +26,9 @@ When a CLI failure can be tied to this registry, stderr uses the same
 | 3 | `cell-load-failed` | Cell data or field loading failed or returned an unusable result. | Check that the expected input, output, or dep cell exists and is reachable by the generated script. |
 | 4 | `exact-size-mismatch` | Loaded bytes did not match the exact fixed-size schema requirement. | Check fixed-width schema fields and ensure the builder encodes the exact Molecule byte length. |
 | 5 | `assertion-failed` | A source-level assert or invariant check evaluated to false. | Inspect the action invariant or assert expression and the transaction values that feed it. |
-| 7 | `lifecycle-transition-mismatch` | A lifecycle state transition did not match the declared transition rule. | Compare consumed and produced lifecycle state fields with the declared lifecycle transitions. |
-| 8 | `lifecycle-new-state-invalid` | A created or replacement lifecycle state was outside the declared state range. | Check created output lifecycle state values and declared lifecycle states. |
-| 9 | `lifecycle-old-state-invalid` | A consumed lifecycle state was outside the declared state range. | Check consumed input lifecycle state values and declared lifecycle states. |
+| 7 | `lifecycle-transition-mismatch` | A state-machine transition did not match the declared transition rule. | Compare consumed and produced state fields with the declared state-machine transitions. |
+| 8 | `lifecycle-new-state-invalid` | A created or replacement state value was outside the declared state range. | Check created output state values and declared state-machine states. |
+| 9 | `lifecycle-old-state-invalid` | A consumed state value was outside the declared state range. | Check consumed input state values and declared state-machine states. |
 | 10 | `entry-witness-magic-mismatch` | Entry witness bytes did not start with the CellScript witness ABI magic. | Encode entry witnesses with `cellc entry-witness` or the documented `CSARGv1\0` wire format. |
 | 11 | `type-hash-preservation-mismatch` | A replacement output did not preserve the consumed input type hash. | Check the replacement output type script and builder output ordering. |
 | 12 | `lock-hash-preservation-mismatch` | A replacement output did not preserve the consumed input lock hash. | Check the replacement output lock script and builder output ordering. |

docs/wiki/Tutorial-04-Packages-and-CLI-Workflow.md

@@ -133,7 +133,7 @@ cellc doc --json
 ```
 
 Generated docs summarize modules, actions, resources, receipts, locks,
-lifecycle rules, and lowering metadata.
+state-machine rules, and lowering metadata.
 
 ## Audit And Evidence Reports
 

docs/wiki/Tutorial-07-LSP-and-Tooling.md

@@ -1,10 +1,10 @@
 You can write CellScript with any text editor and the `cellc` CLI. The LSP and
-VS Code extension make that loop shorter. Parse errors, type errors, lifecycle
-mistakes, symbols, hovers, formatting, and compiler-backed reports can show up
-while you work instead of after a long command sequence.
+VS Code extension make that loop shorter. Parse errors, type errors,
+state-machine mistakes, symbols, hovers, formatting, and compiler-backed reports
+can show up while you work instead of after a long command sequence.
 
 The useful thing to remember is that editor feedback is not a separate language
-implementation. It is tied to the same parser, type checker, lifecycle checks,
+implementation. It is tied to the same parser, type checker, state-transition checks,
 and lowering metadata used by `cellc`.
 
 ## What You Will Learn
@@ -20,10 +20,10 @@ and lowering metadata used by `cellc`.
 The LSP implementation supports the editor features you expect while writing a
 contract:
 
-- diagnostics for parse, type, lifecycle, and lowering errors;
-- hover information for actions, receipts, fields, local variables, lifecycle
+- diagnostics for parse, type, state-machine, and lowering errors;
+- hover information for actions, receipts, fields, local variables, state-machine
   states, and lowering metadata;
-- keyword, type, symbol, field, local, enum variant, and qualified lifecycle
+- keyword, type, symbol, field, local, enum variant, and qualified state-machine
   state completions such as `Ticket::Active`;
 - go-to-definition;
 - find-references;

docs/wiki/Tutorial-08-Bundled-Example-Contracts.md

@@ -12,8 +12,8 @@ example.
 |---|---|
 | `examples/token.cell` | Minting, transfer, burn, and guarded token merge. |
 | `examples/nft.cell` | Unique assets, metadata, ownership transitions, and owner locks. |
-| `examples/timelock.cell` | Time-gated state transitions, release requests, and approval flow. |
-| `examples/multisig.cell` | Threshold policy, proposals, signatures-as-data, and lock-boundary predicates. |
+| `examples/timelock.cell` | Time-gated release checks, release requests, and approval flow. |
+| `examples/multisig.cell` | Threshold policy, proposal records, signatures-as-data, and lock-boundary predicates. |
 | `examples/vesting.cell` | Vesting grants, receipts, claim lifecycle, and admin-boundary comments. |
 | `examples/amm_pool.cell` | Shared pool state, swap logic, liquidity receipts, and settlement effects. |
 | `examples/launch.cell` | Launch/pool composition patterns. |
@@ -46,8 +46,8 @@ If you are learning the language, read them in this order:
 1. `token.cell`: start here. It is the smallest example with a clear resource
    lifecycle.
 2. `nft.cell`: learn unique assets and ownership-style locks.
-3. `timelock.cell`: learn time guards and replacement state.
-4. `multisig.cell`: learn proposal lifecycle and threshold logic.
+3. `timelock.cell`: learn time guards and release evidence.
+4. `multisig.cell`: learn proposal records and threshold logic.
 5. `vesting.cell`: learn receipt-style claim flows.
 6. `amm_pool.cell`: learn shared pool state after you understand resources.
 7. `launch.cell`: read this last because it composes multiple patterns.

examples/acceptance/multisig.cell

@@ -43,13 +43,7 @@ receipt Proposal has destroy {
     signatures: Vec<Signature>,
     created_at: u64,
     expires_at: u64,
-    state: u8,
-}
-
-state Proposal.state {
-    Created -> Pending;
-    Pending -> Executed;
-    Executed -> Cancelled;
+    state: ProposalStatus,
 }
 
 struct Signature {
@@ -136,7 +130,7 @@ action propose_transfer(
         signatures: [],
         created_at: current_time,
         expires_at: current_time + DEFAULT_TIMEOUT,
-        state: Created,
+        state: ProposalStatus::Pending,
     };
 
 
@@ -265,7 +259,7 @@ action propose_add_signer(
         signatures: [],
         created_at: current_time,
         expires_at: current_time + DEFAULT_TIMEOUT,
-        state: Created,
+        state: ProposalStatus::Pending,
     };
 
     proposal
@@ -303,7 +297,7 @@ action propose_remove_signer(
         signatures: [],
         created_at: current_time,
         expires_at: current_time + DEFAULT_TIMEOUT,
-        state: Created,
+        state: ProposalStatus::Pending,
     };
 
     proposal
@@ -342,7 +336,7 @@ action propose_change_threshold(
         signatures: [],
         created_at: current_time,
         expires_at: current_time + DEFAULT_TIMEOUT,
-        state: Created,
+        state: ProposalStatus::Pending,
     };
 
     proposal

examples/acceptance/nft.cell

@@ -39,12 +39,6 @@ receipt Listing has destroy {
     state: u8,
 }
 
-state Listing.state {
-    Created -> Active;
-    Active -> Filled;
-    Filled -> Cancelled;
-}
-
 receipt Offer has destroy {
     token_id: u64,
     buyer: Address,
@@ -53,12 +47,6 @@ receipt Offer has destroy {
     state: u8,
 }
 
-state Offer.state {
-    Created -> Active;
-    Active -> Accepted;
-    Accepted -> Expired;
-}
-
 receipt RoyaltyPayment {
     token_id: u64,
     recipient: Address,
@@ -112,7 +100,7 @@ action create_listing(
         seller: nft.owner,
         price,
         created_at: current_time,
-        state: Created,
+        state: 0,
     };
 
     listing
@@ -174,7 +162,7 @@ action create_offer(
         buyer,
         price,
         expires_at,
-        state: Created,
+        state: 0,
     };
 
     offer