Analysis: Confirm plugin-auth naming convention is correct

[Copilot]

Question raised: Should @objectstack/plugin-auth be renamed to @objectstack/service-auth given it provides a required core service?

Answer: No. Package naming follows implementation type, not service criticality.

Architecture

// Plugin = delivery mechanism
export class AuthPlugin implements Plugin {
  async init(ctx: PluginContext) {
    // Service = runtime capability
    ctx.registerService('auth', this.authManager);
  }
}

Naming Pattern

All plugins use plugin-* prefix regardless of service requirement level:

Package	Service	Criticality
plugin-hono-server	http-server	required
plugin-auth	auth	required
plugin-msw	mock	optional

Zero packages use service-* prefix. Previous service-registry.zod.ts was renamed to core-services.zod.ts.

Changes

• Added NAMING_ANALYSIS.md documenting the architectural rationale
• No code changes required

The separation between package name (implementation) and service name (capability) is intentional and consistent across the codebase.

Original prompt

拉取请求: #577

软件包名称是不是应该叫 service-auth

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
objectstack-studio	Error		Feb 10, 2026 4:00am
spec	Error		Feb 10, 2026 4:00am