fix: add map format support to CLI commands and fix docs field syntax

[Copilot]

CLI commands (lint, doctor, validate, compile, info) used Array.isArray() on raw config input, silently skipping map-formatted metadata collections. Documentation examples incorrectly showed fields as arrays when ObjectSchema defines fields as z.record() (map-only).

CLI: normalize before processing

All commands that consume raw user configs now call normalizeStackInput() before processing:

const { config: rawConfig } = await loadConfig(configPath);
const config = normalizeStackInput(rawConfig as Record<string, unknown>);

• lint.ts — map-formatted objects/apps/flows/agents now lint correctly
• doctor.ts — circular dependency, orphan view, unused object checks work with maps
• validate.ts / compile.ts — normalizeStackInput() before safeParse() so map configs pass validation
• info.ts — metadata stats report correct counts for map configs
• format.ts — collectMetadataStats() count helper handles both formats defensively

Docs: fields must always be map format

Fixed all "Array Format" tab examples where fields was incorrectly shown as fields: [{ name: 'x', ... }]. Per ObjectSchema, fields is z.record() — only the top-level collection (objects, apps, etc.) varies between array/map:

// ✗ Wrong — fields is never an array
objects: [{ name: 'user', fields: [{ name: 'email', type: 'email' }] }]

// ✓ Correct — fields is always a map, only objects uses array format here
objects: [{ name: 'user', fields: { email: { type: 'email' } } }]

Files: core-concepts.mdx, common-patterns.mdx (CRUD, master-detail, approval, field-level security, summary)

Audit: packages with correct support (no changes)

core, client, rest, runtime, objectql (explicit dual-format handling in registerPlugin), metadata, studio — all already handle map format correctly or don't consume raw stack configs.

Original prompt

拉取请求: #680

评估所有的内核软件包，所有的api 和client是不是都已经支持新的map语法

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
objectstack-play	Canceled		Feb 15, 2026 2:50am
spec	Ready	Preview, Comment	Feb 15, 2026 2:50am

[Copilot]

Pull request overview

This PR adds map format support to CLI commands and fixes documentation examples where fields was incorrectly shown as an array instead of a map. The changes ensure all CLI tools (lint, doctor, validate, compile, info) correctly process both array and map-formatted metadata collections by calling normalizeStackInput() before processing raw configs.

Changes:

• CLI commands now normalize stack input before validation/processing to support map-formatted metadata
• Documentation examples corrected to show fields as map format (Record) not array format
• collectMetadataStats helper made defensive to handle both array and map formats

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
packages/cli/src/utils/format.ts	Enhanced count helper and field counting logic to handle both array and map formats defensively
packages/cli/src/commands/validate.ts	Added normalizeStackInput() call before schema validation
packages/cli/src/commands/lint.ts	Added normalizeStackInput() call before linting
packages/cli/src/commands/info.ts	Added normalizeStackInput() call before collecting stats
packages/cli/src/commands/doctor.ts	Added normalizeStackInput() call before running diagnostic checks
packages/cli/src/commands/compile.ts	Added normalizeStackInput() call before validation and compilation
content/docs/guides/common-patterns.mdx	Fixed CRUD, master-detail, approval, field-level security, and summary examples to show fields as map format
content/docs/getting-started/core-concepts.mdx	Fixed first defineStack() example to show fields as map format in both Array and Map tabs