docs: add template-manifest and date-macros references

Author: os-zhuang

content/docs/guides/ai-capabilities.mdx

@@ -360,7 +360,7 @@ Use statistical analysis and ML.`,
 
 ## Actions as Tools (auto-exposed)
 
-Every declarative {@link Action} you attach to an object is **automatically exposed as an AI tool**, named `action_<actionName>`. When the LLM picks one, the AI runtime dispatches to the same handler Studio's row toolbar would invoke — your business logic stays in one place.
+Every declarative `Action` you attach to an object is **automatically exposed as an AI tool**, named `action_<actionName>`. When the LLM picks one, the AI runtime dispatches to the same handler Studio's row toolbar would invoke — your business logic stays in one place.
 
 ### What gets exposed
 

content/docs/references/cloud/index.mdx

@@ -15,5 +15,6 @@ This section contains all protocol schemas for the cloud layer of ObjectStack.
   <Card href="/docs/references/cloud/marketplace-admin" title="Marketplace Admin" description="Source: packages/spec/src/cloud/marketplace-admin.zod.ts" />
   <Card href="/docs/references/cloud/package" title="Package" description="Source: packages/spec/src/cloud/package.zod.ts" />
   <Card href="/docs/references/cloud/package-version" title="Package Version" description="Source: packages/spec/src/cloud/package-version.zod.ts" />
+  <Card href="/docs/references/cloud/template-manifest" title="Template Manifest" description="Source: packages/spec/src/cloud/template-manifest.zod.ts" />
   <Card href="/docs/references/cloud/tenant" title="Tenant" description="Source: packages/spec/src/cloud/tenant.zod.ts" />
 </Cards>

content/docs/references/cloud/meta.json

@@ -12,6 +12,7 @@
     "package-version",
     "plugin-security",
     "provisioning",
+    "template-manifest",
     "tenant"
   ]
 }

content/docs/references/cloud/template-manifest.mdx

@@ -0,0 +1,60 @@
+---
+title: Template Manifest
+description: Template Manifest protocol schemas
+---
+
+{/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs go in content/docs/guides/. */}
+
+`objectstack.manifest.json` — on-disk descriptor for a template / package
+
+source tree. Strict projection of `CreatePackageRequestSchema` (server-
+
+managed fields excluded) plus scaffold-time extras (name slug,
+
+specVersion, skills, preview, scaffold, readmePath).
+
+<Callout type="info">
+**Source:** `packages/spec/src/cloud/template-manifest.zod.ts`
+</Callout>
+
+## TypeScript Usage
+
+```typescript
+import { TemplateManifest } from '@objectstack/spec/cloud';
+import type { TemplateManifest } from '@objectstack/spec/cloud';
+
+// Validate data
+const result = TemplateManifest.parse(data);
+```
+
+---
+
+## TemplateManifest
+
+objectstack.manifest.json — template / package source descriptor
+
+### Properties
+
+| Property | Type | Required | Description |
+| :--- | :--- | :--- | :--- |
+| **manifestId** | `string` | ✅ | Globally unique reverse-domain package identifier (e.g. com.acme.crm) |
+| **displayName** | `string` | ✅ | Display name shown in Studio and Marketplace |
+| **description** | `string` | optional | Short package description |
+| **visibility** | `Enum<'private' \| 'org' \| 'marketplace'>` | optional | Package visibility: private = owner org only; org = all envs in owner org; marketplace = public registry |
+| **category** | `string` | optional | Package category for marketplace discovery (e.g. "crm", "hr", "finance", "devtools") |
+| **tags** | `string[]` | optional |  |
+| **iconUrl** | `string` | optional |  |
+| **homepageUrl** | `string` | optional |  |
+| **license** | `string` | optional |  |
+| **publisher** | `Enum<'objectstack' \| 'partner' \| 'community' \| 'private'>` | optional | Package publisher provenance tier |
+| **isStarter** | `boolean` | optional |  |
+| **name** | `string` | ✅ | CLI slug (kebab-case, no namespace prefix) |
+| **specVersion** | `string` | ✅ | Compatible @objectstack/spec semver range |
+| **skills** | `string[]` | optional | Skill ids exercised by this template (for docs / picker) |
+| **preview** | `Object` | optional |  |
+| **scaffold** | `Object` | optional |  |
+| **readmePath** | `string` | optional | Path (relative to manifest) to long-form README |
+
+
+---
+

content/docs/references/data/date-macros.mdx

@@ -0,0 +1,91 @@
+---
+title: Date Macros
+description: Date Macros protocol schemas
+---
+
+{/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs go in content/docs/guides/. */}
+
+Date Macro Tokens — the declarative placeholders the UI substitutes
+
+into filter values before sending a query to the data engine.
+
+# Why this lives in `spec`
+
+Filter values in dashboards, views, reports and pages travel as JSON.
+
+Because JSON cannot evaluate code, callers cannot write `daysAgo(30)`
+
+inline; they use a tiny placeholder grammar instead:
+
+\{ published_at: \{ $gte: '\{last_quarter_start\}' \} \}
+
+\{ signal_at:    \{ $gte: '\{30_days_ago\}' \} \}
+
+The placeholders are expanded **client-side** by
+
+`resolveDateMacros()` in `@object-ui/core` immediately before the
+
+filter is handed to the data source. The data engine itself only
+
+sees ISO date / timestamp strings, never `\{tokens\}`.
+
+AI agents and template authors author these placeholders directly,
+
+so the **set of recognised tokens is part of the platform contract**
+
+and must live here next to the rest of the JSON-DSL schemas, not
+
+inside any single UI implementation.
+
+# Two flavours of token
+
+1. **Fixed tokens** — small, finite list (`\{today\}`,
+
+`\{current_quarter_start\}`, `\{last_year_end\}`, …). Enumerated by
+
+`DATE_MACRO_TOKENS` below.
+
+2. **Parameterised tokens** — `\{N_days_ago\}`, `\{N_weeks_from_now\}`,
+
+etc., where `N` is any non-negative integer. Matched by
+
+`DATE_MACRO_PARAM_RE`. Units: `minute(s)`, `hour(s)`, `day(s)`,
+
+`week(s)`, `month(s)`, `year(s)`. Directions: `ago`, `from_now`.
+
+# Out of scope
+
+- CEL expressions (`cel\`daysAgo(30)\``) run **server-side** in the
+
+formula engine. They are unrelated to these placeholders; see
+
+`@objectstack/formula`.
+
+- Token resolution semantics (week-start day, timezone, fiscal
+
+calendars) are defined by the resolver implementation; spec only
+
+freezes the **vocabulary**.
+
+<Callout type="info">
+**Source:** `packages/spec/src/data/date-macros.zod.ts`
+</Callout>
+
+## TypeScript Usage
+
+```typescript
+import { DateMacroPlaceholder, DateMacroToken } from '@objectstack/spec/data';
+import type { DateMacroPlaceholder, DateMacroToken } from '@objectstack/spec/data';
+
+// Validate data
+const result = DateMacroPlaceholder.parse(data);
+```
+
+---
+
+
+---
+
+
+---
+

content/docs/references/data/index.mdx

@@ -10,6 +10,7 @@ This section contains all protocol schemas for the data layer of ObjectStack.
   <Card href="/docs/references/data/data-engine" title="Data Engine" description="Source: packages/spec/src/data/data-engine.zod.ts" />
   <Card href="/docs/references/data/dataset" title="Dataset" description="Source: packages/spec/src/data/dataset.zod.ts" />
   <Card href="/docs/references/data/datasource" title="Datasource" description="Source: packages/spec/src/data/datasource.zod.ts" />
+  <Card href="/docs/references/data/date-macros" title="Date Macros" description="Source: packages/spec/src/data/date-macros.zod.ts" />
   <Card href="/docs/references/data/document" title="Document" description="Source: packages/spec/src/data/document.zod.ts" />
   <Card href="/docs/references/data/driver" title="Driver" description="Source: packages/spec/src/data/driver.zod.ts" />
   <Card href="/docs/references/data/driver-nosql" title="Driver Nosql" description="Source: packages/spec/src/data/driver-nosql.zod.ts" />

content/docs/references/data/meta.json

@@ -5,6 +5,7 @@
     "data-engine",
     "dataset",
     "datasource",
+    "date-macros",
     "document",
     "driver",
     "driver-nosql",

packages/runtime/src/app-plugin.test.ts

@@ -174,7 +174,7 @@ describe('AppPlugin', () => {
             expect(mockI18n.setDefaultLocale).toHaveBeenCalledWith('zh-CN');
         });
 
-        it('should skip translation loading when i18n service is not registered', async () => {
+        it('should auto-register in-memory i18n fallback when service is not registered', async () => {
             vi.mocked(mockContext.getService).mockImplementation((name: string) => {
                 if (name === 'objectql') return mockQL;
                 return undefined; // No i18n service
@@ -187,13 +187,11 @@ describe('AppPlugin', () => {
             const plugin = new AppPlugin(bundle);
             await plugin.start!(mockContext);
 
-            // Should log warning (translations exist but no i18n service) and not throw
-            expect(mockContext.logger.warn).toHaveBeenCalledWith(
-                expect.stringContaining('no i18n service is registered')
-            );
+            // Auto-registers in-memory fallback and loads translations; does not throw or warn.
+            expect(mockContext.registerService).toHaveBeenCalledWith('i18n', expect.any(Object));
         });
 
-        it('should skip translation loading when getService throws for i18n', async () => {
+        it('should auto-register in-memory i18n fallback when getService throws for i18n', async () => {
             vi.mocked(mockContext.getService).mockImplementation((name: string) => {
                 if (name === 'objectql') return mockQL;
                 throw new Error("[Kernel] Service 'i18n' not found");
@@ -206,10 +204,7 @@ describe('AppPlugin', () => {
             const plugin = new AppPlugin(bundle);
             await plugin.start!(mockContext);
 
-            // Should log warning (translations exist but no i18n service) and not throw
-            expect(mockContext.logger.warn).toHaveBeenCalledWith(
-                expect.stringContaining('no i18n service is registered')
-            );
+            expect(mockContext.registerService).toHaveBeenCalledWith('i18n', expect.any(Object));
         });
 
         it('should handle bundle with no translations gracefully', async () => {