[Decision] Official connector-app listing identity before the first publish: app.objectstack.connector-<vendor> as the package id, <vendor> as the namespace, @objectstack/connector-app-<vendor> as the private npm name #28313

epic:#27293#1 · sunhaolin · session_017xRBcVBKAFk1ntXSjvPt7U

Filing gate: ② a decision only the maintainer takes — a public identifier that can never change once published. Raised by the #28276 dev (open_questions[1], PR #28306). Child of #27293 (E4). ⛔ Not a claim. Nothing is published until the cloud pipeline (#28278) runs, so this card blocks no merge; it must be ruled before the first os package publish.

维护者速读

• 改了什么：不改代码。首个官方连接器应用（GitHub，PR feat(apps): connector-github, GitHub's remote MCP server as an open-edition connector app (E4 batch 1, GitHub half) #28306）上架前，要定下官方连接器应用的「身份」命名规则：包 id、命名空间、npm 包名。
• 为什么改：包 id（manifestId）一旦发布就永远不能改（上架手册：content/docs/deployment/marketplace-handbook.mdx:34「reverse-domain, immutable once published」），每个后续官方连接器都会照这个规则起名；这是对外的品牌与标识，席位不代定。
• 风险与回滚：发布之前改名零成本；发布之后改不了。
• 先看：下面「选项」表。
• 两分钟验证：看 PR feat(apps): connector-github, GitHub's remote MCP server as an open-edition connector app (E4 batch 1, GitHub half) #28306 里 packages/apps/connector-github/objectstack.manifest.json 与 package.json 的前几行。
• 需要你做的：选 A 或 B（B 请直接写出规则）。

Options

四维分析

os-decision-facets

• ① 项目长远合理性：20–30 个官方连接器会沿用同一规则；A 与已有官方应用 app.objectstack.hotcrm 同前缀，并把「执行器包」（connector-mcp）和「连接器应用」（connector-app-github）分开命名，避免一个名字指两种东西。
• ② 实际业务拉动：首个应用已写好，等的就是这条规则；发布前改名零成本。
• ③ 防 AI 犯错：规则写死在一处，写下一个应用的 agent 照抄即可；A 的 npm 名与执行器包不冲突，agent 不会把应用当执行器依赖。
• ④ 创业阶段不扩散：两选项都不加代码或门禁。
  Prior rulings read: manifestId, listing id, package id, namespace → handbook :34 (immutable once published); no ruling on official-app naming; thread: connector apps, E4 batch 1 (static key): GitHub over its remote MCP server and Stripe read over its OpenAPI document, as open-edition metadata packages validated by this repository's CI #28276 report; repo: objectstack-ai/objectstack

Recommendation

A, because it matches the one existing official listing and keeps the executor and app names apart. Confidence gap: whether "official" listings should carry a distinct prefix from future partner listings (for example app.objectstack. vs app.<partner>.) is a marketplace policy this repository does not record.

Self-check: 只看①选 A；②③④ 是否翻转：否。

After the ruling

• A: PR feat(apps): connector-github, GitHub's remote MCP server as an open-edition connector app (E4 batch 1, GitHub half) #28306 lands as is; every later connector app follows the rule; the handbook's listing section gains one line naming it.
• B: the epic PM rewrites the three identifiers on PR feat(apps): connector-github, GitHub's remote MCP server as an open-edition connector app (E4 batch 1, GitHub half) #28306 before it lands (nothing is published yet).