fix(cli): os explain object documented ownership with the wrong values (#3244)

[os-zhuang]

What

os explain object documented the object ownership field as:

{name: 'ownership',type: '"own" | "extend"',description: 'Whether this object is owned or extended'}

But ObjectSchema.ownership (packages/spec/src/data/object.zod.ts:645) is the record-ownership model — z.enum(['user', 'org', 'none']). own / extend is the package contribution kind (ObjectOwnershipEnum, set via registerObject) — a distinct concept the spec explicitly calls out as separate from record-ownership. So the command printed the wrong allowed values and a misleading description.

Change

os explain object now prints:

ownership 'user' | 'org' | 'none' Record-ownership model: user (default,
injects a reassignable owner_id) | org | none (no per-record owner).
Distinct from the package own/extend contribution kind.

• packages/cli/src/commands/explain.ts — fixed the ownership catalog entry; exported SCHEMAS so it can be asserted in tests.
• packages/cli/test/commands.test.ts — regression guard pinning the documented values to the record-ownership enum, so the two concepts can't drift back together. Verified it goes red on the old "own" | "extend" value and green on the fix.
• Changeset (@objectstack/cli patch).

Verification

• os explain object run against the built CLI — output confirmed correct.
• pnpm turbo run test --filter=@objectstack/cli → 423 tests pass (incl. the new guard).
• Prove-red / prove-green cycle on the new test.
• Full tsc typecheck + eslint on the changed files → clean.

Found during the #1880 docs implementation-accuracy audit (PR #3243); was out of scope for that docs-only PR.

Closes#3244

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
spec	Building	Preview, Comment	Jul 19, 2026 4:57pm

[github-actions]

📓 Docs Drift Check

This PR changes 1 package(s): @objectstack/cli.

17 hand-written doc(s) reference the affected code and may need an implementation-accuracy re-verification:

• content/docs/ai/skills-reference.mdx(via packages/cli)
• content/docs/api/client-sdk.mdx(via @objectstack/cli)
• content/docs/api/data-flow.mdx(via @objectstack/cli)
• content/docs/api/environment-routing.mdx(via @objectstack/cli)
• content/docs/api/error-catalog.mdx(via @objectstack/cli)
• content/docs/automation/hook-bodies.mdx(via packages/cli)
• content/docs/deployment/backup-restore.mdx(via @objectstack/cli)
• content/docs/deployment/self-hosting.mdx(via @objectstack/cli)
• content/docs/getting-started/cli.mdx(via @objectstack/cli)
• content/docs/getting-started/your-first-project.mdx(via @objectstack/cli)
• content/docs/kernel/runtime-services/data-service.mdx(via packages/cli)
• content/docs/kernel/runtime-services/index.mdx(via packages/cli)
• content/docs/permissions/authentication.mdx(via @objectstack/cli)
• content/docs/plugins/packages.mdx(via @objectstack/cli)
• content/docs/protocol/kernel/plugin-spec.mdx(via @objectstack/cli)
• content/docs/protocol/kernel/realtime-protocol.mdx(via @objectstack/cli)
• content/docs/releases/implementation-status.mdx(via @objectstack/cli)

Advisory only. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs origin/main → pass the list as args.docs.