Update navigation and reorganize spec index

Renamed 'Applications & Navigation' to 'Menus & Navigation' in the VitePress sidebar and updated corresponding links. The spec index was reorganized for clarity, with improved sectioning and descriptions, and removed the AI-Native Metadata Design section for conciseness.

Author: hotlong

docs/.vitepress/config.mts

@@ -118,7 +118,7 @@ export default defineConfig({
             { text: 'Views & Layouts', link: '/spec/view' },
             { text: 'Forms', link: '/spec/form' },
             { text: 'Reports & Dashboards', link: '/spec/report' },
-            { text: 'Applications & Navigation', link: '/spec/application' },
+            { text: 'Menus & Navigation', link: '/spec/menu' },
           ]
         },
         {

docs/spec/index.md

@@ -1,47 +1,17 @@
-# ObjectQL Metadata Specifications
+# Metadata Specifications
 
 This section contains the complete metadata specifications for the ObjectQL platform. ObjectQL is a metadata-driven standard for enterprise applications - every aspect of your application is defined through structured metadata.
 
 📖 **[Read the Complete Metadata Standard Guide](./metadata-standard.md)** - A comprehensive overview of the entire metadata system and how all pieces fit together.
 
-## 🤖 AI-Native Metadata Design
-
-ObjectQL metadata is designed from the ground up to be **AI-friendly**, enabling:
-
-- **Better Code Generation**: AI tools understand business intent, not just syntax
-- **Natural Language Queries**: Convert user questions to structured queries
-- **Auto-Documentation**: Generate comprehensive docs from metadata
-- **Smart Validation**: AI suggests improvements and catches errors
-- **Realistic Test Data**: Generate test data following proper patterns
-
-### AI Context Blocks
-
-All metadata types support optional `ai_context` blocks that provide semantic information:
-
-```yaml
-# Example: Object with AI context
-name: project
-fields:
-  status:
-    type: select
-    options: [planning, active, completed]
-    
-    ai_context:
-      intent: "Track project through its lifecycle"
-      is_state_machine: true
-      transitions:
-        planning: [active, cancelled]
-        active: [completed, cancelled]
-```
-
-## 🗂️ Specification Categories
+## Core Data Layer
 
-### Core Data Layer
-*   [**Objects & Fields**](./object.md) - Data model definitions, field types, relationships, and validation
+*   [**Objects & Fields**](./object.md) - Data model definitions, field types, relationships, and validation rules
 *   [**Query Language (JSON-DSL)**](./query-language.md) - Unified query protocol for database-agnostic data access
 *   [**Validation Rules**](./validation.md) - Data quality and business rule enforcement
 
-### Business Logic Layer
+## Business Logic Layer
+
 *   [**Hooks (Triggers)**](./hook.md) - Event-driven logic attached to data operations
 *   [**Actions (RPC)**](./action.md) - Custom server-side functions and APIs
 *   [**Workflows & Processes**](./workflow.md) - Automated business processes and approval chains
@@ -53,8 +23,14 @@ fields:
 *   [**Reports & Dashboards**](./report.md) - Analytics and BI
 *   [**Menus & Navigation**](./menu.md) - Application structure and navigation hierarchy
 
-### Security & Access Control
-*   [**Permissions**](./permission.md) - Role-based access control and security rules
+*   [**Views & Layouts**](./view.md) - Data presentation configurations (list, grid, kanban, calendar)
+*   [**Forms**](./form.md) - Data entry and editing interfaces
+*   [**Reports & Dashboards**](./report.md) - Analytics, visualizations, and business intelligence
+*   [**Applications & Navigation**](./application.md) - Application structure and menu hierarchy
+
+## Security & Access Control
+
+*   [**Permissions**](./permission.md) - Role-based access control, field-level security, and record-level rules
 
 ## Design Philosophy