Guide Studio authoring and reviewed deployment operations

CHANGELOG.md

@@ -18,6 +18,51 @@ SPDX-License-Identifier: Apache-2.0
 
 # Changelog
 
+## 0.1.0a12
+
+- Add environment-scoped deployment targets, desired state, observations,
+  immutable approval plans, fenced runner jobs, and explicit reconciliation
+  for uncertain external effects. Provider credentials remain on an outbound
+  runner with local destination and image allowlists.
+- Add Operations in Studio and the CLI for reviewed container deployment
+  changes. Support trusted Compose deployment and bounded existing Kubernetes
+  and Azure Container Apps changes; provisioning cloud clusters is separate.
+- Report dated worker contact and capacity, with revision-checked drain and
+  resume controls that preserve active leases.
+- Let Lumi explain explicitly selected Operations records using bounded,
+  permission-checked context. Deployment changes retain their separate plan,
+  approval, and application process.
+- Reject unsupported component and destination changes before plan approval.
+  Mark stopped or stalled compatibility monitors unhealthy so container
+  supervisors can replace the affected API process.
+- Guide target registration with named application accounts, downloadable
+  nonsecret runner setup, observed-resource import, explicit resource capacity,
+  and admitted worker release selection.
+- Allow reviewed Compose plans to restart stopped workers, checking readiness
+  after the restart instead of during the dry run.
+- Keep worker lease renewal retrying explicit capacity rejections while the
+  current lease remains valid, including while a completed task awaits its
+  acknowledgment. Ambiguous transport failures never replay the task handler.
+- Keep invalid inspector edits and unapplied AI profile changes visible before
+  saving, publishing, or switching views. Edit workflow AI profiles in a dialog,
+  with multiline prompts and direct connection-slot selection.
+- Organize editor commands into aligned rows and step settings into purposeful
+  sections. Keep palette search visible and explain data sources through
+  keyboard-accessible information controls. Filter source modes and formulas
+  by the receiving field's type while preserving imported expressions for repair.
+- Separate reusable project actions from creating a new API action, with a
+  direct connection entry point and contextual guidance for local authoring.
+- Keep Studio pages and editor assets loading while platform requests are busy,
+  and retry temporary session-read capacity rejections within a bounded budget.
+- Use standard OpenAI and Anthropic endpoints automatically, retain explicit
+  Azure configuration, and group advanced model settings separately. Check
+  model-setting combinations with the canonical local validator before applying
+  them; configuration validation does not claim live provider readiness.
+- Add migrations `0029_deployments` and `0030_worker_presence`, with explicit
+  scoped Operations roles. Existing workflow roles gain no deployment authority.
+- Publish worker packages 0.1.4 pinned to core 0.1.0a12 and desktop alpha12.
+  Keep the verified alpha10 Azure acceptance history separate from this release.
+
 ## 0.1.0a11
 
 - Guide AI provider connections, Lumi settings, and workflow AI profiles through

CONTRIBUTING.md

@@ -49,7 +49,9 @@ update lock or upstream framework provenance casually to resolve an unrelated
 failure.
 
 **Studio and desktop changes need their own checks.** Python-only contributors do
-not need Node.js. If you change `studio/`, run the same steps as the Studio CI
+not need Node.js. Use Node 24 LTS; CI pins 24.15.0. Check `node --version`
+before installing dependencies so local builds and browser tests use the same
+major version as CI. If you change `studio/`, run the same steps as the Studio CI
 job. Many unit and browser tests run Weave's Python code, including the real
 Studio host, from the repository's `.venv`, so run the `uv sync` command above
 first.

README.md

@@ -53,7 +53,7 @@ maps service tasks, user tasks, gateways, and timers to Weave steps.
 
 ## What you get
 
-The **v0.1.0a11 alpha** release provides the **API, CLI, Python SDK, and Studio**
+The **v0.1.0a12 alpha** release provides the **API, CLI, Python SDK, and Studio**
 visual workspace, with human-task inboxes, email conversations, execution
 management, and administration of people and access. Run Weave as a standalone
 service or embed it in another product.
@@ -81,7 +81,7 @@ See the illustrated [AI workflow guide](docs/guides/ai-workers.md) and
 Read the [capability matrix](docs/capabilities.md) for tested boundaries and
 live-provider checks that remain environment-specific.
 
-Studio runs in your browser from the [installed CLI](docs/guides/studio.md#install-the-alpha11-browser-application)
+Studio runs in your browser from the [installed CLI](docs/guides/studio.md#install-the-alpha12-browser-application)
 or as a [desktop app](docs/guides/desktop.md). The macOS desktop bundles
 are ad-hoc signed, not Developer ID signed or notarized, so macOS may ask you to
 approve them; do not use the alpha5 macOS installers, which were damaged. The
@@ -119,20 +119,20 @@ integration code. Each has its own guide, so you can stop at the result you need
 ## Install and discover the CLI
 
 On macOS, Linux, or WSL, install **Python 3.12 or newer** with `venv` support,
-then run this block in Bash or Zsh. It installs the pinned **v0.1.0a11 alpha**
+then run this block in Bash or Zsh. It installs the pinned **v0.1.0a12 alpha**
 into your user account without `sudo`, Git, or Docker:
 
 ```sh
 (
   # Stop if downloading the installer fails.
   set -o pipefail
   curl --proto '=https' --tlsv1.2 -fsSL \
-    https://github.com/fireflyframework/firefly-weave/releases/download/v0.1.0a11/install.sh \
-    | sh -s -- --version v0.1.0a11
+    https://github.com/fireflyframework/firefly-weave/releases/download/v0.1.0a12/install.sh \
+    | sh -s -- --version v0.1.0a12
 )
 ```
 
-Expected: `Installed Firefly Weave 0.1.0a11:` followed by the command's path. Then
+Expected: `Installed Firefly Weave 0.1.0a12:` followed by the command's path. Then
 make the default command directory available in this terminal and look around:
 
 ```sh
@@ -146,7 +146,7 @@ weave help workflow
 weave docs platform
 ```
 
-Expected: `Firefly Weave 0.1.0a11`, the command overview, the `workflow`
+Expected: `Firefly Weave 0.1.0a12`, the command overview, the `workflow`
 commands, and the address of the platform guide. You do not need to learn every
 command first: help explains each family and its next steps. The
 [installation guide](docs/installation.md) covers choosing Python, a permanent
@@ -179,7 +179,7 @@ Compose files and setup helpers. Clone the tag that matches the CLI:
 
 ```sh
 # Keep the platform files at the same version as the CLI.
-git clone --branch v0.1.0a11 --single-branch https://github.com/fireflyframework/firefly-weave.git
+git clone --branch v0.1.0a12 --single-branch https://github.com/fireflyframework/firefly-weave.git
 cd firefly-weave
 
 # Check prerequisites, then prepare private settings and dependencies once.
@@ -265,7 +265,7 @@ path, and the detailed diagrams.
 
 ## Current release and limits
 
-The recommended installation is **v0.1.0a11**, an **alpha** release. Download
+The recommended installation is **v0.1.0a12**, an **alpha** release. Download
 packages and checksums from
 [GitHub Releases](https://github.com/fireflyframework/firefly-weave/releases).
 The documentation on a branch describes the source on that branch; a release tag

desktop/RELEASE.md

@@ -17,16 +17,16 @@ SPDX-License-Identifier: Apache-2.0
 -->
 # Desktop release versions
 
-The alpha11 product version is `0.1.0-alpha.11` in npm, Cargo and Tauri. It corresponds
-to Python `0.1.0a11` and the repository prerelease tag `v0.1.0a11`.
+The alpha12 product version is `0.1.0-alpha.12` in npm, Cargo and Tauri. It corresponds
+to Python `0.1.0a12` and the repository prerelease tag `v0.1.0a12`.
 
-Windows MSI uses the explicit numeric version `0.1.11`. Tauri's pinned bundler rejects
+Windows MSI uses the explicit numeric version `0.1.12`. Tauri's pinned bundler rejects
 nonnumeric prerelease identifiers when deriving MSI versions; its `windows.wix.version`
 override supplies the valid numeric installer version while filenames retain the product
 version. MSI compares only the first three fields. Future desktop alpha and stable
 releases must advance this numeric installer counter: the stable product `0.1.0`
 must not reset the MSI counter to `0.1.0`. The macOS internal bundle version also uses
-numeric `0.1.11`; its displayed product version remains the alpha product version.
+numeric `0.1.12`; its displayed product version remains the alpha product version.
 
 The Desktop installers workflow builds on four native runners and is dispatchable by
 an exact branch/tag ref. Versioned, target-specific unsigned artifacts contain only

desktop/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@firefly-weave/desktop",
-  "version": "0.1.0-alpha.11",
+  "version": "0.1.0-alpha.12",
   "private": true,
   "license": "Apache-2.0",
   "scripts": {

desktop/src-tauri/Cargo.toml

@@ -16,7 +16,7 @@
 
 [package]
 name = "firefly-weave-studio"
-version = "0.1.0-alpha.11"
+version = "0.1.0-alpha.12"
 description = "Firefly Weave Studio desktop"
 authors = ["Firefly Software Foundation"]
 license = "Apache-2.0"

desktop/src-tauri/tauri.conf.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://schema.tauri.app/config/2",
   "productName": "Firefly Weave Studio",
-  "version": "0.1.0-alpha.11",
+  "version": "0.1.0-alpha.12",
   "identifier": "io.getfirefly.weave.studio",
   "build": {
     "frontendDist": "../bootstrap"
@@ -52,7 +52,7 @@
           "y": 160
         }
       },
-      "bundleVersion": "0.1.11",
+      "bundleVersion": "0.1.12",
       "signingIdentity": "-",
       "entitlements": "entitlements.plist"
     },
@@ -61,7 +61,7 @@
         "type": "downloadBootstrapper"
       },
       "wix": {
-        "version": "0.1.11"
+        "version": "0.1.12"
       }
     },
     "icon": [

docs/README.md

@@ -47,7 +47,7 @@ gives the steps and what you finish with.
 | An administrator | Install the platform, configure sign-in, and give people access | [Start a local platform](guides/local-platform.md) | [Identity and secrets](operations/identity-and-secrets.md), [remote deployment](operations/remote-deployment.md), [people and access](guides/people-and-access.md), and [configuration](operations/configuration.md) |
 | An operator | Keep runs healthy, fix incidents, upgrade, and back up | [Connect the CLI](guides/connect-to-api.md), then [manage runs](guides/execution-management.md) | [Incidents](reference/incident-operations.md), [troubleshooting](operations/troubleshooting.md), [observability](operations/observability.md), [upgrades](operations/upgrades.md), [backup](operations/backup-restore.md), and [debug-session retention](operations/retention.md) |
 
-Start each path by [installing the CLI](installation.md) from the v0.1.0a11
+Start each path by [installing the CLI](installation.md) from the v0.1.0a12
 release.
 
 [Who does what](guides/roles-and-lifecycle.md) explains these roles with an
@@ -104,7 +104,7 @@ Run one command block, check its **Expected** result, then continue. Comments
 inside code blocks explain why each command is there. When a terminal shows
 server logs, keep it open and use a second terminal for client commands.
 
-The guides pin the **v0.1.0a11 alpha** release, a preview, which includes every
+The guides pin the **v0.1.0a12 alpha** release, a preview, which includes every
 feature they describe, such as saved platforms, REST calls without code, and the
 Studio editor. When a guide shows how to work with an alpha6 or earlier client
 or server, it says so.

docs/capabilities.md

@@ -51,8 +51,8 @@ permissions, and real delivery still need checking in your deployment.
 ## Which release this page describes
 
 Weave is an alpha workflow and integration platform. This branch prepares release
-**`0.1.0a11`**, with PyFly 26.9.15 and database schema revision
-`0028_files`; published packages are on
+**`0.1.0a12`**, with PyFly 26.9.15 and database schema revision
+`0030_worker_presence`; published packages are on
 [GitHub Releases](https://github.com/fireflyframework/firefly-weave/releases).
 It includes [Studio](guides/studio.md), [human tasks and operator
 pause and resume](guides/human-tasks.md), [email conversations and