docs(runtime): retire the dead objectui-lockstep rename promise in packages.ts

[hotlong]

Fixes#7578

What

Comment-only reword at packages/runtime/src/domains/packages.ts (the block documenting why the publish-drafts response keeps the unhiddenApps / unhideError wire-field spelling). The old text promised: "The rename rides the objectui follow-up card, together."

That follow-up card was #6955. Its dev measured the rename out rather than in: the server still emits the old names (unchanged emit sites — not touched by this PR) and objectui reads neither field anywhere (zero grep hits repo-wide). Under the card's own "rename in lockstep, or not at all" rule, the resolution was not at all — PM-ratified as option A: a rename of a zero-reader diagnostic payload buys no capability (startup-scope discipline).

The comment now records that settled state instead of pointing the next reader at work that will never arrive: the spellings are kept deliberately and permanently, cites #6955 for the measurement + ruling, and notes the option-B escape hatch (a standalone producer-side rename card) for anyone who later wants the vocabulary tidy on its own merits.

Scope proof

One file, one hunk, comment-only:

$ git diff --stat
packages/runtime/src/domains/packages.ts | 19 ++++++++++++++-----
1 file changed, 14 insertions(+), 5 deletions(-)

Zero behaviour change. The three emit sites the card called out as off-limits (unhideError assignment, unhiddenApps assignment, the metadata:reloaded announce read) are untouched — confirmed by diff review, not just by not editing them.

Tests

• node scripts/check-nul-bytes.mjs — OK (7230 files scanned).
• pnpm check:changeset-gate-self-tests — green (empty-changeset, ADR-0087 registration, changeset-no-major self-tests).
• pnpm check:route-envelope — green (9 route modules audited, no regression).
• pnpm --filter '@objectstack/runtime^...' build then pnpm --filter '@objectstack/runtime' build — green (build closure first, per AGENTS.md [skill] 新 worktree 里第一次验证之前必须先 build 依赖闭包 —— AGENTS.md §9 的陈旧产物陷阱当日连咬三个 dev（假红 + 假绿两个方向） #6371).
• pnpm --filter '@objectstack/runtime' typecheck — green, no errors.
• pnpm --filter '@objectstack/runtime' test — 137 test files, 2086 tests, all passed (includes packages-capability-gate.test.ts, packages-uninstall-envelope.test.ts, packages-readonly-gate.test.ts).

No new tests: comment-only diff has no observable behaviour to test.

Changeset

skip-changeset label applied — comment-only diff releases nothing.

---

Generated by Claude Code

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
objectstack	Ignored		Aug 12, 2026 3:32am

[github-actions]

📓 Docs Drift Check

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

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

• content/docs/api/client-sdk.mdx(via packages/runtime)
• content/docs/api/index.mdx(via @objectstack/runtime)
• content/docs/api/wire-format.mdx(via @objectstack/runtime)
• content/docs/automation/hook-bodies.mdx(via @objectstack/runtime)
• content/docs/concepts/metadata-lifecycle.mdx(via @objectstack/runtime)
• content/docs/concepts/north-star.mdx(via packages/runtime)
• content/docs/data-modeling/drivers.mdx(via @objectstack/runtime)
• content/docs/deployment/index.mdx(via @objectstack/runtime)
• content/docs/deployment/production-readiness.mdx(via @objectstack/runtime)
• content/docs/deployment/single-project-mode.mdx(via @objectstack/runtime)
• content/docs/deployment/vercel.mdx(via @objectstack/runtime)
• content/docs/getting-started/your-first-project.mdx(via @objectstack/runtime)
• content/docs/kernel/cluster.mdx(via @objectstack/runtime)
• content/docs/permissions/authentication.mdx(via @objectstack/runtime)
• content/docs/permissions/authorization.mdx(via packages/runtime)
• content/docs/permissions/system-context.mdx(via packages/runtime)
• content/docs/plugins/packages.mdx(via @objectstack/runtime)
• content/docs/protocol/kernel/http-protocol.mdx(via @objectstack/runtime)
• content/docs/protocol/kernel/index.mdx(via @objectstack/runtime)
• content/docs/protocol/kernel/lifecycle.mdx(via @objectstack/runtime)

⛔ 2 release-owned page(s) also reference the affected code. These are read-only:

• content/docs/releases/implementation-status.mdx(via @objectstack/runtime)
• content/docs/releases/v17.mdx(via @objectstack/runtime)

content/docs/releases/ is RELEASE-OWNED (AGENTS.md "Documentation Guardrails"): release
notes are written centrally at release time, and a code PR that edits them is the exact PR
that guardrail exists to stop. They are still audited — read-only. If one of them is actually
wrong, file an issue or open a dedicated docs-only PR; do not edit it here.

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.