Organize JSON schema output by protocol category

[Copilot]

With 325+ schemas in a flat directory, navigation was becoming unwieldy. JSON schema generation now mirrors the source protocol structure.

Changes

• Build script (scripts/build-schemas.ts): Generates schemas into category subdirectories matching namespace organization
• Directory structure: json-schema/{data,ui,system,ai,api}/ instead of flat 325-file directory
• Documentation: Added json-schema/README.md with category breakdown and usage patterns

Schema Distribution

data/    74 schemas  (Business Logic & Data Modeling)
ui/      39 schemas  (Presentation & Interaction)
system/ 112 schemas  (Runtime Configuration & Security)
ai/      86 schemas  (AI/ML Capabilities)
api/     12 schemas  (API Contracts & Envelopes)

The package.json files array already includes json-schema/, so subdirectories are automatically included in published packages.

Original prompt

协议越来越多，json schema是不是也应该按分类 build 生成

---

💬 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	Review	Updated (UTC)
spec	Ready	Preview, Comment	Jan 23, 2026 3:55pm

[github-actions]

This PR is very large. Consider breaking it into smaller PRs for easier review.

[Copilot]

Pull request overview

This PR reorganizes the JSON schema generation to output schemas into category-specific subdirectories (data/, ui/, system/, ai/, api/) instead of a flat directory structure, making the 325+ schemas easier to navigate and understand as the protocol continues to grow.

Changes:

• Modified build script to generate schemas organized by protocol namespace/category
• Created comprehensive README documentation for the json-schema directory
• Migrated all JSON schemas from flat structure to categorized subdirectories

Reviewed changes

Copilot reviewed 4 out of 328 changed files in this pull request and generated 2 comments.

File	Description
json-schema/README.md	Added comprehensive documentation explaining the new categorized structure, usage examples, and conventions
json-schema/MenuItem.json	Removed from flat directory (moved to appropriate category subdirectory)
json-schema/AuthenticationProvider.json	Removed from flat directory (moved to system/ subdirectory)
json-schema/AuthenticationConfig.json	Removed from flat directory (moved to system/ subdirectory)

[Copilot]

The TypeScript import example shows importing from '@objectstack/spec' but doesn't clarify the actual package structure. If this package publishes the json-schema directory at the package root, the import path should be verified. Consider adding a note about how the package exports these schemas or whether users should use relative paths.

Suggested change

	```typescript
	import fieldSchema from '@objectstack/spec/json-schema/data/Field.json';
	```typescript
	// If your bundler/runtime supports JSON imports and the package publishes
	// the `json-schema` directory at the package root:
	import fieldSchema from '@objectstack/spec/json-schema/data/Field.json';
	// Or, if you are working within this repository or have the schemas copied
	// locally, you can use a relative path instead:
	// import fieldSchema from '../json-schema/data/Field.json';

[Copilot]

The IDE example uses a relative path through node_modules which may not work correctly for all IDEs or project structures. Consider adding an alternative example using a $schema reference that works with published packages or providing guidance on when to use relative vs package-based paths.