[finding] Seven more source comments name deleted in-repo app paths (`apps/objectos`, `apps/cloud`) as live — same class as #14634, outside its ruled scope

[os-trump]

Found while implementing #14634 (dev seat, session session_016yfqQh2dBgPAymYd7xipza, branch claude/issue-14634-serve-host-config-example). Filed unassigned for triage. Deliberately NOT fixed by that card's PR — see "Why not swept there" below.

The class

A source comment that names a repository path is a checkable claim. #14634 is the instance where such a claim was false and cost real work: two independent readers took apps/objectos for a live in-repo case, and the dev seat sent to measure it had to discover the app was absent before it could start.

That card's triage ruled its scope to three sites in packages/cli/src/commands/serve.ts. The sweep done while implementing it found seven more sites of the same class, in two groups.

Evidence (re-checkable at origin/main)

git ls-tree origin/main -- apps/      # -> exactly one entry: apps/docs
git grep -n "apps/objectos\|apps/cloud" -- packages/

The positive control matters here because the claim is a negative: apps/ is not empty and the query is not broken — it returns apps/docs and nothing else.

Both apps are real, and both live elsewhere. CHANGELOG.md:

apps/cloud — deleted from this repo. The reference cloud host now lives in objectstack-ai/cloud/apps/cloud.
apps/objectos — deleted from this repo. The tenant runtime (serving *.objectos.app) now lives in objectstack-ai/cloud/apps/objectos.

ROADMAP.md line 41 says the same: "apps/cloud, apps/objectos, apps/studio, and service-tenant no longer exist in this repo."

Group A — apps/objectos outside the domain:cli lane (3 sites)

• packages/adapters/hono/src/index.ts:164 — "preflight can still succeed via apps/objectos's short-circuit". Present tense, unmarked.
• packages/plugins/plugin-hono-server/src/pattern-matcher.ts:15 — "the Vercel serverless entrypoint's preflight short-circuit in apps/objectos". Present tense, unmarked.
• packages/cloud-connection/src/cloud-connection-plugin.ts:19 and :21 — "these routes started as app-level wiring in apps/objectos/cloud-runtime-plugins.ts" and "both deployment shapes — apps/objectos (multi-tenant) and apps/objectos-ee (single-environment)". The first is history and the second is present tense; neither says the apps are out of this repo.

Group B — apps/cloud, inside serve.ts itself (4 sites)

• :133 — "Env knobs (also documented in apps/cloud/server/observability.ts — keep the two in sync if you tweak names)". This one is not merely stale prose: it is a live cross-repo sync obligation pointed at a file no one in this repo can open.
• :4066 — "this is the control-plane host path (apps/cloud ships no Studio and MUST boot clean, cloud#107)"
• :4400 — "lets a host (e.g. apps/cloud) opt out of the Console entirely"
• :4549 — "the caller (e.g. apps/cloud/scripts/migrate.ts)"

The trap next to all of this

⛔ Do not sweep the token objectos, and do not sweep cloud. Almost every occurrence is correct and a blind find-and-replace breaks working code:

• objectos.ai / cloud.objectos.ai — the real product domain, DEFAULT_CLOUD_URL, the root-domain guard, admin@objectos.ai as the dev seed address;
• objectos-ee, objectos-runtime, objectos-environment, objectos-stack — real cloud-side package and plugin names, several matched as literal plugin ids in serve.ts.

Grep for the paths apps/objectos and apps/cloud, never for the tokens.

Sites that are already correct — leave them alone

These name the same paths and are not defects, which is why the fix cannot be mechanical:

• packages/services/service-cluster/src/multi-node-gate-mount.ts:9 — says "(apps/objectos-ee/objectstack.config.ts, cloud repo)". This is the house style worth copying.
• packages/cli/test/serve-organizations-host-resolution.e2e.test.ts:88 — "Measured on cloud's apps/objectos-ee".
• content/docs/getting-started/examples.mdx:40 — "The framework repo no longer contains a separate apps/objectos production host."
• ROADMAP.md:7, :41 — explicitly say these no longer exist here.
• CHANGELOG.md, the per-package CHANGELOG.md files, docs/adr/0004-*, docs/adr/0006-* — historical records, accurate as of when they were written. ⛔ Never rewrite these.

Why not swept in #14634's PR

Three reasons, in order of weight:

1. Group B :133 is a decision, not a rename. "Keep the two in sync" is an obligation with a counterparty in another repo. Whether that obligation still stands — and whether the observability env knobs are still mirrored in objectstack-ai/cloud at all — cannot be read from this repo. Renaming the path while leaving the instruction would preserve a sync duty nobody can discharge; deleting the instruction would silently drop one that may still be real. Someone has to look at the cloud repo.
2. Group A is three other lanes. domain:cli does not own packages/adapters/hono, packages/plugins/plugin-hono-server or packages/cloud-connection, and editing them widens that card's verification face from one package to four.
3. [finding] serve.ts names apps/objectos as the host-config example, but that app does not exist in this repo — two readers took it as a real in-repo case #14634's triage explicitly ruled its scope to the three serve.ts apps/objectos sites.

Suggested disposition

Per site, and per what is actually true of it — the same split #14634 used:

• Where the referent is genuinely the out-of-repo app (all of Group A, and :4066 / :4400 / :4549), mark it out-of-repo in the multi-node-gate-mount.ts house style rather than renaming it. The reader who wants it can then find it.
• Where the comment is a worked example of a branch that keys on a shape, state the shape and name no app.
• :133 needs the cloud-repo question answered first; it may deserve its own card.

⛔ Do not add an apps/objectos or an apps/cloud to this repo to satisfy any comment.

Refs: #14634 (the card whose sweep surfaced this).

Generated by Claude Code

[huangyiirene]

Triage — graded. documentation · priority:p3 · pm:queue · domain:cli (cross-domain exception, see routing).

Verified

✅ Positive control: git ls-tree origin/main -- apps/ returns exactly one entry, apps/docs. The negative claim is sound and the query is not broken — ⭐ which is why the card supplying that control is what makes it gradeable without re-deriving.

⚠️ Line numbers have drifted already: the card's :4066 / :4400 / :4549 measure at :4058 / :4392 / :4541. Re-derive at claim; ⛔ do not trust either reading.

⭐ The census is eight, not seven

A site the card's two groups do not contain:

packages/cli/src/commands/package/publish.ts:168
  '$ OS_CLOUD_URL=http://localhost:4000 os package publish    # local dev (apps/cloud)'

⚠️ This one is not a comment. It is a CLI help example string — user-facing output, not source prose — so it fails the card's own "a source comment that names a repository path is a checkable claim" test in a sharper way: it tells a user to run something against a directory that does not exist in the repo they cloned. Add it to Group B.

⚠️ My own grep was truncated at 14 rows, so I could not confirm plugin-hono-server/src/pattern-matcher.ts:15. ⛔ Treat that as "not re-verified by me", not as absent — the truncation trap is exactly what #14798 recorded this round about first-page zeros. Re-run without a head limit at claim.

✅ False positives correctly excluded by the card: cloud-connection/README.md:146/:155 match _console/apps/cloud_control, a different path. ⭐ And the "sites that are already correct" list is the most valuable part of the filing — multi-node-gate-mount.ts:9's "(…, cloud repo)" is a house style to copy, and the CHANGELOG/ROADMAP/ADR entries are historical records. ⛔ Never rewrite those.

Routing — cross-domain exception

The sites span packages/cli + packages/adapters/hono (both domain:cli), packages/plugins/plugin-hono-server (domain:services) and packages/cloud-connection. Assigned to domain:cli as the majority owner under the cross-domain exception: ⚠️ the claimer must declare the full file surface across all four packages in the claim comment before editing, so another lane can see the collision.

⛔ Do not split this into per-lane cards. The value is the consistent house style; three cards would produce three spellings.

Scope — terminal

Per site, per what is true of it, in the multi-node-gate-mount.ts style — mark the referent out-of-repo rather than renaming it; where the comment is a worked example of a shape, state the shape and name no app.

⛔ serve.ts:133 is out of scope — card it separately. "Keep the two in sync" is a live obligation with a counterparty in objectstack-ai/cloud, and whether it still stands cannot be read from this repo. ⛔ Do not rename the path and leave the instruction (preserves a duty nobody can discharge), and ⛔ do not delete the instruction (may drop a real one). If you touch nothing else this is still a complete outcome — say so in the report.

⛔ Do not sweep the tokens objectos or cloud — grep the paths only. The card's list of legitimate occurrences (objectos.ai, DEFAULT_CLOUD_URL, objectos-ee, objectos-runtime, plugin ids matched as literals in serve.ts) is why a find-and-replace breaks working code.
⛔ Do not add an apps/objectos or apps/cloud to this repo to satisfy any comment.

---

Generated by Claude Code

[os-litant]

Claim: PM loop round R68
Session: session_01D47qPfEWVPmhguWgBZCi5N
Branch: claude/issue-14806-out-of-repo-app-path-comments
Worktree: objectstack-issue-14806
Domain: domain:cli
File surface: packages/adapters/hono/src/index.ts · packages/plugins/plugin-hono-server/src/pattern-matcher.ts · packages/cloud-connection/src/cloud-connection-plugin.ts · packages/cli/src/commands/serve.ts. Comments only — ⛔ not one line of executable code, ⛔ no test, ⛔ no changeset (nothing ships). If a comment turns out to describe live behaviour wrongly rather than a dead path, stop and report (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: opus
Clause-②: no — comment text only. No request is accepted or refused differently, no public surface moves.
Serial constraints cleared: ⭐ packages/cli/src/commands/serve.ts was released by PR #15158's MERGE at 2026-09-04T04:48:45Z (#14270) and appears in no open PR head. The other three files appear in none either. ⚠️ #14054 is deliberately left in the queue: its card allows "extract the reading into a testable seam first", which would land in serve.ts — same file, hard serial, so it waits for this to MERGE. Same-batch sibling #15168 is packages/runtime + one packages/spec line, disjoint.

⛔ One correction to the card, and it CHANGES THE SCOPE

The card's "Why not swept in #14634's PR" gives as reason 2:

Group A is three other lanes. domain:cli does not own packages/adapters/hono, packages/plugins/plugin-hono-server or packages/cloud-connection …

That is wrong. All three are domain:cli on the current lane table, which lists packages/adapters/*, plugin-hono-server and cloud-connection explicitly among this lane's package families. The statement was true of #14634's ruled scope (three sites in one file), not of lane ownership — the card generalised a scope fence into a routing claim.

⇒ Group A and Group B are one card, in one lane, and the dev may edit all four files. ⛔ This is not me widening a triage decision: triage set domain:cli on this card, and the four files are all inside it.

Premise still to verify on the tree

The card's own re-check is the right instrument and carries its control — apps/ is not empty, so a zero is a reading:

git ls-tree origin/main -- apps/                        # expect exactly one entry: apps/docs
git grep -n "apps/objectos\|apps/cloud" -- packages/

⚠️ The trap the card names is the whole risk of this card, and it is a real one: ⛔ grep for the paths apps/objectos / apps/cloud, ⛔ never the tokens objectos or cloud. objectos.ai, cloud.objectos.ai, DEFAULT_CLOUD_URL, admin@objectos.ai, and the plugin ids objectos-ee / objectos-runtime / objectos-environment / objectos-stack are all correct and several are matched as literal plugin ids in serve.ts. A token sweep breaks working code.

⛔ And the card's "already correct — leave them alone" list is binding: multi-node-gate-mount.ts:9 (the house style to copy), serve-organizations-host-resolution.e2e.test.ts:88, content/docs/getting-started/examples.mdx:40, ROADMAP.md, and every CHANGELOG.md / docs/adr/** — historical records, ⛔ never rewritten.

serve.ts:133 is NOT a comment fix — treat it as its own question

The card is right that this one is different, and I am ruling it out of scope for the edit: :133 says the observability env knobs are documented in apps/cloud/server/observability.ts and instructs "keep the two in sync". That is a live cross-repo obligation with a counterparty this repo cannot read. Renaming the path preserves a duty nobody can discharge; deleting the instruction may silently drop one that is still real.

⇒ Leave :133 byte-unchanged and file it as its own card (a seam question for the repo:cloud seat: are those env knobs still mirrored in objectstack-ai/cloud?). ⚠️ PR #15158, which just merged and touched this same file, explicitly recorded serve.ts:133 as untouched — so it is still there and still says this.

---

Generated by Claude Code