@@ -0,0 +1,25 @@
+---
+'@objectstack/cli': patch
+'@objectstack/spec': patch
+---
+
+feat: `kind:'react'` pages are off unless the deployment turns them on
+
+Clause-②: no
+Metadata-protocol: none
+
+**BREAKING**: the `kind:'react'` page tier, which runs page source in the Console, now defaults to **off** (ADR-0081, amended). A deployment that serves react pages turns the tier on with `OS_PAGE_REACT_ENABLED=true`, in the environment or the project's `.env` file. With it off, each react page shows a notice naming that switch instead of running, and the Console document's content-security-policy no longer allows `'unsafe-eval'`. `kind:'html'` pages are unaffected.
+
+### Migration: FROM → TO
+
+```bash
+# FROM — react pages ran unless the deployment set OS_PAGE_REACT=off
+# TO — they run only when the deployment opts in
+OS_PAGE_REACT_ENABLED=true
+```
+
+The earlier name is still read while the new one is unset: `OS_PAGE_REACT=on` turns the tier on and `OS_PAGE_REACT=off` keeps it off, each with a one-time deprecation warning. `true`, `1`, `on`, `yes` and `enabled` turn it on; unset, `false`, `0`, `off`, `no` and `disabled` leave it off; any other value leaves it off and is reported once in the server log.
+
+The server now writes the Console's capability global in both directions, so a Console build with either default follows the server's setting. `examples/app-showcase` opts in through its `.env`, so its three react pages keep running. The `PageSchema.kind` description in `@objectstack/spec` now states the new default.
+
+Operators who collect content-security-policy reports may see one `script-src` eval refusal per Console load while the tier is off: the Console's schema library probes for `eval` once at boot and falls back without it. Nothing on the page is affected, and the probe is removed on the objectui side.
@@ -39,9 +39,9 @@ write the page body as a string. Pick by what the page needs:
 For `html` / `react`, the page body is the `source` string (it is the
 source-of-truth; `regions` is ignored). `html` is **safe by construction** (it
 is parsed into the same SDUI tree this document describes, never executed).
-`react` executes author code, so it is gated by a host capability that is **ON
-by default** and disabled per-deployment with the `OS_PAGE_REACT=off` env
-variable. Both tiers can embed the platform's real data components
+`react` executes author code, so it is gated by a host capability that is **OFF
+by default** and turned on per deployment with the `OS_PAGE_REACT_ENABLED=true`
+env variable. Both tiers can embed the platform's real data components
 (`<ObjectTable>`, `<ObjectForm>`, charts, metrics).
 
 > **Learn more:** [ADR-0080](https://github.com/objectstack-ai/objectstack/blob/main/docs/adr/0080-ai-authored-ui-jsx-source.md)
 
@@ -108,8 +108,9 @@ is rejected by the schema rather than rendering empty.
 `'jsx'` keep loading as `html` pages.
 
 Because `kind: 'react'` executes author JavaScript, it is gated by a host capability that
-defaults **ON** and is disabled server-side per deployment with `OS_PAGE_REACT=off`. The
-`html` tier is unaffected by that switch — it is never executed.
+defaults **OFF** and is turned on server-side per deployment with
+`OS_PAGE_REACT_ENABLED=true`. The `html` tier is unaffected by that switch — it is never
+executed.
 
 <Callout type="warn">
 Neither source tier is styled with Tailwind utility classes. A page's `source` is
 
@@ -58,20 +58,27 @@ The two tiers also differ in what they give you for layout, in opposite directio
 
 ## The security gate
 
-Because the react tier runs author JavaScript, it is gated by a host capability named
-`react-pages`, which defaults **ON** — the platform's assumption is that page authors
-are reviewed and draft-gated.
+Because the react tier runs author JavaScript in every viewer's session, with no sandbox,
+it is gated by a host capability named `react-pages`, which defaults **OFF**. The tier is
+for deployments whose page authors are trusted and reviewed.
 
-A deployment that does not trust its page authors turns the tier off **server-side**:
+A deployment that trusts its page authors turns the tier on **server-side**:
 
 ```bash
-OS_PAGE_REACT=off objectstack start
+OS_PAGE_REACT_ENABLED=true objectstack start
 ```
 
-The server then injects the console's capability-disable flag, and every `kind:'react'`
-page renders an explanatory notice instead of executing. `off`, `0`, `false`, `no` and
-`disabled` are all accepted spellings. `kind:'html'` pages are unaffected — they were
-never executed in the first place, which is the whole point of the split.
+or with the same line in the project's `.env` file. `true`, `1`, `on`, `yes` and `enabled`
+turn it on; unset, `false`, `0`, `off`, `no` and `disabled` leave it off. Any other value
+leaves it off and is reported once in the server log. The earlier name `OS_PAGE_REACT`
+(`on` / `off`) is still read when `OS_PAGE_REACT_ENABLED` is unset, with a deprecation
+warning.
+
+With the tier off, every `kind:'react'` page renders a notice that names the switch
+instead of executing, and the Console's content-security-policy refuses `eval`. With it
+on, the server tells the Console to run react pages and the policy allows the `Function`
+call the runtime compiles them with. `kind:'html'` pages are unaffected either way — they
+are never executed, which is the whole point of the split.
 
 ## What is in scope
 
 
@@ -1,6 +1,6 @@
 # ADR-0081: A trusted `kind:'react'` page tier — real React executed in the main tree, gated by a host capability; and renaming `kind:'jsx'` → `kind:'html'`
 
-**Status**: Accepted (2026-06-30) — framework scope implemented (`html`/`react` page kinds + `jsx` alias, lint split `validate-jsx-pages`/`validate-react-pages`, `OS_PAGE_REACT=off` server toggle); the `@object-ui/react-runtime` executor + `CAP_REACT_PAGES` gate live in objectui.
+**Status**: Accepted (2026-06-30) — framework scope implemented (`html`/`react` page kinds + `jsx` alias, lint split `validate-jsx-pages`/`validate-react-pages`, `OS_PAGE_REACT=off` server toggle); the `@object-ui/react-runtime` executor + `CAP_REACT_PAGES` gate live in objectui. **Amended** (2026-10-25 — the `react` tier defaults **OFF**; a deployment opts in with `OS_PAGE_REACT_ENABLED=true`. See "Amendment (2026-10-25): default off, opt in per deployment".)
 **Deciders**: ObjectStack Protocol Architects
 **Builds on**: [ADR-0080](./0080-ai-authored-ui-jsx-source.md) (AI authors a *constrained* JSX text, parsed-never-executed, into the SDUI tree; the component registry is the contract; capability ≠ contract), [ADR-0033](./0033-ai-assisted-metadata-authoring.md) (AI writes metadata via draft-gated `saveMetaItem` — the human-review boundary), [ADR-0077](./0077-authoring-surface-boundary-hook-flow-validation.md) (route by intent; verifiability tier = friction tier; **code is the flagged escape hatch**), [ADR-0078](./0078-no-silently-inert-metadata.md) (no silently-inert metadata).
 **Consumers**: `@objectstack/spec` (`packages/spec/src/ui/page.zod.ts` — `kind` gains `'html'` and `'react'`; `'jsx'` kept as a deprecated alias), `@objectstack/lint` (`validate-jsx-pages` — lints `html`/`jsx`, **skips** `react`), `../objectui` `@object-ui/react-runtime` (**new** — the trusted runtime-React executor) + `@object-ui/core` (the host capability gate) + `@object-ui/components` (PageRenderer routing + the full HTML tag set).
@@ -13,6 +13,8 @@
 
 > **Amendment (2026-06-30 — ADR-0065 styling correction).** The "HTML + **Tailwind**" framing for page `source` is **superseded on styling**. A page's `source` is *runtime metadata*, so the console's build-time Tailwind never scans it — authored utility `className`s silently produce no CSS (the exact failure ADR-0065 was written to prevent; the Task Desk modal's `bg-black/50` backdrop rendered transparent). The tiers themselves stand; only the styling **primitive** changes: `kind:'html'` styles via the registered components' structured props + a JSON `style` object; `kind:'react'` styles via inline `style={{}}` with `hsl(var(--token))` theme colors and renders drawer/modal overlays through `<ObjectForm formType="drawer"|"modal">` (never a hand-rolled `fixed inset-0`). **Do not author Tailwind classes in page source.** See [ADR-0065](./0065-sdui-styling-model.md).
 
+> **Amendment (2026-10-25): default off, opt in per deployment.** Decision 3 and TL;DR 4 are **superseded on the default**; the tier, its gate and its host-only control stand. `CAP_REACT_PAGES` now defaults **OFF** in `@object-ui/core`, and the ObjectStack console serving (`cli/utils/console.ts`, `readReactPagesTier`) turns it on only when the operator sets `OS_PAGE_REACT_ENABLED=true` (`OS_PAGE_REACT=on`, the earlier name, is still read through `readEnvWithDeprecation`). The server writes the capability global in **both** directions — the enable list when on, the disable list when off — so its answer holds against a Console build with either default. The Console document's content-security-policy keeps `'unsafe-eval'` tied to the same per-request read. Off, a react page renders the named "React pages are disabled on this deployment" notice. **Why the default moved:** "trust + review" names a property of one deployment's page authors, which only that deployment's operator can vouch for, so the platform default no longer vouches for it on every deployment; the operator makes the trust decision explicitly. Reference deployments that ship react pages opt in in their own configuration (`examples/app-showcase/.env`).
+
 ## TL;DR
 
 1. **[rename] `kind:'jsx'` → `kind:'html'`.** The constrained, parse-never-execute tier (ADR-0080) is renamed to match what it is: author-written **HTML + Tailwind** (expressed as constrained JSX) compiled to the SDUI tree. `'jsx'` stays as a **deprecated alias** (already-saved pages keep loading); all authored examples/docs move to `'html'`.