Merge pull request #1139 from objectstack-ai/claude/standardize-examples-app-host-to-apps-server

[WIP] Standardize examples/app-host to apps/server for unified application structure

Author: xuyushun441-sys

.github/copilot-instructions.md

@@ -79,12 +79,12 @@ objectstack-ai/spec/
 │
 ├── apps/
 │   ├── studio/            # 🎨 Studio UI (React + Hono, web-based)
-│   └── docs/              # 📖 Documentation site (Fumadocs + Next.js)
+│   ├── docs/              # 📖 Documentation site (Fumadocs + Next.js)
+│   └── server/            # 🚀 Production server (multi-app orchestration)
 │
 ├── examples/              # 📚 Reference implementations
 │   ├── app-todo/          # Beginner: simple CRUD
 │   ├── app-crm/           # Advanced: full CRM with relations
-│   ├── app-host/          # Host application bootstrap
 │   └── plugin-bi/         # Plugin example: BI dashboard
 │
 ├── skills/                # 🤖 AI skill definitions (for Copilot/Cursor)

CHANGELOG.md

@@ -290,7 +290,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Removed `value` field from data API responses** — The `findData` protocol
   implementation no longer returns the deprecated `value` field alongside `records`.
   Only `records` is returned, matching the `FindDataResponseSchema` spec. All
-  downstream consumers (Studio, app-host example, tests) updated to use `records`
+  downstream consumers (Studio, server example, tests) updated to use `records`
   exclusively. OData-specific responses (`ODataResponseSchema`) retain `value` per
   the OData v4 standard — protocol-to-OData adaptation is handled in the HTTP
   dispatch layer.

README.md

@@ -181,7 +181,7 @@ os doctor         # Check environment health
 | :--- | :--- | :--- |
 | [`@example/app-todo`](examples/app-todo) | Task management app — objects, views, dashboards, flows | Beginner |
 | [`@example/app-crm`](examples/app-crm) | Enterprise CRM — accounts, contacts, opportunities, leads | Intermediate |
-| [`@example/app-host`](examples/app-host) | Server host — multi-app orchestration with plugins | Advanced |
+| [`@objectstack/server`](apps/server) | Production server — multi-app orchestration with plugins | Advanced |
 | [`@example/plugin-bi`](examples/plugin-bi) | BI plugin — analytics objects and reports | Intermediate |
 
 ## Codebase Metrics

ROADMAP.md

@@ -852,7 +852,7 @@ Final polish and advanced features.
 
 - [x] **app-todo** — Beginner reference (objects, actions, flows, dashboards, reports, i18n) ✅
 - [x] **app-crm** — Enterprise reference (10 objects, 5 AI agents, 4 RAG pipelines, security profiles) ✅
-- [x] **app-host** — Multi-app orchestration pattern ✅
+- [x] **server** (formerly app-host) — Production server with multi-app orchestration pattern ✅
 - [ ] **plugin-bi** — Business Intelligence plugin (currently a stub/placeholder)
 - [ ] **app-hrm** — Human Resource Management example
 - [ ] **app-project** — Project Management example

examples/app-host/.env.example apps/server/.env.exampleexamples/app-host/.env.example renamed to apps/server/.env.example

@@ -1,6 +1,6 @@
-# Deploying App Host to Vercel
+# Deploying ObjectStack Server to Vercel
 
-This example demonstrates how to deploy the ObjectStack app-host to Vercel using Hono.
+This guide demonstrates how to deploy the ObjectStack production server to Vercel using Hono.
 
 ## Prerequisites
 
@@ -26,9 +26,9 @@ You can get these credentials from [Turso Dashboard](https://turso.tech/).
    npm i -g vercel
    ```
 
-2. Navigate to the app-host directory:
+2. Navigate to the server directory:
    ```bash
-   cd examples/app-host
+   cd apps/server
    ```
 
 3. Deploy to Vercel:
@@ -46,7 +46,7 @@ You can get these credentials from [Turso Dashboard](https://turso.tech/).
 ### Option 2: Using Vercel Dashboard
 
 1. Import the repository to Vercel
-2. Set the root directory to `examples/app-host`
+2. Set the root directory to `apps/server`
 3. Add environment variables in the project settings
 4. Deploy
 
@@ -64,7 +64,7 @@ The build is configured in `vercel.json`:
 ## How It Works
 
 1. **Build Process** (`scripts/build-vercel.sh`):
-   - Builds both app-host and Studio using Turbo
+   - Builds both server and Studio using Turbo
    - Studio is built with `VITE_RUNTIME_MODE=server` (set in vercel.json build.env)
    - Bundles the server code using esbuild (`scripts/bundle-api.mjs`)
    - Copies Studio dist files to `public/` for static file serving
@@ -95,7 +95,7 @@ The build is configured in `vercel.json`:
 The deployment follows Vercel's serverless function pattern:
 
 ```
-examples/app-host/
+apps/server/
 ├── api/
 │   ├── [[...route]].js      # Committed entry point
 │   └── _handler.js           # Generated bundle (not committed)

examples/app-host/.gitignore apps/server/.gitignoreexamples/app-host/.gitignore renamed to apps/server/.gitignore

@@ -1,11 +1,11 @@
-# ObjectStack Example Server
+# ObjectStack Production Server
 
 This is a reference implementation of the ObjectStack Server Protocol (Kernel).
 It demonstrates how to build a metadata-driven backend that dynamically loads object definitions from plugins and automatically generates REST APIs.
 
 ## Deployment
 
-[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/clone?repository-url=https://github.com/objectstack-ai/framework/tree/main/examples/app-host&project-name=objectstack-app-host&repository-name=objectstack-app-host)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/clone?repository-url=https://github.com/objectstack-ai/framework/tree/main/apps/server&project-name=objectstack-server&repository-name=objectstack-server)
 
 See [DEPLOYMENT.md](./DEPLOYMENT.md) for detailed deployment instructions.