Release candidate 3: credentials stay on the server, every source kind creates, contradictions are visible

.github/workflows/release.yml

@@ -9,7 +9,7 @@ on:
   workflow_dispatch:
     inputs:
       tag:
-        description: "Image tag to publish (e.g. 0.1.0-rc2)"
+        description: "Image tag to publish (e.g. 0.1.0-rc3)"
         required: true
 
 permissions:

Cargo.toml

@@ -41,6 +41,8 @@ dotenvy = "0.15"
 tracing = "0.1"
 tracing-subscriber = { version = "0.3", features = ["env-filter"] }
 flate2 = "1"
+# 枚举的字符串化与遍历（来源种类 `SourceKind`）——手写两份清单的漂移就是 #247
+strum = { version = "0.27", features = ["derive"] }
 
 # Phase 1: 摄入/检索/LLM
 utopia-ingest = { path = "crates/utopia-ingest" }

README.md

@@ -61,7 +61,7 @@ One Rust binary and one Postgres. Full-text search is embedded in the binary, ve
 | **Entity resolution and review** | Duplicates are resolved in three stages: exact name or alias, embedding similarity, then a model's call on the doubtful pairs. Every merge can be undone. Uncertain cases go to a review queue: low-confidence extractions, suspected duplicates and cardinality conflicts. |
 | **Reasoning and derivation** | Ontology axioms compile into rules: transitivity, symmetry, inverses and relation hierarchy derive new facts by forward chaining. Derivation is off by default, since a wrong axiom derives wrong facts. A derived fact is marked as such on the graph, carries validity and confidence like any other, and shows what it was derived from. When it contradicts an asserted fact, the asserted one stands. |
 | **Conflict detection** | Three kinds of conflict, three sets of choices. A new fact that clashes with an older one: close the old, keep both, or reject the new. Data that breaks an axiom (self-loop, asymmetry, transitive cycle, cardinality): retract the fact, relax the axiom, or accept both. The ontology itself is checked first, because violations of a self-contradictory ontology are noise. |
-| **Ontology-driven querying** | Mount a Postgres database on a base and chat can query it alongside the documents. The agent proposes how its tables map onto the ontology, and you confirm. The method behind it, [Ontology2SQL](https://github.com/deeplethe/ontology2sql), is state of the art on BIRD Mini-Dev for SQLite and PostgreSQL ([submission](https://github.com/bird-bench/bird-bench.github.io/pull/218)). |
+| **Ontology-driven querying** | Mount a database on a base (Postgres, Trino for Iceberg / Delta Lake / Hive, Databricks, Snowflake) and chat can query it alongside the documents. The agent proposes how its tables map onto the ontology, and you confirm. The method behind it, [Ontology2SQL](https://github.com/deeplethe/ontology2sql), is state of the art on BIRD Mini-Dev for SQLite and PostgreSQL ([submission](https://github.com/bird-bench/bird-bench.github.io/pull/218)). |
 | **Multi-user and permissions** | Each knowledge base has its own members and roles: owner, admin, editor and viewer. Open bases are readable by everyone in the deployment, restricted ones only by invitation. The first account registered becomes the system administrator. |
 | **Decision ledger** | Confirming or rejecting a fact, merging or reverting an entity, rebuilding the graph: each leaves a record of who, when, and what the object looked like at the time. The ledger is append-only, and a record outlives its object, even the base it belonged to. |
 | **[Decision intelligence (in development)](#roadmap)** | Record a decision, replay both what was understood and the course it took, and reason over overlaid scenarios. |
@@ -103,7 +103,7 @@ cd web && pnpm install && pnpm dev
 
 - [ ] **Decision reasoning**: constraint computation, and replaying a decision after the fact
 - [ ] **Execution gate**: checking an agent's calls against ontology rules and symbolic logic
-- [ ] **Lakehouse for mapping and querying**: mapping exploration and Ontology2SQL over Iceberg / Delta Lake, Databricks, Snowflake and MaxCompute
+- [ ] **MaxCompute**: mapping exploration and Ontology2SQL over Alibaba Cloud MaxCompute (Iceberg / Delta Lake via Trino, Databricks and Snowflake are in, awaiting a run against a real cluster)
 - [ ] **More sources**: MySQL, ClickHouse and Doris drivers; S3, WebDAV, Notion and Feishu connectors
 - [ ] **Time to the moment**: an `instant` precision beside year / month / day, for sources that carry a real timestamp. Today a connector rounds it to a UTC day, which can shift an event across midnight by one day
 - [ ] **Agent memory over MCP**: episode writes, the retrieve endpoint, and the MCP server

SECURITY.md

@@ -45,5 +45,7 @@ source.
 
 ## Reporting a vulnerability
 
-Open an issue. If it involves exploitable detail, start with the minimum needed to reproduce
-and we will follow up privately.
+Email **security@deeplethe.com** rather than opening a public issue. Include the affected
+version or commit, the endpoint or component, and steps to reproduce. You will get an
+acknowledgement within a few days, and the release that carries the fix names you unless you
+ask otherwise.

SECURITY.zh-CN.md

@@ -25,4 +25,4 @@ Utopia 目前是 v0.1。下面是**已知的、尚未解决的**限制 —— 
 
 ## 报告漏洞
 
-请开一个 issue。如果涉及可被利用的细节，先只写复现的最小信息，我们再私下沟通完整内容。
+请发邮件到 **security@deeplethe.com**，不要开公开 issue。写明受影响的版本或提交、端点或组件、复现步骤。几天内会有回复；带修复的那个版本会在说明里致谢，除非你不希望。

crates/utopia-core/Cargo.toml

@@ -14,3 +14,4 @@ chrono.workspace = true
 sqlx.workspace = true
 figment.workspace = true
 pgvector.workspace = true
+strum.workspace = true