fix(spec): attribute the cloud registration reading to its filer

The list's header already says this half of the contract cannot be
conformance-tested from this repository. The pin comment and the changeset
stated the cloud registration chain as though this change had re-taken it;
they now name it as a reading carried on the filer's name, at the cloud ref
it was taken against, and say plainly that only the objectstack half is
asserted here.

Claude-Session: https://claude.ai/code/session_01JbZnqu8bt6YqfJsr9vaFb3
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/spec-cloud-provided-environment-credential.md

@@ -15,12 +15,15 @@ an action parameter `reference`, a field `reference`, a dashboard
 `objects.<name>` subtree naming `sys_environment_credential` all stop being
 diagnosed.
 
-Why this name: `@objectstack/service-tenant` registers it in the cloud
-repository on exactly the path the list's existing `sys_package`,
-`sys_package_version` and `sys_package_installation` members take —
-`objects/sys-environment-credential.object.ts` exported through
+Why this name: as read in the cloud repository at `cb8ee7ff60`,
+`@objectstack/service-tenant` registers it on exactly the path the list's
+existing `sys_package`, `sys_package_version` and `sys_package_installation`
+members take — `objects/sys-environment-credential.object.ts` exported through
 `objects/index.ts`, listed in `tenantObjects`, spread into
-`manifestService.register({ objects })` by `tenant-plugin.ts`.
+`manifestService.register({ objects })` by `tenant-plugin.ts`. That reading is
+the cloud repository's and is carried here on its filer's name; per this list's
+header it cannot be conformance-tested from this repo, and this change does not
+claim to have re-taken it.
 
 Unlike the earlier additions, this one fixes no diagnostic that fires today: no
 `*.object.ts` in this repository references the name, so nothing shipped was

packages/spec/src/system/constants/platform-object-names.test.ts

@@ -186,8 +186,12 @@ describe('platform-object predicates', () => {
   });
 
   it('resolves the tenant credential store the cloud runtime registers', () => {
-    // `sys_environment_credential` is registered by `@objectstack/service-tenant`
-    // on the same path as the `sys_package*` family above: declared in
+    // The cloud-side registration is a READING TAKEN IN THE CLOUD REPOSITORY,
+    // at `cb8ee7ff60`, and carried here on its filer's name — like every other
+    // member of this list, it is not re-checkable from this repo, which is what
+    // the list's own header means by "they cannot be conformance-tested from
+    // this repo". As read there, `@objectstack/service-tenant` registers the
+    // name on the same path as the `sys_package*` family above: declared in
     // `objects/sys-environment-credential.object.ts`, exported through
     // `objects/index.ts`, listed in `tenantObjects` in `manifest.ts`, and spread
     // into `manifestService.register({ objects })` by `tenant-plugin.ts`.
@@ -202,9 +206,9 @@ describe('platform-object predicates', () => {
     // So the first author to write the reference would have been told it looked
     // like a typo. Pinned by name, beside `sys_license` and the package family,
     // for the same reason: dropping it fails one readable assertion instead of
-    // nothing. The other half of the contract — that the cloud runtime really
-    // registers the table — is owned by the cloud repository per the list's
-    // header, and is not asserted here.
+    // nothing. What this test asserts is the objectstack half alone — that the
+    // list carries the name and the predicate resolves it. The cloud half is
+    // owned by the cloud repository and is not asserted here.
     expect(isPlatformProvidedObjectName('sys_environment_credential')).toBe(true);
     expect(CLOUD_PROVIDED_OBJECT_NAMES).toContain('sys_environment_credential');
   });