refactor: rename service references arcadia-app → arcadia-core

The Phoenix auth/identity/tenancy backend repo is being renamed
arcadia-app → arcadia-core (its primary OTP app is already arcadia_core).
Updates prose, doc paths, and git.sky-ai.com repo URLs. Deliberately
leaves the Rust crate arcadia-app-client and host arcadia-app.internal
(handled separately), and the kept namespace (issuer/release "arcadia").

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

app/lib/admin-tools.ts

@@ -53,7 +53,7 @@ const docsClient = createRAGClient("/docs-index.json")
 //      tooling and wire it through `.env.local`.
 //   3. operator session JWT — works only when arcadia-search shares the
 //      JWT signing secret with the arcadia issuing the operator's session
-//      (i.e. local arcadia-app + local arcadia-search with matching keys).
+//      (i.e. local arcadia-core + local arcadia-search with matching keys).
 //   4. "dev" literal — only accepted by AUTH_MODE=dev backends.
 function readEnv(key: string): string | undefined {
   if (typeof import.meta === "undefined") return undefined
@@ -667,7 +667,7 @@ const TOOLS: ToolDef<ToolCtx>[] = [
   {
     name: "search_docs",
     description:
-      "Search the arcadia-app documentation (architecture, API surface, deploy/setup guides) for passages relevant to a question. Use this for conceptual or procedural questions where the live API tools won't help — e.g. 'how does multi-tenant isolation work', 'how do I deploy to production', 'what is the modular monolith pattern'. Returns up to `limit` ranked passages with title, sourcePath, and excerpt. Cite results by sourcePath in your reply.",
+      "Search the arcadia-core documentation (architecture, API surface, deploy/setup guides) for passages relevant to a question. Use this for conceptual or procedural questions where the live API tools won't help — e.g. 'how does multi-tenant isolation work', 'how do I deploy to production', 'what is the modular monolith pattern'. Returns up to `limit` ranked passages with title, sourcePath, and excerpt. Cite results by sourcePath in your reply.",
     parameters: {
       type: "object",
       properties: {
@@ -715,7 +715,7 @@ const TOOLS: ToolDef<ToolCtx>[] = [
   {
     name: "search_kb",
     description:
-      "Lexical (BM25) search over the arcadia-search Tantivy backend. Returns chunks with snippets + chunk_ids that can be passed to `read_chunk` to expand. Prefer this over `search_docs` (browser) when you need richer hits or when the content wouldn't be in the bundled docs.\n\nKnown corpora on the platform-admin tenant:\n- `docs` — arcadia-app architecture/ops docs (same as the browser RAG, server-hosted for parity).\n- `operator-tools` — arcadia-search + arcadia-admin documentation (admin sidecar, deploy script, search admin UI, MULTI_TENANT, RAG, AI_FIRST, LIBS, LLM_PROXY_CONTRACT).\n- `files` — markdown/text files uploaded by tenant users via arcadia-app.\n\nIf you're not sure what's available, call `list_search_corpora` first. Operators can add new corpora via the `/search` route.",
+      "Lexical (BM25) search over the arcadia-search Tantivy backend. Returns chunks with snippets + chunk_ids that can be passed to `read_chunk` to expand. Prefer this over `search_docs` (browser) when you need richer hits or when the content wouldn't be in the bundled docs.\n\nKnown corpora on the platform-admin tenant:\n- `docs` — arcadia-core architecture/ops docs (same as the browser RAG, server-hosted for parity).\n- `operator-tools` — arcadia-search + arcadia-admin documentation (admin sidecar, deploy script, search admin UI, MULTI_TENANT, RAG, AI_FIRST, LIBS, LLM_PROXY_CONTRACT).\n- `files` — markdown/text files uploaded by tenant users via arcadia-core.\n\nIf you're not sure what's available, call `list_search_corpora` first. Operators can add new corpora via the `/search` route.",
     parameters: {
       type: "object",
       properties: {

app/lib/arcadia-knowledge.ts

@@ -1,5 +1,5 @@
 // Domain primer baked into the assistant's system prompt so it understands
-// what arcadia-app is, what platform admins do, and how the data model fits
+// what arcadia-core is, what platform admins do, and how the data model fits
 // together. Keep this tight — it costs context tokens on every turn.
 
 export const ARCADIA_KNOWLEDGE = `Arcadia (the backend you administer):
@@ -31,7 +31,7 @@ Things to keep in mind when assisting:
 - Writes are auditable. Suggest the user double-check tenant slug and impact before suspend/deactivate. Deactivate is harsher than suspend — only use when clearly intended.
 - The operator can impersonate tenant users for debugging (POST /api/v1/admin/impersonate/:user_id) — surface this when they ask "why can't user X log in".
 - Quotas / rate cards / billing config errors usually surface as 402/403 from /api/v1 endpoints — diagnose by checking the tenant's billing-config and api-metering quotas.
-- The reference Phoenix app lives at \`reference/arcadia-app/\` in the workspace; its OpenAPI spec is at /api/openapi (sync via \`node ../lib-arcadia-core-client/scripts/sync-spec.mjs\`).
+- The reference Phoenix app lives at \`reference/arcadia-core/\` in the workspace; its OpenAPI spec is at /api/openapi (sync via \`node ../lib-arcadia-core-client/scripts/sync-spec.mjs\`).
 - Search admin (arcadia-search) is a separate service. Manage tenants/corpora at \`/search\`. Use \`list_search_corpora\` if you don't know what's indexed; \`rebuild_search_corpus\` after uploads or when results look stale; \`search_kb\` / \`read_chunk\` to query.
 
 When the user asks something that maps to a tool, call it. When they ask about a concept, explain it from this primer in plain language. Write tools (suspend_tenant, activate_tenant) prompt the operator with an inline confirm card before they actually run — you do not need to ask in prose first; just call the tool and the user will see the confirmation UI. If the user denies a write, do not retry it; ask what they'd like to do differently.

app/lib/arcadia/health.ts

@@ -2,7 +2,7 @@
 //
 // Backed by /api/v1/health* (public — no auth). Each subsystem is probed
 // independently; the overall endpoint aggregates and returns 503 if any
-// subsystem is not "ok". See arcadia-app commit f427892.
+// subsystem is not "ok". See arcadia-core commit f427892.
 
 import type { ArcadiaClient } from "@crema/arcadia-core-client"
 

app/lib/arcadia/llm-configs.ts

@@ -124,7 +124,7 @@ export async function getCatalog(arcadia: ArcadiaClient): Promise<CatalogEntry[]
 /**
  * Compute cost in cents for a given input/output token count using a
  * configuration's published rates. Mirrors `LlmConfiguration.compute_cost_cents/3`
- * in arcadia-app — keep in sync.
+ * in arcadia-core — keep in sync.
  */
 export function computeCostCents(
   config: Pick<LlmConfiguration, "input_cost_per_million" | "output_cost_per_million">,

app/lib/arcadia/llm-proxy.ts

@@ -1,6 +1,6 @@
 // Arcadia LLM proxy client.
 //
-// Implements the spec in docs/LLM_PROXY_CONTRACT.md against arcadia-app's
+// Implements the spec in docs/LLM_PROXY_CONTRACT.md against arcadia-core's
 // POST /api/v1/ai/llm/chat. The lib (@crema/llm-providers-ui buildAdapter)
 // owns the streaming chat path itself; this module exposes a lightweight
 // non-streaming probe so the Settings "Test connection" button can verify

app/lib/gateway.ts

@@ -1,9 +1,9 @@
 // Arcadia LLM-gateway client.
 //
-// The integration registry lives on arcadia-llm-gateway, not arcadia-app, so
+// The integration registry lives on arcadia-llm-gateway, not arcadia-core, so
 // it needs its own ArcadiaClient pointed at a different base URL. Everything
-// else is identical to the arcadia-app client: the same access token (the
-// gateway validates arcadia-app JWTs via the shared Guardian secret) and the
+// else is identical to the arcadia-core client: the same access token (the
+// gateway validates arcadia-core JWTs via the shared Guardian secret) and the
 // same 401 cleanup. The gateway's CORS already allows localhost + any
 // *.sky-ai.com origin, so the browser calls it directly.