Update documentation: consolidate repository URLs and fix broken links

[Copilot]

Standardized all GitHub repository references from objectql/objectui to objectstack-ai/objectui and fixed broken internal documentation links.

Changes

Repository URL Migration (18 instances)

• Root documentation: README.md, CONTRIBUTING.md
• Developer guides: 6 docs/ files, .github/copilot-instructions.md
• Package documentation: designer, vscode-extension

Package Metadata (11 packages)

• Added repository, homepage, and bugs fields to all package.json files
• Improves NPM discoverability and provides proper attribution links

Broken Link Remediation

• docs/protocol/overview.md: Removed reference to non-existent implementation-status.md
• docs/integration/api.md: Replaced 4 dead links with correct protocol references
• docs/spec/component.md: Fixed 4 links to point to existing architecture docs

Example

Before:

- [GitHub](https://github.com/objectql/objectui)
- [View Implementation Status](./implementation-status.md)

After:

- [GitHub](https://github.com/objectstack-ai/objectui)
- [Protocol Overview](../protocol/overview.md)

Original prompt

审视和更新所有的文档

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[vercel]

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

Project	Deployment	Review	Updated (UTC)
objectui-docs	Error		Jan 17, 2026 11:04am

[github-actions]

📦 Bundle Size Report

Package	Size	Gzipped
components (index.js)	1494.76KB	349.01KB
core (index.js)	0.27KB	0.14KB
data-objectql (ObjectQLDataSource.js)	12.31KB	2.87KB
data-objectql (hooks.js)	5.43KB	1.32KB
data-objectql (index.js)	0.42KB	0.26KB
designer (index.js)	1.27KB	0.40KB
plugin-charts (AdvancedChartImpl-LUnT2ZAf.js)	74.89KB	15.82KB
plugin-charts (BarChart-CRc8MAtI.js)	551.60KB	127.51KB
plugin-charts (ChartImpl-DiqV9Evl.js)	3.17KB	1.10KB
plugin-charts (index-BcjHuFVN.js)	24.05KB	7.06KB
plugin-charts (index.js)	0.21KB	0.16KB
plugin-editor (MonacoImpl-BSiaJCGx.js)	18.15KB	5.59KB
plugin-editor (index-Bx39x2XN.js)	21.72KB	6.53KB
plugin-editor (index.js)	0.19KB	0.15KB
plugin-kanban (KanbanImpl-mGLdSHcd.js)	76.50KB	20.46KB
plugin-kanban (index-i_5clVsp.js)	23.51KB	6.90KB
plugin-kanban (index.js)	0.18KB	0.15KB
plugin-markdown (MarkdownImpl-Dp8rFxgw.js)	256.79KB	64.50KB
plugin-markdown (index-DDihmVdn.js)	21.25KB	6.37KB
plugin-markdown (index.js)	0.19KB	0.15KB
react (SchemaRenderer.js)	1.25KB	0.62KB
react (index.js)	0.13KB	0.11KB
react (index.test.js)	0.14KB	0.14KB
types (api-types.js)	0.24KB	0.19KB
types (app.js)	0.19KB	0.17KB
types (base.js)	0.24KB	0.19KB
types (complex.js)	0.17KB	0.16KB
types (crud.js)	0.24KB	0.20KB
types (data-display.js)	0.19KB	0.17KB
types (data.js)	0.23KB	0.18KB
types (disclosure.js)	0.18KB	0.17KB
types (feedback.js)	0.18KB	0.16KB
types (form.js)	0.17KB	0.16KB
types (index.js)	1.46KB	0.74KB
types (layout.js)	0.23KB	0.18KB
types (navigation.js)	0.17KB	0.16KB
types (objectql.js)	0.26KB	0.21KB
types (overlay.js)	0.18KB	0.16KB
types (registry.js)	0.01KB	0.04KB

Size Limits

• ✅ Core packages should be < 50KB gzipped
• ✅ Component packages should be < 100KB gzipped
• ⚠️ Plugin packages should be < 150KB gzipped

[github-actions]

✅ All checks passed!

• ✅ Type check passed
• ✅ Tests passed
• ✅ Lint check completed

[hotlong]

重构vitepress首页这是一个为您精心设计的 AI 指令（Prompt），专门用于生成 ObjectUI 官网首页 (objectui.org) 的核心内容。
ObjectUI 的定位比较独特：它既要吸引那些喜欢 React + Tailwind + Shadcn 现代技术栈的前端开发者，又要向架构师兜售 Server-Driven UI (SDUI) 的高级理念。
这个指令旨在平衡这两者，强调“用你喜欢的现代技术，但以更高效的协议驱动方式工作”。
请将以下内容复制并发送给您的 AI 助手：
🎨 指令：ObjectUI 官网首页内容生成
Context (Role & Goal):
Act as the Lead Frontend Architect & Product Designer for ObjectUI. Your task is to write the compelling copy and structure for the objectui.org homepage.
Your audience is Frontend Developers, UI/UX Engineers, and Full-Stack Architects. They love modern tech (React, Tailwind, Shadcn UI) but hate writing repetitive boilerplate code for enterprise forms, data tables, and dashboards.
YOUR GOAL: Convince them that ObjectUI is not a restrictive "low-code" tool, but a professional Server-Driven UI Engine that gives them the speed of configuration with the flexibility of code.
Core Narrative (The "Hook"):

• The Pain: "Frontend development for enterprise apps is repetitive. You spend 80% of your time gluing together form libraries, data tables, and validation logic."
• The Solution: "ObjectUI turns UI into Data. Define your interface in standard JSON, and let our engine render pixel-perfect, accessible React + Tailwind components."
  Tone & Voice:
• Design-Conscious Techie: Professional, clean, appreciative of good aesthetics (Shadcn style).
• Confident & Efficient: Focus on speed, standardization, and scalability.
• No "No-Code" Hype: Avoid sounding like a tool for non-developers. This is a tool for pros who want to move faster.
  Task: Generate the Homepage Content (Markdown)
  Please write the homepage content covering the following 6 sections:

1. The Hero Section (The Value Prop)

• Headline: A punchy statement about "Server-Driven UI" or "Stop Hand-Coding UIs".
• Sub-headline: Mention the key stack: React, Tailwind, Shadcn, and JSON Protocol. Emphasize building complex apps faster.
• CTA Buttons: "Read the Spec" and "View Component Gallery".

2. The "Magic Trick" Section (Visual Proof)

• This needs to be a side-by-side comparison concept.
• Left Side (Input): A clean JSON Schema example defining a complex component (e.g., a Data Table with sorting and an action button).
• Right Side (Output): A description of the rendered, beautiful Shadcn UI component.
• Caption: "You define the intent (JSON). We render the reality (React)."

3. Why ObjectUI? (The 3 Pillars)
   Write 3 feature cards targeted at modern frontend devs:

• Card 1: The Stack You Love. Emphasize that it's built on React, Radix primitives (Shadcn), and native Tailwind CSS. It's not a black box; you can override styles with utility classes.
• Card 2: Server-Driven Agility. Explain the value of SDUI: update layout, fields, and validation instantly from the backend without redeploying frontend code.
• Card 3: Enterprise Ready-Made. Mention built-in support for complex patterns like Kanbans, Gantt charts, and multi-step forms, so they don't have to build them from scratch.

4. The Architecture (How it Works)
   A brief, simplified explanation of the flow:

• Step 1: The Protocol. (JSON Schema defines the view).
• Step 2: The Engine. (ObjectUI Core processes state and logic).
• Step 3: The Renderer. (React maps JSON nodes to Shadcn components).

5. "Not Just a Toy" (Extensibility)
   Address the fear of being locked in.

• Explain that developers can register their own custom React components into the engine and use them in the JSON schema. They are not limited to the built-in set.

6. Part of ObjectStack (The Ecosystem)
   A small section at the bottom linking it to the bigger picture.

• Mention that while it works standalone with any REST API, it pairs perfectly with ObjectQL for an end-to-end protocol-driven experience.
  Output Requirement:
• Use clean Markdown formatting.
• Use code blocks for the JSON examples in Section 2.
• Keep the tone energetic but professional.
  💡 这个指令的设计巧思：
• 精准的画像定位：
  • 我特别强调了受众是喜欢 "React + Tailwind + Shadcn" 的开发者。这意味着文案不能带有“低代码/无代码”的廉价感，而必须体现出对现代前端工程化的尊重。
• "Magic Trick" (视觉证明)：
  • 就像 ObjectQL 官网要展示 "YAML vs SQL" 一样，ObjectUI 官网必须展示 "JSON vs UI"。这是最能体现 Server-Driven UI 价值的时刻。
• 解决信任危机 (Extensibility)：
  • 前端开发者最怕用这种框架被“锁死”，导致无法实现特殊需求。所以第 5 部分专门要求强调**“可扩展性”**（你可以注册自己的 React 组件），这能极大降低开发者的抵触心理。
• 强调 Shadcn/Tailwind Native：
  • 这两个是目前前端圈的顶流技术。强调 ObjectUI 是基于它们构建的，等于告诉开发者：“生成的界面不仅不丑，而且是你最喜欢的那种风格，并且你可以用你熟悉的 tailwind 类名去修改它。”

[Copilot]

Pull request overview

This PR consolidates the repository organization name from objectql/objectui to objectstack-ai/objectui across all documentation and package metadata, while fixing broken internal documentation links.

Changes:

• Standardized 18 repository URL references across root docs, developer guides, and package documentation
• Added NPM metadata fields (repository, homepage, bugs) to 11 packages for improved discoverability
• Fixed broken documentation links by replacing references to non-existent files with correct protocol references

Reviewed changes

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

Show a summary per file

File	Description
packages/*/package.json (11 files)	Added repository, homepage, and bugs metadata fields with consistent URLs
README.md	Updated 4 GitHub repository URL references
CONTRIBUTING.md	Updated upstream remote URL
.github/copilot-instructions.md	Updated repository reference in system prompt
docs/ROADMAP.md	Updated 3 GitHub repository URLs
docs/README.md	Updated GitHub Discussions and Issues URLs
docs/guide/introduction.md	Updated GitHub repository URL
docs/api/*.md (3 files)	Updated GitHub repository URLs in references
docs/protocol/overview.md	Removed non-existent implementation-status.md reference and updated 3 GitHub URLs
docs/integration/api.md	Replaced 4 broken links with correct references to existing protocol docs
docs/spec/component.md	Fixed 4 links to point to existing architecture documentation
packages/designer/TOUCH_DRAG_GUIDE.md	Updated GitHub Issues URL