feat: Refactor framework documentation and remove deprecated files

Author: hotlong

content/docs/framework/cli.mdx

@@ -0,0 +1,44 @@
+---
+title: Command Line Interface
+description: Guide for using the ObjectStack CLI
+---
+
+# @objectstack/cli
+
+Command Line Interface for developing and managing ObjectStack applications.
+
+## Installation
+
+```bash
+pnpm add -D @objectstack/cli
+```
+
+## Commands
+
+### Development
+
+- **`os serve`**: Start the backend server.
+  - Auto-detects configuration.
+  - Auto-loads `ObjectQL` and `InMemoryDriver` if not specified.
+- **`os dev`**: Start in development mode (with watch).
+- **`os doctor`**: Check environment health.
+
+### Scaffolding
+
+- **`os create`**: Scaffold new projects.
+
+## Configuration
+
+The CLI automatically looks for `objectstack.config.ts` in the current directory to load the runtime configuration.
+
+```typescript
+// objectstack.config.ts
+export default {
+    metadata: { 
+        // ... 
+    },
+    plugins: [ 
+        // ... 
+    ]
+}
+```

content/docs/framework/cli/meta.json

@@ -28,29 +28,55 @@ The kernel scans for registered plugins. In a typical app, plugins are explicitl
 Each plugin's manifest is validated against the **Plugin Protocol** specific in `@objectstack/spec`.
 - **Name**: Must be unique.
 - **Version**: SemVer compatible.
-- **Dependencies**: Declared dependencies must be present.
 
-### 3. Resolution Phase (Topological Sort)
-The kernel builds a dependency graph of all plugins. If Plugin A depends on Plugin B, Plugin B is guaranteed to be initialized first. Circular dependencies will throw a fatal error.
+### 3. Resolution Phase
+The kernel resolves the dependency graph. If Plugin A depends on Plugin B, the kernel ensures Plugin B is loaded first. Circular dependencies are detected and will throw an error.
 
-### 4. Init Phase (Synchronous Setup)
-The `init(ctx)` hook is called for every plugin in order.
-- **Purpose**: Register Services, Validate Configuration.
-- **Restriction**: NO side effects (e.g., do not connect to DB, do not start HTTP server).
-- **Outcome**: The Service Registry is fully populated.
+### 4. Init Phase (`onInit`)
+The `onInit` hook is called for all plugins in dependency order. This is where plugins should:
+- Register Services involved in Dependency Injection.
+- Register Event Listeners.
+- **NOT** perform async IO (like database connections) if possible.
 
-### 5. Start Phase (Async Execution)
-The `start(ctx)` hook is called.
-- **Purpose**: Connect to databases, bind network ports, start background jobs.
-- **Outcome**: The system is live.
+### 5. Start Phase (`onStart`)
+After all plugins have successfully initialized, the `onStart` hook is called in dependency order. This is where the application "comes alive":
+- Database connections are established.
+- HTTP servers start listening.
+- Background jobs are scheduled.
 
-## Error Handling
+## IKernel Interface Reference
 
-The Kernel implements a **Rollback Mechanism**. If any plugin fails during the `start` phase, the kernel attempts to stop all previously started plugins in reverse order to ensure a clean exit.
+The `IKernel` is the central orchestrator exposed to the host application.
 
 ```typescript
-const kernel = new ObjectKernel({
-    rollbackOnFailure: true, // Default: true
-    defaultStartupTimeout: 30000 // 30s timeout per plugin
-});
+export interface IKernel {
+    /**
+     * Start the Kernel
+     * Initializes and starts all registered plugins and drivers.
+     */
+    start(): Promise<void>;
+
+    /**
+     * Stop the Kernel
+     * Gracefully shuts down all plugins.
+     */
+    stop(): Promise<void>;
+
+    /**
+     * Get a Service
+     * Retrieves a registered service by ID.
+     */
+    getService<T>(id: string): T;
+
+    /**
+     * Register a Service
+     * Manually register a service instance (dynamic registration).
+     */
+    registerService(id: string, instance: any): void;
+
+    /**
+     * Check Service Availability
+     */
+    hasService(id: string): boolean;
+}
 ```

content/docs/framework/core/architecture.mdx

@@ -5,7 +5,6 @@
     "architecture",
     "plugins",
     "services",
-    "events",
-    "types"
+    "events"
   ]
 }

content/docs/framework/core/meta.json

@@ -28,41 +28,71 @@ export class MyPlugin implements Plugin {
         apiKey: z.string()
     });
 
-    // 1. Initialization
-    async init(ctx: PluginContext) {
-        // Register services here
-        const myService = new MyService();
-        ctx.registerService('my-service', myService);
+    /**
+     * Initialization Phase
+     * Use this to register services, listeners, or other early setup.
+     */
+    async onInit(ctx: PluginContext) {
+        // Register a service
+        ctx.services.register('myService', new MyService());
     }
 
-    // 2. Startup
-    async start(ctx: PluginContext) {
-        // Resolve other services
-        const db = ctx.getService('database');
-        await db.connect();
-    }
-
-    // 3. Shutdown
-    async stop(ctx: PluginContext) {
-        // Cleanup
+    /**
+     * Start Phase
+     * The system is fully initialized. Use this to start servers or background jobs.
+     */
+    async onStart(ctx: PluginContext) {
+        console.log('MyPlugin started!');
     }
 }
 ```
 
-## The Plugin Context
+## RuntimePlugin Interface Reference
+
+The `RuntimePlugin` interface defines the contract that all functionality modules must implement.
+
+```typescript
+export interface RuntimePlugin {
+    /**
+     * Plugin Unique Identifier
+     * Recommended format: com.organization.plugin-name
+     */
+    name: string;
+
+    /**
+     * Plugin Version
+     * Must follow Semantic Versioning (SemVer)
+     */
+    version?: string;
 
-The `PluginContext` is passed to every lifecycle hook. It is the plugin's gateway to the Kernel.
+    /**
+     * Description
+     * Brief explanation of the plugin's purpose.
+     */
+    description?: string;
 
-| Method | Description |
-| :--- | :--- |
-| `ctx.logger` | A structured logger scoped to this plugin (e.g., labeled `[com.example.plugin]`). |
-| `ctx.registerService(name, impl)` | Expose a capability to other plugins. |
-| `ctx.getService(name)` | Retrieve a capability from another plugin. |
-| `ctx.hook(event, callback)` | Listen for system events. |
-| `ctx.emit(event, payload)` | Broadcast an event. |
+    /**
+     * Initialization Hook
+     * Called during Kernel bootstrap. Use this to:
+     * - Register Services
+     * - Register Event Listeners
+     * - Extend Metadata
+     */
+    onInit?: (context: PluginContext) => Promise<void>;
 
-## Best Practices
+    /**
+     * Start Hook
+     * Called after all plugins are initialized. Use this to:
+     * - Start HTTP servers
+     * - Connect to databases
+     * - Start background workers
+     */
+    onStart?: (context: PluginContext) => Promise<void>;
 
-1.  **Prefix Names**: Use reverse domain notation (e.g., `com.mycompany.plugin`) to avoid collisions.
-2.  **Define Contracts**: If your plugin exposes a service, export a TypeScript interface for it so consumers can type-check.
-3.  **Config Validation**: Use `configSchema` (Zod) to validate user input. The Kernel automatically validates this before `init` is called.
+    /**
+     * Stop Hook
+     * Called during Kernel shutdown. cleanup resources here.
+     */
+    onStop?: (context: PluginContext) => Promise<void>;
+}
+```

content/docs/framework/core/plugins.mdx

@@ -0,0 +1,45 @@
+---
+title: Database Drivers
+description: Configuration reference for supported database drivers
+---
+
+# Database Drivers
+
+ObjectStack supports multiple database backends through a unified driver configurations.
+
+## MongoDB
+
+Configuration properties for the MongoDB driver.
+
+| Property | Type | Required | Description |
+| :--- | :--- | :--- | :--- |
+| **url** | `string` | optional | Connection URI |
+| **database** | `string` | ✅ | Database Name |
+| **host** | `string` | optional | Host address |
+| **port** | `number` | optional | Port number |
+| **username** | `string` | optional | Auth User |
+| **password** | `string` | optional | Auth Password |
+| **authSource** | `string` | optional | Authentication Database |
+| **ssl** | `boolean` | optional | Enable SSL |
+| **replicaSet** | `string` | optional | Replica Set Name |
+| **readPreference** | `Enum` | optional | Read Preference ('primary', 'secondary', etc.) |
+| **maxPoolSize** | `number` | optional | Max Connection Pool Size |
+| **minPoolSize** | `number` | optional | Min Connection Pool Size |
+
+## PostgreSQL
+
+Configuration properties for the PostgreSQL driver (node-postgres / pg).
+
+| Property | Type | Required | Description |
+| :--- | :--- | :--- | :--- |
+| **url** | `string` | optional | Connection URI |
+| **database** | `string` | ✅ | Database Name |
+| **host** | `string` | optional | Host address |
+| **port** | `number` | optional | Port number |
+| **username** | `string` | optional | Auth User |
+| **password** | `string` | optional | Auth Password |
+| **schema** | `string` | optional | Default Schema (defaults to 'public') |
+| **ssl** | `boolean \| object` | optional | Enable SSL |
+| **applicationName** | `string` | optional | Application Name |
+| **max** | `number` | optional | Max Pool Size |
+| **min** | `number` | optional | Min Pool Size |