Code extension 0.2.0

Code extension 0.2.0

Code 0.2.0 adds capability-based module composition, template generation and reviewed native dependency management. It runs on the published Lenso CLI 1.0.0 (Host 0.2.4, Project 0.1.2) with JSON ABI 1.

What's included

• Independent adapter selection, optional capabilities and explicit shared instances.
• Strict templates, isolated generated directories, named samples and code validate.
• Generated-file ownership, three-way updates, conflict decisions and reviewed cleanup when switching adapters.
• Cargo/npm manifest updates with shared ownership, separate file/command authorization, installation retry and safe dependency retirement.
• Existing resource search, preview, add, diff and update commands.

Install this version

The official Registry and Code preset now select Code 0.2.0. In a project containing author/catalog.toml and its templates:

lenso init --preset empty
lenso ext add code --constraint '=0.2.0' \
  --input '{"author_root":"author","target":"src"}'
lenso code validate
lenso code compose-preview --sample memory
lenso code compose --sample memory

Use the complete Rust memory/disk/shared example as a starting catalog. CLI and extension installation need no Node.js, Git or Wasm compiler. Compiling generated applications and approved Cargo/npm installation require their native toolchains.

The manifest and deterministic archive are SHA-256 pinned through lenso-release.json; resolved versions and asset identities are recorded in project lenso.lock and reuse the user cache.

Verification

The release workflow installs CLI 1.0.0 from its existing native Release, then consumes this exact Code Release in fresh projects and caches. It verifies real repository downloads, cache restoration, preview/decline/approve flows, compiled memory/disk/shared samples, adapter cleanup, preservation of local edits, Cargo/npm updates and safe removal, and locked/offline replay. Reports are attached to the workflow as code-release-verification.

See generator authoring and native dependency management for configuration and supported scope.

Official alias and preset onboarding also passed on macOS, Linux and Windows using published CLI 1.0.0: verification workflow. Each platform checks ext add code, new --preset code, init --preset code and preset apply code with fresh caches and empty PATH, including preview/consent, generation and locked/offline replay.