chore: rename project to DataFoundry

Author: iancaoo

.docs-internal/engineering/adr-0002-memory-authority-and-mastra-memory-boundary.md

@@ -18,7 +18,7 @@ These mechanisms overlap. Without a clear authority model, the same fact can ent
 paths, for example through a metadata summary, Mastra WorkingMemory, long-term memory, and future observational memory.
 This would waste context budget, create inconsistent priority, and make audit/replay unclear.
 
-The project also has a stricter requirement than a generic chatbot memory layer: data-agent context must be scoped,
+The project also has a stricter requirement than a generic chatbot memory layer: data-foundry context must be scoped,
 auditable, and governed before it reaches the model. In particular, datasource-scoped memory must not leak across
 datasources, fresh SQL/tool evidence must outrank stale memory, and prompt-visible context must be explainable through
 `ContextPackage` / `ContextPromptView`.
@@ -47,9 +47,9 @@ not treat `metadata.conversation_summaries` and Mastra WorkingMemory as two comp
 
 ### 2. Long-Term Memory
 
-`metadata.long_term_memories` remains the authoritative long-term memory store for this data-agent system.
+`metadata.long_term_memories` remains the authoritative long-term memory store for this data-foundry system.
 
-Long-term memory records must preserve data-agent-specific governance fields:
+Long-term memory records must preserve data-foundry-specific governance fields:
 
 - `scope`: `user` / `session` / `datasource`;
 - `kind`: preference, constraint, dataset fact, analysis finding, decision, session state;
@@ -86,7 +86,7 @@ Mastra OM / Semantic Recall
 
 ### 4. Prompt Injection Ownership
 
-The model-visible prompt must be decided by the data-agent context compiler:
+The model-visible prompt must be decided by the data-foundry context compiler:
 
 ```text
 logical sources
@@ -143,7 +143,7 @@ Positive:
 
 - prompt-visible memory has a single governance path;
 - compact memory cannot silently duplicate through metadata and Mastra WorkingMemory;
-- Mastra-native features can still be used without surrendering data-agent audit boundaries;
+- Mastra-native features can still be used without surrendering data-foundry audit boundaries;
 - future Semantic Recall / OM can be evaluated safely in shadow mode.
 
 Negative:

.docs-internal/engineering/adr-0003-context-layering-and-naming.md

@@ -137,7 +137,7 @@ Current migration:
   register built-in runtime sources.
 - New run-scoped sources that are not yet built in should enter through `additionalSources` on the source-layer
   runtime registry boundary, then through `additionalRuntimeSources` on the Mastra processor boundary. They must not
-  require `createDataAgent()` to manually instantiate or register runtime sources.
+  require `createDataFoundry()` to manually instantiate or register runtime sources.
 - Runtime source processors replace the current inventory snapshot for their registered `sourceType`s on every step,
   including when a source returns no items. Runtime sources are therefore fresh step-scoped projections, not append-only
   history; durable history must enter through memory/metadata repositories or explicit tool-history reference records.
@@ -417,8 +417,8 @@ Current migration:
   for message-id based rules such as `memory-summary:*` and `context:long-term-memory`.
 - The Mastra processor boundary is also the only production path that connects the source-layer runtime registry
   boundary to Mastra processors. This keeps long-term memory and WorkingMemory projection registration out of
-  `createDataAgent()`.
-- `createDataAgent()` still creates the AG-UI event sink because AG-UI wrapping is a northbound protocol concern; the
+  `createDataFoundry()`.
+- `createDataFoundry()` still creates the AG-UI event sink because AG-UI wrapping is a northbound protocol concern; the
   Mastra processor boundary consumes only the protocol-neutral `ContextProtocolEventSink`.
 
 Abstract base/interface:

.docs-internal/engineering/ag-ui-agent-runtime-architecture.puml

@@ -1,5 +1,5 @@
 @startuml
-title Data Agent - Current Runtime
+title DataFoundry - Current Runtime
 
 left to right direction
 skinparam componentStyle rectangle
@@ -20,14 +20,14 @@ package "API Surface :8787" #D8EAF1 {
   component "/api/v1/*\nConfig REST" as ConfigRest #FFFFFF
   component "ConfigApiRequest\nresources / jobs / artifacts" as ConfigApi #FFFFFF
   component "POST /api/copilotkit" as Endpoint #FFFFFF
-  component "DataAgentAgUiAgent" as Bridge #FFFFFF
+  component "DataFoundryAgUiAgent" as Bridge #FFFFFF
   component "Run Identity\nfingerprint / claim / replay" as Identity #F7C9B6
   component "TaskPlanProjector\ndynamic PLAN snapshot" as Plan #F7C9B6
 }
 
 package "Mastra Agent Runtime" #DCE8C9 {
   component "@ag-ui/mastra\nMastraAgent" as AgUiMastra
-  component "Mastra DataAgent\nReAct + tool calling" as Agent
+  component "Mastra DataFoundry\nReAct + tool calling" as Agent
   component "@ag-ui/mcp-middleware\nenabled MCP servers" as McpMiddleware
   component "MastraContextBudgetProcessor\nevery ReAct step" as ContextProcessor #F9D65C
   component "MastraTaskStateContextProcessor\nthread task snapshot" as TaskProcessor #F9D65C
@@ -70,7 +70,7 @@ ConfigApi --> Secrets
 ConfigApi --> Gateway : datasource test / introspect
 ConfigApi --> Knowledge : KB upload / search / reindex
 ConfigApi --> Artifacts : detail / preview / download
-Endpoint --> Bridge : route dataAgent
+Endpoint --> Bridge : route dataFoundry
 Bridge --> Identity : threadId / runId / parentRunId
 Identity --> Metadata : find or atomic claim
 Identity --> Events : terminal duplicate replay

.docs-internal/engineering/ag-ui-agent-runtime-architecture.svg

@@ -341,7 +341,7 @@
   <main class="shell">
     <header class="masthead">
       <div>
-        <p class="kicker">Open Data Agent Workbench / R&amp;D B</p>
+        <p class="kicker">DataFoundry Workbench / R&amp;D B</p>
         <h1>Context Control Room</h1>
         <p class="subtitle">一张图看清外部内容如何按五层上下文治理进入模型：Source、Inventory、Policy、Projection、Protocol。tool-observation 是 Source Layer 的工具结果子域，不是第六层。</p>
       </div>

.docs-internal/engineering/agent-context-architecture.html

@@ -414,7 +414,7 @@ MCP middleware 不能成为模型上下文和安全策略的旁路：
 3. 根据已缓存 manifest 为每个解析后的 MCP tool 注册独立 `ToolObservationAdapter`；可以共享
    参数化 `McpToolObservationAdapter` 类，但 registry 中仍是一工具一 adapter 实例。
 4. middleware 挂在 run 内创建的 `MastraAgent` 上，而不是包裹最外层
-   `DataAgentAgUiAgent`。这样它生成的 continuation 不会重复进入 run claim，所有标准
+   `DataFoundryAgUiAgent`。这样它生成的 continuation 不会重复进入 run claim，所有标准
    `TOOL_CALL_RESULT` 也继续经过现有 `emit -> RunEventWriter -> subscriber` 北向链路。
 5. middleware 把 MCP observation 追加到下一轮 messages 后，现有 Mastra
    `MastraContextBudgetProcessor.processInputStep` 和 `MastraToolObservationRouter` 在每一步将结果路由到
@@ -619,7 +619,7 @@ GET 响应：五类数组（结构同各资源列表，**不含明文凭据**）
     "enabledKnowledgeIds": [],
     "enabledMcpServerIds": ["notion"],
     "activeLlmProfileId": "qwen-plus-default",
-    "activeSkillId": "data-agent-default"
+    "activeSkillId": "data-foundry-default"
   }
 }
 ```
@@ -639,7 +639,7 @@ GET 响应：五类数组（结构同各资源列表，**不含明文凭据**）
         "enabledDatasourceIds": ["sales-prod-readonly"],
         "enabledKnowledgeIds": [],
         "enabledMcpServerIds": ["notion"],
-        "enabledSkillIds": ["data-agent-default", "schema-explore"],
+        "enabledSkillIds": ["data-foundry-default", "schema-explore"],
         "fileIds": ["file-ref-1"],
         "activeDatasourceId": "sales-prod-readonly",
         "activeLlmProfileId": "qwen-plus-default",

.docs-internal/engineering/config-management-api.md

@@ -17,7 +17,7 @@ flowchart LR
   subgraph API["agent-runtime Package Boundary"]
     PUBLIC["index.ts<br/>public app API"]
     TESTING["testing.ts<br/>smoke-only internal seams"]
-    AGENT["createDataAgent<br/>tool + context boundary assembly"]
+    AGENT["createDataFoundry<br/>tool + context boundary assembly"]
   end
 
   subgraph SOURCE["1. Source Layer<br/>runtime sources + tool observation subdomain"]

.docs-internal/engineering/context-governance-pipeline.mmd

@@ -11,7 +11,7 @@ skinparam componentStyle rectangle
 actor "CopilotKit / AG-UI\nClient" as Client
 
 package "apps/api" #E0F2FE {
-  component "DataAgentAgUiAgent" as Api
+  component "DataFoundryAgUiAgent" as Api
   component "ConversationMemory\nService" as MemoryService
   component "Window Policy\nToken + Char Budget" as WindowPolicy
   component "ConversationMemory\nEventObserver" as Observer
@@ -27,10 +27,10 @@ package "packages/metadata" #ECFDF5 {
 }
 
 package "packages/agent-runtime" #FEF3C7 {
-  component "createDataAgent" as Factory
+  component "createDataFoundry" as Factory
   component "MastraContextBudgetProcessor" as Budget
   component "MastraTaskStateContextProcessor" as TaskState
-  component "Mastra DataAgent\nReAct + tools" as Agent
+  component "Mastra DataFoundry\nReAct + tools" as Agent
 }
 
 package "Mastra / AG-UI" #FCE7F3 {