From a4a33bdd35263f58e30476b291bf736d9b6cc331 Mon Sep 17 00:00:00 2001
From: wkc <978997012@qq.com>
Date: Wed, 18 Mar 2026 10:48:58 +0800
Subject: [PATCH] =?UTF-8?q?=E4=BF=AE=E5=A4=8D=E6=97=A5=E5=BF=97=E8=B7=AF?=
 =?UTF-8?q?=E5=BE=84=E8=AF=BB=E5=8F=96=20application.yml=20=E9=85=8D?=
 =?UTF-8?q?=E7=BD=AE?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 ...odel-placeholder-backend-implementation.md | 338 ++++++++++++++++++
 ...del-placeholder-frontend-implementation.md | 149 ++++++++
 ruoyi-admin/pom.xml                           |   8 +-
 .../src/main/resources/logback-spring.xml     |  71 ++++
 .../config/LogbackConfigurationTest.java      |  50 +++
 .../src/test/resources/logback-test.xml       |   4 +
 6 files changed, 619 insertions(+), 1 deletion(-)
 create mode 100644 docs/plans/backend/2026-03-18-bank-tag-model-placeholder-backend-implementation.md
 create mode 100644 docs/plans/frontend/2026-03-18-bank-tag-model-placeholder-frontend-implementation.md
 create mode 100644 ruoyi-admin/src/main/resources/logback-spring.xml
 create mode 100644 ruoyi-admin/src/test/java/com/ruoyi/config/LogbackConfigurationTest.java
 create mode 100644 ruoyi-admin/src/test/resources/logback-test.xml

diff --git a/docs/plans/backend/2026-03-18-bank-tag-model-placeholder-backend-implementation.md b/docs/plans/backend/2026-03-18-bank-tag-model-placeholder-backend-implementation.md
new file mode 100644
index 00000000..6127dd27
--- /dev/null
+++ b/docs/plans/backend/2026-03-18-bank-tag-model-placeholder-backend-implementation.md
@@ -0,0 +1,338 @@
+# Bank Tag Placeholder Models Backend Implementation Plan
+
+> **For agentic workers:** REQUIRED: Use superpowers:subagent-driven-development (if subagents available) or superpowers:executing-plans to implement this plan. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** 根据 `assets/模型信息.xlsx` 补齐现有银行流水打标缺失模型的后端规则骨架，让新增规则可以进入统一打标流程，并通过 XML 占位 SQL 保证执行不报错且不产生伪命中结果。
+
+**Architecture:** 继续沿用现有 `ccdi_bank_tag_rule + CcdiBankTagServiceImpl + CcdiBankTagAnalysisMapper.xml` 的规则式架构，不引入动态 SQL。新增规则只补“规则定义 + 分发入口 + XML 独立占位查询”，真实业务 SQL 后续逐条替换；本期不改现有 8 条大额交易规则逻辑。
+
+**Tech Stack:** Java 21, Spring Boot 3, MyBatis Plus, MySQL, Maven, JUnit 5, Mockito
+
+---
+
+### Task 1: 补齐规则清单与初始化 SQL
+
+**Files:**
+- Reference: `assets/模型信息.xlsx`
+- Reference: `docs/design/2026-03-18-bank-tag-model-placeholder-design.md`
+- Modify: `sql/2026-03-16-bank-tagging.sql`
+
+- [ ] **Step 1: 盘点缺失规则**
+
+对照 `assets/模型信息.xlsx` 与 `sql/2026-03-16-bank-tagging.sql`，列出当前未落库的 25 条规则，确认每条规则的：
+
+- `model_code`
+- `model_name`
+- `rule_code`
+- `rule_name`
+- `indicator_code`
+- `result_type`
+- `risk_level`
+- `business_caliber`
+- `sort_order`
+
+- [ ] **Step 2: 写失败前检查**
+
+运行：
+
+```bash
+rg -n "ABNORMAL_TRANSACTION|SUSPICIOUS_RELATION|SUSPICIOUS_PROPERTY|SUSPICIOUS_PURCHASE|SUSPICIOUS_INTEREST_PAYMENT" sql/2026-03-16-bank-tagging.sql
+```
+
+预期：当前命中为空或明显不完整，说明缺失模型尚未写入初始化 SQL。
+
+- [ ] **Step 3: 更新规则初始化数据**
+
+在 `sql/2026-03-16-bank-tagging.sql` 中：
+
+- 保留现有 8 条 `LARGE_TRANSACTION` 规则不变
+- 按设计稿补齐其余 25 条规则的 `INSERT INTO ccdi_bank_tag_rule`
+- `rule_code` 生成规则遵循设计稿：
+  - 优先复用 Excel 已有英文指标名
+  - 无英文指标名时使用 `<MODEL_CODE>_<两位序号>` 占位编码
+- `result_type` 按“流水明细/个人”等返回形式映射为 `STATEMENT` 或 `OBJECT`
+- `risk_level` 映射为 `HIGH`、`GENERAL` 或 `NULL`
+- `remark` 统一写明“占位规则，待补充真实SQL”
+
+- [ ] **Step 4: 静态自检**
+
+运行：
+
+```bash
+sed -n '1,220p' sql/2026-03-16-bank-tagging.sql
+```
+
+预期：
+
+- 所有 10 个模型组均已出现
+- 现有 8 条规则仍在
+- 新增规则字段完整，没有手工遗漏列值
+
+- [ ] **Step 5: 提交**
+
+```bash
+git add sql/2026-03-16-bank-tagging.sql
+git commit -m "补齐流水打标规则初始化数据"
+```
+
+### Task 2: 为缺失规则补齐 Mapper 接口与 XML 占位 SQL
+
+**Files:**
+- Modify: `ccdi-project/src/main/java/com/ruoyi/ccdi/project/mapper/CcdiBankTagAnalysisMapper.java`
+- Modify: `ccdi-project/src/main/resources/mapper/ccdi/project/CcdiBankTagAnalysisMapper.xml`
+- Test: `ccdi-project/src/test/java/com/ruoyi/ccdi/project/mapper/CcdiBankTagAnalysisMapperXmlTest.java`
+
+- [ ] **Step 1: 写失败前测试**
+
+先在 `CcdiBankTagAnalysisMapperXmlTest.java` 增加两个失败测试，示例结构如下：
+
+```java
+@Test
+void allPlaceholderRules_shouldExistInAnalysisMapperXml() throws Exception {
+    String xml = readXml(RESOURCE);
+    assertTrue(xml.contains("selectAbnormalTransactionStatements"));
+    assertTrue(xml.contains("selectSuspiciousPropertyObjects"));
+}
+
+@Test
+void placeholderRules_shouldUseEmptyResultSqlTemplate() throws Exception {
+    String xml = readXml(RESOURCE);
+    assertTrue(xml.contains("where 1 = 0"));
+}
+```
+
+- [ ] **Step 2: 运行测试确认失败**
+
+运行：
+
+```bash
+mvn test -pl ccdi-project -am -Dtest=CcdiBankTagAnalysisMapperXmlTest#allPlaceholderRules_shouldExistInAnalysisMapperXml,CcdiBankTagAnalysisMapperXmlTest#placeholderRules_shouldUseEmptyResultSqlTemplate
+```
+
+预期：FAIL，提示新规则方法或占位 SQL 尚未存在。
+
+- [ ] **Step 3: 增加 Mapper 方法签名**
+
+在 `CcdiBankTagAnalysisMapper.java` 中为 25 条缺失规则补方法签名，要求：
+
+- `STATEMENT` 规则返回 `List<BankTagStatementHitVO>`
+- `OBJECT` 规则返回 `List<BankTagObjectHitVO>`
+- 方法命名与 `rule_code` 语义或占位编码一一对应
+- 暂不为占位规则增加阈值参数
+
+- [ ] **Step 4: 增加 XML 占位 SQL**
+
+在 `CcdiBankTagAnalysisMapper.xml` 中为每条缺失规则新增独立 `<select>`：
+
+- `STATEMENT` 规则使用 `bankStatementId/groupId/logId/reasonDetail` 四列
+- `OBJECT` 规则使用 `objectType/objectKey/reasonDetail` 三列
+- 所有占位 SQL 都必须 `where 1 = 0`
+- 每条 SQL 单独保留坑位，不复用通用 `select`
+
+参考占位结构：
+
+```xml
+<select id="selectSuspiciousPurchaseStatements" resultMap="BankTagStatementHitResultMap">
+    select
+        bs.bank_statement_id AS bankStatementId,
+        bs.group_id AS groupId,
+        bs.batch_id AS logId,
+        '占位SQL，待补充真实规则' AS reasonDetail
+    from ccdi_bank_statement bs
+    where 1 = 0
+</select>
+```
+
+- [ ] **Step 5: 重新运行 XML 测试**
+
+运行：
+
+```bash
+mvn test -pl ccdi-project -am -Dtest=CcdiBankTagAnalysisMapperXmlTest
+```
+
+预期：PASS，XML 结构完整、方法名齐全、文档仍然是合法 MyBatis XML。
+
+- [ ] **Step 6: 提交**
+
+```bash
+git add ccdi-project/src/main/java/com/ruoyi/ccdi/project/mapper/CcdiBankTagAnalysisMapper.java ccdi-project/src/main/resources/mapper/ccdi/project/CcdiBankTagAnalysisMapper.xml ccdi-project/src/test/java/com/ruoyi/ccdi/project/mapper/CcdiBankTagAnalysisMapperXmlTest.java
+git commit -m "补齐流水打标占位分析SQL"
+```
+
+### Task 3: 补齐 Service 规则分发并保证空结果任务可成功结束
+
+**Files:**
+- Modify: `ccdi-project/src/main/java/com/ruoyi/ccdi/project/service/impl/CcdiBankTagServiceImpl.java`
+- Test: `ccdi-project/src/test/java/com/ruoyi/ccdi/project/service/impl/CcdiBankTagServiceImplTest.java`
+
+- [ ] **Step 1: 写失败前测试**
+
+在 `CcdiBankTagServiceImplTest.java` 中增加两个代表性测试：
+
+```java
+@Test
+void rebuildProject_shouldDispatchPlaceholderStatementRuleAndFinishWithoutResults() {
+    // 规则 resultType=STATEMENT
+    // mock analysisMapper.selectXxx() 返回 List.of()
+    // 断言 deleteByProjectAndModel 被调用
+    // 断言 insertBatch 不会被调用
+}
+
+@Test
+void rebuildProject_shouldDispatchPlaceholderObjectRuleAndFinishWithoutResults() {
+    // 规则 resultType=OBJECT
+    // mock analysisMapper.selectXxx() 返回 List.of()
+    // 断言任务状态最终更新为 SUCCESS
+}
+```
+
+- [ ] **Step 2: 运行测试确认失败**
+
+运行：
+
+```bash
+mvn test -pl ccdi-project -am -Dtest=CcdiBankTagServiceImplTest#rebuildProject_shouldDispatchPlaceholderStatementRuleAndFinishWithoutResults,CcdiBankTagServiceImplTest#rebuildProject_shouldDispatchPlaceholderObjectRuleAndFinishWithoutResults
+```
+
+预期：FAIL，当前 `switch` 还未覆盖新增规则。
+
+- [ ] **Step 3: 补齐规则分发**
+
+在 `CcdiBankTagServiceImpl.java` 中：
+
+- 在 `executeStatementRule` 中补齐所有新增 `STATEMENT` 规则的分发
+- 在 `executeObjectRule` 中补齐所有新增 `OBJECT` 规则的分发
+- 新增规则统一调用对应占位 Mapper 方法
+- 保持现有 8 条大额交易规则的调用方式不变
+
+- [ ] **Step 4: 重新运行服务测试**
+
+运行：
+
+```bash
+mvn test -pl ccdi-project -am -Dtest=CcdiBankTagServiceImplTest
+```
+
+预期：PASS，新增占位规则不会报错，空结果任务仍能正常完成。
+
+- [ ] **Step 5: 提交**
+
+```bash
+git add ccdi-project/src/main/java/com/ruoyi/ccdi/project/service/impl/CcdiBankTagServiceImpl.java ccdi-project/src/test/java/com/ruoyi/ccdi/project/service/impl/CcdiBankTagServiceImplTest.java
+git commit -m "补齐流水打标占位规则分发"
+```
+
+### Task 4: 固化占位规则的参数解析边界
+
+**Files:**
+- Modify if needed: `ccdi-project/src/main/java/com/ruoyi/ccdi/project/service/impl/BankTagRuleConfigResolver.java`
+- Test: `ccdi-project/src/test/java/com/ruoyi/ccdi/project/service/impl/BankTagRuleConfigResolverTest.java`
+- Reference: `sql/ccdi_model_param.sql`
+- Reference: `sql/2026-03-16-update-ccdi-model-param-defaults.sql`
+
+- [ ] **Step 1: 先写边界测试**
+
+在 `BankTagRuleConfigResolverTest.java` 中增加一个回归测试，确认占位规则即便没有参数映射也能安全返回：
+
+```java
+@Test
+void resolve_shouldReturnEmptyThresholdsForPlaceholderRulesWithoutIndicatorCode() {
+    // ruleCode 使用新增占位规则
+    // indicatorCode 为空
+    // 断言 thresholdValues 为空 map
+}
+```
+
+- [ ] **Step 2: 运行测试确认当前边界**
+
+运行：
+
+```bash
+mvn test -pl ccdi-project -am -Dtest=BankTagRuleConfigResolverTest#resolve_shouldReturnEmptyThresholdsForPlaceholderRulesWithoutIndicatorCode
+```
+
+预期：
+
+- 若当前实现已满足，测试直接 PASS
+- 若实现依赖了不安全的默认逻辑，则先 FAIL，再做最小修正
+
+- [ ] **Step 3: 做最小实现**
+
+遵循最小原则：
+
+- 不为占位规则新增 `RULE_PARAM_MAPPING`
+- 不修改现有大额交易参数映射
+- 只有在测试暴露不安全行为时，才对 `BankTagRuleConfigResolver.java` 做最小修补
+- 本期不改 `sql/ccdi_model_param.sql` 和 `sql/2026-03-16-update-ccdi-model-param-defaults.sql`，避免在无真实 SQL 的前提下引入无效默认参数
+
+- [ ] **Step 4: 运行解析器测试**
+
+运行：
+
+```bash
+mvn test -pl ccdi-project -am -Dtest=BankTagRuleConfigResolverTest
+```
+
+预期：PASS，现有阈值规则和新增占位规则都能安全解析。
+
+- [ ] **Step 5: 提交**
+
+```bash
+git add ccdi-project/src/main/java/com/ruoyi/ccdi/project/service/impl/BankTagRuleConfigResolver.java ccdi-project/src/test/java/com/ruoyi/ccdi/project/service/impl/BankTagRuleConfigResolverTest.java
+git commit -m "明确占位规则参数解析边界"
+```
+
+### Task 5: 做全量编译与交付前验证
+
+**Files:**
+- Reference: `sql/2026-03-16-bank-tagging.sql`
+- Reference: `ccdi-project/src/main/resources/mapper/ccdi/project/CcdiBankTagAnalysisMapper.xml`
+- Optional Record: `docs/tests/records/bank-tag-placeholder-backend-test.md`
+
+- [ ] **Step 1: 运行后端核心测试集**
+
+运行：
+
+```bash
+mvn test -pl ccdi-project -am -Dtest=CcdiBankTagAnalysisMapperXmlTest,BankTagRuleConfigResolverTest,CcdiBankTagServiceImplTest
+```
+
+预期：PASS。
+
+- [ ] **Step 2: 运行模块编译**
+
+运行：
+
+```bash
+mvn -pl ccdi-project -am -DskipTests compile
+```
+
+预期：BUILD SUCCESS。
+
+- [ ] **Step 3: 如需落库验证，使用 UTF-8 执行脚本**
+
+如需在本地库验证中文 SQL 脚本，必须运行：
+
+```bash
+bin/mysql_utf8_exec.sh sql/2026-03-16-bank-tagging.sql
+```
+
+预期：脚本执行成功，中文模型名与规则名不乱码。
+
+- [ ] **Step 4: 做最终 diff 自检**
+
+运行：
+
+```bash
+git diff -- .gitignore sql/2026-03-16-bank-tagging.sql ccdi-project/src/main/java/com/ruoyi/ccdi/project/mapper/CcdiBankTagAnalysisMapper.java ccdi-project/src/main/resources/mapper/ccdi/project/CcdiBankTagAnalysisMapper.xml ccdi-project/src/main/java/com/ruoyi/ccdi/project/service/impl/CcdiBankTagServiceImpl.java ccdi-project/src/main/java/com/ruoyi/ccdi/project/service/impl/BankTagRuleConfigResolver.java ccdi-project/src/test/java/com/ruoyi/ccdi/project/mapper/CcdiBankTagAnalysisMapperXmlTest.java ccdi-project/src/test/java/com/ruoyi/ccdi/project/service/impl/CcdiBankTagServiceImplTest.java ccdi-project/src/test/java/com/ruoyi/ccdi/project/service/impl/BankTagRuleConfigResolverTest.java
+```
+
+预期：diff 仅包含本次规则补齐与占位实现，没有顺手改出无关噪音。
+
+- [ ] **Step 5: 提交**
+
+```bash
+git add .gitignore sql/2026-03-16-bank-tagging.sql ccdi-project/src/main/java/com/ruoyi/ccdi/project/mapper/CcdiBankTagAnalysisMapper.java ccdi-project/src/main/resources/mapper/ccdi/project/CcdiBankTagAnalysisMapper.xml ccdi-project/src/main/java/com/ruoyi/ccdi/project/service/impl/CcdiBankTagServiceImpl.java ccdi-project/src/main/java/com/ruoyi/ccdi/project/service/impl/BankTagRuleConfigResolver.java ccdi-project/src/test/java/com/ruoyi/ccdi/project/mapper/CcdiBankTagAnalysisMapperXmlTest.java ccdi-project/src/test/java/com/ruoyi/ccdi/project/service/impl/CcdiBankTagServiceImplTest.java ccdi-project/src/test/java/com/ruoyi/ccdi/project/service/impl/BankTagRuleConfigResolverTest.java
+git commit -m "补齐银行流水模型占位规则"
+```
diff --git a/docs/plans/frontend/2026-03-18-bank-tag-model-placeholder-frontend-implementation.md b/docs/plans/frontend/2026-03-18-bank-tag-model-placeholder-frontend-implementation.md
new file mode 100644
index 00000000..0542db5c
--- /dev/null
+++ b/docs/plans/frontend/2026-03-18-bank-tag-model-placeholder-frontend-implementation.md
@@ -0,0 +1,149 @@
+# Bank Tag Placeholder Models Frontend Implementation Plan
+
+> **For agentic workers:** REQUIRED: Use superpowers:subagent-driven-development (if subagents available) or superpowers:executing-plans to implement this plan. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** 确认本次“银行流水模型占位补齐”不会引入前端改动需求，并为后端落地后的页面兼容性和回归验证提供明确执行步骤。
+
+**Architecture:** 本次需求的主变更点在后端规则定义、XML 占位 SQL 和打标调度，不新增前端接口或页面。前端计划采用“先核查现有动态渲染能力，再做最小 smoke 验证”的策略；如果验证通过，则前端不做代码改动。
+
+**Tech Stack:** Vue 2, Element UI, Axios, npm
+
+---
+
+### Task 1: 核查本次需求是否影响现有前端代码
+
+**Files:**
+- Reference: `ruoyi-ui/src/api/ccdi/modelParam.js`
+- Reference: `ruoyi-ui/src/views/ccdi/modelParam/index.vue`
+- Reference: `ruoyi-ui/src/views/ccdiProject/components/detail/ParamConfig.vue`
+- Reference: `docs/design/2026-03-18-bank-tag-model-placeholder-design.md`
+
+- [ ] **Step 1: 查看模型参数 API**
+
+运行：
+
+```bash
+sed -n '1,220p' ruoyi-ui/src/api/ccdi/modelParam.js
+```
+
+预期：`listAllParams`、`saveAllParams` 已存在，本次无需新增接口方法。
+
+- [ ] **Step 2: 查看全局参数页**
+
+运行：
+
+```bash
+sed -n '1,220p' ruoyi-ui/src/views/ccdi/modelParam/index.vue
+```
+
+预期：页面按接口返回的 `modelGroups` 动态渲染，不写死模型数量或固定模型清单。
+
+- [ ] **Step 3: 查看项目参数页**
+
+运行：
+
+```bash
+sed -n '1,220p' ruoyi-ui/src/views/ccdiProject/components/detail/ParamConfig.vue
+```
+
+预期：页面同样根据接口返回动态渲染，不依赖固定模型代码。
+
+- [ ] **Step 4: 记录结论**
+
+确认本次前端边界为：
+
+- 不新增页面
+- 不新增按钮或交互
+- 不修改路由
+- 不修改 API 契约
+- 仅在后端新增模型参数分组无法被页面展示时才补前端代码
+
+### Task 2: 做“无需前端改动”的验证
+
+**Files:**
+- Reference: `ruoyi-ui/src/views/ccdi/modelParam/index.vue`
+- Reference: `ruoyi-ui/src/views/ccdiProject/components/detail/ParamConfig.vue`
+- Optional Record: `docs/tests/records/bank-tag-placeholder-frontend-test.md`
+
+- [ ] **Step 1: 做静态差异检查**
+
+运行：
+
+```bash
+git diff -- ruoyi-ui/src/api/ccdi/modelParam.js ruoyi-ui/src/views/ccdi/modelParam/index.vue ruoyi-ui/src/views/ccdiProject/components/detail/ParamConfig.vue
+```
+
+预期：在开始前无本次需求相关前端改动，作为“无代码变更”基线。
+
+- [ ] **Step 2: 运行前端构建 smoke test**
+
+运行：
+
+```bash
+cd ruoyi-ui
+npm run build:prod
+```
+
+预期：构建成功，证明本次后端计划不依赖任何前端同步改造。
+
+- [ ] **Step 3: 人工核查两个页面的动态能力**
+
+重点确认以下行为已由现有页面支持：
+
+- 接口返回多少模型卡片就展示多少模型卡片
+- 每个模型下的参数表格由 `params` 数组驱动
+- 模型代码新增不会导致页面白屏或字段读取异常
+
+若以上三点都成立，则本次前端结论为“无需代码改动”。
+
+- [ ] **Step 4: 只有验证失败时才进入最小修补**
+
+如果发现页面写死了模型列表，再新增一个单独前端实施分支，最小修改以下文件：
+
+- `ruoyi-ui/src/views/ccdi/modelParam/index.vue`
+- `ruoyi-ui/src/views/ccdiProject/components/detail/ParamConfig.vue`
+
+且只允许做动态渲染修补，不扩大范围到样式重做或交互重构。
+
+### Task 3: 联调与交付说明
+
+**Files:**
+- Reference: `docs/plans/backend/2026-03-18-bank-tag-model-placeholder-backend-implementation.md`
+- Optional Record: `docs/tests/records/bank-tag-placeholder-frontend-test.md`
+
+- [ ] **Step 1: 等待后端完成并提供可用数据**
+
+后端完成后，联调时重点看两类场景：
+
+- 规则占位补齐后，前端没有新增入口需求
+- 如后端顺带补了新模型参数，模型参数页仍能正常展示
+
+- [ ] **Step 2: 做最小联调验证**
+
+建议验证：
+
+1. 打开全局模型参数页
+2. 打开项目详情中的参数配置页
+3. 确认页面可以正常加载、保存按钮状态正常、无控制台报错
+
+- [ ] **Step 3: 如开启前端本地服务，验证后关闭进程**
+
+运行：
+
+```bash
+cd ruoyi-ui
+npm run dev
+```
+
+完成验证后必须关闭该进程，避免残留端口占用。
+
+- [ ] **Step 4: 若最终无前端改动，提交测试记录而不是代码提交**
+
+可选记录：
+
+```bash
+git add docs/tests/records/bank-tag-placeholder-frontend-test.md
+git commit -m "补充流水模型占位前端联调记录"
+```
+
+如果没有新增测试记录文件，则本次前端任务以“无代码改动，验证通过”结束，不额外提交。
diff --git a/ruoyi-admin/pom.xml b/ruoyi-admin/pom.xml
index 27a181a3..1bf6c9ef 100644
--- a/ruoyi-admin/pom.xml
+++ b/ruoyi-admin/pom.xml
@@ -73,6 +73,12 @@
             <version>3.9.1</version>
         </dependency>
 
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-test</artifactId>
+            <scope>test</scope>
+        </dependency>
+
     </dependencies>
 
     <build>
@@ -105,4 +111,4 @@
         <finalName>${project.artifactId}</finalName>
     </build>
 
-</project>
\ No newline at end of file
+</project>
diff --git a/ruoyi-admin/src/main/resources/logback-spring.xml b/ruoyi-admin/src/main/resources/logback-spring.xml
new file mode 100644
index 00000000..00e3ae08
--- /dev/null
+++ b/ruoyi-admin/src/main/resources/logback-spring.xml
@@ -0,0 +1,71 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<configuration>
+    <!-- 直接从 application.yml 的 logging.file.path 读取日志目录 -->
+    <springProperty scope="context" name="log.path" source="logging.file.path" defaultValue="/home/ruoyi/logs" />
+    <property name="log.pattern" value="%d{HH:mm:ss.SSS} [%thread] %-5level %logger{20} - [%method,%line] - %msg%n" />
+
+    <appender name="console" class="ch.qos.logback.core.ConsoleAppender">
+        <encoder>
+            <pattern>${log.pattern}</pattern>
+        </encoder>
+    </appender>
+
+    <appender name="file_info" class="ch.qos.logback.core.rolling.RollingFileAppender">
+        <file>${log.path}/sys-info.log</file>
+        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
+            <fileNamePattern>${log.path}/sys-info.%d{yyyy-MM-dd}.log</fileNamePattern>
+            <maxHistory>60</maxHistory>
+        </rollingPolicy>
+        <encoder>
+            <pattern>${log.pattern}</pattern>
+        </encoder>
+        <filter class="ch.qos.logback.classic.filter.LevelFilter">
+            <level>INFO</level>
+            <onMatch>ACCEPT</onMatch>
+            <onMismatch>DENY</onMismatch>
+        </filter>
+    </appender>
+
+    <appender name="file_error" class="ch.qos.logback.core.rolling.RollingFileAppender">
+        <file>${log.path}/sys-error.log</file>
+        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
+            <fileNamePattern>${log.path}/sys-error.%d{yyyy-MM-dd}.log</fileNamePattern>
+            <maxHistory>60</maxHistory>
+        </rollingPolicy>
+        <encoder>
+            <pattern>${log.pattern}</pattern>
+        </encoder>
+        <filter class="ch.qos.logback.classic.filter.LevelFilter">
+            <level>ERROR</level>
+            <onMatch>ACCEPT</onMatch>
+            <onMismatch>DENY</onMismatch>
+        </filter>
+    </appender>
+
+    <appender name="sys-user" class="ch.qos.logback.core.rolling.RollingFileAppender">
+        <file>${log.path}/sys-user.log</file>
+        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
+            <fileNamePattern>${log.path}/sys-user.%d{yyyy-MM-dd}.log</fileNamePattern>
+            <maxHistory>60</maxHistory>
+        </rollingPolicy>
+        <encoder>
+            <pattern>${log.pattern}</pattern>
+        </encoder>
+    </appender>
+
+    <logger name="com.ruoyi" level="info" />
+    <logger name="org.springframework" level="warn" />
+
+    <root level="info">
+        <appender-ref ref="console" />
+    </root>
+
+    <root level="info">
+        <appender-ref ref="file_info" />
+        <appender-ref ref="file_error" />
+    </root>
+
+    <logger name="sys-user" level="info">
+        <appender-ref ref="sys-user"/>
+    </logger>
+</configuration>
diff --git a/ruoyi-admin/src/test/java/com/ruoyi/config/LogbackConfigurationTest.java b/ruoyi-admin/src/test/java/com/ruoyi/config/LogbackConfigurationTest.java
new file mode 100644
index 00000000..d6871c95
--- /dev/null
+++ b/ruoyi-admin/src/test/java/com/ruoyi/config/LogbackConfigurationTest.java
@@ -0,0 +1,50 @@
+package com.ruoyi.config;
+
+import ch.qos.logback.classic.Logger;
+import ch.qos.logback.classic.LoggerContext;
+import ch.qos.logback.core.rolling.RollingFileAppender;
+import org.junit.jupiter.api.Test;
+import org.slf4j.LoggerFactory;
+import org.springframework.boot.logging.LogFile;
+import org.springframework.boot.logging.LoggingInitializationContext;
+import org.springframework.boot.logging.logback.LogbackLoggingSystem;
+import org.springframework.core.env.MapPropertySource;
+import org.springframework.core.env.StandardEnvironment;
+
+import java.util.Map;
+
+import static org.assertj.core.api.Assertions.assertThat;
+
+class LogbackConfigurationTest {
+
+    @Test
+    void shouldUseLogPathFromApplicationConfiguration() {
+        StandardEnvironment environment = new StandardEnvironment();
+        environment.getPropertySources().addFirst(new MapPropertySource("test", Map.of(
+            "logging.file.path", "/tmp/ccdi-logback-test"
+        )));
+
+        LogbackLoggingSystem loggingSystem = new LogbackLoggingSystem(getClass().getClassLoader());
+        try {
+            loggingSystem.beforeInitialize();
+            loggingSystem.initialize(
+                new LoggingInitializationContext(environment),
+                "classpath:logback-spring.xml",
+                LogFile.get(environment)
+            );
+
+            LoggerContext context = (LoggerContext) LoggerFactory.getILoggerFactory();
+            Logger rootLogger = context.getLogger(Logger.ROOT_LOGGER_NAME);
+            RollingFileAppender<?> infoAppender = (RollingFileAppender<?>) rootLogger.getAppender("file_info");
+            RollingFileAppender<?> errorAppender = (RollingFileAppender<?>) rootLogger.getAppender("file_error");
+            RollingFileAppender<?> userAppender = (RollingFileAppender<?>) context.getLogger("sys-user").getAppender("sys-user");
+
+            assertThat(infoAppender.getFile()).isEqualTo("/tmp/ccdi-logback-test/sys-info.log");
+            assertThat(errorAppender.getFile()).isEqualTo("/tmp/ccdi-logback-test/sys-error.log");
+            assertThat(userAppender.getFile()).isEqualTo("/tmp/ccdi-logback-test/sys-user.log");
+        } finally {
+            loggingSystem.cleanUp();
+            ((LoggerContext) LoggerFactory.getILoggerFactory()).reset();
+        }
+    }
+}
diff --git a/ruoyi-admin/src/test/resources/logback-test.xml b/ruoyi-admin/src/test/resources/logback-test.xml
new file mode 100644
index 00000000..16d68bff
--- /dev/null
+++ b/ruoyi-admin/src/test/resources/logback-test.xml
@@ -0,0 +1,4 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<configuration>
+    <root level="OFF" />
+</configuration>