docs(spec): restore the historical table name in the ADR-0006 rename sentence (#13684)

* docs(spec): restore the historical table name in the ADR-0006 rename sentence

The sentence documenting the ADR-0006 v4 rename read `sys_environment` was
renamed to `sys_environment` — a table renamed to itself. A mechanical
project -> environment sweep had rewritten the *historical* name inside the
very sentence whose job is to carry it, destroying the one fact the sentence
exists to record.

The source name is `sys_project`, corroborated at packages/metadata/CHANGELOG.md
(`sys_project` -> `sys_environment`, platform-objects object renames) and by
ADR-0006 v4 itself.

Fixed at the producer: content/docs/references/cloud/environment.mdx is
generated from the doc comment in packages/spec/src/cloud/environment.zod.ts
by build-docs.ts, so the .mdx is regenerated rather than hand-edited.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Pk26oZ12t5N1hwGW1m1MgC

* docs(spec): add changeset for the ADR-0006 rename-sentence fix

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Pk26oZ12t5N1hwGW1m1MgC

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: os-project-manager

.changeset/environment-rename-sentence-historical-name.md

@@ -0,0 +1,29 @@
+---
+"@objectstack/spec": patch
+---
+
+docs(spec): restore the historical table name in the ADR-0006 rename sentence (#12485)
+
+The Environment protocol's module doc comment — and therefore the generated
+page at `content/docs/references/cloud/environment.mdx` — claimed that
+`sys_environment` was renamed to `sys_environment`: a table renamed to itself.
+The sentence is not merely stale, it is self-refuting, and it destroyed the one
+fact it exists to carry, for the reader who consults it precisely because they
+are confused about the rename.
+
+The historical name is `sys_project`, corroborated by `packages/metadata`'s
+changelog entry for the platform-objects object renames (`sys_project` →
+`sys_environment`, alongside `sys_project_member` and `sys_project_credential`)
+and by ADR-0006 v4 itself.
+
+Cause, which generalises past this one line: a mechanical `project` →
+`environment` sweep rewrote the *historical* name inside the very sentence
+documenting the rename. A sweep that cannot distinguish "the name we use now"
+from "the name we used to use" will always corrupt exactly the prose that
+explains a rename. **In a sentence that documents a rename, the old name is the
+payload — it is not drift, and it must never be "consistency-fixed".**
+
+Fixed at the producer: the `.mdx` under `content/docs/references/` is generated
+from the spec source by `build-docs.ts` and pinned by `check:docs`, so the doc
+comment in `packages/spec/src/cloud/environment.zod.ts` is the fix site and the
+page is regenerated.

content/docs/references/cloud/environment.mdx

@@ -17,7 +17,7 @@ This file defines the Control-Plane schemas for the `sys_environment`,
 data lives in each environment's own database — those data-plane DBs hold
 no system tables.
 
-See ADR-0006 v4: `sys_environment` was renamed to `sys_environment`; the
+See ADR-0006 v4: `sys_project` 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
 a per-org `manifest_id` (see ADR-0003), so a single package + version

packages/spec/src/cloud/environment.zod.ts

@@ -17,7 +17,7 @@ import { lazySchema } from '../shared/lazy-schema';
  * data lives in each environment's own database — those data-plane DBs hold
  * no system tables.
  *
- * See ADR-0006 v4: `sys_environment` was renamed to `sys_environment`; the
+ * See ADR-0006 v4: `sys_project` 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
  * a per-org `manifest_id` (see ADR-0003), so a single package + version