docs(objectql,cloud-connection): mark the two remaining out-of-repo app paths (#16977)

`apps/cloud` and `apps/objectos-ee` were deleted from this repository and now
live in `objectstack-ai/cloud`. Two source comments still named them as live
paths here and were in neither of the two earlier censuses.

`ObjectQLPluginOptions.skipSchemaSync`'s TSDoc is the main repair: it is an
imperative naming `apps/cloud/scripts/migrate.ts`, a script this repo does not
contain, and it is the same sentence about the same script as the
migrate-and-exit note in `packages/cli/src/commands/serve.ts`. The two were
written as a pair and only one had ever been swept, so the marker is copied
from that pair verbatim.

The `marketplace-install-local-seed-replayer` test's rationale uses the older
terse in-repo form, matching the spelling its siblings already use.

The objectql docblock is emitted into `dist/index.d.ts` and `dist/index.d.mts`,
both inside the published tarball, so it takes a patch changeset. The
cloud-connection half publishes nothing — no test file is in that tarball.


Claude-Session: https://claude.ai/code/session_01ADLdAs2pVcH17h9tZKWMBg

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

Author: os-musk

.changeset/objectql-skip-schema-sync-out-of-repo-migrate-script.md

@@ -0,0 +1,21 @@
+---
+"@objectstack/objectql": patch
+---
+
+`ObjectQLPluginOptions.skipSchemaSync`'s TSDoc no longer presents `apps/cloud/scripts/migrate.ts` as a path in this repository.
+
+The option's docblock names a concrete script as the out-of-band DDL example:
+
+```ts
+   * assume DDL is managed out-of-band (e.g. an `apps/cloud/scripts/migrate.ts`
+   * run before deploy that connects directly to the database and creates
+   * all `sys_*` + custom tables once).
+```
+
+`apps/cloud` was deleted from this repository — the reference cloud host now lives in `objectstack-ai/cloud` — so an unmarked present-tense mention sends a reader looking for a script that is not in the tree they cloned. The referent is genuine, so the sentence is marked rather than re-pointed or deleted.
+
+This ships to consumers: the docblock is emitted into `dist/index.d.ts` and `dist/index.d.mts`, both of which are in the published tarball (`files: ["dist", "README.md", "CHANGELOG.md"]`), so it is the text an IDE shows on `skipSchemaSync`.
+
+The wording is copied from `packages/cli/src/commands/serve.ts`'s migrate-and-exit note, which names the same script and was already marked — the two sentences were written as a pair and only one of them had been swept.
+
+No behaviour changes: the diff is comment text only. No exported symbol, signature, default or runtime path moves.

packages/cloud-connection/src/marketplace-install-local-seed-replayer.test.ts

@@ -13,7 +13,7 @@
 //
 // A runtime that declares no data of its own — `objects: []`, no `data`, which is
 // exactly what a marketplace-install target looks like and exactly what
-// `apps/objectos-ee` is — therefore ended up with `seed-datasets` POPULATED and
+// `apps/objectos-ee` (cloud repo) is — therefore ended up with `seed-datasets` POPULATED and
 // `seed-replayer` ABSENT. The org-scoping middleware reads both, finds the
 // datasets, finds no replayer, logs `datasets present but no replayer registered`
 // and does nothing. Every organization founded after the install boots EMPTY,

packages/objectql/src/plugin.ts

@@ -162,7 +162,8 @@ export interface ObjectQLPluginOptions {
    * Skip both `syncRegisteredSchemas()` calls inside `start()` and
    * assume DDL is managed out-of-band (e.g. an `apps/cloud/scripts/migrate.ts`
    * run before deploy that connects directly to the database and creates
-   * all `sys_*` + custom tables once).
+   * all `sys_*` + custom tables once — that script lives in the separate
+   * `objectstack-ai/cloud` repo and is NOT a path in this one).
    *
    * Use this on cold-start-sensitive runtimes (Cloudflare Containers,
    * Lambda) where the platform's inbound-request budget is shorter than