feat(docs): Update protocol titles and descriptions for consistency across documentation

Author: hotlong

content/docs/introduction/architecture.mdx

@@ -1,29 +1,29 @@
 ---
-title: The Stack - ObjectQL + ObjectUI + ObjectOS
-description: How the three protocols work together as one cohesive system
+title: Protocol Architecture
+description: How the Data, System, and UI protocols work together as one cohesive system
 ---
 
 import { Database, Layout, Cpu, ArrowRight, CheckCircle, Workflow } from 'lucide-react';
 
-# The Three-Layer Stack
+# The Protocol Stack
 
-ObjectStack is built on three foundational protocols that work together as a unified system:
+The architecture is built on three foundational protocols that work together as a unified system:
 
 <Cards>
   <Card
     icon={<Database />}
-    title="ObjectQL"
-    description="Data Protocol - Structure and queries"
+    title="Data Protocol"
+    description="Structure, queries, and constraints."
   />
   <Card
     icon={<Cpu />}
-    title="ObjectOS"
-    description="Control Protocol - Runtime and governance"
+    title="System Protocol"
+    description="Control, runtime, and governance."
   />
   <Card
     icon={<Layout />}
-    title="ObjectUI"
-    description="View Protocol - Presentation and interaction"
+    title="UI Protocol"
+    description="Presentation, interaction, and routing."
   />
 </Cards>
 
@@ -35,19 +35,19 @@ ObjectStack enforces **Separation of Concerns** through protocol boundaries:
 
 ```
 ┌─────────────────────────────────────────┐
-│          ObjectUI (View Layer)          │
+│              UI Protocol                │
 │  Apps, Views, Dashboards, Reports       │
 │  "How do users interact?"                │
 └──────────────┬──────────────────────────┘
-               │ API Protocol
+               │ View-Data Interface
 ┌──────────────┴──────────────────────────┐
-│        ObjectOS (Control Layer)         │
+│            System Protocol              │
 │  Auth, Permissions, Workflows, Events   │
 │  "Who can do what, when?"                │
 └──────────────┬──────────────────────────┘
-               │ Query Protocol
+               │ Control-Data Interface
 ┌──────────────┴──────────────────────────┐
-│         ObjectQL (Data Layer)           │
+│             Data Protocol               │
 │  Objects, Fields, Queries, Drivers      │
 │  "What is the data structure?"           │
 └─────────────────────────────────────────┘

content/docs/introduction/index.mdx

@@ -22,22 +22,22 @@ When requirements change, you update code in multiple places. This is **Implemen
 
 ## The Solution
 
-ObjectStack centralizes the "Intent" into a single Protocol Definition (JSON/YAML). The implementation layers (React, Node.js, SQL) act merely as **Runtime Engines** that interpret this protocol.
+We centralize the "Intent" into a single Protocol Definition (JSON/YAML). The implementation layers (React, Node.js, SQL) act merely as **Runtime Engines** that interpret this protocol.
 
 <Cards>
   <Card
     icon={<Database />}
-    title="ObjectQL (Data Layer)"
+    title="Data Protocol"
     description="Define data structures, queries, and business logic. Database-agnostic abstraction layer."
   />
   <Card
     icon={<Layout />}
-    title="ObjectUI (Presentation Layer)"
+    title="UI Protocol"
     description="Server-driven UI definitions. Express interfaces as JSON, not code."
   />
   <Card
     icon={<Cog />}
-    title="ObjectOS (Control Layer)"
+    title="System Protocol"
     description="Runtime kernel, plugins, security, and integration. The platform foundation."
   />
 </Cards>

content/docs/objectos/meta.json

@@ -1,5 +1,5 @@
 {
-  "title": "Protocol: System (ObjectOS)",
+  "title": "System Protocol",
   "root": true,
   "pages": [
     "index",

content/docs/objectql/meta.json

@@ -1,5 +1,5 @@
 {
-  "title": "Protocol: Data (ObjectQL)",
+  "title": "Data Protocol",
   "root": true,
   "pages": [
     "schema",

content/docs/objectui/meta.json

@@ -1,5 +1,5 @@
 {
-  "title": "Protocol: UI (ObjectUI)",
+  "title": "UI Protocol",
   "root": true,
   "pages": [
     "concept",