assuremind 1.5.3 → 1.6.0

package/docs/GETTING-STARTED.md

@@ -377,26 +377,42 @@ npx assuremind apply-healing --yes
 
 ---
 
-## 11. Use Test Variables
+## 11. Use Test Variables (per-environment + CI secrets)
 
-Variables let you avoid hardcoding credentials and URLs. Define them in `variables/global.json`:
+Variables let you avoid hardcoding credentials and URLs. Reference them in steps with double-braces:
 
-```json
-{
-  "BASE_URL": "http://localhost:3000",
-  "ADMIN_EMAIL": "admin@example.com",
-  "ADMIN_PASSWORD": { "value": "supersecret", "secret": true }
-}
 ```
+Enter "{{ADMIN_EMAIL}}" in the email field
+Enter "{{ADMIN_PASSWORD}}" in the password field
+```
+
+### Environments
+Projects define a set of environments — by default **DEV, TEST, STAGE, INT, PROD** — editable in **Settings → Environment** (add, rename, delete, and set a base URL per environment). The **active** environment determines which values and base URL a run uses (override per run with `--env <NAME>`).
 
-Reference them in step instructions using double-braces:
+### Per-environment values
+In **Studio → Variables**, each variable can hold a different value **per environment**, plus a **Global (default)** that applies when an environment has no specific value. On disk this is plain JSON:
 
 ```
-Enter "{{ADMIN_EMAIL}}" in the email field
-Enter "{{ADMIN_PASSWORD}}" in the password field
+variables/global.json        # defaults
+variables/DEV.env.json        # DEV overrides
+variables/PROD.env.json       # PROD overrides
 ```
 
-Or manage variables in the Studio → **Variables** page.
+```jsonc
+// variables/global.json
+{ "ADMIN_EMAIL": "admin@example.com",
+  "ADMIN_PASSWORD": { "value": "local_secret", "secret": true } }
+
+// variables/PROD.env.json  — overrides only for PROD
+{ "ADMIN_PASSWORD": { "value": "prod_secret", "secret": true } }
+```
+
+### CI/CD secret overrides (highest priority)
+At runtime, resolution is: **`process.env` → environment value → global default**. So if your pipeline injects a repository **secret** with the same key name (e.g. a GitHub Actions/GitLab secret `ADMIN_PASSWORD`), it **automatically overrides** the stored value — no file changes needed. Locally, with no such env var set, the stored value is used. This gives you one workflow that's safe locally and seamless in CI.
+
+> Tip: keep real production secrets **out of the repo** — store a placeholder (or nothing) locally and inject the real value via CI secrets.
+
+Manage all of this in the Studio → **Variables** page (environment grid) and **Settings → Environment**.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "assuremind",
-  "version": "1.5.3",
+  "version": "1.6.0",
   "description": "AI-powered codeless UI & API automation framework",
   "author": "Deepak Hiremath",
   "license": "Apache-2.0",

package/templates/docs/GETTING-STARTED.md

@@ -330,16 +330,17 @@ Enter "{{USERNAME}}" in the email field
 Enter "{{PASSWORD}}" in the password field
 ```
 
-**Environment-specific variables** (override globals per env):
-- `variables/dev.env.json` — used with `--env dev`
-- `variables/staging.env.json` — used with `--env staging`
-- `variables/prod.env.json` — used with `--env prod`
+**Per-environment values:** each variable can hold a different value per environment (default envs: **DEV, TEST, STAGE, INT, PROD**, editable in Settings → Environment), with a **Global (default)** fallback. On disk:
+- `variables/global.json` — defaults
+- `variables/DEV.env.json`, `variables/PROD.env.json`, … — per-environment overrides
 
 ```bash
-npx assuremind run --all --env staging
+npx assuremind run --all --env PROD
 ```
 
-**Manage via Studio:** Settings → Variables page lets you add/edit/delete variables with a UI.
+**CI/CD secret overrides:** at runtime, resolution is **`process.env` → environment value → global default**. If your pipeline injects a repository **secret** with the same key name (e.g. `PASSWORD`), it overrides the stored value automatically — no file changes. Locally (no such env var) the stored value is used.
+
+**Manage via Studio:** the **Variables** page shows an environment grid (set a value per env + global); add/rename/delete environments in **Settings → Environment**.
 
 ---