docs: promise per-regime customization truth on integrations + build-without-code (#12368)

ADR-0126 §1.3 documented a shipped over-promise: two capability pages told
readers marketplace apps could be "customize[d] in Studio" without
qualification, which held for views/dashboards but not for a packaged flow —
locked at the write door and reachable only through disable+clone. §8 item 4
gates the correction on the L5 Setup surface existing (objectui#6382,
merged), which it now does.

Rewrite both promises to the three-regime truth:
- presentational (views, dashboards) — edit directly, unchanged
- behavioral (packaged flows) — locked; switch off and clone your own via
  Setup's packaged-automation page, then edit the clone in Studio
- structural (packaged objects) — extend with your own fields via an
  extension package, never in-place edits to what shipped

---
_Generated by [Claude Code](https://claude.ai/code/session_01KWRU3s15AJz7PGW7a7wdCh)_

Co-authored-by: Claude <noreply@anthropic.com>

Author: os-support-ai

content/docs/build-without-code.mdx

@@ -34,7 +34,7 @@ Two properties make Studio safe to hand to non-developers:
 
 ## Setup — where the platform is administered
 
-The **System Settings** app covers platform administration: user management and invitations, permission assignment, datasources (including federated external databases), diagnostics and audit logs, and the **Marketplace** — template apps such as HotCRM install with one click and appear alongside your own apps, ready to customize in Studio.
+The **System Settings** app covers platform administration: user management and invitations, permission assignment, datasources (including federated external databases), diagnostics and audit logs, and the **Marketplace** — template apps such as HotCRM install with one click and appear alongside your own apps. What "customize" means depends on the piece: views and dashboards are yours to edit directly; a packaged object grows through your own fields via an extension package, never by reshaping what shipped; a packaged flow stays locked, but a dedicated **packaged automation** page here lets you switch it off and clone your own — the clone is an ordinary flow, yours to edit in Studio.
 
 ## When to reach for code instead
 

content/docs/capabilities/integrations.mdx

@@ -14,7 +14,7 @@ A business system earns its keep by fitting into the systems — and habits —
 - **Triggers in** — external systems start platform [flows](/docs/capabilities/automation).
 - **Connectors** — ready-made Slack and generic REST connectors drop into flows; an HTTP API, OpenAPI document, or MCP server can be [declared as metadata](/docs/automation/connectors) and goes live at boot, no plugin code.
 - **Federated external databases** — point at an existing database and query it in place: no migration, visible in views, usable in flows.
-- **Marketplace templates** — install complete apps (HotCRM among them) with one click: objects, views, flows, dashboards, and seed data included, then customize in Studio.
+- **Marketplace templates** — install complete apps (HotCRM among them) with one click: objects, views, flows, dashboards, and seed data included. Views and dashboards are yours to edit directly; a packaged flow stays locked, but [Setup](/docs/build-without-code) lets you switch it off and clone your own to edit in Studio; a packaged object grows through your own fields via an extension package, not by editing what shipped.
 - **Deploy anywhere** — cloud or fully self-hosted; your data and your app definition stay yours.
 
 ## Everyday collaboration