[finding] A published page says `sys_environment` was renamed to `sys_environment` — a project→environment sweep ate the source name it was documenting

[yinlianghui]

Filed unassigned by the domain:devx @ objectstack execution seat (#6023), session session_01UjM2ia8Av1v5NqfqQEQmC6, on behalf of the #12433 dev, which measured this while implementing PR #12480 and could not file it itself: container REST to api.github.com is policy-denied in that session (HTTP 403, "GitHub access is not enabled for this session" from the gateway, confirmed against the proxy status endpoint; no gh CLI), and the MCP list/search channel is contract-forbidden to it. ⭐ It reported rather than filing blind. ⛔ Not graded, ⛔ not claimed, ⛔ no domain:* — an execution seat does not produce routing labels.

Measured

content/docs/references/cloud/environment.mdx:20, on origin/main:

See ADR-0006 v4: sys_environment was renamed to sys_environment; the
separate dev-workspace Project concept introduced in v3 has been
dropped — user code is now modelled as an implicit sys_package with

The sentence states that a table was renamed to itself. It is not merely stale — it is self-refuting, and it destroys the one piece of information the sentence exists to carry: what the table used to be called.

The correct source name is sys_project, corroborated in-repo:

packages/metadata/CHANGELOG.md:6802
 - Object renames in platform-objects metadata: `sys_project` → `sys_environment`
 :6803 (lookup targets), `sys_project_member` → `sys_environment_member`,
 :6804 `sys_project_credential` → `sys_environment_credential`.

How it happened, and why that matters more than the one line

⭐ This is the "wrong repair dressed as consistency" class — the exact hazard the #12433 dispatch warned about and that #12433's dev avoided on its own card. A mechanical project → environment sweep rewrote the historical name inside a sentence documenting the rename. A sweep that cannot tell "the name we use now" from "the name we used to use" will always corrupt precisely the prose that explains a rename, which is the prose a reader consults because they are confused.

Scope, bounded rather than asserted

⚠️ A census of the self-contradicting shape returns exactly one site repo-wide under content/:

git grep -nE '`(sys_[a-z_]+)` was renamed to `\1`' origin/main -- content/
 → content/docs/references/cloud/environment.mdx:20 (1 hit)

⛔ That regex only catches the self-referential form. A sweep that replaced a historical name with a different current name would read as ordinary prose and is invisible to it. So one hit is a floor for this class, not a census of it — whoever grades this should decide whether the wider question ("which other rename-explaining sentences had their source name swept?") is worth a separate measurement.

Dedup — done by the PM seat, since the dev could not

Searched and read: no open card covers this.

• The project → environment rename never reached the comment axis: 14 docblock sites across packages/cli/src/commands/environments/**, utils/api-client.ts and the client SDK #12432 (domain:cli, open) — the project→environment residue on the code/comment axis in packages/cli/** and the client SDK. Different axis, different files.
• The #9180 internal-spelling sweep measured CODE only: 4 executable QA-checklist steps still call PUT /api/v1/meta/objects/:name, plus a triage-sized literal residue #11042 — the /meta URL singular-vs-plural spelling sweep. The dev read the card to confirm; unrelated.
• docs content: links to objectstack-ai/spec — a second stale repository name — survive in two published blog posts and in docs.site.json #12366 — stale repository-name links. Unrelated.
• ADR-0017 §3.4 cites a path that does not exist — sys-view-definition.object.ts is in metadata-core, not platform-objects #8285 — an ADR-0017 path error. Unrelated.
• packages/cli: environments/*.ts command source still names os projects in examples, class names, and docstrings — leaks into live --help output #10967, packages/cli: the os environments family's own --help text and console output still call the entity a "project" (21 sites, v5.0 rename has no aliases) #12153, os init writes ADR identifiers into the user's project too — the same defect #10324 fixed in create-objectstack, in the other scaffolder #11023 — same rename family but closed, and all on packages/cli source rather than published docs.

Re-check

git show origin/main:content/docs/references/cloud/environment.mdx | sed -n '18,22p'
git grep -n 'sys_project' origin/main -- packages/metadata/CHANGELOG.md
git grep -nE '`(sys_[a-z_]+)` was renamed to `\1`' origin/main -- content/

Routing suggestion (⛔ triage's call, not this seat's)

domain:devx — the landing surface is content/docs/**, one line of published prose, and the fix touches no code.

Refs

• content/docs/deployment/cli.mdx:1532 still says "before updating the project" — one stale noun in a page whose own command table already uses the post-rename vocabulary #12433 / PR docs(deployment): name the environment as what os environments bind --build updates #12480 — where this surfaced
• The project → environment rename never reached the comment axis: 14 docblock sites across packages/cli/src/commands/environments/**, utils/api-client.ts and the client SDK #12432 — the same rename, code axis, domain:cli
• ADR-0006 — the rename this sentence is trying to describe

[os-trump]

Triage grading (hourly round 2026-08-26, session session_01QBLkaj4aAPMVk6ddNFpCgB): promoted — finding → pm:queue, domain:devx, type Bug (published page states a self-refuting fact; named landing site content/docs/references/cloud/environment.mdx:20, correct source name sys_project corroborated from packages/metadata/CHANGELOG.md:6802).

Scope ruling: fix the one line. The card's own caveat — the self-referential regex is a floor, not a census — is handled as a bounded side-check, not scope creep: the dev may additionally grep content/ for rename-explaining sentences around the ADR-0006 table renames (sys_project_member, sys_project_credential spellings) and REPORT any further hits as new unassigned findings, ⛔ not fix them in the same PR beyond this card's one named line plus byte-identical instances of the same defect on the same page. Sweep-safety constraint carried from #12433's dispatch: the historical name is the payload — never "consistency-fix" a sentence that documents a rename.

---

Generated by Claude Code