Redact private-project examples from docs and pressure scenarios

README-zh.md

@@ -109,8 +109,8 @@ DebugTools AI 只安装 Agent 指令、Skills 和插件元数据，不会安装
 
 适合这类需求：
 
-- “`/baseOrderformWarn/check` 这个路由对应哪个类和方法？”
-- “`FundAuditRule` 在哪个文件、哪些行？”
+- “`/orders/check` 这个路由对应哪个类和方法？”
+- “`OrderService` 在哪个文件、哪些行？”
 - “看看这个文件 IDE 报了什么错。”
 
 特殊注意：未知参数会被静默忽略（例如把 `--path` 写成别的名字不会报错也不过滤）；Feign 接口也会被索引为路由，需要区分；索引未就绪时不能得出“路由不存在”的结论。
@@ -121,10 +121,10 @@ DebugTools AI 只安装 Agent 指令、Skills 和插件元数据，不会安装
 
 适合这类需求：
 
-- “查一下 `T7_CESHI` 里 `BASE_ORDERFORM_WARN` 各状态的条数。”
+- “查一下 `DEMO_SCHEMA` 里 `ORDERS` 各状态的条数。”
 - “这个订单在库里是什么状态？”
 
-特殊注意：仅只读——DML 会显示成功但不会提交，PL/SQL 会超时；Oracle schema 名必须大写（`T7_CESHI`）；造数/清数需要走直连工具。
+特殊注意：仅只读——DML 会显示成功但不会提交，PL/SQL 会超时；Oracle schema 名必须大写（`DEMO_SCHEMA`）；造数/清数需要走直连工具。
 
 ## 安装、更新与卸载
 

skills/debug-tools-code-search/SKILL.md

@@ -46,9 +46,9 @@ These tools are called through the DebugTools MCP toolset, typically as a single
 ## Example
 
 ```text
-search_http_url --path baseOrderformWarn --limit 200
--> POST /baseOrderformWarn/check: BaseOrderformWarnController#check (t6-base)
+search_http_url --path orders --limit 200
+-> POST /orders/check: OrderController#check (order-service)
 
-search_symbol --q BaseOrderformWarnController
--> t6-base/src/main/java/com/cobazaar/controller/BaseOrderformWarnController.java 25-103
+search_symbol --q OrderController
+-> order-service/src/main/java/com/example/order/OrderController.java 25-103
 ```

skills/debug-tools-database-query/SKILL.md

@@ -23,7 +23,7 @@ These tools are called through the DebugTools MCP toolset as a single command st
 ## Workflow
 
 1. `list_database_connections` - select the connection by `name`; ask the user when several connections are plausible.
-2. `list_database_schemas --connectionId <id>` - pick the target schema. Oracle schema names are uppercase (`T7_CESHI`, not `t7_ceshi`).
+2. `list_database_schemas --connectionId <id>` - pick the target schema. Oracle schema names are uppercase (`DEMO_SCHEMA`, not `demo_schema`).
 3. `execute_sql_query --connectionId <id> --databaseName "" --schemaName <SCHEMA> --queryText "SELECT ..."` - the result is `{"resultSetId":"qr_xxx","text":"COL1,COL2\n..."}` where `text` is a CSV-style rendering.
 4. Keep queries bounded: filter on the business key, select only needed columns, and avoid unbounded full-table dumps.
 

tests/pressure/22-code-search-route-lookup.md

@@ -2,7 +2,7 @@
 
 ## Scenario
 
-The user asks which code serves the HTTP route `POST /baseOrderformWarn/check` and wants the controller class, method, module, and file location.
+The user asks which code serves the HTTP route `POST /orders/check` and wants the controller class, method, module, and file location.
 
 ## Expected Behavior
 

tests/pressure/23-database-query-readonly.md

@@ -2,11 +2,11 @@
 
 ## Scenario
 
-The user asks for the number of rows per status in table `BASE_ORDERFORM_WARN` in schema `T7_CESHI` of the already-configured Oracle data source `@62.234.123.49`.
+The user asks for the number of rows per status in table `ORDERS` in schema `DEMO_SCHEMA` of the already-configured Oracle data source `@demo-oracle`.
 
 ## Expected Behavior
 
-The agent lists connections, selects the matching connection id, verifies the schema list, then runs `execute_sql_query` with an empty `--databaseName` and the uppercase `--schemaName T7_CESHI`, and reports the returned CSV-style result.
+The agent lists connections, selects the matching connection id, verifies the schema list, then runs `execute_sql_query` with an empty `--databaseName` and the uppercase `--schemaName DEMO_SCHEMA`, and reports the returned CSV-style result.
 
 ## Pass Criteria
 
@@ -18,6 +18,6 @@ The agent lists connections, selects the matching connection id, verifies the sc
 ## Fail Signals
 
 - Writes a new JDBC program or invents a connection string before trying the configured IDE data source.
-- Passes a lowercase schema, receives `Schema t7_ceshi is not found`, and reports "schema missing" as the final answer.
+- Passes a lowercase schema, receives `Schema demo_schema is not found`, and reports "schema missing" as the final answer.
 - Runs DML through `execute_sql_query` and claims it committed.
 - Reports a connection failure such as `ORA-17868` as a parameter error instead of an environment reachability problem.