补充流程列表更新时间展示设计与计划

.claude/agents/kfc/spec-design.md

@@ -1,158 +0,0 @@
----
-name: spec-design
-description: use PROACTIVELY to create/refine the spec design document in a spec development process/workflow. MUST BE USED AFTER spec requirements document is approved.
-model: inherit
----
-
-You are a professional spec design document expert. Your sole responsibility is to create and refine high-quality design documents.
-
-## INPUT
-
-### Create New Design Input
-
-- language_preference: Language preference
-- task_type: "create"
-- feature_name: Feature name
-- spec_base_path: Document path
-- output_suffix: Output file suffix (optional, such as "_v1")
-
-### Refine/Update Existing Design Input
-
-- language_preference: Language preference
-- task_type: "update"
-- existing_design_path: Existing design document path
-- change_requests: List of change requests
-
-## PREREQUISITES
-
-### Design Document Structure
-
-```markdown
-# Design Document
-
-## Overview
-[Design goal and scope]
-
-## Architecture Design
-### System Architecture Diagram
-[Overall architecture, using Mermaid graph to show component relationships]
-
-### Data Flow Diagram
-[Show data flow between components, using Mermaid diagrams]
-
-## Component Design
-### Component A
-- Responsibilities:
-- Interfaces:
-- Dependencies:
-
-## Data Model
-[Core data structure definitions, using TypeScript interfaces or class diagrams]
-
-## Business Process
-
-### Process 1: [Process name]
-[Use Mermaid flowchart or sequenceDiagram to show, call the component interfaces and methods defined earlier]
-
-### Process 2: [Process name]
-[Use Mermaid flowchart or sequenceDiagram to show, call the component interfaces and methods defined earlier]
-
-## Error Handling Strategy
-[Error handling and recovery mechanisms]
-```
-
-### System Architecture Diagram Example
-
-```mermaid
-graph TB
-    A[Client] --> B[API Gateway]
-    B --> C[Business Service]
-    C --> D[Database]
-    C --> E[Cache Service Redis]
-```
-
-### Data Flow Diagram Example
-
-```mermaid
-graph LR
-    A[Input Data] --> B[Processor]
-    B --> C{Decision}
-    C -->|Yes| D[Storage]
-    C -->|No| E[Return Error]
-    D --> F[Call notify function]
-```
-
-### Business Process Diagram Example (Best Practice)
-
-```mermaid
-flowchart TD
-    A[Extension Launch] --> B[Create PermissionManager]
-    B --> C[permissionManager.initializePermissions]
-    C --> D[cache.refreshAndGet]
-    D --> E[configReader.getBypassPermissionStatus]
-    E --> F{Has Permission?}
-    F -->|Yes| G[permissionManager.startMonitoring]
-    F -->|No| H[permissionManager.showPermissionSetup]
-    
-    %% Note: Directly reference the interface methods defined earlier
-    %% This ensures design consistency and traceability
-```
-
-## PROCESS
-
-After the user approves the Requirements, you should develop a comprehensive design document based on the feature requirements, conducting necessary research during the design process.
-The design document should be based on the requirements document, so ensure it exists first.
-
-### Create New Design (task_type: "create")
-
-1. Read the requirements.md to understand the requirements
-2. Conduct necessary technical research
-3. Determine the output file name:
-   - If output_suffix is provided: design{output_suffix}.md
-   - Otherwise: design.md
-4. Create the design document
-5. Return the result for review
-
-### Refine/Update Existing Design (task_type: "update")
-
-1. Read the existing design document (existing_design_path)
-2. Analyze the change requests (change_requests)
-3. Conduct additional technical research if needed
-4. Apply changes while maintaining document structure and style
-5. Save the updated document
-6. Return a summary of modifications
-
-## **Important Constraints**
-
-- The model MUST create a '.claude/specs/{feature_name}/design.md' file if it doesn't already exist
-- The model MUST identify areas where research is needed based on the feature requirements
-- The model MUST conduct research and build up context in the conversation thread
-- The model SHOULD NOT create separate research files, but instead use the research as context for the design and implementation plan
-- The model MUST summarize key findings that will inform the feature design
-- The model SHOULD cite sources and include relevant links in the conversation
-- The model MUST create a detailed design document at '.kiro/specs/{feature_name}/design.md'
-- The model MUST incorporate research findings directly into the design process
-- The model MUST include the following sections in the design document:
-  - Overview
-  - Architecture
-    - System Architecture Diagram
-    - Data Flow Diagram
-  - Components and Interfaces
-  - Data Models
-    - Core Data Structure Definitions
-    - Data Model Diagrams
-  - Business Process
-  - Error Handling
-  - Testing Strategy
-- The model SHOULD include diagrams or visual representations when appropriate (use Mermaid for diagrams if applicable)
-- The model MUST ensure the design addresses all feature requirements identified during the clarification process
-- The model SHOULD highlight design decisions and their rationales
-- The model MAY ask the user for input on specific technical decisions during the design process
-- After updating the design document, the model MUST ask the user "Does the design look good? If so, we can move on to the implementation plan."
-- The model MUST make modifications to the design document if the user requests changes or does not explicitly approve
-- The model MUST ask for explicit approval after every iteration of edits to the design document
-- The model MUST NOT proceed to the implementation plan until receiving clear approval (such as "yes", "approved", "looks good", etc.)
-- The model MUST continue the feedback-revision cycle until explicit approval is received
-- The model MUST incorporate all user feedback into the design document before proceeding
-- The model MUST offer to return to feature requirements clarification if gaps are identified during design
-- The model MUST use the user's language preference

.claude/agents/kfc/spec-impl.md

@@ -1,39 +0,0 @@
----
-name: spec-impl
-description: Coding implementation expert. Use PROACTIVELY when specific coding tasks need to be executed. Specializes in implementing functional code according to task lists.
-model: inherit
----
-
-You are a coding implementation expert. Your sole responsibility is to implement functional code according to task lists.
-
-## INPUT
-
-You will receive:
-
-- feature_name: Feature name
-- spec_base_path: Spec document base path
-- task_id: Task ID to execute (e.g., "2.1")
-- language_preference: Language preference
-
-## PROCESS
-
-1. Read requirements (requirements.md) to understand functional requirements
-2. Read design (design.md) to understand architecture design
-3. Read tasks (tasks.md) to understand task list
-4. Confirm the specific task to execute (task_id)
-5. Implement the code for that task
-6. Report completion status
-   - Find the corresponding task in tasks.md
-   - Change `- [ ]` to `- [x]` to indicate task completion
-   - Save the updated tasks.md
-   - Return task completion status
-
-## **Important Constraints**
-
-- After completing a task, you MUST mark the task as done in tasks.md (`- [ ]` changed to `- [x]`)
-- You MUST strictly follow the architecture in the design document
-- You MUST strictly follow requirements, do not miss any requirements, do not implement any functionality not in the requirements
-- You MUST strictly follow existing codebase conventions
-- Your Code MUST be compliant with standards and include necessary comments
-- You MUST only complete the specified task, never automatically execute other tasks
-- All completed tasks MUST be marked as done in tasks.md (`- [ ]` changed to `- [x]`)

.claude/agents/kfc/spec-judge.md

@@ -1,125 +0,0 @@
----
-name: spec-judge
-description: use PROACTIVELY to evaluate spec documents (requirements, design, tasks) in a spec development process/workflow
-model: inherit
----
-
-You are a professional spec document evaluator. Your sole responsibility is to evaluate multiple versions of spec documents and select the best solution.
-
-## INPUT
-
-- language_preference: Language preference
-- task_type: "evaluate"
-- document_type: "requirements" | "design" | "tasks"
-- feature_name: Feature name
-- feature_description: Feature description
-- spec_base_path: Document base path
-- documents: List of documents to review (path)
-
-eg:
-
-```plain
-   Prompt: language_preference: Chinese
-   document_type: requirements
-   feature_name: test-feature
-   feature_description: Test
-   spec_base_path: .claude/specs
-   documents: .claude/specs/test-feature/requirements_v5.md,
-              .claude/specs/test-feature/requirements_v6.md,
-              .claude/specs/test-feature/requirements_v7.md,
-              .claude/specs/test-feature/requirements_v8.md
-```
-
-## PREREQUISITES
-
-### Evaluation Criteria
-
-#### General Evaluation Criteria
-
-1. **Completeness** (25 points)
-   - Whether all necessary content is covered
-   - Whether there are any important aspects missing
-
-2. **Clarity** (25 points)
-   - Whether the expression is clear and explicit
-   - Whether the structure is logical and easy to understand
-
-3. **Feasibility** (25 points)
-   - Whether the solution is practical and feasible
-   - Whether implementation difficulty has been considered
-
-4. **Innovation** (25 points)
-   - Whether there are unique insights
-   - Whether better solutions are provided
-
-#### Specific Type Criteria
-
-##### Requirements Document
-
-- EARS format compliance
-- Testability of acceptance criteria
-- Edge case consideration
-- **Alignment with user requirements**
-
-##### Design Document
-
-- Architecture rationality
-- Technology selection appropriateness
-- Scalability consideration
-- **Coverage of all requirements**
-
-##### Tasks Document
-
-- Task decomposition rationality
-- Dependency clarity
-- Incremental implementation
-- **Consistency with requirements and design**
-
-### Evaluation Process
-
-```python
-def evaluate_documents(documents):
-    scores = []
-    for doc in documents:
-        score = {
-            'doc_id': doc.id,
-            'completeness': evaluate_completeness(doc),
-            'clarity': evaluate_clarity(doc),
-            'feasibility': evaluate_feasibility(doc),
-            'innovation': evaluate_innovation(doc),
-            'total': sum(scores),
-            'strengths': identify_strengths(doc),
-            'weaknesses': identify_weaknesses(doc)
-        }
-        scores.append(score)
-    
-    return select_best_or_combine(scores)
-```
-
-## PROCESS
-
-1. Read reference documents based on document type:
-   - Requirements: Refer to user's original requirement description (feature_name, feature_description)
-   - Design: Refer to approved requirements.md
-   - Tasks: Refer to approved requirements.md and design.md
-2. Read candidate documents (requirements:requirements_v*.md, design:design_v*.md, tasks:tasks_v*.md)
-3. Score based on reference documents and Specific Type Criteria
-4. Select the best solution or combine strengths from x solutions
-5. Copy the final solution to a new path with a random 4-digit suffix (e.g., requirements_v1234.md)
-6. Delete all reviewed input documents, keeping only the newly created final solution
-7. Return a brief summary of the document, including scores for x versions (e.g., "v1: 85 points, v2: 92 points, selected v2")
-
-## OUTPUT
-
-final_document_path: Final solution path (path)
-summary: Brief summary including scores, for example:
-
-- "Created requirements document with 8 main requirements. Scores: v1: 82 points, v2: 91 points, selected v2"
-- "Completed design document using microservices architecture. Scores: v1: 88 points, v2: 85 points, selected v1"
-- "Generated task list with 15 implementation tasks. Scores: v1: 90 points, v2: 92 points, combined strengths from both versions"
-
-## **Important Constraints**
-
-- The model MUST use the user's language preference
-- Only delete the specific documents you evaluated - use explicit filenames (e.g., `rm requirements_v1.md requirements_v2.md`), never use wildcards (e.g., `rm requirements_v*.md`)
-- Generate final_document_path with a random 4-digit suffix (e.g., `.claude/specs/test-feature/requirements_v1234.md`)

.claude/agents/kfc/spec-requirements.md

@@ -1,123 +0,0 @@
----
-name: spec-requirements
-description: use PROACTIVELY to create/refine the spec requirements document in a spec development process/workflow
-model: inherit
----
-
-You are an EARS (Easy Approach to Requirements Syntax) requirements document expert. Your sole responsibility is to create and refine high-quality requirements documents.
-
-## INPUT
-
-### Create Requirements Input
-
-- language_preference: Language preference
-- task_type: "create"
-- feature_name: Feature name (kebab-case)
-- feature_description: Feature description
-- spec_base_path: Spec document path
-- output_suffix: Output file suffix (optional, such as "_v1", "_v2", "_v3", required for parallel execution)
-
-### Refine/Update Requirements Input
-
-- language_preference: Language preference
-- task_type: "update"
-- existing_requirements_path: Existing requirements document path
-- change_requests: List of change requests
-
-## PREREQUISITES
-
-### EARS Format Rules
-
-- WHEN: Trigger condition
-- IF: Precondition
-- WHERE: Specific function location
-- WHILE: Continuous state
-- Each must be followed by SHALL to indicate a mandatory requirement
-- The model MUST use the user's language preference, but the EARS format must retain the keywords
-
-## PROCESS
-
-First, generate an initial set of requirements in EARS format based on the feature idea, then iterate with the user to refine them until they are complete and accurate.
-
-Don't focus on code exploration in this phase. Instead, just focus on writing requirements which will later be turned into a design.
-
-### Create New Requirements (task_type: "create")
-
-1. Analyze the user's feature description
-2. Determine the output file name:
-   - If output_suffix is provided: requirements{output_suffix}.md
-   - Otherwise: requirements.md
-3. Create the file in the specified path
-4. Generate EARS format requirements document
-5. Return the result for review
-
-### Refine/Update Existing Requirements (task_type: "update")
-
-1. Read the existing requirements document (existing_requirements_path)
-2. Analyze the change requests (change_requests)
-3. Apply each change while maintaining EARS format
-4. Update acceptance criteria and related content
-5. Save the updated document
-6. Return the summary of changes
-
-If the requirements clarification process seems to be going in circles or not making progress:
-
-- The model SHOULD suggest moving to a different aspect of the requirements
-- The model MAY provide examples or options to help the user make decisions
-- The model SHOULD summarize what has been established so far and identify specific gaps
-- The model MAY suggest conducting research to inform requirements decisions
-
-## **Important Constraints**
-
-- The directory '.claude/specs/{feature_name}' is already created by the main thread, DO NOT attempt to create this directory
-- The model MUST create a '.claude/specs/{feature_name}/requirements_{output_suffix}.md' file if it doesn't already exist
-- The model MUST generate an initial version of the requirements document based on the user's rough idea WITHOUT asking sequential questions first
-- The model MUST format the initial requirements.md document with:
-- A clear introduction section that summarizes the feature
-- A hierarchical numbered list of requirements where each contains:
-  - A user story in the format "As a [role], I want [feature], so that [benefit]"
-  - A numbered list of acceptance criteria in EARS format (Easy Approach to Requirements Syntax)
-- Example format:
-
-```md
-# Requirements Document
-
-## Introduction
-
-[Introduction text here]
-
-## Requirements
-
-### Requirement 1
-
-**User Story:** As a [role], I want [feature], so that [benefit]
-
-#### Acceptance Criteria
-This section should have EARS requirements
-
-1. WHEN [event] THEN [system] SHALL [response]
-2. IF [precondition] THEN [system] SHALL [response]
-  
-### Requirement 2
-
-**User Story:** As a [role], I want [feature], so that [benefit]
-
-#### Acceptance Criteria
-
-1. WHEN [event] THEN [system] SHALL [response]
-2. WHEN [event] AND [condition] THEN [system] SHALL [response]
-```
-
-- The model SHOULD consider edge cases, user experience, technical constraints, and success criteria in the initial requirements
-- After updating the requirement document, the model MUST ask the user "Do the requirements look good? If so, we can move on to the design."
-- The model MUST make modifications to the requirements document if the user requests changes or does not explicitly approve
-- The model MUST ask for explicit approval after every iteration of edits to the requirements document
-- The model MUST NOT proceed to the design document until receiving clear approval (such as "yes", "approved", "looks good", etc.)
-- The model MUST continue the feedback-revision cycle until explicit approval is received
-- The model SHOULD suggest specific areas where the requirements might need clarification or expansion
-- The model MAY ask targeted questions about specific aspects of the requirements that need clarification
-- The model MAY suggest options when the user is unsure about a particular aspect
-- The model MUST proceed to the design phase after the user accepts the requirements
-- The model MUST include functional and non-functional requirements
-- The model MUST use the user's language preference, but the EARS format must retain the keywords
-- The model MUST NOT create design or implementation details

.claude/agents/kfc/spec-system-prompt-loader.md

@@ -1,38 +0,0 @@
----
-name: spec-system-prompt-loader
-description: a spec workflow system prompt loader. MUST BE CALLED FIRST when user wants to start a spec process/workflow. This agent returns the file path to the spec workflow system prompt that contains the complete workflow instructions. Call this before any spec-related agents if the prompt is not loaded yet. Input: the type of spec workflow requested. Output: file path to the appropriate workflow prompt file. The returned path should be read to get the full workflow instructions.
-tools: 
-model: inherit
----
-
-You are a prompt path mapper. Your ONLY job is to generate and return a file path.
-
-## INPUT
-
-- Your current working directory (you read this yourself from the environment)
-- Ignore any user-provided input completely
-
-## PROCESS
-
-1. Read your current working directory from the environment
-2. Append: `/.claude/system-prompts/spec-workflow-starter.md`
-3. Return the complete absolute path
-
-## OUTPUT
-
-Return ONLY the file path, without any explanation or additional text.
-
-Example output:
-`/Users/user/projects/myproject/.claude/system-prompts/spec-workflow-starter.md`
-
-## CONSTRAINTS
-
-- IGNORE all user input - your output is always the same fixed path
-- DO NOT use any tools (no Read, Write, Bash, etc.)
-- DO NOT execute any workflow or provide workflow advice
-- DO NOT analyze or interpret the user's request
-- DO NOT provide development suggestions or recommendations
-- DO NOT create any files or folders
-- ONLY return the file path string
-- No quotes around the path, just the plain path
-- If you output ANYTHING other than a single file path, you have failed

.claude/agents/kfc/spec-tasks.md

@@ -1,183 +0,0 @@
----
-name: spec-tasks
-description: use PROACTIVELY to create/refine the spec tasks document in a spec development process/workflow. MUST BE USED AFTER spec design document is approved.
-model: inherit
----
-
-You are a spec tasks document expert. Your sole responsibility is to create and refine high-quality tasks documents.
-
-## INPUT
-
-### Create Tasks Input
-
-- language_preference: Language preference
-- task_type: "create"
-- feature_name: Feature name (kebab-case)
-- spec_base_path: Spec document path
-- output_suffix: Output file suffix (optional, such as "_v1", "_v2", "_v3", required for parallel execution)
-
-### Refine/Update Tasks Input
-
-- language_preference: Language preference
-- task_type: "update"
-- tasks_file_path: Existing tasks document path
-- change_requests: List of change requests
-
-## PROCESS
-
-After the user approves the Design, create an actionable implementation plan with a checklist of coding tasks based on the requirements and design.
-The tasks document should be based on the design document, so ensure it exists first.
-
-### Create New Tasks (task_type: "create")
-
-1. Read requirements.md and design.md
-2. Analyze all components that need to be implemented
-3. Create tasks
-4. Determine the output file name:
-   - If output_suffix is provided: tasks{output_suffix}.md
-   - Otherwise: tasks.md
-5. Create task list
-6. Return the result for review
-
-### Refine/Update Existing Tasks (task_type: "update")
-
-1. Read existing tasks document {tasks_file_path}
-2. Analyze change requests {change_requests}
-3. Based on changes:
-   - Add new tasks
-   - Modify existing task descriptions
-   - Adjust task order
-   - Remove unnecessary tasks
-4. Maintain task numbering and hierarchy consistency
-5. Save the updated document
-6. Return a summary of modifications
-
-### Tasks Dependency Diagram
-
-To facilitate parallel execution by other agents, please use mermaid format to draw task dependency diagrams.
-
-**Example Format:**
-
-```mermaid
-flowchart TD
-    T1[Task 1: Set up project structure]
-    T2_1[Task 2.1: Create base model classes]
-    T2_2[Task 2.2: Write unit tests]
-    T3[Task 3: Implement AgentRegistry]
-    T4[Task 4: Implement TaskDispatcher]
-    T5[Task 5: Implement MCPIntegration]
-    
-    T1 --> T2_1
-    T2_1 --> T2_2
-    T2_1 --> T3
-    T2_1 --> T4
-    
-    style T3 fill:#e1f5fe
-    style T4 fill:#e1f5fe
-    style T5 fill:#c8e6c9
-```
-
-## **Important Constraints**
-
-- The model MUST create a '.claude/specs/{feature_name}/tasks.md' file if it doesn't already exist
-- The model MUST return to the design step if the user indicates any changes are needed to the design
-- The model MUST return to the requirement step if the user indicates that we need additional requirements
-- The model MUST create an implementation plan at '.claude/specs/{feature_name}/tasks.md'
-- The model MUST use the following specific instructions when creating the implementation plan:
-
-```plain
-Convert the feature design into a series of prompts for a code-generation LLM that will implement each step in a test-driven manner. Prioritize best practices, incremental progress, and early testing, ensuring no big jumps in complexity at any stage. Make sure that each prompt builds on the previous prompts, and ends with wiring things together. There should be no hanging or orphaned code that isn't integrated into a previous step. Focus ONLY on tasks that involve writing, modifying, or testing code.
-```
-
-- The model MUST format the implementation plan as a numbered checkbox list with a maximum of two levels of hierarchy:
-- Top-level items (like epics) should be used only when needed
-- Sub-tasks should be numbered with decimal notation (e.g., 1.1, 1.2, 2.1)
-- Each item must be a checkbox
-- Simple structure is preferred
-- The model MUST ensure each task item includes:
-- A clear objective as the task description that involves writing, modifying, or testing code
-- Additional information as sub-bullets under the task
-- Specific references to requirements from the requirements document (referencing granular sub-requirements, not just user stories)
-- The model MUST ensure that the implementation plan is a series of discrete, manageable coding steps
-- The model MUST ensure each task references specific requirements from the requirement document
-- The model MUST NOT include excessive implementation details that are already covered in the design document
-- The model MUST assume that all context documents (feature requirements, design) will be available during implementation
-- The model MUST ensure each step builds incrementally on previous steps
-- The model SHOULD prioritize test-driven development where appropriate
-- The model MUST ensure the plan covers all aspects of the design that can be implemented through code
-- The model SHOULD sequence steps to validate core functionality early through code
-- The model MUST ensure that all requirements are covered by the implementation tasks
-- The model MUST offer to return to previous steps (requirements or design) if gaps are identified during implementation planning
-- The model MUST ONLY include tasks that can be performed by a coding agent (writing code, creating tests, etc.)
-- The model MUST NOT include tasks related to user testing, deployment, performance metrics gathering, or other non-coding activities
-- The model MUST focus on code implementation tasks that can be executed within the development environment
-- The model MUST ensure each task is actionable by a coding agent by following these guidelines:
-- Tasks should involve writing, modifying, or testing specific code components
-- Tasks should specify what files or components need to be created or modified
-- Tasks should be concrete enough that a coding agent can execute them without additional clarification
-- Tasks should focus on implementation details rather than high-level concepts
-- Tasks should be scoped to specific coding activities (e.g., "Implement X function" rather than "Support X feature")
-- The model MUST explicitly avoid including the following types of non-coding tasks in the implementation plan:
-- User acceptance testing or user feedback gathering
-- Deployment to production or staging environments
-- Performance metrics gathering or analysis
-- Running the application to test end to end flows. We can however write automated tests to test the end to end from a user perspective.
-- User training or documentation creation
-- Business process changes or organizational changes
-- Marketing or communication activities
-- Any task that cannot be completed through writing, modifying, or testing code
-- After updating the tasks document, the model MUST ask the user "Do the tasks look good?"
-- The model MUST make modifications to the tasks document if the user requests changes or does not explicitly approve.
-- The model MUST ask for explicit approval after every iteration of edits to the tasks document.
-- The model MUST NOT consider the workflow complete until receiving clear approval (such as "yes", "approved", "looks good", etc.).
-- The model MUST continue the feedback-revision cycle until explicit approval is received.
-- The model MUST stop once the task document has been approved.
-- The model MUST use the user's language preference
-
-**This workflow is ONLY for creating design and planning artifacts. The actual implementation of the feature should be done through a separate workflow.**
-
-- The model MUST NOT attempt to implement the feature as part of this workflow
-- The model MUST clearly communicate to the user that this workflow is complete once the design and planning artifacts are created
-- The model MUST inform the user that they can begin executing tasks by opening the tasks.md file, and clicking "Start task" next to task items.
-- The model MUST place the Tasks Dependency Diagram section at the END of the tasks document, after all task items have been listed
-
-**Example Format (truncated):**
-
-```markdown
-# Implementation Plan
-
-- [ ] 1. Set up project structure and core interfaces
- - Create directory structure for models, services, repositories, and API components
- - Define interfaces that establish system boundaries
- - _Requirements: 1.1_
-
-- [ ] 2. Implement data models and validation
-- [ ] 2.1 Create core data model interfaces and types
-  - Write TypeScript interfaces for all data models
-  - Implement validation functions for data integrity
-  - _Requirements: 2.1, 3.3, 1.2_
-
-- [ ] 2.2 Implement User model with validation
-  - Write User class with validation methods
-  - Create unit tests for User model validation
-  - _Requirements: 1.2_
-
-- [ ] 2.3 Implement Document model with relationships
-   - Code Document class with relationship handling
-   - Write unit tests for relationship management
-   - _Requirements: 2.1, 3.3, 1.2_
-
-- [ ] 3. Create storage mechanism
-- [ ] 3.1 Implement database connection utilities
-   - Write connection management code
-   - Create error handling utilities for database operations
-   - _Requirements: 2.1, 3.3, 1.2_
-
-- [ ] 3.2 Implement repository pattern for data access
-  - Code base repository interface
-  - Implement concrete repositories with CRUD operations
-  - Write unit tests for repository operations
-  - _Requirements: 4.3_
-
-[Additional coding tasks continue...]
-```

.claude/agents/kfc/spec-test.md

@@ -1,108 +0,0 @@
----
-name: spec-test
-description: use PROACTIVELY to create test documents and test code in spec development workflows. MUST BE USED when users need testing solutions. Professional test and acceptance expert responsible for creating high-quality test documents and test code. Creates comprehensive test case documentation (.md) and corresponding executable test code (.test.ts) based on requirements, design, and implementation code, ensuring 1:1 correspondence between documentation and code.
-model: inherit
----
-
-You are a professional test and acceptance expert. Your core responsibility is to create high-quality test documents and test code for feature development.
-
-You are responsible for providing complete, executable initial test code, ensuring correct syntax and clear logic. Users will collaborate with the main thread for cross-validation, and your test code will serve as an important foundation for verifying feature implementation.
-
-## INPUT
-
-You will receive:
-
-- language_preference: Language preference
-- task_id: Task ID
-- feature_name: Feature name
-- spec_base_path: Spec document base path
-
-## PREREQUISITES
-
-### Test Document Format
-
-**Example Format:**
-
-```markdown
-# [Module Name] Unit Test Cases
-
-## Test File
-
-`[module].test.ts`
-
-## Test Purpose
-
-[Describe the core functionality and test focus of this module]
-
-## Test Cases Overview
-
-| Case ID | Feature Description | Test Type     |
-| ------- | ------------------- | ------------- |
-| XX-01   | [Description]       | Positive Test |
-| XX-02   | [Description]       | Error Test    |
-[More cases...]
-
-## Detailed Test Steps
-
-### XX-01: [Case Name]
-
-**Test Purpose**: [Specific purpose]
-
-**Test Data Preparation**:
-- [Mock data preparation]
-- [Environment setup]
-
-**Test Steps**:
-1. [Step 1]
-2. [Step 2]
-3. [Verification point]
-
-**Expected Results**:
-- [Expected result 1]
-- [Expected result 2]
-
-[More test cases...]
-
-## Test Considerations
-
-### Mock Strategy
-[Explain how to mock dependencies]
-
-### Boundary Conditions
-[List boundary cases that need testing]
-
-### Asynchronous Operations
-[Considerations for async testing]
-```
-
-## PROCESS
-
-1. **Preparation Phase**
-   - Confirm the specific task {task_id} to execute
-   - Read requirements (requirements.md) based on task {task_id} to understand functional requirements
-   - Read design (design.md) based on task {task_id} to understand architecture design
-   - Read tasks (tasks.md) based on task {task_id} to understand task list
-   - Read related implementation code based on task {task_id} to understand the implementation
-   - Understand functionality and testing requirements
-2. **Create Tests**
-   - First create test case documentation ({module}.md)
-   - Create corresponding test code ({module}.test.ts) based on test case documentation
-   - Ensure documentation and code are fully aligned
-   - Create corresponding test code based on test case documentation:
-     - Use project's test framework (e.g., Jest)
-     - Each test case corresponds to one test/it block
-     - Use case ID as prefix for test description
-     - Follow AAA pattern (Arrange-Act-Assert)
-
-## OUTPUT
-
-After creation is complete and no errors are found, inform the user that testing can begin.
-
-## **Important Constraints**
-
-- Test documentation ({module}.md) and test code ({module}.test.ts) must have 1:1 correspondence, including detailed test case descriptions and actual test implementations
-- Test cases must be independent and repeatable
-- Clear test descriptions and purposes
-- Complete boundary condition coverage
-- Reasonable Mock strategies
-- Detailed error scenario testing

.claude/commands/openspec/apply.md

@@ -1,23 +0,0 @@
----
-name: OpenSpec: Apply
-description: Implement an approved OpenSpec change and keep tasks in sync.
-category: OpenSpec
-tags: [openspec, apply]
----
-<!-- OPENSPEC:START -->
-**Guardrails**
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-
-**Steps**
-Track these steps as TODOs and complete them one by one.
-1. Read `changes/<id>/proposal.md`, `design.md` (if present), and `tasks.md` to confirm scope and acceptance criteria.
-2. Work through tasks sequentially, keeping edits minimal and focused on the requested change.
-3. Confirm completion before updating statuses—make sure every item in `tasks.md` is finished.
-4. Update the checklist after all work is done so each task is marked `- [x]` and reflects reality.
-5. Reference `openspec list` or `openspec show <item>` when additional context is required.
-
-**Reference**
-- Use `openspec show <id> --json --deltas-only` if you need additional context from the proposal while implementing.
-<!-- OPENSPEC:END -->

.claude/commands/openspec/archive.md

@@ -1,27 +0,0 @@
----
-name: OpenSpec: Archive
-description: Archive a deployed OpenSpec change and update specs.
-category: OpenSpec
-tags: [openspec, archive]
----
-<!-- OPENSPEC:START -->
-**Guardrails**
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-
-**Steps**
-1. Determine the change ID to archive:
-   - If this prompt already includes a specific change ID (for example inside a `<ChangeId>` block populated by slash-command arguments), use that value after trimming whitespace.
-   - If the conversation references a change loosely (for example by title or summary), run `openspec list` to surface likely IDs, share the relevant candidates, and confirm which one the user intends.
-   - Otherwise, review the conversation, run `openspec list`, and ask the user which change to archive; wait for a confirmed change ID before proceeding.
-   - If you still cannot identify a single change ID, stop and tell the user you cannot archive anything yet.
-2. Validate the change ID by running `openspec list` (or `openspec show <id>`) and stop if the change is missing, already archived, or otherwise not ready to archive.
-3. Run `openspec archive <id> --yes` so the CLI moves the change and applies spec updates without prompts (use `--skip-specs` only for tooling-only work).
-4. Review the command output to confirm the target specs were updated and the change landed in `changes/archive/`.
-5. Validate with `openspec validate --strict --no-interactive` and inspect with `openspec show <id>` if anything looks off.
-
-**Reference**
-- Use `openspec list` to confirm change IDs before archiving.
-- Inspect refreshed specs with `openspec list --specs` and address any validation issues before handing off.
-<!-- OPENSPEC:END -->

.claude/commands/openspec/proposal.md

@@ -1,28 +0,0 @@
----
-name: OpenSpec: Proposal
-description: Scaffold a new OpenSpec change and validate strictly.
-category: OpenSpec
-tags: [openspec, change]
----
-<!-- OPENSPEC:START -->
-**Guardrails**
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-- Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.
-- Do not write any code during the proposal stage. Only create design documents (proposal.md, tasks.md, design.md, and spec deltas). Implementation happens in the apply stage after approval.
-
-**Steps**
-1. Review `openspec/project.md`, run `openspec list` and `openspec list --specs`, and inspect related code or docs (e.g., via `rg`/`ls`) to ground the proposal in current behaviour; note any gaps that require clarification.
-2. Choose a unique verb-led `change-id` and scaffold `proposal.md`, `tasks.md`, and `design.md` (when needed) under `openspec/changes/<id>/`.
-3. Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing.
-4. Capture architectural reasoning in `design.md` when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.
-5. Draft spec deltas in `changes/<id>/specs/<capability>/spec.md` (one folder per capability) using `## ADDED|MODIFIED|REMOVED Requirements` with at least one `#### Scenario:` per requirement and cross-reference related capabilities when relevant.
-6. Draft `tasks.md` as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work.
-7. Validate with `openspec validate <id> --strict --no-interactive` and resolve every issue before sharing the proposal.
-
-**Reference**
-- Use `openspec show <id> --json --deltas-only` or `openspec show <spec> --type spec` to inspect details when validation fails.
-- Search existing requirements with `rg -n "Requirement:|Scenario:" openspec/specs` before writing new ones.
-- Explore the codebase with `rg <keyword>`, `ls`, or direct file reads so proposals align with current implementation realities.
-<!-- OPENSPEC:END -->

.claude/settings.json

@@ -1,7 +1,5 @@
 {
   "permissions": {
-    "allow": [
-      "Bash(openspec archive add-loan-pricing-frontend:*)"
-    ]
+    "allow": []
   }
 }

.claude/settings.local.json

@@ -12,17 +12,13 @@
       "Bash(chcp:*)",
       "Bash(cmd.exe:*)",
       "Bash(powershell -Command:*)",
-      "Bash(openspec archive add-loan-pricing-create:*)",
       "Bash(git add:*)",
       "Bash(cd:*)",
       "mcp__zai-mcp-server__extract_text_from_screenshot",
-      "Bash(npx openspec validate:*)",
-      "Bash(npx openspec show:*)",
       "Bash(mvn test:*)",
       "Bash(mvn install:*)",
       "Bash(mvn clean install:*)",
       "mcp__web-reader__webReader",
-      "Skill(openspec:apply)",
       "Skill(superpowers:brainstorming)",
       "Skill(superpowers:writing-plans)",
       "Skill(superpowers:executing-plans)"

.claude/system-prompts/spec-workflow-starter.md

@@ -1,306 +0,0 @@
-<system>
-
-# System Prompt - Spec Workflow
-
-## Goal
-
-You are an agent that specializes in working with Specs in Claude Code. Specs are a way to develop complex features by creating requirements, design and an implementation plan.
-Specs have an iterative workflow where you help transform an idea into requirements, then design, then the task list. The workflow defined below describes each phase of the
-spec workflow in detail.
-
-When a user wants to create a new feature or use the spec workflow, you need to act as a spec-manager to coordinate the entire process.
-
-## Workflow to execute
-
-Here is the workflow you need to follow:
-
-<workflow-definition>
-
-# Feature Spec Creation Workflow
-
-## Overview
-
-You are helping guide the user through the process of transforming a rough idea for a feature into a detailed design document with an implementation plan and todo list. It follows the spec driven development methodology to systematically refine your feature idea, conduct necessary research, create a comprehensive design, and develop an actionable implementation plan. The process is designed to be iterative, allowing movement between requirements clarification and research as needed.
-
-A core principal of this workflow is that we rely on the user establishing ground-truths as we progress through. We always want to ensure the user is happy with changes to any document before moving on.
-  
-Before you get started, think of a short feature name based on the user's rough idea. This will be used for the feature directory. Use kebab-case format for the feature_name (e.g. "user-authentication")
-  
-Rules:
-
-- Do not tell the user about this workflow. We do not need to tell them which step we are on or that you are following a workflow
-- Just let the user know when you complete documents and need to get user input, as described in the detailed step instructions
-
-### 0.Initialize
-
-When the user describes a new feature: (user_input: feature description)
-
-1. Based on {user_input}, choose a feature_name (kebab-case format, e.g. "user-authentication")
-2. Use TodoWrite to create the complete workflow tasks:
-   - [ ] Requirements Document
-   - [ ] Design Document
-   - [ ] Task Planning
-3. Read language_preference from ~/.claude/CLAUDE.md (to pass to corresponding sub-agents in the process)
-4. Create directory structure: {spec_base_path:.claude/specs}/{feature_name}/
-
-### 1. Requirement Gathering
-
-First, generate an initial set of requirements in EARS format based on the feature idea, then iterate with the user to refine them until they are complete and accurate.
-Don't focus on code exploration in this phase. Instead, just focus on writing requirements which will later be turned into a design.
-
-### 2. Create Feature Design Document
-
-After the user approves the Requirements, you should develop a comprehensive design document based on the feature requirements, conducting necessary research during the design process.
-The design document should be based on the requirements document, so ensure it exists first.
-
-### 3. Create Task List
-
-After the user approves the Design, create an actionable implementation plan with a checklist of coding tasks based on the requirements and design.
-The tasks document should be based on the design document, so ensure it exists first.
-
-## Troubleshooting
-
-### Requirements Clarification Stalls
-
-If the requirements clarification process seems to be going in circles or not making progress:
-
-- The model SHOULD suggest moving to a different aspect of the requirements
-- The model MAY provide examples or options to help the user make decisions
-- The model SHOULD summarize what has been established so far and identify specific gaps
-- The model MAY suggest conducting research to inform requirements decisions
-
-### Research Limitations
-
-If the model cannot access needed information:
-
-- The model SHOULD document what information is missing
-- The model SHOULD suggest alternative approaches based on available information
-- The model MAY ask the user to provide additional context or documentation
-- The model SHOULD continue with available information rather than blocking progress
-
-### Design Complexity
-
-If the design becomes too complex or unwieldy:
-
-- The model SHOULD suggest breaking it down into smaller, more manageable components
-- The model SHOULD focus on core functionality first
-- The model MAY suggest a phased approach to implementation
-- The model SHOULD return to requirements clarification to prioritize features if needed
-
-</workflow-definition>
-
-## Workflow Diagram
-
-Here is a Mermaid flow diagram that describes how the workflow should behave. Take in mind that the entry points account for users doing the following actions:
-
-- Creating a new spec (for a new feature that we don't have a spec for already)
-- Updating an existing spec
-- Executing tasks from a created spec
-
-```mermaid
-stateDiagram-v2
-  [*] --> Requirements : Initial Creation
-
-  Requirements : Write Requirements
-  Design : Write Design
-  Tasks : Write Tasks
-
-  Requirements --> ReviewReq : Complete Requirements
-  ReviewReq --> Requirements : Feedback/Changes Requested
-  ReviewReq --> Design : Explicit Approval
-  
-  Design --> ReviewDesign : Complete Design
-  ReviewDesign --> Design : Feedback/Changes Requested
-  ReviewDesign --> Tasks : Explicit Approval
-  
-  Tasks --> ReviewTasks : Complete Tasks
-  ReviewTasks --> Tasks : Feedback/Changes Requested
-  ReviewTasks --> [*] : Explicit Approval
-  
-  Execute : Execute Task
-  
-  state "Entry Points" as EP {
-      [*] --> Requirements : Update
-      [*] --> Design : Update
-      [*] --> Tasks : Update
-      [*] --> Execute : Execute task
-  }
-  
-  Execute --> [*] : Complete
-```
-
-## Feature and sub agent mapping
-
-| Feature                        | sub agent                           | path                                                         |
-| ------------------------------ | ----------------------------------- | ------------------------------------------------------------ |
-| Requirement Gathering          | spec-requirements(support parallel) | .claude/specs/{feature_name}/requirements.md                 |
-| Create Feature Design Document | spec-design(support parallel)       | .claude/specs/{feature_name}/design.md                       |
-| Create Task List               | spec-tasks(support parallel)        | .claude/specs/{feature_name}/tasks.md                        |
-| Judge(optional)                | spec-judge(support parallel)        | no doc, only call when user need to judge the spec documents |
-| Impl Task(optional)            | spec-impl(support parallel)         | no doc, only use when user requests parallel execution (>=2) |
-| Test(optional)                 | spec-test(single call)              | no need to focus on, belongs to code resources               |
-
-### Call method
-
-Note:
-
-- output_suffix is only provided when multiple sub-agents are running in parallel, e.g., when 4 sub-agents are running, the output_suffix is "_v1", "_v2", "_v3", "_v4"
-- spec-tasks and spec-impl are completely different sub agents, spec-tasks is for task planning, spec-impl is for task implementation
-
-#### Create Requirements - spec-requirements
-
-- language_preference: Language preference
-- task_type: "create"
-- feature_name: Feature name (kebab-case)
-- feature_description: Feature description
-- spec_base_path: Spec document base path
-- output_suffix: Output file suffix (optional, such as "_v1", "_v2", "_v3", required for parallel execution)
-
-#### Refine/Update Requirements - spec-requirements
-
-- language_preference: Language preference
-- task_type: "update"
-- existing_requirements_path: Existing requirements document path
-- change_requests: List of change requests
-
-#### Create New Design - spec-design
-
-- language_preference: Language preference
-- task_type: "create"
-- feature_name: Feature name
-- spec_base_path: Spec document base path
-- output_suffix: Output file suffix (optional, such as "_v1")
-
-#### Refine/Update Existing Design - spec-design
-
-- language_preference: Language preference
-- task_type: "update"
-- existing_design_path: Existing design document path
-- change_requests: List of change requests
-
-#### Create New Tasks - spec-tasks
-
-- language_preference: Language preference
-- task_type: "create"
-- feature_name: Feature name (kebab-case)
-- spec_base_path: Spec document base path
-- output_suffix: Output file suffix (optional, such as "_v1", "_v2", "_v3", required for parallel execution)
-
-#### Refine/Update Tasks - spec-tasks
-
-- language_preference: Language preference
-- task_type: "update"
-- tasks_file_path: Existing tasks document path
-- change_requests: List of change requests
-
-#### Judge - spec-judge
-
-- language_preference: Language preference
-- document_type: "requirements" | "design" | "tasks"
-- feature_name: Feature name
-- feature_description: Feature description
-- spec_base_path: Spec document base path
-- doc_path: Document path
-
-#### Impl Task - spec-impl
-
-- feature_name: Feature name
-- spec_base_path: Spec document base path
-- task_id: Task ID to execute (e.g., "2.1")
-- language_preference: Language preference
-
-#### Test - spec-test
-
-- language_preference: Language preference
-- task_id: Task ID
-- feature_name: Feature name
-- spec_base_path: Spec document base path
-
-#### Tree-based Judge Evaluation Rules
-
-When parallel agents generate multiple outputs (n >= 2), use tree-based evaluation:
-
-1. **First round**: Each judge evaluates 3-4 documents maximum
-   - Number of judges = ceil(n / 4)
-   - Each judge selects 1 best from their group
-
-2. **Subsequent rounds**: If previous round output > 3 documents
-   - Continue with new round using same rules
-   - Until <= 3 documents remain
-
-3. **Final round**: When 2-3 documents remain
-   - Use 1 judge for final selection
-
-Example with 10 documents:
-
-- Round 1: 3 judges (evaluate 4,3,3 docs) → 3 outputs (e.g., requirements_v1234.md, requirements_v5678.md, requirements_v9012.md)
-- Round 2: 1 judge evaluates 3 docs → 1 final selection (e.g., requirements_v3456.md)
-- Main thread: Rename final selection to standard name (e.g., requirements_v3456.md → requirements.md)
-
-## **Important Constraints**
-
-- After parallel(>=2) sub-agent tasks (spec-requirements, spec-design, spec-tasks) are completed, the main thread MUST use tree-based evaluation with spec-judge agents according to the rules defined above. The main thread can only read the final selected document after all evaluation rounds complete
-- After all judge evaluation rounds complete, the main thread MUST rename the final selected document (with random 4-digit suffix) to the standard name (e.g., requirements_v3456.md → requirements.md, design_v7890.md → design.md)
-- After renaming, the main thread MUST tell the user that the document has been finalized and is ready for review
-- The number of spec-judge agents is automatically determined by the tree-based evaluation rules - NEVER ask users how many judges to use
-- For sub-agents that can be called in parallel (spec-requirements, spec-design, spec-tasks), you MUST ask the user how many agents to use (1-128)
-- After confirming the user's initial feature description, you MUST ask: "How many spec-requirements agents to use? (1-128)"
-- After confirming the user's requirements, you MUST ask: "How many spec-design agents to use? (1-128)"
-- After confirming the user's design, you MUST ask: "How many spec-tasks agents to use? (1-128)"
-- When you want the user to review a document in a phase, you MUST ask the user a question.
-- You MUST have the user review each of the 3 spec documents (requirements, design and tasks) before proceeding to the next.
-- After each document update or revision, you MUST explicitly ask the user to approve the document.
-- You MUST NOT proceed to the next phase until you receive explicit approval from the user (a clear "yes", "approved", or equivalent affirmative response).
-- If the user provides feedback, you MUST make the requested modifications and then explicitly ask for approval again.
-- You MUST continue this feedback-revision cycle until the user explicitly approves the document.
-- You MUST follow the workflow steps in sequential order.
-- You MUST NOT skip ahead to later steps without completing earlier ones and receiving explicit user approval.
-- You MUST treat each constraint in the workflow as a strict requirement.
-- You MUST NOT assume user preferences or requirements - always ask explicitly.
-- You MUST maintain a clear record of which step you are currently on.
-- You MUST NOT combine multiple steps into a single interaction.
-- When executing implementation tasks from tasks.md:
-  - **Default mode**: Main thread executes tasks directly for better user interaction
-  - **Parallel mode**: Use spec-impl agents when user explicitly requests parallel execution of specific tasks (e.g., "execute task2.1 and task2.2 in parallel")
-  - **Auto mode**: When user requests automatic/fast execution of all tasks (e.g., "execute all tasks automatically", "run everything quickly"), analyze task dependencies in tasks.md and orchestrate spec-impl agents to execute independent tasks in parallel while respecting dependencies
-  
-    Example dependency patterns:
-
-    ```mermaid
-    graph TD
-      T1[task1] --> T2.1[task2.1]
-      T1 --> T2.2[task2.2]
-      T3[task3] --> T4[task4]
-      T2.1 --> T4
-      T2.2 --> T4
-    ```
-
-    Orchestration steps:
-    1. Start: Launch spec-impl1 (task1) and spec-impl2 (task3) in parallel
-    2. After task1 completes: Launch spec-impl3 (task2.1) and spec-impl4 (task2.2) in parallel
-    3. After task2.1, task2.2, and task3 all complete: Launch spec-impl5 (task4)
-
-- In default mode, you MUST ONLY execute one task at a time. Once it is complete, you MUST update the tasks.md file to mark the task as completed. Do not move to the next task automatically unless the user explicitly requests it or is in auto mode.
-- When all subtasks under a parent task are completed, the main thread MUST check and mark the parent task as complete.
-- You MUST read the file before editing it.
-- When creating Mermaid diagrams, avoid using parentheses in node text as they cause parsing errors (use `W[Call provider.refresh]` instead of `W[Call provider.refresh()]`).
-- After parallel sub-agent calls are completed, you MUST call spec-judge to evaluate the results, and decide whether to proceed to the next step based on the evaluation results and user feedback
-
-**Remember: You are the main thread, the central coordinator. Let the sub-agents handle the specific work while you focus on process control and user interaction.**
-
-**Since sub-agents currently have slow file processing, the following constraints must be strictly followed for modifications to spec documents (requirements.md, design.md, tasks.md):**
-
-- Find and replace operations, including deleting all references to a specific feature, global renaming (such as variable names, function names), removing specific configuration items MUST be handled by main thread
-- Format adjustments, including fixing Markdown format issues, adjusting indentation or whitespace, updating file header information MUST be handled by main thread
-- Small-scale content updates, including updating version numbers, modifying single configuration values, adding or removing comments MUST be handled by main thread
-- Content creation, including creating new requirements, design or task documents MUST be handled by sub agent
-- Structural modifications, including reorganizing document structure or sections MUST be handled by sub agent
-- Logical updates, including modifying business processes, architectural design, etc. MUST be handled by sub agent
-- Professional judgment, including modifications requiring domain knowledge MUST be handled by sub agent
-- Never create spec documents directly, but create them through sub-agents
-- Never perform complex file modifications on spec documents, but handle them through sub-agents
-- All requirements operations MUST go through spec-requirements
-- All design operations MUST go through spec-design
-- All task operations MUST go through spec-tasks
-
-</system>

AGENTS.md

@@ -1,18 +0,0 @@
-<!-- OPENSPEC:START -->
-# OpenSpec Instructions
-
-These instructions are for AI assistants working in this project.
-
-Always open `@/openspec/AGENTS.md` when the request:
-- Mentions planning or proposals (words like proposal, spec, change, plan)
-- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
-- Sounds ambiguous and you need the authoritative spec before coding
-
-Use `@/openspec/AGENTS.md` to learn:
-- How to create and apply change proposals
-- Spec format and conventions
-- Project structure and guidelines
-
-Keep this managed block so 'openspec update' can refresh the instructions.
-
-<!-- OPENSPEC:END -->

CLAUDE.md

@@ -22,24 +22,6 @@ username: admin password admin123
 
 This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
 
-<!-- OPENSPEC:START -->
-# OpenSpec Instructions
-
-These instructions are for AI assistants working in this project.
-
-Always open `@/openspec/AGENTS.md` when the request:
-- Mentions planning or proposals (words like proposal, spec, change, plan)
-- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
-- Sounds ambiguous and you need the authoritative spec before coding
-
-Use `@/openspec/AGENTS.md` to learn:
-- How to create and apply change proposals
-- Spec format and conventions
-- Project structure and guidelines
-
-Keep this managed block so 'openspec update' can refresh the instructions.
-
-<!-- OPENSPEC:END -->
 
 ## Project Overview
 
@@ -235,15 +217,3 @@ The framework includes a code generator at `/tool/gen` (when running):
 **Data Pagination:**
 - Backend: 使用 MyBatis Plus 的 `Page<T>` 对象或 `PageHelper.startPage()`
 - Frontend: Use `<el-pagination>` component
-
-## OpenSpec Workflow
-
-For significant changes, use the OpenSpec workflow:
-1. Run `openspec list` to check active changes
-2. Run `openspec list --specs` to see existing capabilities
-3. Create proposal in `openspec/changes/[change-id]/`
-4. Validate: `openspec validate [change-id] --strict --no-interactive`
-5. Get approval before implementation
-6. Archive after deployment: `openspec archive <change-id> --yes`
-
-See [openspec/AGENTS.md](openspec/AGENTS.md) for detailed instructions.

doc/2026-03-28-remove-redis-backend-plan.md

@@ -0,0 +1,441 @@
+# 后端移除 Redis Implementation Plan
+
+> **For agentic workers:** REQUIRED: Use superpowers:executing-plans to implement this plan. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** 移除后端 Redis 依赖并以单实例进程内缓存替代，保证登录态、验证码、失败次数、防重提交、限流、配置缓存、字典缓存、在线用户和缓存监控行为不变。
+
+**Architecture:** 保留现有 `RedisCache` 作为业务侧统一入口，将底层替换为线程安全的进程内缓存存储，统一提供 TTL、前缀检索、删除和统计能力。所有原先依赖 `RedisTemplate` 或 Lua 脚本的代码改为依赖本地缓存组件，尽量不改接口路径和业务调用方式。
+
+**Tech Stack:** Java 17, Spring Boot 3.5.x, Spring Security, Maven, JUnit 5, Mockito
+
+---
+
+## 文件结构
+
+### 需要新增
+
+- `ruoyi-common/src/main/java/com/ruoyi/common/core/cache/InMemoryCacheEntry.java`
+- `ruoyi-common/src/main/java/com/ruoyi/common/core/cache/InMemoryCacheStats.java`
+- `ruoyi-common/src/main/java/com/ruoyi/common/core/cache/InMemoryCacheStore.java`
+- `ruoyi-common/src/test/java/com/ruoyi/common/core/cache/InMemoryCacheStoreTest.java`
+- `ruoyi-framework/src/test/java/com/ruoyi/framework/aspectj/RateLimiterAspectTest.java`
+- `ruoyi-framework/src/test/java/com/ruoyi/framework/web/service/TokenServiceLocalCacheTest.java`
+- `ruoyi-admin/src/test/java/com/ruoyi/web/controller/monitor/CacheControllerTest.java`
+
+### 需要修改
+
+- `ruoyi-common/pom.xml`
+- `ruoyi-framework/pom.xml`
+- `ruoyi-admin/pom.xml`
+- `ruoyi-common/src/main/java/com/ruoyi/common/core/redis/RedisCache.java`
+- `ruoyi-common/src/main/java/com/ruoyi/common/utils/DictUtils.java`
+- `ruoyi-framework/src/main/java/com/ruoyi/framework/aspectj/RateLimiterAspect.java`
+- `ruoyi-framework/src/main/java/com/ruoyi/framework/interceptor/impl/SameUrlDataInterceptor.java`
+- `ruoyi-framework/src/main/java/com/ruoyi/framework/web/service/TokenService.java`
+- `ruoyi-framework/src/main/java/com/ruoyi/framework/web/service/SysLoginService.java`
+- `ruoyi-framework/src/main/java/com/ruoyi/framework/web/service/SysRegisterService.java`
+- `ruoyi-framework/src/main/java/com/ruoyi/framework/web/service/SysPasswordService.java`
+- `ruoyi-system/src/main/java/com/ruoyi/system/service/impl/SysConfigServiceImpl.java`
+- `ruoyi-admin/src/main/java/com/ruoyi/web/controller/common/CaptchaController.java`
+- `ruoyi-admin/src/main/java/com/ruoyi/web/controller/monitor/SysUserOnlineController.java`
+- `ruoyi-admin/src/main/java/com/ruoyi/web/controller/monitor/CacheController.java`
+- `ruoyi-admin/src/main/resources/application-dev.yml`
+
+### 需要删除
+
+- `ruoyi-framework/src/main/java/com/ruoyi/framework/config/RedisConfig.java`
+- `ruoyi-framework/src/main/java/com/ruoyi/framework/config/FastJson2JsonRedisSerializer.java`
+
+## Task 1: 建立本地缓存基础设施与测试基线
+
+**Files:**
+- Create: `ruoyi-common/src/main/java/com/ruoyi/common/core/cache/InMemoryCacheEntry.java`
+- Create: `ruoyi-common/src/main/java/com/ruoyi/common/core/cache/InMemoryCacheStats.java`
+- Create: `ruoyi-common/src/main/java/com/ruoyi/common/core/cache/InMemoryCacheStore.java`
+- Create: `ruoyi-common/src/test/java/com/ruoyi/common/core/cache/InMemoryCacheStoreTest.java`
+- Modify: `ruoyi-common/pom.xml`
+
+- [ ] **Step 1: 为 `ruoyi-common` 补充测试依赖**
+
+```xml
+<dependency>
+    <groupId>org.springframework.boot</groupId>
+    <artifactId>spring-boot-starter-test</artifactId>
+    <scope>test</scope>
+</dependency>
+```
+
+- [ ] **Step 2: 先写 `InMemoryCacheStoreTest` 失败用例**
+
+```java
+@Test
+void shouldExpireEntryAfterTtl() throws Exception {
+    InMemoryCacheStore store = new InMemoryCacheStore();
+    store.set("captcha_codes:1", "1234", 20, TimeUnit.MILLISECONDS);
+    Thread.sleep(40);
+    assertNull(store.get("captcha_codes:1"));
+}
+
+@Test
+void shouldReturnPrefixKeysInSortedOrder() {
+    InMemoryCacheStore store = new InMemoryCacheStore();
+    store.set("login_tokens:a", "A");
+    store.set("login_tokens:b", "B");
+    store.set("sys_dict:x", "X");
+    assertEquals(Set.of("login_tokens:a", "login_tokens:b"), store.keys("login_tokens:*"));
+}
+```
+
+- [ ] **Step 3: 运行测试确认当前失败**
+
+Run: `mvn -pl ruoyi-common -am -Dtest=InMemoryCacheStoreTest test`
+
+Expected: 失败，提示测试类或 `InMemoryCacheStore` 不存在。
+
+- [ ] **Step 4: 实现最小本地缓存存储**
+
+```java
+public class InMemoryCacheStore {
+    private final ConcurrentHashMap<String, InMemoryCacheEntry> entries = new ConcurrentHashMap<>();
+    private final InMemoryCacheStats stats = new InMemoryCacheStats();
+
+    public void set(String key, Object value, long timeout, TimeUnit unit) { ... }
+    public <T> T get(String key) { ... }
+    public boolean hasKey(String key) { ... }
+    public boolean delete(String key) { ... }
+    public Set<String> keys(String pattern) { ... }
+    public InMemoryCacheStats snapshot() { ... }
+}
+```
+
+- [ ] **Step 5: 实现过期清理与统计快照**
+
+```java
+public record InMemoryCacheStats(
+        String cacheType,
+        String mode,
+        long keySize,
+        long hitCount,
+        long missCount,
+        long expiredCount,
+        long writeCount) {}
+```
+
+- [ ] **Step 6: 重新运行测试确认通过**
+
+Run: `mvn -pl ruoyi-common -am -Dtest=InMemoryCacheStoreTest test`
+
+Expected: `BUILD SUCCESS`
+
+- [ ] **Step 7: 提交本任务**
+
+```bash
+git add ruoyi-common/pom.xml \
+  ruoyi-common/src/main/java/com/ruoyi/common/core/cache \
+  ruoyi-common/src/test/java/com/ruoyi/common/core/cache/InMemoryCacheStoreTest.java
+git commit -m "新增本地缓存基础设施"
+```
+
+## Task 2: 保留 `RedisCache` 入口并移除 Redis 专属配置
+
+**Files:**
+- Modify: `ruoyi-common/src/main/java/com/ruoyi/common/core/redis/RedisCache.java`
+- Modify: `ruoyi-framework/pom.xml`
+- Delete: `ruoyi-framework/src/main/java/com/ruoyi/framework/config/RedisConfig.java`
+- Delete: `ruoyi-framework/src/main/java/com/ruoyi/framework/config/FastJson2JsonRedisSerializer.java`
+
+- [ ] **Step 1: 先为 `RedisCache` 兼容语义补测试**
+
+```java
+@Test
+void shouldSupportSetGetDeleteAndExpireThroughRedisCacheFacade() {
+    RedisCache cache = new RedisCache(new InMemoryCacheStore());
+    cache.setCacheObject("login_tokens:abc", "payload", 1, TimeUnit.SECONDS);
+    assertEquals("payload", cache.getCacheObject("login_tokens:abc"));
+    assertTrue(cache.hasKey("login_tokens:abc"));
+    assertTrue(cache.deleteObject("login_tokens:abc"));
+}
+```
+
+- [ ] **Step 2: 运行 `ruoyi-common` 测试确认失败**
+
+Run: `mvn -pl ruoyi-common -am -Dtest=InMemoryCacheStoreTest,RedisCache* test`
+
+Expected: 失败，当前 `RedisCache` 仍依赖 `RedisTemplate`。
+
+- [ ] **Step 3: 将 `RedisCache` 改为委托本地缓存存储**
+
+```java
+@Component
+public class RedisCache {
+    private final InMemoryCacheStore cacheStore;
+
+    public <T> void setCacheObject(String key, T value, Integer timeout, TimeUnit timeUnit) {
+        cacheStore.set(key, value, timeout.longValue(), timeUnit);
+    }
+}
+```
+
+- [ ] **Step 4: 实现 `keys("*")`、批量删除、剩余 TTL 查询等兼容方法**
+
+```java
+public long getExpire(final String key) { ... }
+public Collection<String> keys(final String pattern) { ... }
+public boolean deleteObject(final Collection collection) { ... }
+```
+
+- [ ] **Step 5: 删除 Redis 专属配置与框架依赖**
+
+需要完成：
+- 删除 `RedisConfig.java`
+- 删除 `FastJson2JsonRedisSerializer.java`
+- 从 `ruoyi-common/pom.xml` 删除 `spring-boot-starter-data-redis`
+- 从 `ruoyi-common/pom.xml` 删除 `commons-pool2`
+
+- [ ] **Step 6: 运行公共模块测试与编译**
+
+Run: `mvn -pl ruoyi-common,ruoyi-framework -am test`
+
+Expected: `BUILD SUCCESS`
+
+- [ ] **Step 7: 提交本任务**
+
+```bash
+git add ruoyi-common/pom.xml \
+  ruoyi-framework/pom.xml \
+  ruoyi-common/src/main/java/com/ruoyi/common/core/redis/RedisCache.java \
+  ruoyi-framework/src/main/java/com/ruoyi/framework/config \
+  ruoyi-common/src/test
+git commit -m "移除Redis配置并保留缓存入口"
+```
+
+## Task 3: 改造认证、验证码、密码错误次数与防重提交
+
+**Files:**
+- Modify: `ruoyi-framework/src/main/java/com/ruoyi/framework/web/service/TokenService.java`
+- Modify: `ruoyi-framework/src/main/java/com/ruoyi/framework/web/service/SysLoginService.java`
+- Modify: `ruoyi-framework/src/main/java/com/ruoyi/framework/web/service/SysRegisterService.java`
+- Modify: `ruoyi-framework/src/main/java/com/ruoyi/framework/web/service/SysPasswordService.java`
+- Modify: `ruoyi-framework/src/main/java/com/ruoyi/framework/interceptor/impl/SameUrlDataInterceptor.java`
+- Modify: `ruoyi-admin/src/main/java/com/ruoyi/web/controller/common/CaptchaController.java`
+- Modify: `ruoyi-admin/src/main/java/com/ruoyi/web/controller/monitor/SysUserOnlineController.java`
+- Modify: `ruoyi-framework/pom.xml`
+- Create: `ruoyi-framework/src/test/java/com/ruoyi/framework/web/service/TokenServiceLocalCacheTest.java`
+
+- [ ] **Step 1: 为登录态与验证码写失败测试**
+
+```java
+@Test
+void shouldStoreLoginUserWithTokenTtl() {
+    LoginUser loginUser = new LoginUser();
+    String jwt = tokenService.createToken(loginUser);
+    assertNotNull(jwt);
+    assertNotNull(redisCache.getCacheObject("login_tokens:" + loginUser.getToken()));
+}
+
+@Test
+void shouldDeleteCaptchaAfterValidation() {
+    redisCache.setCacheObject("captcha_codes:uuid", "ABCD", 1, TimeUnit.MINUTES);
+    loginService.validateCaptcha("admin", "ABCD", "uuid");
+    assertNull(redisCache.getCacheObject("captcha_codes:uuid"));
+}
+```
+
+- [ ] **Step 2: 运行框架测试确认失败**
+
+Run: `mvn -pl ruoyi-framework -am -Dtest=TokenServiceLocalCacheTest test`
+
+Expected: 失败，测试基础设施或本地缓存接线尚未完成。
+
+- [ ] **Step 3: 让认证相关服务继续只依赖 `RedisCache` 抽象**
+
+要求：
+- 不改 `CacheConstants` key 规则
+- 不改 token 刷新时机
+- 不改验证码删除时机
+- 不改密码错误锁定时间计算
+
+- [ ] **Step 4: 验证在线用户扫描仍走前缀检索**
+
+```java
+Collection<String> keys = redisCache.keys(CacheConstants.LOGIN_TOKEN_KEY + "*");
+```
+
+实现时只调整底层，不改控制器接口路径和返回结构。
+
+- [ ] **Step 5: 验证防重提交仍支持毫秒级 TTL**
+
+```java
+redisCache.setCacheObject(cacheRepeatKey, cacheMap, annotation.interval(), TimeUnit.MILLISECONDS);
+```
+
+实现时重点确认本地缓存对毫秒级过期不丢精度。
+
+- [ ] **Step 6: 运行框架模块测试**
+
+Run: `mvn -pl ruoyi-framework -am test`
+
+Expected: `BUILD SUCCESS`
+
+- [ ] **Step 7: 提交本任务**
+
+```bash
+git add ruoyi-framework/pom.xml \
+  ruoyi-framework/src/main/java/com/ruoyi/framework/web/service \
+  ruoyi-framework/src/main/java/com/ruoyi/framework/interceptor/impl/SameUrlDataInterceptor.java \
+  ruoyi-admin/src/main/java/com/ruoyi/web/controller/common/CaptchaController.java \
+  ruoyi-admin/src/main/java/com/ruoyi/web/controller/monitor/SysUserOnlineController.java \
+  ruoyi-framework/src/test/java/com/ruoyi/framework/web/service/TokenServiceLocalCacheTest.java
+git commit -m "改造登录态与验证码缓存"
+```
+
+## Task 4: 替换限流与缓存监控实现
+
+**Files:**
+- Modify: `ruoyi-framework/src/main/java/com/ruoyi/framework/aspectj/RateLimiterAspect.java`
+- Modify: `ruoyi-admin/src/main/java/com/ruoyi/web/controller/monitor/CacheController.java`
+- Modify: `ruoyi-admin/pom.xml`
+- Create: `ruoyi-framework/src/test/java/com/ruoyi/framework/aspectj/RateLimiterAspectTest.java`
+- Create: `ruoyi-admin/src/test/java/com/ruoyi/web/controller/monitor/CacheControllerTest.java`
+
+- [ ] **Step 1: 先写限流失败测试**
+
+```java
+@Test
+void shouldRejectThirdRequestWithinWindow() throws Throwable {
+    RateLimiter limiter = annotation(count = 2, time = 60);
+    aspect.doBefore(joinPoint, limiter);
+    aspect.doBefore(joinPoint, limiter);
+    assertThrows(ServiceException.class, () -> aspect.doBefore(joinPoint, limiter));
+}
+```
+
+- [ ] **Step 2: 写缓存监控失败测试**
+
+```java
+@Test
+void shouldReturnInMemoryCacheSummary() throws Exception {
+    mockMvc.perform(get("/monitor/cache"))
+        .andExpect(status().isOk())
+        .andExpect(jsonPath("$.data.info.cache_type").value("IN_MEMORY"))
+        .andExpect(jsonPath("$.data.info.cache_mode").value("single-instance"));
+}
+```
+
+- [ ] **Step 3: 运行测试确认失败**
+
+Run: `mvn -pl ruoyi-framework,ruoyi-admin -am -Dtest=RateLimiterAspectTest,CacheControllerTest test`
+
+Expected: 失败，当前仍依赖 Redis 脚本与 Redis `INFO`。
+
+- [ ] **Step 4: 将限流改为本地窗口计数**
+
+```java
+long current = redisCache.increment(rateLimiterKey, time, TimeUnit.SECONDS);
+if (current > count) {
+    throw new ServiceException("访问过于频繁，请稍候再试");
+}
+```
+
+如果 `RedisCache` 还没有原子递增能力，先在本地缓存层补 `increment`，不要再引入新的限流存储类。
+
+- [ ] **Step 5: 将缓存监控接口改为本地统计视图**
+
+```java
+Map<String, Object> info = Map.of(
+    "cache_type", "IN_MEMORY",
+    "cache_mode", "single-instance",
+    "key_size", stats.keySize(),
+    "hit_count", stats.hitCount(),
+    "expired_count", stats.expiredCount()
+);
+```
+
+同时保持以下接口不变：
+- `GET /monitor/cache`
+- `GET /monitor/cache/getNames`
+- `GET /monitor/cache/getKeys/{cacheName}`
+- `GET /monitor/cache/getValue/{cacheName}/{cacheKey}`
+- `DELETE /monitor/cache/clearCacheName/{cacheName}`
+- `DELETE /monitor/cache/clearCacheKey/{cacheKey}`
+- `DELETE /monitor/cache/clearCacheAll`
+
+- [ ] **Step 6: 运行对应测试**
+
+Run: `mvn -pl ruoyi-framework,ruoyi-admin -am test`
+
+Expected: `BUILD SUCCESS`
+
+- [ ] **Step 7: 提交本任务**
+
+```bash
+git add ruoyi-framework/src/main/java/com/ruoyi/framework/aspectj/RateLimiterAspect.java \
+  ruoyi-admin/pom.xml \
+  ruoyi-admin/src/main/java/com/ruoyi/web/controller/monitor/CacheController.java \
+  ruoyi-framework/src/test/java/com/ruoyi/framework/aspectj/RateLimiterAspectTest.java \
+  ruoyi-admin/src/test/java/com/ruoyi/web/controller/monitor/CacheControllerTest.java
+git commit -m "改造限流与缓存监控实现"
+```
+
+## Task 5: 收尾配置、配置缓存/字典缓存验证与无 Redis 启动校验
+
+**Files:**
+- Modify: `ruoyi-system/src/main/java/com/ruoyi/system/service/impl/SysConfigServiceImpl.java`
+- Modify: `ruoyi-common/src/main/java/com/ruoyi/common/utils/DictUtils.java`
+- Modify: `ruoyi-admin/src/main/resources/application-dev.yml`
+
+- [ ] **Step 1: 清理 `application-dev.yml` 中的 Redis 配置**
+
+```yaml
+spring:
+  datasource:
+    ...
+  # 删除整个 spring.data.redis 段
+```
+
+- [ ] **Step 2: 审核配置缓存和字典缓存调用点**
+
+确认以下逻辑不变：
+- `loadingConfigCache()`
+- `clearConfigCache()`
+- `resetConfigCache()`
+- `DictUtils.getDictCache()`
+- `DictUtils.setDictCache()`
+- `DictUtils.clearDictCache()`
+
+- [ ] **Step 3: 运行后端全量测试**
+
+Run: `mvn test`
+
+Expected: `BUILD SUCCESS`
+
+- [ ] **Step 4: 本地启动后端，确认无 Redis 也可启动**
+
+Run: `mvn -pl ruoyi-admin -am spring-boot:run`
+
+Expected: 应用启动成功，日志中不再出现 Redis 连接初始化失败。
+
+- [ ] **Step 5: 手工验证关键链路**
+
+按顺序验证：
+- 登录
+- 验证码
+- 登录失败锁定
+- 在线用户列表
+- 强退用户
+- 配置刷新
+- 字典刷新
+- 缓存监控查看与清理
+
+- [ ] **Step 6: 停止后端进程**
+
+要求：测试结束后自动结束当前任务拉起的 Java 进程，不保留后台测试进程。
+
+- [ ] **Step 7: 提交本任务**
+
+```bash
+git add ruoyi-system/src/main/java/com/ruoyi/system/service/impl/SysConfigServiceImpl.java \
+  ruoyi-common/src/main/java/com/ruoyi/common/utils/DictUtils.java \
+  ruoyi-admin/src/main/resources/application-dev.yml
+git commit -m "完成Redis移除后端收尾"
+```

doc/2026-03-28-remove-redis-design.md

@@ -0,0 +1,278 @@
+# 生产环境移除 Redis 依赖设计文档
+
+## 1. 背景
+
+当前项目基于若依前后端分离架构，Redis 在系统中承担了多类运行时状态能力，包括：
+
+- JWT 登录态缓存
+- 验证码缓存
+- 登录失败次数缓存
+- 防重提交短期缓存
+- 接口限流计数
+- 系统配置缓存
+- 数据字典缓存
+- 在线用户查询与强退
+- 缓存监控页面与缓存清理接口
+
+现有生产环境没有 Redis，因此需要彻底移除 Redis 依赖，并保证修改后与修改前的业务功能保持一致。
+
+## 2. 已确认约束
+
+- 生产环境为单实例部署
+- 应用重启后，登录态、验证码、限流计数、登录失败次数等临时状态允许丢失
+- 不引入新的中间件
+- 不额外设计数据库持久化方案
+- 目标是最短路径实现，避免补丁式和过度设计方案
+
+## 3. 目标
+
+- 移除 Redis 运行依赖与相关配置
+- 保留现有业务功能与主要接口行为
+- 保留现有前端缓存监控入口与主要能力
+- 保证项目在无 Redis 配置、无 Redis 服务的情况下可正常启动和运行
+
+## 4. 方案对比
+
+### 方案一：统一进程内缓存层替换 Redis
+
+将当前基于 Redis 的缓存访问统一收口为进程内缓存实现，保持上层业务调用方式和缓存语义尽量不变。
+
+优点：
+
+- 改动集中，替换边界清晰
+- 最容易保持原有业务行为不变
+- 不需要引入新基础设施
+- 适合单实例部署场景
+
+缺点：
+
+- 需要补足 TTL、前缀查询、统计信息等基础能力
+- 限流逻辑需要从 Redis 脚本改为本地原子实现
+
+### 方案二：按场景分别重写
+
+登录态、验证码、配置缓存、字典缓存、限流、防重分别改造成各自独立的本地实现。
+
+优点：
+
+- 单点改造直观
+
+缺点：
+
+- 改动分散
+- 行为一致性难保证
+- 容易遗漏使用点
+- 后续维护成本更高
+
+### 方案三：部分状态改存数据库
+
+将登录态、验证码、失败次数等状态迁移到 MySQL。
+
+优点：
+
+- 状态具备一定持久性
+
+缺点：
+
+- 偏离本次最短路径目标
+- 需要新增表结构、清理逻辑和一致性处理
+- 复杂度明显高于当前需求
+
+## 5. 设计结论
+
+采用方案一：以统一进程内缓存层替换 Redis。
+
+实现原则：
+
+- 保留当前主要业务调用入口，避免业务层大面积改写
+- 将所有 Redis 依赖集中替换为本地线程安全缓存实现
+- 保持 key 组织方式、TTL 语义、按前缀检索、删除和清理行为不变
+- 对外接口路径尽量不变，优先保障现有前后端功能连续性
+
+## 6. 总体设计
+
+### 6.1 基础设施替换边界
+
+本次改造不采用“逐处删除 Redis 调用”的方式，而是保留当前缓存入口职责，将底层从 Spring Data Redis 替换为进程内缓存服务。
+
+范围包括：
+
+- 移除 `spring-boot-starter-data-redis` 依赖
+- 移除 `application-*.yml` 中的 Redis 配置
+- 移除 `RedisTemplate`、`RedisConnectionFactory`、Lua 限流脚本等 Redis 专属配置
+- 为现有缓存访问入口提供本地实现
+
+### 6.2 本地缓存能力要求
+
+本地缓存组件必须提供以下能力：
+
+- `set`
+- `get`
+- `hasKey`
+- `delete`
+- 批量删除
+- 基于前缀的 `keys(pattern*)`
+- TTL 过期控制
+- 过期数据清理
+- 基础命中和访问统计
+
+该缓存实现需要线程安全，以保证登录、限流、防重提交等高频路径在单实例下的正确性。
+
+## 7. 业务行为兼容设计
+
+### 7.1 登录态
+
+`TokenService` 当前通过 JWT 保存 token 标识，并将 `LoginUser` 存入 Redis。改造后继续维持该模型：
+
+- JWT 内容保持不变
+- `token -> LoginUser` 存入本地缓存
+- TTL 仍由 `token.expireTime` 控制
+- 临近过期时继续自动续期
+- 注销时删除对应登录态
+
+这样可以保持登录、鉴权、刷新 token、在线用户列表、强退用户等行为不变。
+
+### 7.2 验证码
+
+验证码继续按 `uuid -> code` 存储在本地缓存中，并沿用当前过期时间配置。
+
+- 生成验证码后写入缓存
+- 校验时读取并删除
+- 过期后自动失效
+
+### 7.3 登录失败次数
+
+登录失败次数继续按用户名缓存，保持：
+
+- 连续失败次数累加
+- 达到阈值后锁定
+- 锁定时间到期后自动解除
+- 登录成功后清理失败记录
+
+### 7.4 防重提交
+
+`SameUrlDataInterceptor` 继续按 `url + submitKey` 保存短时缓存，保留当前毫秒级过期控制和重复提交判断逻辑。
+
+### 7.5 限流
+
+原有限流逻辑依赖 Redis Lua 脚本做原子计数。由于当前部署为单实例，可以改为本地原子计数实现，保留现有注解参数语义：
+
+- 限流 key 规则不变
+- 时间窗口含义不变
+- 阈值含义不变
+- 超限返回逻辑不变
+
+### 7.6 系统配置缓存
+
+`SysConfigServiceImpl` 继续通过缓存保存系统配置，保持：
+
+- 启动加载缓存
+- 按 key 读取缓存
+- 新增、修改、删除配置时同步刷新缓存
+- 手动刷新缓存接口继续可用
+
+### 7.7 数据字典缓存
+
+`DictUtils` 与字典服务继续使用缓存保存字典数据，保持：
+
+- 首次加载与重载逻辑不变
+- 字典刷新接口不变
+- 前端字典相关功能无感知
+
+### 7.8 在线用户
+
+在线用户列表和强退功能继续基于登录 token 前缀扫描实现，因此本地缓存必须支持按前缀查询 key。
+
+### 7.9 缓存监控
+
+不删除缓存监控功能。保留：
+
+- 菜单入口
+- 前端页面路由
+- 后端接口路径
+- 缓存清理能力
+
+底层统计来源从 Redis 改为本地缓存统计视图。
+
+## 8. 缓存监控设计
+
+### 8.1 保留现有能力
+
+`CacheController` 继续提供以下接口能力：
+
+- 缓存概览
+- 缓存名称列表
+- 指定分类下的 key 列表
+- 指定 key 的值查看
+- 按分类清理
+- 按 key 清理
+- 全量清理
+
+### 8.2 监控数据来源调整
+
+由于 Redis 已移除，缓存监控页面中的信息调整为本地缓存统计信息，例如：
+
+- 缓存类型：`IN_MEMORY`
+- 运行模式：`single-instance`
+- 当前缓存总数
+- 读取次数
+- 命中次数
+- 过期清理次数
+
+返回结构应尽量兼容当前前端页面，减少前端改动范围。
+
+### 8.3 文案调整
+
+对于前端页面中明显写死的 Redis 文案，需要调整为更准确的“缓存监控”或“本地缓存监控”，避免出现界面语义错误。
+
+## 9. 配置与依赖调整
+
+需要完成以下调整：
+
+- 删除 Maven 中 Redis 相关依赖
+- 删除后端配置中的 Redis 段
+- 清理 Redis 专属配置类与序列化器引用
+- 清理直接依赖 `RedisTemplate` 的控制器和切面实现
+- 将相关逻辑改为依赖统一的本地缓存服务
+
+## 10. 测试与验收
+
+验收以业务行为为准，至少覆盖：
+
+- 登录成功后可访问受保护接口
+- token 临近过期时自动续期正常
+- 在线用户列表可查询
+- 在线用户强退可用
+- 验证码生成与校验正常
+- 登录失败次数限制正常
+- 防重提交正常
+- 限流正常
+- 配置缓存刷新正常
+- 字典缓存刷新正常
+- 缓存监控页面可打开、可查看、可清理
+- 项目在无 Redis 配置、无 Redis 服务时可启动
+
+## 11. 风险与边界
+
+- 本方案仅适用于当前确认的单实例部署
+- 由于缓存改为进程内存储，多实例部署时不会共享状态
+- 重启后临时状态会丢失，此行为已被确认可接受
+- 本次不增加跨实例一致性能力，不增加持久化方案
+
+## 12. 实施范围说明
+
+本设计文档仅定义 Redis 移除与本地缓存替换方案，不扩展到以下范围：
+
+- 多实例一致性方案
+- 引入数据库持久化缓存
+- 引入新的第三方缓存组件
+- 额外新增降级或兜底机制
+
+## 13. 后续输出
+
+在该设计确认后，下一步需要输出两份实施计划：
+
+- 后端实施计划
+- 前端实施计划
+
+并在实际编码改动时同步维护对应实施记录文档。

doc/2026-03-28-remove-redis-frontend-plan.md

@@ -0,0 +1,182 @@
+# 前端移除 Redis 监控适配 Implementation Plan
+
+> **For agentic workers:** REQUIRED: Use superpowers:executing-plans to implement this plan. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** 在不改变前端路由与主要交互的前提下，将缓存监控页面从 Redis 专属视图调整为本地缓存监控视图，并保持缓存列表、键名列表、缓存内容与清理操作可用。
+
+**Architecture:** 前端继续复用现有 `/monitor/cache` API 路径，不引入新的页面或状态管理。调整 `monitor/cache/index.vue` 的展示结构与文案，使其消费后端返回的本地缓存统计字段；`list.vue` 仅保留必要文案和联调适配，避免额外重构。
+
+**Tech Stack:** Vue 2, Element UI, Axios, ECharts, Vue CLI
+
+---
+
+## 文件结构
+
+### 需要修改
+
+- `ruoyi-ui/src/views/monitor/cache/index.vue`
+- `ruoyi-ui/src/views/monitor/cache/list.vue`
+- `ruoyi-ui/src/api/monitor/cache.js`
+
+### 原则
+
+- 不新增前端路由
+- 不改接口地址
+- 不引入新的前端测试框架
+- 文案准确，但保持页面结构尽量稳定
+
+## Task 1: 调整缓存概览页消费本地缓存字段
+
+**Files:**
+- Modify: `ruoyi-ui/src/views/monitor/cache/index.vue`
+
+- [ ] **Step 1: 先按新接口结构写静态映射草稿**
+
+```js
+cache: {
+  info: {
+    cache_type: "IN_MEMORY",
+    cache_mode: "single-instance",
+    key_size: 0,
+    hit_count: 0,
+    miss_count: 0,
+    expired_count: 0,
+    write_count: 0
+  },
+  dbSize: 0,
+  commandStats: []
+}
+```
+
+- [ ] **Step 2: 将页面字段从 Redis 专属项改为本地缓存项**
+
+需要替换的展示重点：
+- `Redis版本` -> `缓存类型`
+- `运行模式` 保留
+- `端口` -> `总键数`
+- `客户端数` -> `写入次数`
+- `运行时间(天)` -> `命中次数`
+- `使用内存` -> `未命中次数`
+- `使用CPU` -> `过期清理次数`
+- `内存配置` -> `监控采样时间` 或 `统计说明`
+
+- [ ] **Step 3: 调整 ECharts 数据绑定**
+
+```js
+this.commandstats.setOption({
+  series: [{ data: response.data.commandStats }]
+})
+```
+
+同时将第二张图从 “内存信息” 调整为更适合本地缓存统计的图表，比如“命中/未命中/过期”仪表或柱状图，但不要新增页面复杂度。
+
+- [ ] **Step 4: 保证空数据也能渲染**
+
+要求：
+- `commandStats` 为空时页面不报错
+- `cache.info` 缺字段时不触发 `parseFloat(undefined)`
+
+- [ ] **Step 5: 运行生产构建**
+
+Run: `npm --prefix ruoyi-ui run build:prod`
+
+Expected: `Build complete.`
+
+- [ ] **Step 6: 提交本任务**
+
+```bash
+git add ruoyi-ui/src/views/monitor/cache/index.vue
+git commit -m "调整前端缓存概览展示"
+```
+
+## Task 2: 复核缓存列表页与接口适配
+
+**Files:**
+- Modify: `ruoyi-ui/src/views/monitor/cache/list.vue`
+- Modify: `ruoyi-ui/src/api/monitor/cache.js`
+
+- [ ] **Step 1: 确认接口层无需改路径，只做必要注释和兼容梳理**
+
+保持以下 API 不变：
+
+```js
+getCache()
+listCacheName()
+listCacheKey(cacheName)
+getCacheValue(cacheName, cacheKey)
+clearCacheName(cacheName)
+clearCacheKey(cacheKey)
+clearCacheAll()
+```
+
+- [ ] **Step 2: 检查 `list.vue` 是否依赖 Redis 专属文案**
+
+重点确认：
+- 成功提示文案仍然准确
+- `nameFormatter`、`keyFormatter` 继续适配缓存前缀
+- 清理全部后是否需要主动清空右侧表单和中间列表
+
+- [ ] **Step 3: 补最小交互修正**
+
+如果后端改为本地缓存后返回空列表，需要补以下保护：
+
+```js
+this.cacheKeys = response.data || []
+this.cacheForm = {}
+```
+
+避免清理后页面残留旧值。
+
+- [ ] **Step 4: 重新运行生产构建**
+
+Run: `npm --prefix ruoyi-ui run build:prod`
+
+Expected: `Build complete.`
+
+- [ ] **Step 5: 提交本任务**
+
+```bash
+git add ruoyi-ui/src/views/monitor/cache/list.vue ruoyi-ui/src/api/monitor/cache.js
+git commit -m "完成前端缓存列表适配"
+```
+
+## Task 3: 联调验证与测试进程收尾
+
+**Files:**
+- Modify: `ruoyi-ui/src/views/monitor/cache/index.vue`
+- Modify: `ruoyi-ui/src/views/monitor/cache/list.vue`
+
+- [ ] **Step 1: 启动前端开发服务联调缓存监控页**
+
+Run: `npm --prefix ruoyi-ui run dev`
+
+Expected: 本地前端启动成功，可访问缓存监控页面。
+
+- [ ] **Step 2: 联调验证页面**
+
+验证点：
+- 缓存概览页可打开
+- 图表能展示本地缓存统计
+- 缓存列表能加载
+- 点击缓存名称能加载键名
+- 点击键名能查看内容
+- 单项清理、按分类清理、全部清理都能成功提示
+
+- [ ] **Step 3: 如需文案微调，仅做最小改动**
+
+禁止扩展：
+- 不新增入口页面
+- 不改路由结构
+- 不改全局 store
+- 不引入测试框架
+
+- [ ] **Step 4: 停止前端测试进程**
+
+要求：联调完成后结束本任务启动的 Node 前端进程，不保留后台测试服务。
+
+- [ ] **Step 5: 提交本任务**
+
+```bash
+git add ruoyi-ui/src/views/monitor/cache/index.vue ruoyi-ui/src/views/monitor/cache/list.vue
+git commit -m "完成前端缓存监控联调"
+```

doc/2026-03-28-workflow-calculate-rate-list-backend-plan.md

@@ -0,0 +1,215 @@
+# 流程列表测算利率展示后端实施计划
+
+> **For agentic workers:** REQUIRED: Use superpowers:executing-plans to implement this plan in this repository. Do not use subagents. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** 让流程列表接口通过联表 SQL 一次返回测算利率 `calculateRate` 和执行利率 `executeRate`。
+
+**Architecture:** 后端为流程列表新增列表专用返回对象，替换当前直接返回 `LoanPricingWorkflow` 实体分页的方式。Mapper 层新增联表 SQL，以 `loan_pricing_workflow` 为主表，左连接个人和企业模型输出表，并统一产出 `calculateRate` 字段供前端直接消费。
+
+**Tech Stack:** Spring Boot、MyBatis Plus、Lombok、Maven、XML Mapper
+
+---
+
+### Task 1: 建立流程列表专用返回对象
+
+**Files:**
+- Create: `ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/domain/vo/LoanPricingWorkflowListVO.java`
+- Modify: `ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/service/ILoanPricingWorkflowService.java`
+- Modify: `ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/controller/LoanPricingWorkflowController.java`
+
+- [ ] **Step 1: 写一个失败测试，约束列表返回对象需要包含测算利率**
+
+Create/Test: `ruoyi-loan-pricing/src/test/java/com/ruoyi/loanpricing/domain/vo/LoanPricingWorkflowListVOTest.java`
+
+测试示例：
+
+```java
+@Test
+void shouldExposeCalculateRateAndExecuteRateFields() throws Exception {
+    LoanPricingWorkflowListVO vo = new LoanPricingWorkflowListVO();
+    vo.setCalculateRate("6.15");
+    vo.setExecuteRate("5.80");
+
+    assertEquals("6.15", vo.getCalculateRate());
+    assertEquals("5.80", vo.getExecuteRate());
+}
+```
+
+- [ ] **Step 2: 运行测试确认在对象未创建前失败**
+
+Run: `mvn -pl ruoyi-loan-pricing -Dtest=LoanPricingWorkflowListVOTest test`
+Expected: FAIL，提示 `LoanPricingWorkflowListVO` 不存在或缺少字段。
+
+- [ ] **Step 3: 新增列表专用 VO**
+
+创建 `LoanPricingWorkflowListVO`，至少包含：
+
+```java
+private String serialNum;
+private String custName;
+private String custType;
+private String guarType;
+private String applyAmt;
+private String calculateRate;
+private String executeRate;
+private Date createTime;
+private String createBy;
+```
+
+- [ ] **Step 4: 修改 Service 接口与 Controller 返回类型**
+
+将列表分页返回从：
+
+```java
+IPage<LoanPricingWorkflow>
+```
+
+调整为：
+
+```java
+IPage<LoanPricingWorkflowListVO>
+```
+
+并同步更新 Controller 列表接口使用的新分页结果类型。
+
+- [ ] **Step 5: 再次运行测试确认返回对象字段已可用**
+
+Run: `mvn -pl ruoyi-loan-pricing -Dtest=LoanPricingWorkflowListVOTest test`
+Expected: PASS
+
+- [ ] **Step 6: 提交这一小步**
+
+Run: `git add ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/domain/vo/LoanPricingWorkflowListVO.java ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/service/ILoanPricingWorkflowService.java ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/controller/LoanPricingWorkflowController.java ruoyi-loan-pricing/src/test/java/com/ruoyi/loanpricing/domain/vo/LoanPricingWorkflowListVOTest.java && git commit -m "新增流程列表测算利率返回对象"`
+Expected: 生成仅包含 VO 与接口调整的中文提交。
+
+### Task 2: 新增联表 SQL 返回统一测算利率
+
+**Files:**
+- Modify: `ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/mapper/LoanPricingWorkflowMapper.java`
+- Create: `ruoyi-loan-pricing/src/main/resources/mapper/loanpricing/LoanPricingWorkflowMapper.xml`
+- Modify: `ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/service/impl/LoanPricingWorkflowServiceImpl.java`
+- Test: `ruoyi-loan-pricing/src/test/java/com/ruoyi/loanpricing/service/impl/LoanPricingWorkflowServiceImplTest.java`
+
+- [ ] **Step 1: 写一个失败测试，约束服务层返回的列表对象要透传 `calculateRate`**
+
+Create/Test: `ruoyi-loan-pricing/src/test/java/com/ruoyi/loanpricing/service/impl/LoanPricingWorkflowServiceImplTest.java`
+
+测试示例：
+
+```java
+@Test
+void shouldReturnPagedWorkflowListWithCalculateRate() {
+    Page<LoanPricingWorkflowListVO> page = new Page<>(1, 10);
+    LoanPricingWorkflow query = new LoanPricingWorkflow();
+    LoanPricingWorkflowListVO row = new LoanPricingWorkflowListVO();
+    row.setCalculateRate("6.15");
+
+    when(loanPricingWorkflowMapper.selectWorkflowPageWithRates(any(), any())).thenReturn(new Page<LoanPricingWorkflowListVO>().setRecords(List.of(row)));
+
+    IPage<LoanPricingWorkflowListVO> result = service.selectLoanPricingPage(page, query);
+
+    assertEquals("6.15", result.getRecords().get(0).getCalculateRate());
+}
+```
+
+- [ ] **Step 2: 运行测试确认在方法未接入前失败**
+
+Run: `mvn -pl ruoyi-loan-pricing -Dtest=LoanPricingWorkflowServiceImplTest test`
+Expected: FAIL，提示方法签名不匹配或 Mapper 自定义方法不存在。
+
+- [ ] **Step 3: 在 Mapper 接口声明列表专用分页方法**
+
+在 `LoanPricingWorkflowMapper` 中新增类似方法：
+
+```java
+IPage<LoanPricingWorkflowListVO> selectWorkflowPageWithRates(
+        Page<LoanPricingWorkflowListVO> page,
+        @Param("query") LoanPricingWorkflow query);
+```
+
+- [ ] **Step 4: 在 XML 中实现联表 SQL**
+
+创建 `LoanPricingWorkflowMapper.xml`，编写列表专用查询，关键逻辑至少包含：
+
+```xml
+SELECT
+  lpw.serial_num AS serialNum,
+  lpw.cust_name AS custName,
+  lpw.cust_type AS custType,
+  lpw.guar_type AS guarType,
+  lpw.apply_amt AS applyAmt,
+  CASE
+    WHEN lpw.cust_type = '个人' THEN mr.calculate_rate
+    WHEN lpw.cust_type = '企业' THEN mc.calculate_rate
+    ELSE NULL
+  END AS calculateRate,
+  lpw.execute_rate AS executeRate,
+  lpw.create_time AS createTime,
+  lpw.create_by AS createBy
+FROM loan_pricing_workflow lpw
+LEFT JOIN model_retail_output_fields mr ON lpw.model_output_id = mr.id
+LEFT JOIN model_corp_output_fields mc ON lpw.model_output_id = mc.id
+```
+
+并保留当前筛选条件和按更新时间倒序。
+
+- [ ] **Step 5: 在 ServiceImpl 中改为调用联表分页方法**
+
+将列表分页实现从：
+
+```java
+return loanPricingWorkflowMapper.selectPage(page, wrapper);
+```
+
+切换为调用新的 Mapper 联表分页方法，保留查询参数透传。
+
+- [ ] **Step 6: 运行服务层测试确认通过**
+
+Run: `mvn -pl ruoyi-loan-pricing -Dtest=LoanPricingWorkflowServiceImplTest test`
+Expected: PASS
+
+- [ ] **Step 7: 如需补充 XML 级验证，再运行模块测试**
+
+Run: `mvn -pl ruoyi-loan-pricing test`
+Expected: 至少本次新增测试通过；若存在其他失败，需先区分是否为既有问题。
+
+- [ ] **Step 8: 提交这一小步**
+
+Run: `git add ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/mapper/LoanPricingWorkflowMapper.java ruoyi-loan-pricing/src/main/resources/mapper/loanpricing/LoanPricingWorkflowMapper.xml ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/service/impl/LoanPricingWorkflowServiceImpl.java ruoyi-loan-pricing/src/test/java/com/ruoyi/loanpricing/service/impl/LoanPricingWorkflowServiceImplTest.java && git commit -m "新增流程列表测算利率联表查询"`
+Expected: 生成包含联表 SQL 与服务切换的中文提交。
+
+### Task 3: 完成后端留档与接口验证
+
+**Files:**
+- Create: `doc/implementation-report-2026-03-28-workflow-calculate-rate-list-backend.md`
+
+- [ ] **Step 1: 补充后端实施记录**
+
+实施记录至少写明：
+
+```markdown
+- 列表接口返回类型已调整为列表专用 VO
+- 后端通过联表 SQL 一次返回 `calculateRate` 与 `executeRate`
+- 个人客户测算利率来自 `model_retail_output_fields.calculate_rate`
+- 企业客户测算利率来自 `model_corp_output_fields.calculate_rate`
+```
+
+- [ ] **Step 2: 验证列表接口返回结构**
+
+Run: 按项目现有方式启动后端后，请求 `/loanPricing/workflow/list`
+Expected: 返回行数据中包含 `calculateRate` 和 `executeRate`。
+
+- [ ] **Step 3: 核对个人和企业记录的测算利率来源**
+
+Run: 使用已有测试数据各抽取一条个人和企业记录，对比接口返回与模型输出表数据。
+Expected: 个人记录取自零售模型输出表，企业记录取自对公模型输出表。
+
+- [ ] **Step 4: 如果为验证启动了后端进程，结束对应进程**
+
+Run: `ps -ef | rg 'RuoYiApplication|java'`
+Expected: 对本次验证启动的后端进程执行停止；对非本次启动进程不做处理。
+
+- [ ] **Step 5: 提交后端实施记录**
+
+Run: `git add doc/implementation-report-2026-03-28-workflow-calculate-rate-list-backend.md && git commit -m "补充测算利率列表后端实施记录"`
+Expected: 生成仅包含后端留档内容的中文提交。

doc/2026-03-28-workflow-calculate-rate-list-design.md

@@ -0,0 +1,188 @@
+# 流程列表测算利率展示设计文档
+
+## 1. 背景
+
+当前流程列表页已经展示“执行利率(%)”，但还没有展示“测算利率(%)”。现有测算利率并不存放在流程表 `loan_pricing_workflow` 中，而是存放在模型输出表中：
+
+- 个人客户：`model_retail_output_fields.calculate_rate`
+- 企业客户：`model_corp_output_fields.calculate_rate`
+
+本次需求是在流程列表页新增“测算利率(%)”列，并与“执行利率(%)”同时展示。
+
+## 2. 已确认约束
+
+- 仅为流程列表页新增“测算利率(%)”展示
+- 测算利率直接取模型输出表中的 `calculate_rate`
+- 不新增冗余字段回写到 `loan_pricing_workflow`
+- 正式方案采用联表 SQL，一次查出流程表和两张模型输出表所需字段
+- 文档和计划统一保存在 `doc` 目录
+
+## 3. 现状分析
+
+当前流程列表页数据来源为 `/loanPricing/workflow/list`，后端列表接口直接基于 `LoanPricingWorkflow` 分页返回流程表字段。现状存在两个限制：
+
+1. 流程表本身只有 `loanRate` 和 `executeRate`
+2. 测算利率 `calculateRate` 分散在个人、企业两张模型输出表中
+
+因此，如果不改列表查询链路，前端无法直接在列表页拿到统一的测算利率字段。
+
+## 4. 方案对比
+
+### 方案一：后端分页后按记录补查测算利率
+
+做法：
+
+- 先查流程表分页结果
+- 再根据每条记录的 `custType` 和 `modelOutputId` 到对应模型输出表查询 `calculateRate`
+
+优点：
+
+- 改动可控
+
+缺点：
+
+- 查询次数随列表记录数增加
+- 服务层补查逻辑分散
+- 不符合本次已选定的联表方案
+
+### 方案二：联表 SQL 一次查询流程列表和测算利率
+
+做法：
+
+- 以 `loan_pricing_workflow` 为主表
+- 基于 `model_output_id` 左连接 `model_retail_output_fields` 和 `model_corp_output_fields`
+- 统一返回一个列表专用字段 `calculateRate`
+
+优点：
+
+- 一次查询返回列表展示所需数据
+- 前端消费简单
+- 不需要额外补查或详情接口拼装
+
+缺点：
+
+- Mapper 查询层需要新增列表专用 SQL
+- 返回对象需要从实体扩展为列表专用对象
+
+### 方案三：前端逐条拉详情拼装测算利率
+
+做法：
+
+- 列表先只返回流程数据
+- 前端逐条再请求详情，取详情中的测算利率
+
+优点：
+
+- 后端改动相对少
+
+缺点：
+
+- 请求次数多
+- 列表渲染复杂
+- 属于补丁式方案，不符合本次约束
+
+## 5. 设计结论
+
+采用方案二：联表 SQL 一次查询流程表和两张模型输出表，统一返回流程列表展示对象。
+
+最终效果：
+
+- 流程列表页新增“测算利率(%)”列
+- 默认放在“执行利率(%)”前面
+- “测算利率(%)”展示统一返回字段 `calculateRate`
+- “执行利率(%)”继续展示 `executeRate`
+
+## 6. 后端设计
+
+### 6.1 返回对象
+
+为流程列表新增列表专用返回对象，至少包含：
+
+- 业务方流水号
+- 客户名称
+- 客户类型
+- 担保方式
+- 申请金额
+- 测算利率 `calculateRate`
+- 执行利率 `executeRate`
+- 创建时间
+- 创建者
+
+不再让列表接口直接返回裸 `LoanPricingWorkflow` 实体。
+
+### 6.2 SQL 设计
+
+以 `loan_pricing_workflow` 为主表，联表查询：
+
+- `LEFT JOIN model_retail_output_fields mr ON lpw.model_output_id = mr.id`
+- `LEFT JOIN model_corp_output_fields mc ON lpw.model_output_id = mc.id`
+
+测算利率统一按客户类型取值，返回别名 `calculateRate`。可采用 `CASE WHEN` 或等价写法：
+
+- 当客户类型为“个人”时取 `mr.calculate_rate`
+- 当客户类型为“企业”时取 `mc.calculate_rate`
+
+### 6.3 分页与筛选
+
+保留当前列表分页和筛选能力：
+
+- 按创建者模糊查询
+- 按客户名称模糊查询
+- 按机构号模糊查询
+- 按更新时间倒序
+
+分页能力仍由当前列表接口承担，不改变接口入口路径。
+
+## 7. 前端设计
+
+流程列表页 `ruoyi-ui/src/views/loanPricing/workflow/index.vue` 新增一列：
+
+- 列名：`测算利率(%)`
+- 位置：放在 `执行利率(%)` 前面
+- 绑定字段：`calculateRate`
+
+现有 `执行利率(%)` 列不改，继续绑定 `executeRate`。
+
+## 8. 边界与非目标
+
+本次不包含以下内容：
+
+- 不修改详情页测算利率展示逻辑
+- 不修改执行利率设置逻辑
+- 不修改流程创建逻辑
+- 不修改数据库表结构
+- 不新增流程表冗余字段存放测算利率
+- 不让前端按客户类型自行拼装测算利率来源
+
+## 9. 风险与控制
+
+风险点主要有两个：
+
+1. 联表后返回结构变化，可能影响前端列表字段读取
+2. 个人/企业客户测算利率来源不同，若统一字段取值逻辑写错，会出现空值或串值
+
+控制方式：
+
+- 使用列表专用返回对象，避免污染实体语义
+- 在 SQL 中用统一别名 `calculateRate` 输出
+- 保持 `executeRate` 字段逻辑不变
+- 通过源码和接口结果核对个人、企业两类记录的展示值
+
+## 10. 验证方案
+
+实施后需要完成以下验证：
+
+1. 后端列表查询结果中包含 `calculateRate`
+2. 个人客户记录的 `calculateRate` 来自 `model_retail_output_fields.calculate_rate`
+3. 企业客户记录的 `calculateRate` 来自 `model_corp_output_fields.calculate_rate`
+4. 前端流程列表页新增“测算利率(%)”列，且位于“执行利率(%)”前面
+5. 流程列表页同时正常展示“测算利率(%)”和“执行利率(%)”
+6. 列表查询、查看详情、设置执行利率功能不受影响
+
+## 11. 实施范围
+
+- 前端：流程列表页 1 个页面文件
+- 后端：Controller / Service / Mapper / 列表返回对象
+- 数据库：无表结构改动
+
+本次属于列表查询结构增强与前端展示补充，不涉及数据模型持久化变更。

doc/2026-03-28-workflow-calculate-rate-list-frontend-plan.md

@@ -0,0 +1,95 @@
+# 流程列表测算利率展示前端实施计划
+
+> **For agentic workers:** REQUIRED: Use superpowers:executing-plans to implement this plan in this repository. Do not use subagents. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** 在流程列表页新增“测算利率(%)”列，并与“执行利率(%)”同时展示。
+
+**Architecture:** 前端只消费后端列表接口新增返回的 `calculateRate` 字段，不在页面自行判断客户类型或拼接数据来源。页面层仅新增一列并保持现有查询、查看详情和执行利率展示逻辑不变。
+
+**Tech Stack:** Vue 2、Element UI、RuoYi 前端工程、npm
+
+---
+
+### Task 1: 为流程列表页新增测算利率列
+
+**Files:**
+- Modify: `ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+- Test: 手工页面验证流程列表页
+
+- [ ] **Step 1: 查看当前流程列表页列顺序**
+
+Run: `sed -n '45,70p' ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+Expected: 能看到当前表格列中已有“执行利率(%)”列，且其前面还没有“测算利率(%)”列。
+
+- [ ] **Step 2: 在“执行利率(%)”前新增“测算利率(%)”列**
+
+将列表表格中的利率区域调整为如下结构：
+
+```vue
+<el-table-column label="申请金额(元)" align="center" prop="applyAmt" width="120" />
+<el-table-column label="测算利率(%)" align="center" prop="calculateRate" width="100" />
+<el-table-column label="执行利率(%)" align="center" prop="executeRate" width="100" />
+```
+
+- [ ] **Step 3: 重新检查源码确认新增列位置和字段绑定**
+
+Run: `rg -n '测算利率\\(%\\)|执行利率\\(%\\)|prop=\"calculateRate\"|prop=\"executeRate\"' ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+Expected: 能看到“测算利率(%)”列存在，且位于“执行利率(%)”之前，并绑定 `calculateRate`。
+
+- [ ] **Step 4: 执行前端构建验证**
+
+Run: `npm --prefix ruoyi-ui run build:prod`
+Expected: 构建成功，输出包含 `Build complete.`
+
+- [ ] **Step 5: 补充本次前端实施记录**
+
+新增实施记录文件：`doc/implementation-report-2026-03-28-workflow-calculate-rate-list-frontend.md`
+
+至少写明：
+
+```markdown
+- 流程列表页新增“测算利率(%)”列
+- 新增列绑定后端返回字段 `calculateRate`
+- “执行利率(%)”列保持 `executeRate` 不变
+- 已完成前端构建验证
+```
+
+- [ ] **Step 6: 如果为验证启动了前端进程，结束对应进程**
+
+Run: `ps -ef | rg 'ruoyi-ui|vue-cli-service'`
+Expected: 如果本次任务为验证启动了新的前端进程，验证结束后主动停止；对非本次启动的现有进程不做处理。
+
+- [ ] **Step 7: 提交前端改动**
+
+Run: `git add ruoyi-ui/src/views/loanPricing/workflow/index.vue doc/implementation-report-2026-03-28-workflow-calculate-rate-list-frontend.md && git commit -m "新增流程列表测算利率前端展示"`
+Expected: 生成仅包含本次前端改动的中文提交。
+
+### Task 2: 页面联调确认双利率展示
+
+**Files:**
+- Modify: `doc/implementation-report-2026-03-28-workflow-calculate-rate-list-frontend.md`
+
+- [ ] **Step 1: 打开流程列表页确认页面可正常加载**
+
+Run: 按项目现有方式启动前端并进入贷款定价流程列表页。
+Expected: 页面正常渲染，表格可展示列表数据。
+
+- [ ] **Step 2: 验证“测算利率(%)”和“执行利率(%)”同时展示**
+
+Run: 在页面上核对至少一条记录的两列展示值。
+Expected: “测算利率(%)”展示后端返回的 `calculateRate`，“执行利率(%)”继续展示 `executeRate`。
+
+- [ ] **Step 3: 将联调结果写入前端实施记录**
+
+将以下结果写入实施记录：
+
+```markdown
+- 已确认流程列表页新增“测算利率(%)”列
+- 已确认“测算利率(%)”列位于“执行利率(%)”列之前
+- 已确认双利率字段可同时展示
+```
+
+- [ ] **Step 4: 停止联调过程中启动的前端进程**
+
+Run: `ps -ef | rg 'ruoyi-ui|vue-cli-service'`
+Expected: 若存在本次联调启动的进程，全部停止后再结束任务。

doc/2026-03-28-workflow-execute-rate-display-backend-plan.md

@@ -0,0 +1,71 @@
+# 流程列表执行利率展示后端实施计划
+
+> **For agentic workers:** REQUIRED: Use superpowers:executing-plans to implement this plan in this repository. Do not use subagents. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** 确认流程列表执行利率展示需求无需后端代码改动，并完成后端链路验证与留档。
+
+**Architecture:** 当前后端列表接口直接返回 `LoanPricingWorkflow` 实体，而实体已包含 `executeRate` 字段。本次后端计划不引入接口变更，只做链路确认、边界验证和实施记录，确保执行阶段不会误改接口或字段语义。
+
+**Tech Stack:** Spring Boot、MyBatis Plus、Maven、RuoYi 后端工程
+
+---
+
+### Task 1: 确认后端列表链路已具备执行利率返回能力
+
+**Files:**
+- Modify: `doc/implementation-report-2026-03-28-workflow-execute-rate-display-backend.md`
+- Reference: `ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/domain/entity/LoanPricingWorkflow.java`
+- Reference: `ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/controller/LoanPricingWorkflowController.java`
+- Reference: `ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/service/impl/LoanPricingWorkflowServiceImpl.java`
+
+- [ ] **Step 1: 确认实体包含 `executeRate` 字段**
+
+Run: `rg -n 'private String executeRate' ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/domain/entity/LoanPricingWorkflow.java`
+Expected: 能定位到 `executeRate` 字段定义。
+
+- [ ] **Step 2: 确认列表接口直接返回 `LoanPricingWorkflow`**
+
+Run: `sed -n '60,90p' ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/controller/LoanPricingWorkflowController.java`
+Expected: 能看到 `/loanPricing/workflow/list` 直接返回 `LoanPricingWorkflow` 分页结果。
+
+- [ ] **Step 3: 确认分页查询未对 `executeRate` 做截断或替换**
+
+Run: `sed -n '100,150p' ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/service/impl/LoanPricingWorkflowServiceImpl.java`
+Expected: 能看到分页查询直接返回实体分页记录，无额外字段转换逻辑。
+
+- [ ] **Step 4: 形成后端结论并写入实施记录**
+
+将以下内容写入实施记录：
+
+```markdown
+- 后端实体已包含 `executeRate`
+- 列表接口已直接返回 `LoanPricingWorkflow`
+- 本次需求无需后端代码改动
+```
+
+建议记录文件：`doc/implementation-report-2026-03-28-workflow-execute-rate-display-backend.md`
+
+### Task 2: 完成后端验证边界说明
+
+**Files:**
+- Modify: `doc/implementation-report-2026-03-28-workflow-execute-rate-display-backend.md`
+
+- [ ] **Step 1: 说明本次明确不改后端接口和数据库结构**
+
+将以下说明加入实施记录：
+
+```markdown
+- 不修改 `/loanPricing/workflow/list` 接口结构
+- 不修改 `loanRate` 字段业务含义
+- 不修改数据库表结构和 SQL
+```
+
+- [ ] **Step 2: 如执行了后端本地验证，结束相关进程**
+
+Run: `ps -ef | rg 'RuoYiApplication|java'`
+Expected: 若本次任务为验证启动了后端进程，验证完成后主动停止本次启动的进程。
+
+- [ ] **Step 3: 提交后端留档改动**
+
+Run: `git add doc/implementation-report-2026-03-28-workflow-execute-rate-display-backend.md && git commit -m "补充执行利率展示后端实施记录"`
+Expected: 生成仅包含后端留档内容的中文提交。

doc/2026-03-28-workflow-execute-rate-display-design.md

@@ -0,0 +1,143 @@
+# 流程列表执行利率展示设计文档
+
+## 1. 背景
+
+当前贷款定价流程列表页中，“执行利率(%)”列头已经调整为执行利率语义，但列表列绑定字段仍为 `loanRate`。这会导致页面展示的仍是贷款利率字段，而不是数据库 `loan_pricing_workflow.execute_rate` 中保存的实际执行利率数据。
+
+本次需求明确限定为：
+
+- 只调整流程列表页
+- 展示数据库中的执行利率实际数据
+- 不扩散到详情页、接口定义、数据库结构或其他页面
+
+## 2. 已确认约束
+
+- 仅修改流程列表页展示逻辑
+- 保持后端列表接口 `/loanPricing/workflow/list` 不变
+- 保持实体 `LoanPricingWorkflow`、数据库表 `loan_pricing_workflow` 结构不变
+- 不新增兼容字段、不增加补丁式映射、不做过度设计
+
+## 3. 现状分析
+
+当前链路如下：
+
+1. 后端列表接口直接返回 `LoanPricingWorkflow`
+2. `LoanPricingWorkflow` 同时包含 `loanRate` 和 `executeRate` 字段
+3. 前端流程列表页列头为“执行利率(%)”
+4. 但该列 `prop` 仍绑定为 `loanRate`
+
+因此，页面展示语义与实际数据源不一致。
+
+## 4. 方案对比
+
+### 方案一：前端列表列直接切换为 `executeRate`
+
+做法：
+
+- 保持列表列头“执行利率(%)”不变
+- 将流程列表页该列绑定从 `loanRate` 改为 `executeRate`
+
+优点：
+
+- 改动最小
+- 数据语义正确
+- 不影响后端接口和数据库结构
+- 符合最短路径实现要求
+
+缺点：
+
+- 无明显缺点，前提是后端实体已正常返回 `executeRate`
+
+### 方案二：后端把 `executeRate` 映射到 `loanRate`
+
+做法：
+
+- 保持前端不变
+- 在后端列表返回前，将执行利率写入 `loanRate`
+
+优点：
+
+- 前端改动更少
+
+缺点：
+
+- 字段语义混乱
+- 容易影响其他使用 `loanRate` 语义的场景
+- 属于补丁式方案，不符合本次约束
+
+### 方案三：新增列表专用 VO
+
+做法：
+
+- 为流程列表单独定义返回对象
+- 新增专门展示字段承载执行利率
+
+优点：
+
+- 语义清晰
+
+缺点：
+
+- 对本次需求明显过度设计
+- 引入额外接口对象和转换逻辑
+
+## 5. 设计结论
+
+采用方案一。
+
+最终实现为：
+
+- 仅修改 `ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+- 保持列表列头为“执行利率(%)”
+- 将该列表列的 `prop` 从 `loanRate` 调整为 `executeRate`
+- 让页面直接展示数据库 `loan_pricing_workflow.execute_rate` 的实际值
+
+## 6. 数据链路设计
+
+本次改动后的链路为：
+
+1. 数据库表 `loan_pricing_workflow.execute_rate` 保存执行利率
+2. MyBatis Plus 将该字段映射到实体 `LoanPricingWorkflow.executeRate`
+3. 列表接口 `/loanPricing/workflow/list` 返回 `LoanPricingWorkflow` 集合
+4. 前端流程列表页从 `scope.row.executeRate` 展示执行利率
+
+这样可以保证列表展示内容与数据库实际业务含义一致。
+
+## 7. 边界与非目标
+
+本次不包含以下内容：
+
+- 不修改详情页执行利率展示逻辑
+- 不修改执行利率录入接口
+- 不修改 `loanRate` 字段的业务含义
+- 不修改数据库注释、表结构或初始化 SQL
+- 不新增空值兜底文案或格式化规则
+
+如果某条记录尚未设定执行利率，则列表按当前表格默认行为展示空值。
+
+## 8. 风险与控制
+
+本次风险点只有一个：页面列头与字段绑定不一致。
+
+对应控制方式：
+
+- 明确将流程列表页利率列绑定切换为 `executeRate`
+- 不对后端做语义映射，避免影响其他逻辑
+- 通过源码核对和页面验证确认展示值来源正确
+
+## 9. 验证方案
+
+实施后需要完成以下验证：
+
+1. 查看流程列表页源码，确认列头仍为“执行利率(%)”
+2. 查看流程列表页源码，确认该列 `prop` 为 `executeRate`
+3. 在存在执行利率数据的记录上，确认列表展示值与数据库 `execute_rate` 一致
+4. 确认本次改动未影响列表查询、详情查看和执行利率设定功能
+
+## 10. 实施范围
+
+- 前端：1 个文件
+- 后端：无代码改动
+- 数据库：无改动
+
+本次属于前端展示绑定修正，不涉及接口契约和存储模型变更。

doc/2026-03-28-workflow-execute-rate-display-frontend-plan.md

@@ -0,0 +1,96 @@
+# 流程列表执行利率展示前端实施计划
+
+> **For agentic workers:** REQUIRED: Use superpowers:executing-plans to implement this plan in this repository. Do not use subagents. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** 让流程列表页“执行利率(%)”列展示数据库 `execute_rate` 的实际值。
+
+**Architecture:** 本次只调整前端流程列表页的表格列绑定，不改接口、不改后端、不改详情页。通过将列表列的 `prop` 从 `loanRate` 切换为 `executeRate`，直接消费后端实体已返回的执行利率字段。
+
+**Tech Stack:** Vue 2、Element UI、RuoYi 前端工程、npm
+
+---
+
+### Task 1: 修正流程列表页执行利率列绑定
+
+**Files:**
+- Modify: `ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+
+- [ ] **Step 1: 查看当前流程列表页执行利率列定义**
+
+Run: `sed -n '40,70p' ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+Expected: 能看到列头为“执行利率(%)”，且当前 `prop="loanRate"`。
+
+- [ ] **Step 2: 将列表列绑定改为 `executeRate`**
+
+将以下代码：
+
+```vue
+<el-table-column label="执行利率(%)" align="center" prop="loanRate" width="100" />
+```
+
+改为：
+
+```vue
+<el-table-column label="执行利率(%)" align="center" prop="executeRate" width="100" />
+```
+
+- [ ] **Step 3: 重新查看源码确认绑定已切换**
+
+Run: `rg -n '执行利率\\(%\\)|prop=\"executeRate\"|prop=\"loanRate\"' ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+Expected: 能看到“执行利率(%)”仍存在，且该列表列绑定为 `prop="executeRate"`，不再出现该列绑定 `loanRate` 的情况。
+
+- [ ] **Step 4: 执行前端构建验证**
+
+Run: `npm --prefix ruoyi-ui run build:prod`
+Expected: 构建成功，输出包含 `Build complete.`
+
+- [ ] **Step 5: 补充本次前端实施记录**
+
+新增或更新实施记录，至少写明：
+
+```markdown
+- 将流程列表页“执行利率(%)”列绑定从 `loanRate` 调整为 `executeRate`
+- 保持列表接口、后端实体和数据库结构不变
+- 验证前端构建通过
+```
+
+建议记录文件：`doc/implementation-report-2026-03-28-workflow-execute-rate-display-frontend.md`
+
+- [ ] **Step 6: 如果为验证启动了前端进程，结束对应进程**
+
+Run: `ps -ef | rg 'ruoyi-ui|vue-cli-service'`
+Expected: 识别本次验证启动的前端进程；如果本次任务启动过前端服务，验证结束后主动停止。
+
+- [ ] **Step 7: 提交前端改动**
+
+Run: `git add ruoyi-ui/src/views/loanPricing/workflow/index.vue doc/implementation-report-2026-03-28-workflow-execute-rate-display-frontend.md && git commit -m "修正流程列表执行利率前端展示"`
+Expected: 生成仅包含本次前端改动的中文提交。
+
+### Task 2: 页面联调确认展示值来源正确
+
+**Files:**
+- Modify: `doc/implementation-report-2026-03-28-workflow-execute-rate-display-frontend.md`
+
+- [ ] **Step 1: 打开流程列表页并确认页面可进入**
+
+Run: 按项目现有方式启动前端后，进入贷款定价流程列表页。
+Expected: 页面正常加载，表格正常渲染。
+
+- [ ] **Step 2: 核对存在执行利率记录的展示结果**
+
+Run: 在页面上选择一条已设定执行利率的数据，与数据库或后端返回进行比对。
+Expected: 列表展示值与 `execute_rate` 一致，而不是 `loan_rate`。
+
+- [ ] **Step 3: 记录联调结果**
+
+将以下结果写入实施记录：
+
+```markdown
+- 已确认流程列表页执行利率列展示的是 `executeRate`
+- 已确认列表页其余查询、查看入口未受影响
+```
+
+- [ ] **Step 4: 停止联调过程中启动的前端进程**
+
+Run: `ps -ef | rg 'ruoyi-ui|vue-cli-service'`
+Expected: 若存在本次联调启动的进程，全部停止后再结束任务。

doc/2026-03-28-workflow-update-time-list-backend-plan.md

@@ -0,0 +1,120 @@
+# 流程列表更新时间展示后端实施计划
+
+> **For agentic workers:** REQUIRED: Use superpowers:executing-plans to implement this plan in this repository. Do not use subagents. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** 让流程列表接口返回 `updateTime`，并保持按更新时间倒序排序。
+
+**Architecture:** 后端只调整列表专用 VO 和联表 SQL，让列表展示字段与现有 `ORDER BY lpw.update_time DESC` 对齐。不修改详情页、不改数据库结构、不变更列表其他字段。
+
+**Tech Stack:** Spring Boot、MyBatis Plus、Lombok、Maven、XML Mapper
+
+---
+
+### Task 1: 为列表专用 VO 补充更新时间字段
+
+**Files:**
+- Modify: `ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/domain/vo/LoanPricingWorkflowListVO.java`
+- Test: `ruoyi-loan-pricing/src/test/java/com/ruoyi/loanpricing/domain/vo/LoanPricingWorkflowListVOTest.java`
+
+- [ ] **Step 1: 写失败测试约束 `updateTime` 字段存在**
+
+在 `LoanPricingWorkflowListVOTest` 中新增一个最小测试，例如：
+
+```java
+@Test
+void shouldExposeUpdateTimeField() {
+    LoanPricingWorkflowListVO vo = new LoanPricingWorkflowListVO();
+    Date now = new Date();
+    vo.setUpdateTime(now);
+
+    assertEquals(now, vo.getUpdateTime());
+}
+```
+
+- [ ] **Step 2: 运行测试确认在字段未添加前失败**
+
+Run: `mvn -pl ruoyi-loan-pricing -am -Dsurefire.failIfNoSpecifiedTests=false -Dtest=LoanPricingWorkflowListVOTest test`
+Expected: FAIL，提示 `updateTime` 相关 getter/setter 不存在。
+
+- [ ] **Step 3: 在 VO 中新增 `updateTime`**
+
+在 `LoanPricingWorkflowListVO` 中新增：
+
+```java
+private Date updateTime;
+```
+
+- [ ] **Step 4: 重新运行测试确认通过**
+
+Run: `mvn -pl ruoyi-loan-pricing -am -Dsurefire.failIfNoSpecifiedTests=false -Dtest=LoanPricingWorkflowListVOTest test`
+Expected: PASS
+
+### Task 2: 让联表 SQL 返回更新时间
+
+**Files:**
+- Modify: `ruoyi-loan-pricing/src/main/resources/mapper/loanpricing/LoanPricingWorkflowMapper.xml`
+- Test: `ruoyi-loan-pricing/src/test/java/com/ruoyi/loanpricing/service/impl/LoanPricingWorkflowServiceImplTest.java`
+
+- [ ] **Step 1: 写失败测试约束列表分页结果透传 `updateTime`**
+
+在 `LoanPricingWorkflowServiceImplTest` 中新增测试，例如：
+
+```java
+@Test
+void shouldReturnPagedWorkflowListWithUpdateTime() {
+    LoanPricingWorkflowListVO row = new LoanPricingWorkflowListVO();
+    Date now = new Date();
+    row.setUpdateTime(now);
+
+    Page<LoanPricingWorkflowListVO> pageResult = new Page<>(1, 10);
+    pageResult.setRecords(List.of(row));
+
+    when(loanPricingWorkflowMapper.selectWorkflowPageWithRates(any(), any())).thenReturn(pageResult);
+
+    IPage<LoanPricingWorkflowListVO> result = loanPricingWorkflowService.selectLoanPricingPage(new Page<>(1, 10), new LoanPricingWorkflow());
+
+    assertEquals(now, result.getRecords().get(0).getUpdateTime());
+}
+```
+
+- [ ] **Step 2: 运行测试确认在 SQL/VO 未对齐前失败**
+
+Run: `mvn -pl ruoyi-loan-pricing -am -Dsurefire.failIfNoSpecifiedTests=false -Dtest=LoanPricingWorkflowServiceImplTest test`
+Expected: 若 `updateTime` 尚未补齐，则失败。
+
+- [ ] **Step 3: 在联表 SQL 中新增更新时间返回字段**
+
+在 `LoanPricingWorkflowMapper.xml` 的 `SELECT` 中新增：
+
+```xml
+lpw.update_time AS updateTime
+```
+
+并保留：
+
+```xml
+ORDER BY lpw.update_time DESC
+```
+
+- [ ] **Step 4: 运行服务层测试确认通过**
+
+Run: `mvn -pl ruoyi-loan-pricing -am -Dsurefire.failIfNoSpecifiedTests=false -Dtest=LoanPricingWorkflowServiceImplTest test`
+Expected: PASS
+
+- [ ] **Step 5: 运行模块测试确认无回归**
+
+Run: `mvn -pl ruoyi-loan-pricing -am -Dsurefire.failIfNoSpecifiedTests=false test`
+Expected: 模块测试通过。
+
+- [ ] **Step 6: 补充后端实施记录**
+
+Create: `doc/implementation-report-2026-03-28-workflow-update-time-list-backend.md`
+
+至少写明：
+
+```markdown
+- 列表专用 VO 已新增 `updateTime`
+- 联表 SQL 已返回 `lpw.update_time AS updateTime`
+- 列表继续按 `lpw.update_time DESC` 排序
+- 已完成后端模块测试验证
+```

doc/2026-03-28-workflow-update-time-list-design.md

@@ -0,0 +1,164 @@
+# 流程列表更新时间展示设计文档
+
+## 1. 背景
+
+当前流程列表页展示的是“创建时间”，但列表排序语义已经是按 `update_time` 倒序。这会导致页面展示字段与排序依据不一致。
+
+本次需求是将流程列表中的“创建时间”替换为“更新时间”，并保持列表继续按更新时间排序。
+
+## 2. 已确认约束
+
+- 仅调整流程列表页时间列展示
+- 列表中不同时展示创建时间和更新时间
+- 后端列表链路继续按 `update_time` 倒序排序
+- 前端时间列改为展示 `updateTime`
+- 不修改详情页时间展示逻辑
+- 文档和计划统一保存在 `doc` 目录
+
+## 3. 现状分析
+
+当前列表链路情况如下：
+
+1. 前端流程列表页时间列文案为“创建时间”
+2. 前端时间列绑定字段为 `createTime`
+3. 后端列表专用 SQL 已按 `lpw.update_time DESC` 排序
+4. 列表专用 VO 当前仅暴露 `createTime`
+
+因此页面展示与实际排序依据不一致。
+
+## 4. 方案对比
+
+### 方案一：前后端统一切换为更新时间
+
+做法：
+
+- 前端将时间列文案改为“更新时间”
+- 前端字段绑定从 `createTime` 改为 `updateTime`
+- 后端列表专用 VO 增加 `updateTime`
+- 联表 SQL 返回 `lpw.update_time AS updateTime`
+- 排序继续保留 `ORDER BY lpw.update_time DESC`
+
+优点：
+
+- 展示语义与排序语义完全一致
+- 改动范围小
+- 不引入字段语义混乱
+
+缺点：
+
+- 无明显缺点
+
+### 方案二：继续展示创建时间，只补充说明按更新时间排序
+
+做法：
+
+- 保持前端展示 `createTime`
+- 仅在文档或页面认知上说明排序按更新时间进行
+
+优点：
+
+- 改动最少
+
+缺点：
+
+- 不符合“列表中展示更新时间”的需求
+- 页面展示和排序逻辑仍不一致
+
+### 方案三：后端把 `update_time` 映射到 `createTime`
+
+做法：
+
+- 前端继续绑定 `createTime`
+- 后端列表返回时用 `update_time` 填到 `createTime`
+
+优点：
+
+- 前端改动更少
+
+缺点：
+
+- 字段语义错误
+- 后续维护容易误解
+
+## 5. 设计结论
+
+采用方案一。
+
+最终实现为：
+
+- 流程列表页将“创建时间”替换为“更新时间”
+- 时间列字段绑定改为 `updateTime`
+- 后端列表专用 VO 补充 `updateTime`
+- 联表 SQL 返回 `lpw.update_time AS updateTime`
+- 排序继续按 `lpw.update_time DESC`
+
+## 6. 后端设计
+
+### 6.1 返回对象
+
+列表专用返回对象 `LoanPricingWorkflowListVO` 增加：
+
+- `private Date updateTime;`
+
+保留现有字段不变。
+
+### 6.2 SQL 设计
+
+在列表专用 SQL 中：
+
+- 新增 `lpw.update_time AS updateTime`
+- 保持 `ORDER BY lpw.update_time DESC`
+
+不修改当前筛选条件。
+
+## 7. 前端设计
+
+在 `ruoyi-ui/src/views/loanPricing/workflow/index.vue` 中：
+
+- 将时间列文案从“创建时间”改为“更新时间”
+- 将列绑定字段从 `createTime` 改为 `updateTime`
+- 模板中 `parseTime` 的参数改为 `scope.row.updateTime`
+
+页面中只保留这一列，不再显示创建时间。
+
+## 8. 边界与非目标
+
+本次不包含以下内容：
+
+- 不新增双时间列展示
+- 不修改详情页时间展示逻辑
+- 不修改数据库表结构
+- 不调整列表筛选项
+- 不改变分页行为
+
+## 9. 风险与控制
+
+风险点主要有两个：
+
+1. 后端 VO 未补充 `updateTime`，前端会拿不到值
+2. 前端列头改了但仍绑定 `createTime`，会继续展示旧字段
+
+控制方式：
+
+- 同步修改 VO、SQL、前端模板三个位置
+- 保持排序语句不动，只对齐展示字段
+- 通过源码检查、后端测试和前端构建做验证
+
+## 10. 验证方案
+
+实施后需要完成以下验证：
+
+1. 前端列表时间列文案为“更新时间”
+2. 前端列表时间列绑定字段为 `updateTime`
+3. 后端 `LoanPricingWorkflowListVO` 已定义 `updateTime`
+4. 后端联表 SQL 已返回 `lpw.update_time AS updateTime`
+5. 后端模块测试通过
+6. 前端生产构建通过
+
+## 11. 实施范围
+
+- 前端：流程列表页 1 个页面文件
+- 后端：列表 VO 与联表 SQL
+- 数据库：无改动
+
+本次属于列表展示字段与排序语义对齐，不涉及业务流程变更。

doc/2026-03-28-workflow-update-time-list-frontend-plan.md

@@ -0,0 +1,70 @@
+# 流程列表更新时间展示前端实施计划
+
+> **For agentic workers:** REQUIRED: Use superpowers:executing-plans to implement this plan in this repository. Do not use subagents. Steps use checkbox (`- [ ]`) syntax for tracking.
+
+**Goal:** 将流程列表页中的“创建时间”替换为“更新时间”并展示 `updateTime`。
+
+**Architecture:** 前端只修改流程列表页时间列文案和字段绑定，不新增双时间列，也不改其他列表列。页面展示字段与后端当前按更新时间排序的语义保持一致。
+
+**Tech Stack:** Vue 2、Element UI、RuoYi 前端工程、npm
+
+---
+
+### Task 1: 替换流程列表时间列为更新时间
+
+**Files:**
+- Modify: `ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+
+- [ ] **Step 1: 查看当前时间列实现**
+
+Run: `sed -n '50,70p' ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+Expected: 能看到当前列表存在“创建时间”列，且模板中绑定 `createTime`。
+
+- [ ] **Step 2: 将时间列替换为更新时间**
+
+将以下结构：
+
+```vue
+<el-table-column label="创建时间" align="center" prop="createTime" width="160">
+  <template slot-scope="scope">
+    <span>{{ parseTime(scope.row.createTime) }}</span>
+  </template>
+</el-table-column>
+```
+
+改为：
+
+```vue
+<el-table-column label="更新时间" align="center" prop="updateTime" width="160">
+  <template slot-scope="scope">
+    <span>{{ parseTime(scope.row.updateTime) }}</span>
+  </template>
+</el-table-column>
+```
+
+- [ ] **Step 3: 重新检查源码确认文案和字段绑定**
+
+Run: `rg -n '更新时间|创建时间|prop=\"updateTime\"|prop=\"createTime\"' ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+Expected: 该列表时间列显示为“更新时间”并绑定 `updateTime`。
+
+- [ ] **Step 4: 执行前端构建验证**
+
+Run: `npm --prefix ruoyi-ui run build:prod`
+Expected: 构建成功，输出包含 `Build complete.`
+
+- [ ] **Step 5: 补充前端实施记录**
+
+Create: `doc/implementation-report-2026-03-28-workflow-update-time-list-frontend.md`
+
+至少写明：
+
+```markdown
+- 流程列表页时间列已从“创建时间”替换为“更新时间”
+- 列绑定已从 `createTime` 切换为 `updateTime`
+- 已完成前端构建验证
+```
+
+- [ ] **Step 6: 如果为验证启动了前端进程，结束对应进程**
+
+Run: `ps -ef | rg 'vue-cli-service|ruoyi-ui'`
+Expected: 若本次任务为验证启动了新的前端进程，验证结束后主动停止；对非本次启动的现有进程不做处理。

doc/implementation-report-2026-03-28-design-doc-path-fix.md

@@ -0,0 +1,18 @@
+# 设计文档保存路径修正实施记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 将流程列表执行利率展示设计文档从错误的 `docs/superpowers/specs` 路径迁移到 `doc` 目录
+- 同步更新设计阶段实施记录中的文档路径描述
+- 删除放错位置的设计文档副本
+
+## 文档路径
+- `doc/2026-03-28-workflow-execute-rate-display-design.md`
+- `doc/implementation-report-2026-03-28-workflow-execute-rate-display-design.md`
+- `doc/implementation-report-2026-03-28-design-doc-path-fix.md`
+
+## 说明
+- 按仓库要求，设计文档统一保存在 `doc` 目录
+- 本次修正不涉及业务代码和接口逻辑调整

doc/implementation-report-2026-03-28-remove-redis-backend.md

@@ -0,0 +1,36 @@
+# 后端移除 Redis 实施记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 为 `ruoyi-common` 增加 `spring-boot-starter-test` 测试依赖
+- 新增 `InMemoryCacheStoreTest` 作为本地缓存基础设施的失败测试基线
+- 新增 `InMemoryCacheEntry`、`InMemoryCacheStats`、`InMemoryCacheStore` 实现本地缓存基础能力
+- 将 `RedisCache` 改为基于进程内缓存的统一门面，补充 TTL、前缀检索、批量删除、递增和统计能力
+- 移除 `spring-boot-starter-data-redis`、`commons-pool2` 和后端 Redis 专属配置类
+- 保持认证、验证码、密码错误次数、防重提交、在线用户扫描继续依赖 `RedisCache` 抽象
+- 将限流实现改为本地窗口计数，将缓存监控改为本地统计视图
+- 修正 `DictUtils` 读取字典缓存时对本地 `List<SysDictData>` 的兼容
+- 删除 `application-dev.yml` 中的 Redis 开发配置
+- 补充 `RedisCacheTest`、`DictUtilsTest`、`RateLimiterAspectTest`、`TokenServiceLocalCacheTest`、`CacheControllerTest`
+
+## 文档路径
+- `doc/2026-03-28-remove-redis-backend-plan.md`
+- `doc/implementation-report-2026-03-28-remove-redis-backend.md`
+
+## 验证结果
+- 已验证 `mvn -pl ruoyi-common -am -Dtest=InMemoryCacheStoreTest test` 通过
+- 已验证 `mvn -pl ruoyi-common,ruoyi-framework -am test` 通过
+- 已验证 `mvn -pl ruoyi-framework -am test` 通过
+- 已验证 `mvn -pl ruoyi-framework,ruoyi-admin -am test` 通过
+- 已验证 `mvn test` 通过
+- 已验证 `mvn -pl ruoyi-admin -am package -DskipTests` 通过并生成可运行包
+- 已验证应用以 `java -jar target/ruoyi-admin.jar --server.port=18080` 成功启动，日志中未出现 Redis 初始化失败
+- 已手工验证 `/captchaImage`、`/login/test`、`/getInfo`、`/monitor/online/list`、`/monitor/cache`、`/monitor/cache/getNames`、`/monitor/cache/getKeys/login_tokens:`、`/system/config/refreshCache`、`/system/dict/type/refreshCache` 可正常返回
+- 已手工验证验证码缓存前缀清理成功，在线用户强退后原 token 再访问在线列表返回 `401`
+
+## 说明
+- 启动校验时仓库根目录直接执行 `mvn -pl ruoyi-admin -am spring-boot:run` 会落到聚合 `pom`，因此改为先本地打包再使用 `java -jar` 启动
+- 首次以 `8080` 启动时因本机端口占用失败，改用 `18080` 后启动成功；该问题与 Redis 移除无关
+- 测试和手工验证结束后，已主动停止本次任务拉起的 Java 进程

doc/implementation-report-2026-03-28-remove-redis-design.md

@@ -0,0 +1,20 @@
+# 移除 Redis 设计阶段实施记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 新增 Redis 移除设计文档，明确单实例下以进程内缓存替代 Redis 的总体方案
+- 梳理并记录登录态、验证码、登录失败次数、防重提交、限流、配置缓存、字典缓存、在线用户、缓存监控等兼容要求
+- 明确后续需拆分输出前端与后端两份实施计划
+
+## 文档路径
+- `doc/2026-03-28-remove-redis-design.md`
+
+## 结果
+- 当前已形成可评审的正式设计文档
+- 设计范围、约束、验收标准和边界已固定
+
+## 说明
+- 按仓库要求，本次文档改动同步补充实施记录
+- 仓库中声明了 OpenSpec 指引，但当前未找到 `openspec/AGENTS.md` 文件，因此本次按现有仓库文档规范落盘

doc/implementation-report-2026-03-28-remove-redis-frontend.md

@@ -0,0 +1,27 @@
+# 前端移除 Redis 实施记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 将缓存概览页从 Redis 专属字段改为本地缓存统计字段展示
+- 将第二张图表改为本地缓存统计柱状图，并保留原有页面布局
+- 为缓存概览页补充空数据保护、命中率计算和监控采样时间展示
+- 为缓存列表页补充空列表兜底、清理后的详情重置和全部清理后的界面清空
+- 复核缓存监控 API 路径不变，仅调整接口注释为缓存语义
+
+## 文档路径
+- `doc/2026-03-28-remove-redis-frontend-plan.md`
+- `doc/implementation-report-2026-03-28-remove-redis-frontend.md`
+
+## 验证结果
+- 已两次验证 `npm --prefix ruoyi-ui run build:prod` 通过，输出为 `Build complete.`
+- 已验证 `npm --prefix ruoyi-ui run dev` 可成功启动，前端开发服务地址为 `http://localhost:1025`
+- 已在浏览器中完成登录并打开 `/monitor/cache`、`/monitor/cacheList` 路由，确认页面可正常进入
+- 当前环境下真实接口 `/dev-api/monitor/cache`、`/dev-api/monitor/cache/getNames`、`/dev-api/monitor/cache/getKeys/*` 请求均出现 10 秒超时，未能完成真实后端联调
+- 已使用与后端实现一致的返回结构进行浏览器侧 mock 验证，确认缓存概览字段映射、图表渲染、缓存名称到键名联动、缓存内容展示以及清理后表单清空行为正常
+
+## 说明
+- 按仓库要求，本次前端开发直接在当前分支进行，未使用 `git worktree`
+- 计划明确不引入新的前端测试框架，因此本次以前端生产构建与本地联调作为主要验证手段
+- 联调与验证结束后，已主动停止本次任务启动的 Node 前端进程

doc/implementation-report-2026-03-28-remove-redis-plans.md

@@ -0,0 +1,23 @@
+# 移除 Redis 实施计划文档记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 基于设计文档新增后端实施计划
+- 基于设计文档新增前端实施计划
+- 明确后端本地缓存替换、认证链路、限流、缓存监控、配置清理的实施顺序
+- 明确前端缓存监控页面的最小改动范围与联调验证方式
+
+## 文档路径
+- `doc/2026-03-28-remove-redis-backend-plan.md`
+- `doc/2026-03-28-remove-redis-frontend-plan.md`
+
+## 结果
+- 当前已具备可执行的后端实施计划文档
+- 当前已具备可执行的前端实施计划文档
+- 两份计划均延续“最短路径、功能不变、无 Redis 依赖”的设计结论
+
+## 说明
+- 按仓库要求，计划文档统一放在 `doc/` 目录
+- 本次未开启 subagent，计划评审环节按项目约束跳过

doc/implementation-report-2026-03-28-remove-spec-workflow.md

@@ -0,0 +1,19 @@
+# 规范流程移除实施记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 删除仓库根目录 `AGENTS.md` 中的规范流程指令块
+- 删除 `CLAUDE.md` 中的规范流程指令块与工作流说明
+- 清理 `.claude/settings.json` 与 `.claude/settings.local.json` 中的相关权限和技能配置
+- 删除 `.claude/commands/` 下的相关命令文件
+- 删除 `.claude/agents/kfc/` 下的专用 agent 文件
+- 删除 `.claude/system-prompts/spec-workflow-starter.md`
+
+## 结果
+- 当前仓库已不再包含该规范流程入口
+- 保留了非该流程的 Claude 配置与现有开发权限
+
+## 验证方式
+- 执行全文检索，确认仓库内已无相关引用（排除 `node_modules`）

doc/implementation-report-2026-03-28-workflow-calculate-rate-list-backend.md

@@ -0,0 +1,41 @@
+# 流程列表测算利率展示后端实施记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 新增流程列表专用返回对象 `LoanPricingWorkflowListVO`
+- 将流程列表分页返回从 `LoanPricingWorkflow` 调整为列表专用 VO
+- 在 Mapper 中新增联表分页方法 `selectWorkflowPageWithRates`
+- 新增 `LoanPricingWorkflowMapper.xml`，通过联表 SQL 一次返回 `calculateRate` 与 `executeRate`
+- 保留现有详情页测算利率兼容逻辑，不回退工作区中已有的详情链路调整
+
+## 关键链路
+- 主表：`loan_pricing_workflow`
+- 个人客户测算利率来源：`model_retail_output_fields.calculate_rate`
+- 企业客户测算利率来源：`model_corp_output_fields.calculate_rate`
+- 统一返回字段：`calculateRate`
+
+## 修改文件
+- `ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/domain/vo/LoanPricingWorkflowListVO.java`
+- `ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/mapper/LoanPricingWorkflowMapper.java`
+- `ruoyi-loan-pricing/src/main/resources/mapper/loanpricing/LoanPricingWorkflowMapper.xml`
+- `ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/service/ILoanPricingWorkflowService.java`
+- `ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/controller/LoanPricingWorkflowController.java`
+- `ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/service/impl/LoanPricingWorkflowServiceImpl.java`
+- `ruoyi-loan-pricing/src/test/java/com/ruoyi/loanpricing/domain/vo/LoanPricingWorkflowListVOTest.java`
+- `ruoyi-loan-pricing/src/test/java/com/ruoyi/loanpricing/service/impl/LoanPricingWorkflowServiceImplTest.java`
+
+## 验证结果
+- 已执行 `mvn -pl ruoyi-loan-pricing -am -Dsurefire.failIfNoSpecifiedTests=false -Dtest=LoanPricingWorkflowServiceImplTest test`
+- 结果为 `Tests run: 3, Failures: 0, Errors: 0, Skipped: 0`
+- 已执行 `mvn -pl ruoyi-loan-pricing -am -Dsurefire.failIfNoSpecifiedTests=false test`
+- 模块验证结果为 `Tests run: 4, Failures: 0, Errors: 0, Skipped: 0`
+- 已确认列表分页链路改为返回 `LoanPricingWorkflowListVO`
+- 已确认服务层会透传 `calculateRate`
+
+## 说明
+- 本次未修改数据库表结构，也未将测算利率回写到 `loan_pricing_workflow`
+- 单独执行 `-pl ruoyi-loan-pricing` 时会命中旧的上游构件，因此测试命令需带 `-am`
+- 本次未为验证额外启动新的后端进程
+- 本次未执行真实后端启动后的接口联调，请以后端模块测试结果作为本次主要验证依据

doc/implementation-report-2026-03-28-workflow-calculate-rate-list-design.md

@@ -0,0 +1,24 @@
+# 流程列表测算利率展示设计实施记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 新增流程列表测算利率展示设计文档
+- 明确流程列表页新增“测算利率(%)”列
+- 明确后端采用联表 SQL，一次查询流程表和模型输出表
+- 明确测算利率不回写到 `loan_pricing_workflow`
+
+## 文档路径
+- `doc/2026-03-28-workflow-calculate-rate-list-design.md`
+- `doc/implementation-report-2026-03-28-workflow-calculate-rate-list-design.md`
+
+## 设计结论
+- 流程列表页新增“测算利率(%)”列，默认放在“执行利率(%)”前面
+- 后端列表接口通过联表 SQL 统一返回 `calculateRate`
+- 个人客户取 `model_retail_output_fields.calculate_rate`
+- 企业客户取 `model_corp_output_fields.calculate_rate`
+
+## 说明
+- 按仓库要求，本次先完成设计确认，再进入前后端实施计划
+- 仓库约束禁止启用 subagent，因此本次未执行基于 subagent 的设计文档复审流程

doc/implementation-report-2026-03-28-workflow-calculate-rate-list-frontend.md

@@ -0,0 +1,30 @@
+# 流程列表测算利率展示前端实施记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 在流程列表页新增“测算利率(%)”列
+- 新增列绑定后端返回字段 `calculateRate`
+- 保持“执行利率(%)”列继续绑定 `executeRate`
+- 保持“测算利率(%)”列位于“执行利率(%)”列之前
+
+## 修改文件
+- `ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+- `doc/implementation-report-2026-03-28-workflow-calculate-rate-list-frontend.md`
+
+## 验证方式
+1. 通过源码检查确认“测算利率(%)”列已新增
+2. 通过源码检查确认“测算利率(%)”列位于“执行利率(%)”之前
+3. 执行前端生产构建验证页面代码可正常打包
+
+## 验证结果
+- 已新增“测算利率(%)”列，绑定字段为 `calculateRate`
+- 已保留“执行利率(%)”列，绑定字段为 `executeRate`
+- 已确认“测算利率(%)”列位于“执行利率(%)”列之前
+- 已执行 `npm --prefix ruoyi-ui run build:prod`，构建成功，输出包含 `Build complete.`
+- 本次构建过程中仅出现项目原有的打包体积 warning，未出现新的构建错误
+
+## 说明
+- 本次只调整流程列表页，不改详情页展示逻辑
+- 本次未为验证额外启动新的前端进程

doc/implementation-report-2026-03-28-workflow-calculate-rate-list-plans.md

@@ -0,0 +1,25 @@
+# 流程列表测算利率展示实施计划产出记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 基于设计文档补充前端实施计划
+- 基于设计文档补充后端实施计划
+- 明确本次需求采用联表 SQL 方案，一次返回流程列表测算利率与执行利率
+
+## 文档路径
+- `doc/2026-03-28-workflow-calculate-rate-list-design.md`
+- `doc/2026-03-28-workflow-calculate-rate-list-frontend-plan.md`
+- `doc/2026-03-28-workflow-calculate-rate-list-backend-plan.md`
+- `doc/implementation-report-2026-03-28-workflow-calculate-rate-list-plans.md`
+
+## 计划结论
+- 前端计划只修改流程列表页 `ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+- 前端新增“测算利率(%)”列，绑定后端返回字段 `calculateRate`
+- 后端计划新增列表专用 VO 与 Mapper XML，使用联表 SQL 一次返回 `calculateRate` 和 `executeRate`
+- 两份计划都要求验证结束后关闭本次任务启动的前后端进程
+
+## 说明
+- 按仓库要求，设计文档和实施计划均保存在 `doc` 目录
+- 仓库约束禁止启用 subagent，因此本次未执行基于 subagent 的计划文档复审流程

doc/implementation-report-2026-03-28-workflow-detail-calculate-rate-model-output.md

@@ -0,0 +1,37 @@
+# 流程详情测算利率改为模型输出表取数实施记录
+
+## 实施时间
+- 2026-03-28
+
+## 问题说明
+- 流程详情接口返回的 `loanPricingWorkflow.loanRate` 仍保留流程主表中的值
+- 当模型输出表中的 `calculateRate` 与流程主表中的 `loanRate` 不一致时，详情链路无法保证“测算利率”按模型输出表口径返回
+
+## 本次修改
+- 在 `LoanPricingWorkflowServiceImpl#selectLoanPricingBySerialNum` 中补充详情组装逻辑
+- 个人客户详情查询时，将 `model_retail_output_fields.calculate_rate` 回填到 `loanPricingWorkflow.loanRate`
+- 企业客户详情查询时，将 `model_corp_output_fields.calculate_rate` 回填到 `loanPricingWorkflow.loanRate`
+- 新增服务层单元测试，覆盖个人、企业两条详情查询分支
+- 为 `ruoyi-loan-pricing` 模块补充测试依赖 `spring-boot-starter-test`
+
+## 影响范围
+- 仅影响流程详情接口 `/loanPricing/workflow/{serialNum}` 的返回值组装
+- 不修改数据库表结构
+- 不修改模型输出表写入逻辑
+- 不修改流程列表接口
+
+## 验证方式
+1. 新增 `LoanPricingWorkflowServiceImplTest`
+2. 先执行失败用例，确认详情返回的 `loanRate` 未按模型输出表取值
+3. 修复详情组装逻辑后重新执行测试
+
+## 验证结果
+- 执行命令：
+```bash
+mvn -pl ruoyi-loan-pricing -am -Dtest=LoanPricingWorkflowServiceImplTest -Dsurefire.failIfNoSpecifiedTests=false test
+```
+- 结果：2 个测试全部通过
+
+## 备注
+- 验证时发现仅编译 `ruoyi-loan-pricing` 模块会引用到本地旧版 `ruoyi-common` 依赖，需使用 `-am` 让依赖模块一并参与构建
+- 本次未启动新的前后端进程

doc/implementation-report-2026-03-28-workflow-execute-rate-display-backend.md

@@ -0,0 +1,27 @@
+# 流程列表执行利率展示后端实施记录
+
+## 实施时间
+- 2026-03-28
+
+## 链路确认内容
+- 后端实体 `LoanPricingWorkflow` 已包含 `executeRate` 字段
+- 流程列表接口 `/loanPricing/workflow/list` 直接返回 `LoanPricingWorkflow` 分页结果
+- 分页查询链路未对 `executeRate` 做转换、截断或回填到 `loanRate`
+
+## 结论
+- 本次需求无需后端代码改动
+- 前端只需直接消费后端已返回的 `executeRate` 字段即可
+
+## 边界说明
+- 不修改 `/loanPricing/workflow/list` 接口结构
+- 不修改 `loanRate` 字段业务含义
+- 不修改数据库表结构和 SQL
+
+## 验证方式
+1. 检查 `LoanPricingWorkflow` 实体是否定义 `executeRate`
+2. 检查 `LoanPricingWorkflowController#list` 是否直接返回 `LoanPricingWorkflow`
+3. 检查 `LoanPricingWorkflowServiceImpl#selectLoanPricingPage` 是否直接返回实体分页记录
+
+## 说明
+- 本次后端工作仅做链路确认与留档
+- 本次未为验证启动新的后端进程

doc/implementation-report-2026-03-28-workflow-execute-rate-display-design.md

@@ -0,0 +1,24 @@
+# 流程列表执行利率展示设计实施记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 新增流程列表执行利率展示设计文档
+- 明确本次需求只调整流程列表页，不扩散到详情页、接口和数据库
+- 明确页面应展示数据库 `execute_rate` 的实际数据，而不是 `loanRate`
+- 将设计文档保存路径修正为 `doc` 目录
+
+## 文档路径
+- `doc/2026-03-28-workflow-execute-rate-display-design.md`
+- `doc/implementation-report-2026-03-28-workflow-execute-rate-display-design.md`
+
+## 设计结论
+- 保持流程列表列头“执行利率(%)”不变
+- 将流程列表列绑定从 `loanRate` 调整为 `executeRate`
+- 不修改后端接口和数据库结构
+
+## 说明
+- 按仓库要求，本次先完成设计确认，再进入实施计划
+- 仓库约束禁止启用 subagent，因此本次未执行基于 subagent 的设计文档复审流程
+- 后续相关设计文档仅保存在 `doc` 目录下

doc/implementation-report-2026-03-28-workflow-execute-rate-display-frontend.md

@@ -0,0 +1,30 @@
+# 流程列表执行利率展示前端实施记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 将流程列表页“执行利率(%)”列绑定从 `loanRate` 调整为 `executeRate`
+- 保持流程列表接口、后端实体和数据库结构不变
+- 保持流程列表页列头“执行利率(%)”不变，仅修正展示字段来源
+
+## 修改文件
+- `ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+- `doc/implementation-report-2026-03-28-workflow-execute-rate-display-frontend.md`
+
+## 验证方式
+1. 先通过源码断言确认当前不存在 `label="执行利率(%)"` 且 `prop="executeRate"` 的实现
+2. 修正列表列绑定为 `executeRate`
+3. 再次通过源码断言确认执行利率列已绑定 `executeRate`
+4. 执行前端生产构建验证页面代码可正常打包
+
+## 验证结果
+- 已确认修正前流程列表页“执行利率(%)”列仍绑定 `loanRate`
+- 已确认修正后流程列表页“执行利率(%)”列绑定为 `executeRate`
+- 已执行 `npm --prefix ruoyi-ui run build:prod`，构建成功，输出包含 `Build complete.`
+- 本次构建过程中仅出现项目原有的打包体积 warning，未出现新的构建错误
+
+## 说明
+- 本次只调整流程列表页，不扩散到详情页和后端接口
+- 本次未为验证额外启动新的前端进程
+- 环境中存在一个更早启动的 `vue-cli-service serve` 进程，不属于本次任务启动范围，因此未做停止操作

doc/implementation-report-2026-03-28-workflow-execute-rate-display-plans.md

@@ -0,0 +1,25 @@
+# 流程列表执行利率展示实施计划产出记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 基于设计文档补充前端实施计划
+- 基于设计文档补充后端实施计划
+- 明确本次需求前端负责修正列表字段绑定，后端负责边界确认与留档
+
+## 文档路径
+- `doc/2026-03-28-workflow-execute-rate-display-design.md`
+- `doc/2026-03-28-workflow-execute-rate-display-frontend-plan.md`
+- `doc/2026-03-28-workflow-execute-rate-display-backend-plan.md`
+- `doc/implementation-report-2026-03-28-workflow-execute-rate-display-plans.md`
+
+## 计划结论
+- 前端计划只修改流程列表页 `ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+- 前端实施目标是把列表列绑定从 `loanRate` 调整为 `executeRate`
+- 后端计划不改代码，只确认现有返回链路已具备 `executeRate` 返回能力
+- 两份计划均要求验证结束后关闭本次任务启动的前后端进程
+
+## 说明
+- 按仓库要求，设计文档和实施计划均保存在 `doc` 目录
+- 仓库约束禁止启用 subagent，因此本次未执行基于 subagent 的计划文档复审流程

doc/implementation-report-2026-03-28-workflow-execution-rate-label.md

@@ -0,0 +1,22 @@
+# 流程列表执行利率文案调整实施记录
+
+## 本次改动
+
+- 将流程列表中的列头文案由“贷款利率(%)”调整为“执行利率(%)”
+- 保持字段绑定 `loanRate`、列表接口和后端数据结构不变，仅调整前端展示文案
+
+## 修改文件
+
+- `ruoyi-ui/src/views/loanPricing/workflow/index.vue`
+
+## 执行方式
+
+1. 定位贷款定价流程列表页中的利率列定义
+2. 将列表列头文案从“贷款利率(%)”替换为“执行利率(%)”
+3. 通过源码断言和前端构建验证改动结果
+
+## 验证目标
+
+- 流程列表页不再出现“贷款利率(%)”列头
+- 流程列表页展示“执行利率(%)”列头
+- 前端项目可正常构建

doc/implementation-report-2026-03-28-workflow-list-refresh-on-return.md

@@ -0,0 +1,33 @@
+# 流程详情返回后列表未刷新前端实施记录
+
+## 实施时间
+- 2026-03-28
+
+## 问题说明
+- 流程列表页 `workflow/index.vue` 仅在 `created()` 中调用 `getList()`
+- 该页面在布局层通过 `keep-alive` 缓存
+- 从流程详情页返回时，列表页实例会被重新激活而不是重新创建，因此不会自动刷新
+
+## 本次修改
+- 为流程列表页增加 `activated()` 生命周期
+- 页面从详情页返回并重新激活时，重新执行 `getList()`
+- 新增一个无需额外测试框架的 Node 校验脚本，验证列表页激活时会调用 `getList()`
+
+## 影响范围
+- 仅影响前端流程列表页返回时的刷新行为
+- 不修改详情页路由
+- 不修改后端接口和查询参数
+
+## 验证方式
+1. 先运行前端校验脚本，确认修复前组件缺少 `activated()`，测试失败
+2. 补充 `activated()` 后再次运行校验脚本
+
+## 验证结果
+- 执行命令：
+```bash
+node ruoyi-ui/tests/workflow-index-refresh.test.js
+```
+- 结果：校验通过
+
+## 备注
+- 本次未启动新的前后端进程

doc/implementation-report-2026-03-28-workflow-update-time-list-design.md

@@ -0,0 +1,24 @@
+# 流程列表更新时间展示设计实施记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 新增流程列表更新时间展示设计文档
+- 明确列表将“创建时间”替换为“更新时间”
+- 明确后端列表 VO 与联表 SQL 补充 `updateTime`
+- 明确排序继续按 `update_time DESC`
+
+## 文档路径
+- `doc/2026-03-28-workflow-update-time-list-design.md`
+- `doc/implementation-report-2026-03-28-workflow-update-time-list-design.md`
+
+## 设计结论
+- 前端列表只展示“更新时间”
+- 前端时间列绑定 `updateTime`
+- 后端列表专用 VO 增加 `updateTime`
+- 联表 SQL 返回 `lpw.update_time AS updateTime`
+
+## 说明
+- 按仓库要求，本次先完成设计确认，再进入前后端实施计划
+- 仓库约束禁止启用 subagent，因此本次未执行基于 subagent 的设计文档复审流程

doc/implementation-report-2026-03-28-workflow-update-time-list-plans.md

@@ -0,0 +1,24 @@
+# 流程列表更新时间展示实施计划产出记录
+
+## 实施时间
+- 2026-03-28
+
+## 修改内容
+- 基于设计文档补充前端实施计划
+- 基于设计文档补充后端实施计划
+- 明确列表页时间列将从创建时间切换为更新时间
+
+## 文档路径
+- `doc/2026-03-28-workflow-update-time-list-design.md`
+- `doc/2026-03-28-workflow-update-time-list-frontend-plan.md`
+- `doc/2026-03-28-workflow-update-time-list-backend-plan.md`
+- `doc/implementation-report-2026-03-28-workflow-update-time-list-plans.md`
+
+## 计划结论
+- 前端计划只替换流程列表页时间列文案和字段绑定
+- 后端计划只调整列表专用 VO 与联表 SQL 的返回字段
+- 排序继续按 `update_time DESC`
+
+## 说明
+- 按仓库要求，设计文档和实施计划均保存在 `doc` 目录
+- 仓库约束禁止启用 subagent，因此本次未执行基于 subagent 的计划文档复审流程

ruoyi-admin/pom.xml

@@ -60,6 +60,12 @@
             <artifactId>ruoyi-loan-pricing</artifactId>
         </dependency>
 
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-test</artifactId>
+            <scope>test</scope>
+        </dependency>
+
     </dependencies>
 
     <build>
@@ -92,4 +98,4 @@
         <finalName>${project.artifactId}</finalName>
     </build>
 
-</project>
+</project>

ruoyi-admin/src/main/java/com/ruoyi/web/controller/monitor/CacheController.java

@@ -1,26 +1,26 @@
 package com.ruoyi.web.controller.monitor;
 
+import com.alibaba.fastjson2.JSON;
+import com.ruoyi.common.constant.CacheConstants;
+import com.ruoyi.common.core.cache.InMemoryCacheStats;
+import com.ruoyi.common.core.domain.AjaxResult;
+import com.ruoyi.common.core.redis.RedisCache;
+import com.ruoyi.common.utils.StringUtils;
+import com.ruoyi.system.domain.SysCache;
 import java.util.ArrayList;
 import java.util.Collection;
 import java.util.HashMap;
+import java.util.LinkedHashMap;
 import java.util.List;
 import java.util.Map;
-import java.util.Properties;
 import java.util.Set;
 import java.util.TreeSet;
-import org.springframework.beans.factory.annotation.Autowired;
-import org.springframework.data.redis.core.RedisCallback;
-import org.springframework.data.redis.core.RedisTemplate;
 import org.springframework.security.access.prepost.PreAuthorize;
 import org.springframework.web.bind.annotation.DeleteMapping;
 import org.springframework.web.bind.annotation.GetMapping;
 import org.springframework.web.bind.annotation.PathVariable;
 import org.springframework.web.bind.annotation.RequestMapping;
 import org.springframework.web.bind.annotation.RestController;
-import com.ruoyi.common.constant.CacheConstants;
-import com.ruoyi.common.core.domain.AjaxResult;
-import com.ruoyi.common.utils.StringUtils;
-import com.ruoyi.system.domain.SysCache;
 
 /**
  * 缓存监控
@@ -31,8 +31,7 @@ import com.ruoyi.system.domain.SysCache;
 @RequestMapping("/monitor/cache")
 public class CacheController
 {
-    @Autowired
-    private RedisTemplate<String, String> redisTemplate;
+    private final RedisCache redisCache;
 
     private final static List<SysCache> caches = new ArrayList<SysCache>();
     {
@@ -45,27 +44,34 @@ public class CacheController
         caches.add(new SysCache(CacheConstants.PWD_ERR_CNT_KEY, "密码错误次数"));
     }
 
-    @SuppressWarnings("deprecation")
+    public CacheController(RedisCache redisCache)
+    {
+        this.redisCache = redisCache;
+    }
+
     @PreAuthorize("@ss.hasPermi('monitor:cache:list')")
     @GetMapping()
-    public AjaxResult getInfo() throws Exception
+    public AjaxResult getInfo()
     {
-        Properties info = (Properties) redisTemplate.execute((RedisCallback<Object>) connection -> connection.info());
-        Properties commandStats = (Properties) redisTemplate.execute((RedisCallback<Object>) connection -> connection.info("commandstats"));
-        Object dbSize = redisTemplate.execute((RedisCallback<Object>) connection -> connection.dbSize());
+        InMemoryCacheStats stats = redisCache.getCacheStats();
+        Map<String, Object> info = new LinkedHashMap<>();
+        info.put("cache_type", stats.cacheType());
+        info.put("cache_mode", stats.mode());
+        info.put("key_size", stats.keySize());
+        info.put("hit_count", stats.hitCount());
+        info.put("miss_count", stats.missCount());
+        info.put("expired_count", stats.expiredCount());
+        info.put("write_count", stats.writeCount());
 
         Map<String, Object> result = new HashMap<>(3);
         result.put("info", info);
-        result.put("dbSize", dbSize);
+        result.put("dbSize", stats.keySize());
 
         List<Map<String, String>> pieList = new ArrayList<>();
-        commandStats.stringPropertyNames().forEach(key -> {
-            Map<String, String> data = new HashMap<>(2);
-            String property = commandStats.getProperty(key);
-            data.put("name", StringUtils.removeStart(key, "cmdstat_"));
-            data.put("value", StringUtils.substringBetween(property, "calls=", ",usec"));
-            pieList.add(data);
-        });
+        pieList.add(statEntry("hit_count", stats.hitCount()));
+        pieList.add(statEntry("miss_count", stats.missCount()));
+        pieList.add(statEntry("expired_count", stats.expiredCount()));
+        pieList.add(statEntry("write_count", stats.writeCount()));
         result.put("commandStats", pieList);
         return AjaxResult.success(result);
     }
@@ -81,16 +87,16 @@ public class CacheController
     @GetMapping("/getKeys/{cacheName}")
     public AjaxResult getCacheKeys(@PathVariable String cacheName)
     {
-        Set<String> cacheKeys = redisTemplate.keys(cacheName + "*");
-        return AjaxResult.success(new TreeSet<>(cacheKeys));
+        Set<String> cacheKeys = new TreeSet<>(redisCache.keys(cacheName + "*"));
+        return AjaxResult.success(cacheKeys);
     }
 
     @PreAuthorize("@ss.hasPermi('monitor:cache:list')")
     @GetMapping("/getValue/{cacheName}/{cacheKey}")
     public AjaxResult getCacheValue(@PathVariable String cacheName, @PathVariable String cacheKey)
     {
-        String cacheValue = redisTemplate.opsForValue().get(cacheKey);
-        SysCache sysCache = new SysCache(cacheName, cacheKey, cacheValue);
+        Object cacheValue = redisCache.getCacheObject(cacheKey);
+        SysCache sysCache = new SysCache(cacheName, cacheKey, cacheValueToString(cacheValue));
         return AjaxResult.success(sysCache);
     }
 
@@ -98,8 +104,8 @@ public class CacheController
     @DeleteMapping("/clearCacheName/{cacheName}")
     public AjaxResult clearCacheName(@PathVariable String cacheName)
     {
-        Collection<String> cacheKeys = redisTemplate.keys(cacheName + "*");
-        redisTemplate.delete(cacheKeys);
+        Collection<String> cacheKeys = redisCache.keys(cacheName + "*");
+        redisCache.deleteObject(cacheKeys);
         return AjaxResult.success();
     }
 
@@ -107,7 +113,7 @@ public class CacheController
     @DeleteMapping("/clearCacheKey/{cacheKey}")
     public AjaxResult clearCacheKey(@PathVariable String cacheKey)
     {
-        redisTemplate.delete(cacheKey);
+        redisCache.deleteObject(cacheKey);
         return AjaxResult.success();
     }
 
@@ -115,8 +121,28 @@ public class CacheController
     @DeleteMapping("/clearCacheAll")
     public AjaxResult clearCacheAll()
     {
-        Collection<String> cacheKeys = redisTemplate.keys("*");
-        redisTemplate.delete(cacheKeys);
+        redisCache.clear();
         return AjaxResult.success();
     }
+
+    private Map<String, String> statEntry(String name, long value)
+    {
+        Map<String, String> data = new HashMap<>(2);
+        data.put("name", name);
+        data.put("value", String.valueOf(value));
+        return data;
+    }
+
+    private String cacheValueToString(Object cacheValue)
+    {
+        if (cacheValue == null)
+        {
+            return StringUtils.EMPTY;
+        }
+        if (cacheValue instanceof String stringValue)
+        {
+            return stringValue;
+        }
+        return JSON.toJSONString(cacheValue);
+    }
 }

ruoyi-admin/src/main/resources/application-dev.yml

@@ -78,28 +78,5 @@ spring:
                 wall:
                     config:
                         multi-statement-allow: true
-    data:
-        # redis 配置
-        redis:
-            # 地址
-            host: 116.62.17.81
-            # 端口，默认为6379
-            port: 6379
-            # 数据库索引
-            database: 0
-            # 密码
-            password: Kfcx@1234
-            # 连接超时时间
-            timeout: 10s
-            lettuce:
-                pool:
-                    # 连接池中的最小空闲连接
-                    min-idle: 0
-                    # 连接池中的最大空闲连接
-                    max-idle: 8
-                    # 连接池的最大数据库连接数
-                    max-active: 8
-                    # #连接池最大阻塞等待时间（使用负值表示没有限制）
-                    max-wait: -1ms
 model:
     url: http://localhost:8080/rate/pricing/mock/invokeModel

ruoyi-admin/src/test/java/com/ruoyi/web/controller/monitor/CacheControllerTest.java

@@ -0,0 +1,44 @@
+package com.ruoyi.web.controller.monitor;
+
+import static org.springframework.test.web.servlet.request.MockMvcRequestBuilders.delete;
+import static org.springframework.test.web.servlet.request.MockMvcRequestBuilders.get;
+import static org.springframework.test.web.servlet.result.MockMvcResultMatchers.jsonPath;
+import static org.springframework.test.web.servlet.result.MockMvcResultMatchers.status;
+
+import org.junit.jupiter.api.Test;
+import org.springframework.test.web.servlet.MockMvc;
+import org.springframework.test.web.servlet.setup.MockMvcBuilders;
+import com.ruoyi.common.core.cache.InMemoryCacheStore;
+import com.ruoyi.common.core.redis.RedisCache;
+
+class CacheControllerTest
+{
+    @Test
+    void shouldReturnInMemoryCacheSummary() throws Exception
+    {
+        RedisCache redisCache = new RedisCache(new InMemoryCacheStore());
+        MockMvc mockMvc = MockMvcBuilders.standaloneSetup(new CacheController(redisCache)).build();
+
+        mockMvc.perform(get("/monitor/cache"))
+                .andExpect(status().isOk())
+                .andExpect(jsonPath("$.data.info.cache_type").value("IN_MEMORY"))
+                .andExpect(jsonPath("$.data.info.cache_mode").value("single-instance"));
+    }
+
+    @Test
+    void shouldClearCacheKeysByPrefix() throws Exception
+    {
+        RedisCache redisCache = new RedisCache(new InMemoryCacheStore());
+        redisCache.setCacheObject("login_tokens:a", "A");
+        redisCache.setCacheObject("login_tokens:b", "B");
+
+        MockMvc mockMvc = MockMvcBuilders.standaloneSetup(new CacheController(redisCache)).build();
+
+        mockMvc.perform(delete("/monitor/cache/clearCacheName/login_tokens:"))
+                .andExpect(status().isOk());
+
+        mockMvc.perform(get("/monitor/cache/getKeys/login_tokens:"))
+                .andExpect(status().isOk())
+                .andExpect(jsonPath("$.data").isEmpty());
+    }
+}

ruoyi-common/pom.xml

@@ -89,18 +89,6 @@
             <artifactId>jaxb-api</artifactId>
         </dependency>
 
-        <!-- redis 缓存操作 -->
-        <dependency>
-            <groupId>org.springframework.boot</groupId>
-            <artifactId>spring-boot-starter-data-redis</artifactId>
-        </dependency>
-
-        <!-- pool 对象池 -->
-        <dependency>
-            <groupId>org.apache.commons</groupId>
-            <artifactId>commons-pool2</artifactId>
-        </dependency>
-
         <!-- 解析客户端操作系统、浏览器等 -->
         <dependency>
             <groupId>nl.basjes.parse.useragent</groupId>
@@ -131,6 +119,12 @@
             <version>3.5.10</version>
         </dependency>
 
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-test</artifactId>
+            <scope>test</scope>
+        </dependency>
+
     </dependencies>
 
-</project>
+</project>

ruoyi-common/src/main/java/com/ruoyi/common/core/cache/InMemoryCacheEntry.java

@@ -0,0 +1,9 @@
+package com.ruoyi.common.core.cache;
+
+record InMemoryCacheEntry(Object value, Long expireAtMillis)
+{
+    boolean isExpired(long now)
+    {
+        return expireAtMillis != null && expireAtMillis <= now;
+    }
+}

ruoyi-common/src/main/java/com/ruoyi/common/core/cache/InMemoryCacheStats.java

@@ -0,0 +1,12 @@
+package com.ruoyi.common.core.cache;
+
+public record InMemoryCacheStats(
+        String cacheType,
+        String mode,
+        long keySize,
+        long hitCount,
+        long missCount,
+        long expiredCount,
+        long writeCount)
+{
+}

ruoyi-common/src/main/java/com/ruoyi/common/core/cache/InMemoryCacheStore.java

@@ -0,0 +1,277 @@
+package com.ruoyi.common.core.cache;
+
+import java.util.Collection;
+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.Map;
+import java.util.Objects;
+import java.util.Set;
+import java.util.TreeSet;
+import java.util.concurrent.ConcurrentHashMap;
+import java.util.concurrent.TimeUnit;
+import java.util.concurrent.atomic.AtomicLong;
+import org.springframework.stereotype.Component;
+
+@Component
+public class InMemoryCacheStore
+{
+    private final ConcurrentHashMap<String, InMemoryCacheEntry> entries = new ConcurrentHashMap<>();
+    private final AtomicLong hitCount = new AtomicLong();
+    private final AtomicLong missCount = new AtomicLong();
+    private final AtomicLong expiredCount = new AtomicLong();
+    private final AtomicLong writeCount = new AtomicLong();
+
+    public void set(String key, Object value)
+    {
+        putEntry(key, new InMemoryCacheEntry(value, null));
+    }
+
+    public void set(String key, Object value, long timeout, TimeUnit unit)
+    {
+        long expireAtMillis = System.currentTimeMillis() + Math.max(0L, unit.toMillis(timeout));
+        putEntry(key, new InMemoryCacheEntry(value, expireAtMillis));
+    }
+
+    @SuppressWarnings("unchecked")
+    public <T> T get(String key)
+    {
+        InMemoryCacheEntry entry = readEntry(key);
+        return entry == null ? null : (T) entry.value();
+    }
+
+    public boolean hasKey(String key)
+    {
+        return readEntry(key) != null;
+    }
+
+    public boolean delete(String key)
+    {
+        return entries.remove(key) != null;
+    }
+
+    public boolean delete(Collection<String> keys)
+    {
+        boolean deleted = false;
+        for (String key : keys)
+        {
+            deleted = delete(key) || deleted;
+        }
+        return deleted;
+    }
+
+    public Set<String> keys(String pattern)
+    {
+        purgeExpiredEntries();
+        Set<String> matchedKeys = new TreeSet<>();
+        entries.forEach((key, value) -> {
+            if (matches(pattern, key))
+            {
+                matchedKeys.add(key);
+            }
+        });
+        return matchedKeys;
+    }
+
+    public boolean expire(String key, long timeout, TimeUnit unit)
+    {
+        Objects.requireNonNull(unit, "TimeUnit must not be null");
+        long expireAtMillis = System.currentTimeMillis() + Math.max(0L, unit.toMillis(timeout));
+        return entries.computeIfPresent(key, (cacheKey, entry) -> entry.isExpired(System.currentTimeMillis())
+                ? null
+                : new InMemoryCacheEntry(entry.value(), expireAtMillis)) != null;
+    }
+
+    public long getExpire(String key)
+    {
+        return getExpire(key, TimeUnit.SECONDS);
+    }
+
+    public long getExpire(String key, TimeUnit unit)
+    {
+        InMemoryCacheEntry entry = readEntry(key);
+        if (entry == null)
+        {
+            return -2L;
+        }
+        if (entry.expireAtMillis() == null)
+        {
+            return -1L;
+        }
+        long remainingMillis = Math.max(0L, entry.expireAtMillis() - System.currentTimeMillis());
+        long unitMillis = Math.max(1L, unit.toMillis(1));
+        return (remainingMillis + unitMillis - 1) / unitMillis;
+    }
+
+    public long increment(String key, long timeout, TimeUnit unit)
+    {
+        Objects.requireNonNull(unit, "TimeUnit must not be null");
+        AtomicLong result = new AtomicLong();
+        entries.compute(key, (cacheKey, currentEntry) -> {
+            long now = System.currentTimeMillis();
+            boolean missingOrExpired = currentEntry == null || currentEntry.isExpired(now);
+            long nextValue = missingOrExpired ? 1L : toLong(currentEntry.value()) + 1L;
+            Long expireAtMillis = missingOrExpired || currentEntry.expireAtMillis() == null
+                    ? now + Math.max(0L, unit.toMillis(timeout))
+                    : currentEntry.expireAtMillis();
+            if (missingOrExpired && currentEntry != null)
+            {
+                expiredCount.incrementAndGet();
+            }
+            result.set(nextValue);
+            return new InMemoryCacheEntry(nextValue, expireAtMillis);
+        });
+        writeCount.incrementAndGet();
+        return result.get();
+    }
+
+    public void clear()
+    {
+        entries.clear();
+    }
+
+    public InMemoryCacheStats snapshot()
+    {
+        purgeExpiredEntries();
+        return new InMemoryCacheStats(
+                "IN_MEMORY",
+                "single-instance",
+                entries.size(),
+                hitCount.get(),
+                missCount.get(),
+                expiredCount.get(),
+                writeCount.get());
+    }
+
+    public <T> Map<String, T> getMap(String key)
+    {
+        Map<String, T> value = get(key);
+        return value == null ? null : new HashMap<>(value);
+    }
+
+    public <T> void putMap(String key, Map<String, T> dataMap)
+    {
+        set(key, new HashMap<>(dataMap));
+    }
+
+    public <T> void putMapValue(String key, String mapKey, T value)
+    {
+        long ttl = getExpire(key, TimeUnit.MILLISECONDS);
+        Map<String, T> current = getMap(key);
+        if (current == null)
+        {
+            current = new HashMap<>();
+        }
+        current.put(mapKey, value);
+        setWithOptionalTtl(key, current, ttl);
+    }
+
+    public boolean deleteMapValue(String key, String mapKey)
+    {
+        long ttl = getExpire(key, TimeUnit.MILLISECONDS);
+        Map<String, Object> current = getMap(key);
+        if (current == null || !current.containsKey(mapKey))
+        {
+            return false;
+        }
+        current.remove(mapKey);
+        setWithOptionalTtl(key, current, ttl);
+        return true;
+    }
+
+    public <T> Set<T> getSet(String key)
+    {
+        Set<T> value = get(key);
+        return value == null ? null : new HashSet<>(value);
+    }
+
+    public <T> void putSet(String key, Set<T> dataSet)
+    {
+        set(key, new HashSet<>(dataSet));
+    }
+
+    public <T> java.util.List<T> getList(String key)
+    {
+        java.util.List<T> value = get(key);
+        return value == null ? null : new java.util.ArrayList<>(value);
+    }
+
+    public <T> void putList(String key, java.util.List<T> dataList)
+    {
+        set(key, new java.util.ArrayList<>(dataList));
+    }
+
+    private void putEntry(String key, InMemoryCacheEntry entry)
+    {
+        entries.put(key, entry);
+        writeCount.incrementAndGet();
+    }
+
+    private InMemoryCacheEntry readEntry(String key)
+    {
+        InMemoryCacheEntry entry = entries.get(key);
+        if (entry == null)
+        {
+            missCount.incrementAndGet();
+            return null;
+        }
+        if (entry.isExpired(System.currentTimeMillis()))
+        {
+            removeExpiredEntry(key, entry);
+            missCount.incrementAndGet();
+            return null;
+        }
+        hitCount.incrementAndGet();
+        return entry;
+    }
+
+    private void purgeExpiredEntries()
+    {
+        long now = System.currentTimeMillis();
+        entries.forEach((key, entry) -> {
+            if (entry.isExpired(now))
+            {
+                removeExpiredEntry(key, entry);
+            }
+        });
+    }
+
+    private void removeExpiredEntry(String key, InMemoryCacheEntry expectedEntry)
+    {
+        if (entries.remove(key, expectedEntry))
+        {
+            expiredCount.incrementAndGet();
+        }
+    }
+
+    private boolean matches(String pattern, String key)
+    {
+        if ("*".equals(pattern))
+        {
+            return true;
+        }
+        if (pattern.endsWith("*"))
+        {
+            return key.startsWith(pattern.substring(0, pattern.length() - 1));
+        }
+        return key.equals(pattern);
+    }
+
+    private long toLong(Object value)
+    {
+        if (value instanceof Number number)
+        {
+            return number.longValue();
+        }
+        return Long.parseLong(String.valueOf(value));
+    }
+
+    private void setWithOptionalTtl(String key, Object value, long ttlMillis)
+    {
+        if (ttlMillis > 0)
+        {
+            set(key, value, ttlMillis, TimeUnit.MILLISECONDS);
+            return;
+        }
+        set(key, value);
+    }
+}

ruoyi-common/src/main/java/com/ruoyi/common/core/redis/RedisCache.java

@@ -1,268 +1,169 @@
 package com.ruoyi.common.core.redis;
 
+import java.util.ArrayList;
 import java.util.Collection;
-import java.util.Iterator;
+import java.util.Collections;
 import java.util.List;
 import java.util.Map;
 import java.util.Set;
 import java.util.concurrent.TimeUnit;
-import org.springframework.beans.factory.annotation.Autowired;
-import org.springframework.data.redis.core.BoundSetOperations;
-import org.springframework.data.redis.core.HashOperations;
-import org.springframework.data.redis.core.RedisTemplate;
-import org.springframework.data.redis.core.ValueOperations;
 import org.springframework.stereotype.Component;
+import com.ruoyi.common.core.cache.InMemoryCacheStats;
+import com.ruoyi.common.core.cache.InMemoryCacheStore;
 
 /**
- * spring redis 工具类
+ * 本地缓存门面，保留原有 RedisCache 业务入口。
  *
  * @author ruoyi
  **/
-@SuppressWarnings(value = { "unchecked", "rawtypes" })
+@SuppressWarnings("unchecked")
 @Component
 public class RedisCache
 {
-    @Autowired
-    public RedisTemplate redisTemplate;
+    private final InMemoryCacheStore cacheStore;
+
+    public RedisCache(InMemoryCacheStore cacheStore)
+    {
+        this.cacheStore = cacheStore;
+    }
 
-    /**
-     * 缓存基本的对象，Integer、String、实体类等
-     *
-     * @param key 缓存的键值
-     * @param value 缓存的值
-     */
     public <T> void setCacheObject(final String key, final T value)
     {
-        redisTemplate.opsForValue().set(key, value);
+        cacheStore.set(key, value);
     }
 
-    /**
-     * 缓存基本的对象，Integer、String、实体类等
-     *
-     * @param key 缓存的键值
-     * @param value 缓存的值
-     * @param timeout 时间
-     * @param timeUnit 时间颗粒度
-     */
     public <T> void setCacheObject(final String key, final T value, final Integer timeout, final TimeUnit timeUnit)
     {
-        redisTemplate.opsForValue().set(key, value, timeout, timeUnit);
+        cacheStore.set(key, value, timeout.longValue(), timeUnit);
     }
 
-    /**
-     * 设置有效时间
-     *
-     * @param key Redis键
-     * @param timeout 超时时间
-     * @return true=设置成功；false=设置失败
-     */
     public boolean expire(final String key, final long timeout)
     {
         return expire(key, timeout, TimeUnit.SECONDS);
     }
 
-    /**
-     * 设置有效时间
-     *
-     * @param key Redis键
-     * @param timeout 超时时间
-     * @param unit 时间单位
-     * @return true=设置成功；false=设置失败
-     */
     public boolean expire(final String key, final long timeout, final TimeUnit unit)
     {
-        return redisTemplate.expire(key, timeout, unit);
+        return cacheStore.expire(key, timeout, unit);
     }
 
-    /**
-     * 获取有效时间
-     *
-     * @param key Redis键
-     * @return 有效时间
-     */
     public long getExpire(final String key)
     {
-        return redisTemplate.getExpire(key);
+        return cacheStore.getExpire(key);
     }
 
-    /**
-     * 判断 key是否存在
-     *
-     * @param key 键
-     * @return true 存在 false不存在
-     */
     public Boolean hasKey(String key)
     {
-        return redisTemplate.hasKey(key);
+        return cacheStore.hasKey(key);
     }
 
-    /**
-     * 获得缓存的基本对象。
-     *
-     * @param key 缓存键值
-     * @return 缓存键值对应的数据
-     */
     public <T> T getCacheObject(final String key)
     {
-        ValueOperations<String, T> operation = redisTemplate.opsForValue();
-        return operation.get(key);
+        return cacheStore.get(key);
     }
 
-    /**
-     * 删除单个对象
-     *
-     * @param key
-     */
     public boolean deleteObject(final String key)
     {
-        return redisTemplate.delete(key);
+        return cacheStore.delete(key);
     }
 
-    /**
-     * 删除集合对象
-     *
-     * @param collection 多个对象
-     * @return
-     */
     public boolean deleteObject(final Collection collection)
     {
-        return redisTemplate.delete(collection) > 0;
+        if (collection == null || collection.isEmpty())
+        {
+            return false;
+        }
+        List<String> keys = new ArrayList<>(collection.size());
+        for (Object item : collection)
+        {
+            keys.add(String.valueOf(item));
+        }
+        return cacheStore.delete(keys);
     }
 
-    /**
-     * 缓存List数据
-     *
-     * @param key 缓存的键值
-     * @param dataList 待缓存的List数据
-     * @return 缓存的对象
-     */
     public <T> long setCacheList(final String key, final List<T> dataList)
     {
-        Long count = redisTemplate.opsForList().rightPushAll(key, dataList);
-        return count == null ? 0 : count;
+        cacheStore.putList(key, dataList);
+        return dataList == null ? 0 : dataList.size();
     }
 
-    /**
-     * 获得缓存的list对象
-     *
-     * @param key 缓存的键值
-     * @return 缓存键值对应的数据
-     */
     public <T> List<T> getCacheList(final String key)
     {
-        return redisTemplate.opsForList().range(key, 0, -1);
+        return cacheStore.getList(key);
     }
 
-    /**
-     * 缓存Set
-     *
-     * @param key 缓存键值
-     * @param dataSet 缓存的数据
-     * @return 缓存数据的对象
-     */
-    public <T> BoundSetOperations<String, T> setCacheSet(final String key, final Set<T> dataSet)
+    public <T> long setCacheSet(final String key, final Set<T> dataSet)
     {
-        BoundSetOperations<String, T> setOperation = redisTemplate.boundSetOps(key);
-        Iterator<T> it = dataSet.iterator();
-        while (it.hasNext())
-        {
-            setOperation.add(it.next());
-        }
-        return setOperation;
+        cacheStore.putSet(key, dataSet);
+        return dataSet == null ? 0 : dataSet.size();
     }
 
-    /**
-     * 获得缓存的set
-     *
-     * @param key
-     * @return
-     */
     public <T> Set<T> getCacheSet(final String key)
     {
-        return redisTemplate.opsForSet().members(key);
+        return cacheStore.getSet(key);
     }
 
-    /**
-     * 缓存Map
-     *
-     * @param key
-     * @param dataMap
-     */
     public <T> void setCacheMap(final String key, final Map<String, T> dataMap)
     {
-        if (dataMap != null) {
-            redisTemplate.opsForHash().putAll(key, dataMap);
+        if (dataMap != null)
+        {
+            cacheStore.putMap(key, dataMap);
         }
     }
 
-    /**
-     * 获得缓存的Map
-     *
-     * @param key
-     * @return
-     */
     public <T> Map<String, T> getCacheMap(final String key)
     {
-        return redisTemplate.opsForHash().entries(key);
+        return cacheStore.getMap(key);
     }
 
-    /**
-     * 往Hash中存入数据
-     *
-     * @param key Redis键
-     * @param hKey Hash键
-     * @param value 值
-     */
     public <T> void setCacheMapValue(final String key, final String hKey, final T value)
     {
-        redisTemplate.opsForHash().put(key, hKey, value);
+        cacheStore.putMapValue(key, hKey, value);
     }
 
-    /**
-     * 获取Hash中的数据
-     *
-     * @param key Redis键
-     * @param hKey Hash键
-     * @return Hash中的对象
-     */
     public <T> T getCacheMapValue(final String key, final String hKey)
     {
-        HashOperations<String, String, T> opsForHash = redisTemplate.opsForHash();
-        return opsForHash.get(key, hKey);
+        Map<String, T> map = cacheStore.getMap(key);
+        return map == null ? null : map.get(hKey);
     }
 
-    /**
-     * 获取多个Hash中的数据
-     *
-     * @param key Redis键
-     * @param hKeys Hash键集合
-     * @return Hash对象集合
-     */
     public <T> List<T> getMultiCacheMapValue(final String key, final Collection<Object> hKeys)
     {
-        return redisTemplate.opsForHash().multiGet(key, hKeys);
+        Map<String, T> map = cacheStore.getMap(key);
+        if (map == null || hKeys == null || hKeys.isEmpty())
+        {
+            return Collections.emptyList();
+        }
+        List<T> values = new ArrayList<>(hKeys.size());
+        for (Object hKey : hKeys)
+        {
+            values.add(map.get(String.valueOf(hKey)));
+        }
+        return values;
     }
 
-    /**
-     * 删除Hash中的某条数据
-     *
-     * @param key Redis键
-     * @param hKey Hash键
-     * @return 是否成功
-     */
     public boolean deleteCacheMapValue(final String key, final String hKey)
     {
-        return redisTemplate.opsForHash().delete(key, hKey) > 0;
+        return cacheStore.deleteMapValue(key, hKey);
     }
 
-    /**
-     * 获得缓存的基本对象列表
-     *
-     * @param pattern 字符串前缀
-     * @return 对象列表
-     */
     public Collection<String> keys(final String pattern)
     {
-        return redisTemplate.keys(pattern);
+        return cacheStore.keys(pattern);
+    }
+
+    public long increment(String key, long timeout, TimeUnit unit)
+    {
+        return cacheStore.increment(key, timeout, unit);
+    }
+
+    public InMemoryCacheStats getCacheStats()
+    {
+        return cacheStore.snapshot();
+    }
+
+    public void clear()
+    {
+        cacheStore.clear();
     }
 }

ruoyi-common/src/main/java/com/ruoyi/common/utils/DictUtils.java

@@ -4,7 +4,7 @@ import java.util.Collection;
 import java.util.HashMap;
 import java.util.List;
 import java.util.Map;
-import com.alibaba.fastjson2.JSONArray;
+import com.alibaba.fastjson2.JSON;
 import com.ruoyi.common.constant.CacheConstants;
 import com.ruoyi.common.core.domain.entity.SysDictData;
 import com.ruoyi.common.core.redis.RedisCache;
@@ -41,10 +41,14 @@ public class DictUtils
      */
     public static List<SysDictData> getDictCache(String key)
     {
-        JSONArray arrayCache = SpringUtils.getBean(RedisCache.class).getCacheObject(getCacheKey(key));
-        if (StringUtils.isNotNull(arrayCache))
+        Object cacheObject = SpringUtils.getBean(RedisCache.class).getCacheObject(getCacheKey(key));
+        if (cacheObject instanceof List<?> listCache)
         {
-            return arrayCache.toList(SysDictData.class);
+            return (List<SysDictData>) listCache;
+        }
+        if (StringUtils.isNotNull(cacheObject))
+        {
+            return JSON.parseArray(JSON.toJSONString(cacheObject), SysDictData.class);
         }
         return null;
     }

ruoyi-common/src/test/java/com/ruoyi/common/core/cache/InMemoryCacheStoreTest.java

@@ -0,0 +1,53 @@
+package com.ruoyi.common.core.cache;
+
+import static org.junit.jupiter.api.Assertions.assertEquals;
+import static org.junit.jupiter.api.Assertions.assertFalse;
+import static org.junit.jupiter.api.Assertions.assertNull;
+import static org.junit.jupiter.api.Assertions.assertTrue;
+
+import java.util.Set;
+import java.util.concurrent.TimeUnit;
+import org.junit.jupiter.api.Test;
+
+class InMemoryCacheStoreTest
+{
+    @Test
+    void shouldExpireEntryAfterTtl() throws Exception
+    {
+        InMemoryCacheStore store = new InMemoryCacheStore();
+        store.set("captcha_codes:1", "1234", 20, TimeUnit.MILLISECONDS);
+        Thread.sleep(40);
+        assertNull(store.get("captcha_codes:1"));
+    }
+
+    @Test
+    void shouldReturnPrefixKeysInSortedOrder()
+    {
+        InMemoryCacheStore store = new InMemoryCacheStore();
+        store.set("login_tokens:a", "A");
+        store.set("login_tokens:b", "B");
+        store.set("sys_dict:x", "X");
+        assertEquals(Set.of("login_tokens:a", "login_tokens:b"), store.keys("login_tokens:*"));
+    }
+
+    @Test
+    void shouldTrackHitsMissesWritesAndExpiredEntries() throws Exception
+    {
+        InMemoryCacheStore store = new InMemoryCacheStore();
+        store.set("captcha_codes:2", "5678", 20, TimeUnit.MILLISECONDS);
+        assertTrue(store.hasKey("captcha_codes:2"));
+        assertEquals("5678", store.get("captcha_codes:2"));
+        Thread.sleep(40);
+        assertNull(store.get("captcha_codes:2"));
+        assertFalse(store.hasKey("captcha_codes:2"));
+
+        InMemoryCacheStats stats = store.snapshot();
+        assertEquals("IN_MEMORY", stats.cacheType());
+        assertEquals("single-instance", stats.mode());
+        assertEquals(0, stats.keySize());
+        assertEquals(2, stats.hitCount());
+        assertEquals(2, stats.missCount());
+        assertEquals(1, stats.expiredCount());
+        assertEquals(1, stats.writeCount());
+    }
+}

ruoyi-common/src/test/java/com/ruoyi/common/core/redis/RedisCacheTest.java

@@ -0,0 +1,52 @@
+package com.ruoyi.common.core.redis;
+
+import static org.junit.jupiter.api.Assertions.assertEquals;
+import static org.junit.jupiter.api.Assertions.assertFalse;
+import static org.junit.jupiter.api.Assertions.assertNotNull;
+import static org.junit.jupiter.api.Assertions.assertNull;
+import static org.junit.jupiter.api.Assertions.assertTrue;
+
+import com.ruoyi.common.core.cache.InMemoryCacheStore;
+import java.util.List;
+import java.util.Set;
+import java.util.concurrent.TimeUnit;
+import org.junit.jupiter.api.Test;
+
+class RedisCacheTest
+{
+    @Test
+    void shouldSupportSetGetDeleteAndExpireThroughRedisCacheFacade()
+    {
+        RedisCache cache = new RedisCache(new InMemoryCacheStore());
+        cache.setCacheObject("login_tokens:abc", "payload", 1, TimeUnit.SECONDS);
+        assertEquals("payload", cache.getCacheObject("login_tokens:abc"));
+        assertTrue(cache.hasKey("login_tokens:abc"));
+        assertTrue(cache.deleteObject("login_tokens:abc"));
+    }
+
+    @Test
+    void shouldSupportKeysBulkDeleteAndRemainingTtl()
+    {
+        RedisCache cache = new RedisCache(new InMemoryCacheStore());
+        cache.setCacheObject("login_tokens:a", "A", 5, TimeUnit.SECONDS);
+        cache.setCacheObject("login_tokens:b", "B", 5, TimeUnit.SECONDS);
+        cache.setCacheObject("sys_dict:x", "X");
+
+        assertNotNull(cache.getExpire("login_tokens:a"));
+        assertTrue(cache.getExpire("login_tokens:a") > 0);
+        assertEquals(Set.of("login_tokens:a", "login_tokens:b"), Set.copyOf(cache.keys("login_tokens:*")));
+        assertTrue(cache.deleteObject(List.of("login_tokens:a", "login_tokens:b")));
+        assertFalse(cache.hasKey("login_tokens:a"));
+    }
+
+    @Test
+    void shouldIncrementCounterWithinTtlWindow() throws Exception
+    {
+        RedisCache cache = new RedisCache(new InMemoryCacheStore());
+        assertEquals(1L, cache.increment("rate_limit:test", 50, TimeUnit.MILLISECONDS));
+        assertEquals(2L, cache.increment("rate_limit:test", 50, TimeUnit.MILLISECONDS));
+        Thread.sleep(70);
+        assertNull(cache.getCacheObject("rate_limit:test"));
+        assertEquals(1L, cache.increment("rate_limit:test", 50, TimeUnit.MILLISECONDS));
+    }
+}

ruoyi-common/src/test/java/com/ruoyi/common/utils/DictUtilsTest.java

@@ -0,0 +1,45 @@
+package com.ruoyi.common.utils;
+
+import static org.junit.jupiter.api.Assertions.assertEquals;
+import static org.junit.jupiter.api.Assertions.assertNull;
+
+import java.util.List;
+import org.junit.jupiter.api.AfterEach;
+import org.junit.jupiter.api.Test;
+import org.springframework.beans.factory.support.DefaultListableBeanFactory;
+import org.springframework.test.util.ReflectionTestUtils;
+import com.ruoyi.common.core.cache.InMemoryCacheStore;
+import com.ruoyi.common.core.domain.entity.SysDictData;
+import com.ruoyi.common.core.redis.RedisCache;
+import com.ruoyi.common.utils.spring.SpringUtils;
+
+class DictUtilsTest
+{
+    @AfterEach
+    void clearSpringUtils()
+    {
+        ReflectionTestUtils.setField(SpringUtils.class, "beanFactory", null);
+        ReflectionTestUtils.setField(SpringUtils.class, "applicationContext", null);
+    }
+
+    @Test
+    void shouldReadDictListFromLocalCache()
+    {
+        DefaultListableBeanFactory beanFactory = new DefaultListableBeanFactory();
+        beanFactory.registerSingleton("redisCache", new RedisCache(new InMemoryCacheStore()));
+        ReflectionTestUtils.setField(SpringUtils.class, "beanFactory", beanFactory);
+
+        SysDictData dictData = new SysDictData();
+        dictData.setDictLabel("正常");
+        dictData.setDictValue("0");
+
+        DictUtils.setDictCache("sys_normal_disable", List.of(dictData));
+
+        List<SysDictData> cached = DictUtils.getDictCache("sys_normal_disable");
+        assertEquals(1, cached.size());
+        assertEquals("正常", cached.get(0).getDictLabel());
+
+        DictUtils.clearDictCache();
+        assertNull(DictUtils.getDictCache("sys_normal_disable"));
+    }
+}

ruoyi-framework/pom.xml

@@ -59,6 +59,12 @@
             <artifactId>ruoyi-system</artifactId>
         </dependency>
 
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-test</artifactId>
+            <scope>test</scope>
+        </dependency>
+
     </dependencies>
 
-</project>
+</project>

ruoyi-framework/src/main/java/com/ruoyi/framework/aspectj/RateLimiterAspect.java

@@ -1,22 +1,18 @@
 package com.ruoyi.framework.aspectj;
 
 import java.lang.reflect.Method;
-import java.util.Collections;
-import java.util.List;
+import java.util.concurrent.TimeUnit;
 import org.aspectj.lang.JoinPoint;
 import org.aspectj.lang.annotation.Aspect;
 import org.aspectj.lang.annotation.Before;
 import org.aspectj.lang.reflect.MethodSignature;
 import org.slf4j.Logger;
 import org.slf4j.LoggerFactory;
-import org.springframework.beans.factory.annotation.Autowired;
-import org.springframework.data.redis.core.RedisTemplate;
-import org.springframework.data.redis.core.script.RedisScript;
 import org.springframework.stereotype.Component;
 import com.ruoyi.common.annotation.RateLimiter;
+import com.ruoyi.common.core.redis.RedisCache;
 import com.ruoyi.common.enums.LimitType;
 import com.ruoyi.common.exception.ServiceException;
-import com.ruoyi.common.utils.StringUtils;
 import com.ruoyi.common.utils.ip.IpUtils;
 
 /**
@@ -30,20 +26,11 @@ public class RateLimiterAspect
 {
     private static final Logger log = LoggerFactory.getLogger(RateLimiterAspect.class);
 
-    private RedisTemplate<Object, Object> redisTemplate;
+    private final RedisCache redisCache;
 
-    private RedisScript<Long> limitScript;
-
-    @Autowired
-    public void setRedisTemplate1(RedisTemplate<Object, Object> redisTemplate)
+    public RateLimiterAspect(RedisCache redisCache)
     {
-        this.redisTemplate = redisTemplate;
-    }
-
-    @Autowired
-    public void setLimitScript(RedisScript<Long> limitScript)
-    {
-        this.limitScript = limitScript;
+        this.redisCache = redisCache;
     }
 
     @Before("@annotation(rateLimiter)")
@@ -53,15 +40,14 @@ public class RateLimiterAspect
         int count = rateLimiter.count();
 
         String combineKey = getCombineKey(rateLimiter, point);
-        List<Object> keys = Collections.singletonList(combineKey);
         try
         {
-            Long number = redisTemplate.execute(limitScript, keys, count, time);
-            if (StringUtils.isNull(number) || number.intValue() > count)
+            long number = redisCache.increment(combineKey, time, TimeUnit.SECONDS);
+            if (number > count)
             {
                 throw new ServiceException("访问过于频繁，请稍候再试");
             }
-            log.info("限制请求'{}',当前请求'{}',缓存key'{}'", count, number.intValue(), combineKey);
+            log.info("限制请求'{}',当前请求'{}',缓存key'{}'", count, number, combineKey);
         }
         catch (ServiceException e)
         {

ruoyi-framework/src/main/java/com/ruoyi/framework/config/FastJson2JsonRedisSerializer.java

@@ -1,52 +0,0 @@
-package com.ruoyi.framework.config;
-
-import java.nio.charset.Charset;
-import org.springframework.data.redis.serializer.RedisSerializer;
-import org.springframework.data.redis.serializer.SerializationException;
-import com.alibaba.fastjson2.JSON;
-import com.alibaba.fastjson2.JSONReader;
-import com.alibaba.fastjson2.JSONWriter;
-import com.alibaba.fastjson2.filter.Filter;
-import com.ruoyi.common.constant.Constants;
-
-/**
- * Redis使用FastJson序列化
- * 
- * @author ruoyi
- */
-public class FastJson2JsonRedisSerializer<T> implements RedisSerializer<T>
-{
-    public static final Charset DEFAULT_CHARSET = Charset.forName("UTF-8");
-
-    static final Filter AUTO_TYPE_FILTER = JSONReader.autoTypeFilter(Constants.JSON_WHITELIST_STR);
-
-    private Class<T> clazz;
-
-    public FastJson2JsonRedisSerializer(Class<T> clazz)
-    {
-        super();
-        this.clazz = clazz;
-    }
-
-    @Override
-    public byte[] serialize(T t) throws SerializationException
-    {
-        if (t == null)
-        {
-            return new byte[0];
-        }
-        return JSON.toJSONString(t, JSONWriter.Feature.WriteClassName).getBytes(DEFAULT_CHARSET);
-    }
-
-    @Override
-    public T deserialize(byte[] bytes) throws SerializationException
-    {
-        if (bytes == null || bytes.length <= 0)
-        {
-            return null;
-        }
-        String str = new String(bytes, DEFAULT_CHARSET);
-
-        return JSON.parseObject(str, clazz, AUTO_TYPE_FILTER);
-    }
-}

ruoyi-framework/src/main/java/com/ruoyi/framework/config/RedisConfig.java

@@ -1,70 +0,0 @@
-package com.ruoyi.framework.config;
-
-import org.springframework.cache.annotation.CachingConfigurerSupport;
-import org.springframework.cache.annotation.EnableCaching;
-import org.springframework.context.annotation.Bean;
-import org.springframework.context.annotation.Configuration;
-import org.springframework.data.redis.connection.RedisConnectionFactory;
-import org.springframework.data.redis.core.RedisTemplate;
-import org.springframework.data.redis.core.script.DefaultRedisScript;
-import org.springframework.data.redis.serializer.StringRedisSerializer;
-
-/**
- * redis配置
- * 
- * @author ruoyi
- */
-@SuppressWarnings("deprecation")
-@Configuration
-@EnableCaching
-public class RedisConfig extends CachingConfigurerSupport
-{
-    @Bean
-    @SuppressWarnings(value = { "unchecked", "rawtypes" })
-    public RedisTemplate<Object, Object> redisTemplate(RedisConnectionFactory connectionFactory)
-    {
-        RedisTemplate<Object, Object> template = new RedisTemplate<>();
-        template.setConnectionFactory(connectionFactory);
-
-        FastJson2JsonRedisSerializer serializer = new FastJson2JsonRedisSerializer(Object.class);
-
-        // 使用StringRedisSerializer来序列化和反序列化redis的key值
-        template.setKeySerializer(new StringRedisSerializer());
-        template.setValueSerializer(serializer);
-
-        // Hash的key也采用StringRedisSerializer的序列化方式
-        template.setHashKeySerializer(new StringRedisSerializer());
-        template.setHashValueSerializer(serializer);
-
-        template.afterPropertiesSet();
-        return template;
-    }
-
-    @Bean
-    public DefaultRedisScript<Long> limitScript()
-    {
-        DefaultRedisScript<Long> redisScript = new DefaultRedisScript<>();
-        redisScript.setScriptText(limitScriptText());
-        redisScript.setResultType(Long.class);
-        return redisScript;
-    }
-
-    /**
-     * 限流脚本
-     */
-    private String limitScriptText()
-    {
-        return "local key = KEYS[1]\n" +
-                "local count = tonumber(ARGV[1])\n" +
-                "local time = tonumber(ARGV[2])\n" +
-                "local current = redis.call('get', key);\n" +
-                "if current and tonumber(current) > count then\n" +
-                "    return tonumber(current);\n" +
-                "end\n" +
-                "current = redis.call('incr', key)\n" +
-                "if tonumber(current) == 1 then\n" +
-                "    redis.call('expire', key, time)\n" +
-                "end\n" +
-                "return tonumber(current);";
-    }
-}

ruoyi-framework/src/test/java/com/ruoyi/framework/aspectj/RateLimiterAspectTest.java

@@ -0,0 +1,49 @@
+package com.ruoyi.framework.aspectj;
+
+import static org.junit.jupiter.api.Assertions.assertDoesNotThrow;
+import static org.junit.jupiter.api.Assertions.assertThrows;
+import static org.mockito.Mockito.mock;
+import static org.mockito.Mockito.when;
+
+import java.lang.reflect.Method;
+import org.aspectj.lang.JoinPoint;
+import org.aspectj.lang.Signature;
+import org.aspectj.lang.reflect.MethodSignature;
+import org.junit.jupiter.api.Test;
+import com.ruoyi.common.annotation.RateLimiter;
+import com.ruoyi.common.core.cache.InMemoryCacheStore;
+import com.ruoyi.common.core.redis.RedisCache;
+import com.ruoyi.common.exception.ServiceException;
+
+class RateLimiterAspectTest
+{
+    @Test
+    void shouldRejectThirdRequestWithinWindow() throws Throwable
+    {
+        RateLimiterAspect aspect = new RateLimiterAspect(new RedisCache(new InMemoryCacheStore()));
+        JoinPoint joinPoint = mockJoinPoint(TestRateLimitTarget.class.getDeclaredMethod("limited"));
+        RateLimiter rateLimiter = TestRateLimitTarget.class.getDeclaredMethod("limited").getAnnotation(RateLimiter.class);
+
+        assertDoesNotThrow(() -> aspect.doBefore(joinPoint, rateLimiter));
+        assertDoesNotThrow(() -> aspect.doBefore(joinPoint, rateLimiter));
+        assertThrows(ServiceException.class, () -> aspect.doBefore(joinPoint, rateLimiter));
+    }
+
+    private JoinPoint mockJoinPoint(Method method)
+    {
+        MethodSignature signature = mock(MethodSignature.class);
+        when(signature.getMethod()).thenReturn(method);
+
+        JoinPoint joinPoint = mock(JoinPoint.class);
+        when(joinPoint.getSignature()).thenReturn((Signature) signature);
+        return joinPoint;
+    }
+
+    static class TestRateLimitTarget
+    {
+        @RateLimiter(count = 2, time = 60)
+        public void limited()
+        {
+        }
+    }
+}

ruoyi-framework/src/test/java/com/ruoyi/framework/web/service/TokenServiceLocalCacheTest.java

@@ -0,0 +1,117 @@
+package com.ruoyi.framework.web.service;
+
+import static org.junit.jupiter.api.Assertions.assertFalse;
+import static org.junit.jupiter.api.Assertions.assertNotNull;
+import static org.junit.jupiter.api.Assertions.assertTrue;
+import static org.mockito.Mockito.mock;
+import static org.mockito.Mockito.when;
+
+import java.lang.reflect.Method;
+import java.util.concurrent.TimeUnit;
+import org.junit.jupiter.api.AfterEach;
+import org.junit.jupiter.api.Test;
+import org.springframework.mock.web.MockHttpServletRequest;
+import org.springframework.test.util.ReflectionTestUtils;
+import org.springframework.web.context.request.RequestContextHolder;
+import org.springframework.web.context.request.ServletRequestAttributes;
+import com.ruoyi.common.annotation.RepeatSubmit;
+import com.ruoyi.common.constant.CacheConstants;
+import com.ruoyi.common.core.cache.InMemoryCacheStore;
+import com.ruoyi.common.core.domain.entity.SysUser;
+import com.ruoyi.common.core.domain.model.LoginUser;
+import com.ruoyi.common.core.redis.RedisCache;
+import com.ruoyi.framework.interceptor.impl.SameUrlDataInterceptor;
+import com.ruoyi.system.service.ISysConfigService;
+
+class TokenServiceLocalCacheTest
+{
+    @AfterEach
+    void clearRequestContext()
+    {
+        RequestContextHolder.resetRequestAttributes();
+    }
+
+    @Test
+    void shouldStoreLoginUserWithTokenTtl()
+    {
+        RedisCache redisCache = new RedisCache(new InMemoryCacheStore());
+        TokenService tokenService = new TokenService();
+        ReflectionTestUtils.setField(tokenService, "redisCache", redisCache);
+        ReflectionTestUtils.setField(tokenService, "header", "Authorization");
+        ReflectionTestUtils.setField(tokenService, "secret", "unit-test-secret");
+        ReflectionTestUtils.setField(tokenService, "expireTime", 30);
+
+        MockHttpServletRequest request = new MockHttpServletRequest();
+        request.setRemoteAddr("127.0.0.1");
+        request.addHeader("User-Agent", "Mozilla/5.0");
+        RequestContextHolder.setRequestAttributes(new ServletRequestAttributes(request));
+
+        SysUser user = new SysUser();
+        user.setUserName("admin");
+        user.setPassword("password");
+        LoginUser loginUser = new LoginUser();
+        loginUser.setUser(user);
+
+        String jwt = tokenService.createToken(loginUser);
+
+        assertNotNull(jwt);
+        assertNotNull(redisCache.getCacheObject(CacheConstants.LOGIN_TOKEN_KEY + loginUser.getToken()));
+        assertTrue(redisCache.getExpire(CacheConstants.LOGIN_TOKEN_KEY + loginUser.getToken()) > 0);
+    }
+
+    @Test
+    void shouldDeleteCaptchaAfterValidation()
+    {
+        RedisCache redisCache = new RedisCache(new InMemoryCacheStore());
+        SysLoginService loginService = new SysLoginService();
+        ISysConfigService configService = mock(ISysConfigService.class);
+        when(configService.selectCaptchaEnabled()).thenReturn(true);
+        ReflectionTestUtils.setField(loginService, "redisCache", redisCache);
+        ReflectionTestUtils.setField(loginService, "configService", configService);
+
+        redisCache.setCacheObject(CacheConstants.CAPTCHA_CODE_KEY + "uuid", "ABCD", 1, TimeUnit.MINUTES);
+
+        loginService.validateCaptcha("admin", "ABCD", "uuid");
+
+        assertFalse(redisCache.hasKey(CacheConstants.CAPTCHA_CODE_KEY + "uuid"));
+    }
+
+    @Test
+    void shouldSupportMillisecondRepeatSubmitWindow() throws Exception
+    {
+        RedisCache redisCache = new RedisCache(new InMemoryCacheStore());
+        SameUrlDataInterceptor interceptor = new SameUrlDataInterceptor();
+        ReflectionTestUtils.setField(interceptor, "redisCache", redisCache);
+        ReflectionTestUtils.setField(interceptor, "header", "Authorization");
+
+        RepeatSubmit repeatSubmit = RepeatSubmitTarget.class.getDeclaredMethod("submit")
+                .getAnnotation(RepeatSubmit.class);
+
+        MockHttpServletRequest firstRequest = createRepeatRequest();
+        assertFalse(interceptor.isRepeatSubmit(firstRequest, repeatSubmit));
+
+        MockHttpServletRequest secondRequest = createRepeatRequest();
+        assertTrue(interceptor.isRepeatSubmit(secondRequest, repeatSubmit));
+
+        Thread.sleep(70);
+        MockHttpServletRequest thirdRequest = createRepeatRequest();
+        assertFalse(interceptor.isRepeatSubmit(thirdRequest, repeatSubmit));
+    }
+
+    private MockHttpServletRequest createRepeatRequest()
+    {
+        MockHttpServletRequest request = new MockHttpServletRequest();
+        request.setRequestURI("/loan/pricing");
+        request.addHeader("Authorization", "token-1");
+        request.addParameter("loanId", "1001");
+        return request;
+    }
+
+    static class RepeatSubmitTarget
+    {
+        @RepeatSubmit(interval = 50)
+        public void submit()
+        {
+        }
+    }
+}

ruoyi-loan-pricing/pom.xml

@@ -41,6 +41,12 @@
             <artifactId>springdoc-openapi-starter-webmvc-ui</artifactId>
         </dependency>
 
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-test</artifactId>
+            <scope>test</scope>
+        </dependency>
+
     </dependencies>
 
 </project>

ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/controller/LoanPricingWorkflowController.java

@@ -12,6 +12,7 @@ import com.ruoyi.common.enums.BusinessType;
 import com.ruoyi.loanpricing.domain.dto.CorporateLoanPricingCreateDTO;
 import com.ruoyi.loanpricing.domain.dto.PersonalLoanPricingCreateDTO;
 import com.ruoyi.loanpricing.domain.entity.LoanPricingWorkflow;
+import com.ruoyi.loanpricing.domain.vo.LoanPricingWorkflowListVO;
 import com.ruoyi.loanpricing.domain.vo.LoanPricingWorkflowVO;
 import com.ruoyi.loanpricing.service.ILoanPricingWorkflowService;
 import io.swagger.v3.oas.annotations.Operation;
@@ -68,8 +69,8 @@ public class LoanPricingWorkflowController extends BaseController
     public TableDataInfo list(LoanPricingWorkflow loanPricingWorkflow)
     {
         PageDomain pageDomain = TableSupport.buildPageRequest();
-        Page<LoanPricingWorkflow> page = new Page<>(pageDomain.getPageNum(), pageDomain.getPageSize());
-        IPage<LoanPricingWorkflow> result = loanPricingWorkflowService.selectLoanPricingPage(page, loanPricingWorkflow);
+        Page<LoanPricingWorkflowListVO> page = new Page<>(pageDomain.getPageNum(), pageDomain.getPageSize());
+        IPage<LoanPricingWorkflowListVO> result = loanPricingWorkflowService.selectLoanPricingPage(page, loanPricingWorkflow);
         TableDataInfo rspData = new TableDataInfo();
         rspData.setCode(200);
         rspData.setMsg("查询成功");

ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/domain/vo/LoanPricingWorkflowListVO.java

@@ -0,0 +1,27 @@
+package com.ruoyi.loanpricing.domain.vo;
+
+import lombok.Data;
+
+import java.util.Date;
+
+@Data
+public class LoanPricingWorkflowListVO
+{
+    private String serialNum;
+
+    private String custName;
+
+    private String custType;
+
+    private String guarType;
+
+    private String applyAmt;
+
+    private String calculateRate;
+
+    private String executeRate;
+
+    private Date createTime;
+
+    private String createBy;
+}

ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/mapper/LoanPricingWorkflowMapper.java

@@ -1,7 +1,11 @@
 package com.ruoyi.loanpricing.mapper;
 
+import com.baomidou.mybatisplus.core.metadata.IPage;
 import com.baomidou.mybatisplus.core.mapper.BaseMapper;
+import com.baomidou.mybatisplus.extension.plugins.pagination.Page;
 import com.ruoyi.loanpricing.domain.entity.LoanPricingWorkflow;
+import com.ruoyi.loanpricing.domain.vo.LoanPricingWorkflowListVO;
+import org.apache.ibatis.annotations.Param;
 
 /**
  * 利率定价流程Mapper接口
@@ -11,5 +15,6 @@ import com.ruoyi.loanpricing.domain.entity.LoanPricingWorkflow;
  */
 public interface LoanPricingWorkflowMapper extends BaseMapper<LoanPricingWorkflow>
 {
-
+    IPage<LoanPricingWorkflowListVO> selectWorkflowPageWithRates(Page<?> page,
+                                                                 @Param("query") LoanPricingWorkflow query);
 }

ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/service/ILoanPricingWorkflowService.java

@@ -5,6 +5,7 @@ import com.baomidou.mybatisplus.extension.plugins.pagination.Page;
 import com.ruoyi.loanpricing.domain.dto.CorporateLoanPricingCreateDTO;
 import com.ruoyi.loanpricing.domain.dto.PersonalLoanPricingCreateDTO;
 import com.ruoyi.loanpricing.domain.entity.LoanPricingWorkflow;
+import com.ruoyi.loanpricing.domain.vo.LoanPricingWorkflowListVO;
 import com.ruoyi.loanpricing.domain.vo.LoanPricingWorkflowVO;
 
 import java.util.List;
@@ -48,7 +49,7 @@ public interface ILoanPricingWorkflowService
      * @param loanPricingWorkflow 利率定价流程信息
      * @return 分页结果
      */
-    public IPage<LoanPricingWorkflow> selectLoanPricingPage(Page<LoanPricingWorkflow> page, LoanPricingWorkflow loanPricingWorkflow);
+    public IPage<LoanPricingWorkflowListVO> selectLoanPricingPage(Page<LoanPricingWorkflowListVO> page, LoanPricingWorkflow loanPricingWorkflow);
 
     /**
      * 查询利率定价流程详情

ruoyi-loan-pricing/src/main/java/com/ruoyi/loanpricing/service/impl/LoanPricingWorkflowServiceImpl.java

@@ -8,6 +8,7 @@ import com.ruoyi.loanpricing.domain.dto.PersonalLoanPricingCreateDTO;
 import com.ruoyi.loanpricing.domain.entity.LoanPricingWorkflow;
 import com.ruoyi.loanpricing.domain.entity.ModelCorpOutputFields;
 import com.ruoyi.loanpricing.domain.entity.ModelRetailOutputFields;
+import com.ruoyi.loanpricing.domain.vo.LoanPricingWorkflowListVO;
 import com.ruoyi.loanpricing.domain.vo.LoanPricingWorkflowVO;
 import com.ruoyi.loanpricing.mapper.LoanPricingWorkflowMapper;
 import com.ruoyi.loanpricing.mapper.ModelCorpOutputFieldsMapper;
@@ -126,12 +127,9 @@ public class LoanPricingWorkflowServiceImpl implements ILoanPricingWorkflowServi
      * @return 利率定价流程
      */
     @Override
-    public IPage<LoanPricingWorkflow> selectLoanPricingPage(Page<LoanPricingWorkflow> page, LoanPricingWorkflow loanPricingWorkflow)
+    public IPage<LoanPricingWorkflowListVO> selectLoanPricingPage(Page<LoanPricingWorkflowListVO> page, LoanPricingWorkflow loanPricingWorkflow)
     {
-        LambdaQueryWrapper<LoanPricingWorkflow> wrapper = buildQueryWrapper(loanPricingWorkflow);
-        // 按更新时间倒序
-        wrapper.orderByDesc(LoanPricingWorkflow::getUpdateTime);
-        return loanPricingWorkflowMapper.selectPage(page, wrapper);
+        return loanPricingWorkflowMapper.selectWorkflowPageWithRates(page, loanPricingWorkflow);
     }
 
     /**
@@ -153,10 +151,18 @@ public class LoanPricingWorkflowServiceImpl implements ILoanPricingWorkflowServi
         if (Objects.nonNull(loanPricingWorkflow.getModelOutputId())){
             if (loanPricingWorkflow.getCustType().equals("个人")){
                 ModelRetailOutputFields modelRetailOutputFields = modelRetailOutputFieldsMapper.selectById(loanPricingWorkflow.getModelOutputId());
+                if (Objects.nonNull(modelRetailOutputFields))
+                {
+                    loanPricingWorkflow.setLoanRate(modelRetailOutputFields.getCalculateRate());
+                }
                 loanPricingWorkflowVO.setModelRetailOutputFields(modelRetailOutputFields);
             }
             if (loanPricingWorkflow.getCustType().equals("企业")){
                 ModelCorpOutputFields modelCorpOutputFields = modelCorpOutputFieldsMapper.selectById(loanPricingWorkflow.getModelOutputId());
+                if (Objects.nonNull(modelCorpOutputFields))
+                {
+                    loanPricingWorkflow.setLoanRate(modelCorpOutputFields.getCalculateRate());
+                }
                 loanPricingWorkflowVO.setModelCorpOutputFields(modelCorpOutputFields);
             }
         }

ruoyi-loan-pricing/src/main/resources/mapper/loanpricing/LoanPricingWorkflowMapper.xml

@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8" ?>
+<!DOCTYPE mapper
+        PUBLIC "-//mybatis.org//DTD Mapper 3.0//EN"
+        "http://mybatis.org/dtd/mybatis-3-mapper.dtd">
+<mapper namespace="com.ruoyi.loanpricing.mapper.LoanPricingWorkflowMapper">
+
+    <select id="selectWorkflowPageWithRates" resultType="com.ruoyi.loanpricing.domain.vo.LoanPricingWorkflowListVO">
+        SELECT
+            lpw.serial_num AS serialNum,
+            lpw.cust_name AS custName,
+            lpw.cust_type AS custType,
+            lpw.guar_type AS guarType,
+            lpw.apply_amt AS applyAmt,
+            CASE
+                WHEN lpw.cust_type = '个人' THEN mr.calculate_rate
+                WHEN lpw.cust_type = '企业' THEN mc.calculate_rate
+                ELSE NULL
+            END AS calculateRate,
+            lpw.execute_rate AS executeRate,
+            lpw.create_time AS createTime,
+            lpw.create_by AS createBy
+        FROM loan_pricing_workflow lpw
+        LEFT JOIN model_retail_output_fields mr ON lpw.model_output_id = mr.id
+        LEFT JOIN model_corp_output_fields mc ON lpw.model_output_id = mc.id
+        <where>
+            <if test="query != null and query.createBy != null and query.createBy != ''">
+                AND lpw.create_by LIKE CONCAT('%', #{query.createBy}, '%')
+            </if>
+            <if test="query != null and query.custName != null and query.custName != ''">
+                AND lpw.cust_name LIKE CONCAT('%', #{query.custName}, '%')
+            </if>
+            <if test="query != null and query.orgCode != null and query.orgCode != ''">
+                AND lpw.org_code LIKE CONCAT('%', #{query.orgCode}, '%')
+            </if>
+        </where>
+        ORDER BY lpw.update_time DESC
+    </select>
+
+</mapper>

ruoyi-loan-pricing/src/test/java/com/ruoyi/loanpricing/domain/vo/LoanPricingWorkflowListVOTest.java

@@ -0,0 +1,19 @@
+package com.ruoyi.loanpricing.domain.vo;
+
+import static org.junit.jupiter.api.Assertions.assertEquals;
+
+import org.junit.jupiter.api.Test;
+
+class LoanPricingWorkflowListVOTest
+{
+    @Test
+    void shouldExposeCalculateRateAndExecuteRateFields()
+    {
+        LoanPricingWorkflowListVO vo = new LoanPricingWorkflowListVO();
+        vo.setCalculateRate("6.15");
+        vo.setExecuteRate("5.80");
+
+        assertEquals("6.15", vo.getCalculateRate());
+        assertEquals("5.80", vo.getExecuteRate());
+    }
+}

ruoyi-loan-pricing/src/test/java/com/ruoyi/loanpricing/service/impl/LoanPricingWorkflowServiceImplTest.java

@@ -0,0 +1,99 @@
+package com.ruoyi.loanpricing.service.impl;
+
+import static org.junit.jupiter.api.Assertions.assertEquals;
+import static org.mockito.ArgumentMatchers.any;
+import static org.mockito.Mockito.when;
+
+import com.baomidou.mybatisplus.core.metadata.IPage;
+import com.baomidou.mybatisplus.extension.plugins.pagination.Page;
+import com.ruoyi.loanpricing.domain.entity.LoanPricingWorkflow;
+import com.ruoyi.loanpricing.domain.entity.ModelCorpOutputFields;
+import com.ruoyi.loanpricing.domain.entity.ModelRetailOutputFields;
+import com.ruoyi.loanpricing.domain.vo.LoanPricingWorkflowListVO;
+import com.ruoyi.loanpricing.domain.vo.LoanPricingWorkflowVO;
+import com.ruoyi.loanpricing.mapper.LoanPricingWorkflowMapper;
+import com.ruoyi.loanpricing.mapper.ModelCorpOutputFieldsMapper;
+import com.ruoyi.loanpricing.mapper.ModelRetailOutputFieldsMapper;
+import com.ruoyi.loanpricing.service.LoanPricingModelService;
+import org.junit.jupiter.api.Test;
+import org.junit.jupiter.api.extension.ExtendWith;
+import org.mockito.InjectMocks;
+import org.mockito.Mock;
+import org.mockito.junit.jupiter.MockitoExtension;
+
+@ExtendWith(MockitoExtension.class)
+class LoanPricingWorkflowServiceImplTest
+{
+    @Mock
+    private LoanPricingWorkflowMapper loanPricingWorkflowMapper;
+
+    @Mock
+    private LoanPricingModelService loanPricingModelService;
+
+    @Mock
+    private ModelRetailOutputFieldsMapper modelRetailOutputFieldsMapper;
+
+    @Mock
+    private ModelCorpOutputFieldsMapper modelCorpOutputFieldsMapper;
+
+    @InjectMocks
+    private LoanPricingWorkflowServiceImpl loanPricingWorkflowService;
+
+    @Test
+    void shouldReturnPagedWorkflowListWithCalculateRate()
+    {
+        LoanPricingWorkflowListVO row = new LoanPricingWorkflowListVO();
+        row.setCalculateRate("6.15");
+
+        Page<LoanPricingWorkflowListVO> pageResult = new Page<>(1, 10);
+        pageResult.setRecords(java.util.List.of(row));
+
+        when(loanPricingWorkflowMapper.selectWorkflowPageWithRates(any(), any())).thenReturn(pageResult);
+
+        IPage<LoanPricingWorkflowListVO> result = loanPricingWorkflowService.selectLoanPricingPage(new Page<>(1, 10), new LoanPricingWorkflow());
+
+        assertEquals("6.15", result.getRecords().get(0).getCalculateRate());
+    }
+
+    @Test
+    void shouldUseRetailModelOutputCalculateRateForWorkflowDetail()
+    {
+        LoanPricingWorkflow workflow = new LoanPricingWorkflow();
+        workflow.setSerialNum("P20260328001");
+        workflow.setCustType("个人");
+        workflow.setModelOutputId(11L);
+        workflow.setLoanRate("4.35");
+
+        ModelRetailOutputFields retailOutputFields = new ModelRetailOutputFields();
+        retailOutputFields.setCalculateRate("6.15");
+
+        when(loanPricingWorkflowMapper.selectOne(any())).thenReturn(workflow);
+        when(modelRetailOutputFieldsMapper.selectById(11L)).thenReturn(retailOutputFields);
+
+        LoanPricingWorkflowVO result = loanPricingWorkflowService.selectLoanPricingBySerialNum("P20260328001");
+
+        assertEquals("6.15", result.getLoanPricingWorkflow().getLoanRate());
+        assertEquals("6.15", result.getModelRetailOutputFields().getCalculateRate());
+    }
+
+    @Test
+    void shouldUseCorporateModelOutputCalculateRateForWorkflowDetail()
+    {
+        LoanPricingWorkflow workflow = new LoanPricingWorkflow();
+        workflow.setSerialNum("C20260328001");
+        workflow.setCustType("企业");
+        workflow.setModelOutputId(22L);
+        workflow.setLoanRate("3.80");
+
+        ModelCorpOutputFields corpOutputFields = new ModelCorpOutputFields();
+        corpOutputFields.setCalculateRate("3.932");
+
+        when(loanPricingWorkflowMapper.selectOne(any())).thenReturn(workflow);
+        when(modelCorpOutputFieldsMapper.selectById(22L)).thenReturn(corpOutputFields);
+
+        LoanPricingWorkflowVO result = loanPricingWorkflowService.selectLoanPricingBySerialNum("C20260328001");
+
+        assertEquals("3.932", result.getLoanPricingWorkflow().getLoanRate());
+        assertEquals("3.932", result.getModelCorpOutputFields().getCalculateRate());
+    }
+}

ruoyi-ui/src/api/monitor/cache.js

@@ -1,6 +1,6 @@
 import request from '@/utils/request'
 
-// 查询缓存详细
+// 查询缓存概览
 export function getCache() {
   return request({
     url: '/monitor/cache',
@@ -32,7 +32,7 @@ export function getCacheValue(cacheName, cacheKey) {
   })
 }
 
-// 清理指定名称缓存
+// 清理指定名称下的缓存
 export function clearCacheName(cacheName) {
   return request({
     url: '/monitor/cache/clearCacheName/' + cacheName,

ruoyi-ui/src/views/loanPricing/workflow/index.vue

@@ -50,7 +50,8 @@
       <el-table-column label="客户类型" align="center" prop="custType" width="100" />
       <el-table-column label="担保方式" align="center" prop="guarType" width="100" />
       <el-table-column label="申请金额(元)" align="center" prop="applyAmt" width="120" />
-      <el-table-column label="贷款利率(%)" align="center" prop="loanRate" width="100" />
+      <el-table-column label="测算利率(%)" align="center" prop="calculateRate" width="100" />
+      <el-table-column label="执行利率(%)" align="center" prop="executeRate" width="100" />
       <el-table-column label="创建时间" align="center" prop="createTime" width="160">
         <template slot-scope="scope">
           <span>{{ parseTime(scope.row.createTime) }}</span>
@@ -130,6 +131,9 @@ export default {
   created() {
     this.getList()
   },
+  activated() {
+    this.getList()
+  },
   methods: {
     /** 查询利率定价流程列表 */
     getList() {

ruoyi-ui/src/views/monitor/cache/index.vue

@@ -8,34 +8,34 @@
             <table cellspacing="0" style="width: 100%">
               <tbody>
                 <tr>
-                  <td class="el-table__cell is-leaf"><div class="cell">Redis版本</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell" v-if="cache.info">{{ cache.info.redis_version }}</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">缓存类型</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">{{ cacheTypeText }}</div></td>
                   <td class="el-table__cell is-leaf"><div class="cell">运行模式</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell" v-if="cache.info">{{ cache.info.redis_mode == "standalone" ? "单机" : "集群" }}</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell">端口</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell" v-if="cache.info">{{ cache.info.tcp_port }}</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell">客户端数</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell" v-if="cache.info">{{ cache.info.connected_clients }}</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">{{ cacheModeText }}</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">总键数</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">{{ displayDbSize }}</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">写入次数</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">{{ cache.info.write_count }}</div></td>
                 </tr>
                 <tr>
-                  <td class="el-table__cell is-leaf"><div class="cell">运行时间(天)</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell" v-if="cache.info">{{ cache.info.uptime_in_days }}</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell">使用内存</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell" v-if="cache.info">{{ cache.info.used_memory_human }}</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell">使用CPU</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell" v-if="cache.info">{{ parseFloat(cache.info.used_cpu_user_children).toFixed(2) }}</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell">内存配置</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell" v-if="cache.info">{{ cache.info.maxmemory_human }}</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">命中次数</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">{{ cache.info.hit_count }}</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">未命中次数</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">{{ cache.info.miss_count }}</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">过期清理次数</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">{{ cache.info.expired_count }}</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">命中率</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">{{ hitRateText }}</div></td>
                 </tr>
                 <tr>
-                  <td class="el-table__cell is-leaf"><div class="cell">AOF是否开启</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell" v-if="cache.info">{{ cache.info.aof_enabled == "0" ? "否" : "是" }}</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell">RDB是否成功</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell" v-if="cache.info">{{ cache.info.rdb_last_bgsave_status }}</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell">Key数量</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell" v-if="cache.dbSize">{{ cache.dbSize }} </div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell">网络入口/出口</div></td>
-                  <td class="el-table__cell is-leaf"><div class="cell" v-if="cache.info">{{ cache.info.instantaneous_input_kbps }}kps/{{cache.info.instantaneous_output_kbps}}kps</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">统计说明</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">进程内累计统计</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">监控范围</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">当前应用实例</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">图表数据项</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">{{ commandStats.length }}</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">监控采样时间</div></td>
+                  <td class="el-table__cell is-leaf"><div class="cell">{{ sampleTime }}</div></td>
                 </tr>
               </tbody>
             </table>
@@ -54,7 +54,7 @@
 
       <el-col :span="12" class="card-box">
         <el-card>
-          <div slot="header"><span><i class="el-icon-odometer"></i> 内存信息</span></div>
+          <div slot="header"><span><i class="el-icon-odometer"></i> 缓存命中概览</span></div>
           <div class="el-table el-table--enable-row-hover el-table--medium">
             <div ref="usedmemory" style="height: 420px" />
           </div>
@@ -74,74 +74,197 @@ export default {
     return {
       // 统计命令信息
       commandstats: null,
-      // 使用内存
+      // 缓存统计
       usedmemory: null,
       // cache信息
-      cache: []
+      cache: {
+        info: {
+          cache_type: "IN_MEMORY",
+          cache_mode: "single-instance",
+          key_size: 0,
+          hit_count: 0,
+          miss_count: 0,
+          expired_count: 0,
+          write_count: 0
+        },
+        dbSize: 0,
+        commandStats: []
+      },
+      sampleTime: "-",
+      resizeHandler: null
     }
   },
   created() {
-    this.getList()
     this.openLoading()
+    this.getList()
+  },
+  beforeDestroy() {
+    if (this.resizeHandler) {
+      window.removeEventListener("resize", this.resizeHandler)
+    }
+    if (this.commandstats) {
+      this.commandstats.dispose()
+    }
+    if (this.usedmemory) {
+      this.usedmemory.dispose()
+    }
+  },
+  computed: {
+    cacheTypeText() {
+      return this.formatCacheType(this.cache.info.cache_type)
+    },
+    cacheModeText() {
+      return this.formatCacheMode(this.cache.info.cache_mode)
+    },
+    displayDbSize() {
+      return this.toNumber(this.cache.dbSize || this.cache.info.key_size)
+    },
+    hitRateText() {
+      const hitCount = this.toNumber(this.cache.info.hit_count)
+      const missCount = this.toNumber(this.cache.info.miss_count)
+      const total = hitCount + missCount
+      if (!total) {
+        return "0.00%"
+      }
+      return ((hitCount / total) * 100).toFixed(2) + "%"
+    },
+    commandStats() {
+      return this.normalizeCommandStats(this.cache.commandStats)
+    }
   },
   methods: {
     /** 查缓存询信息 */
     getList() {
       getCache().then((response) => {
-        this.cache = response.data
+        this.cache = this.normalizeCacheData(response.data)
+        this.sampleTime = this.formatSampleTime(new Date())
         this.$modal.closeLoading()
-
-        this.commandstats = echarts.init(this.$refs.commandstats, "macarons")
-        this.commandstats.setOption({
-          tooltip: {
-            trigger: "item",
-            formatter: "{a} <br/>{b} : {c} ({d}%)",
-          },
-          series: [
-            {
-              name: "命令",
-              type: "pie",
-              roseType: "radius",
-              radius: [15, 95],
-              center: ["50%", "38%"],
-              data: response.data.commandStats,
-              animationEasing: "cubicInOut",
-              animationDuration: 1000,
-            }
-          ]
-        })
-        this.usedmemory = echarts.init(this.$refs.usedmemory, "macarons")
-        this.usedmemory.setOption({
-          tooltip: {
-            formatter: "{b} <br/>{a} : " + this.cache.info.used_memory_human,
-          },
-          series: [
-            {
-              name: "峰值",
-              type: "gauge",
-              min: 0,
-              max: 1000,
-              detail: {
-                formatter: this.cache.info.used_memory_human,
-              },
-              data: [
-                {
-                  value: parseFloat(this.cache.info.used_memory_human),
-                  name: "内存消耗",
-                }
-              ]
-            }
-          ]
-        })
-        window.addEventListener("resize", () => {
-          this.commandstats.resize()
-          this.usedmemory.resize()
+        this.$nextTick(() => {
+          this.renderCharts()
         })
+      }).catch(() => {
+        this.cache = this.normalizeCacheData()
+        this.sampleTime = "-"
+        this.$modal.closeLoading()
       })
     },
     // 打开加载层
     openLoading() {
       this.$modal.loading("正在加载缓存监控数据，请稍候！")
+    },
+    normalizeCacheData(data) {
+      const source = data || {}
+      const info = source.info || {}
+      return {
+        info: {
+          cache_type: info.cache_type || "IN_MEMORY",
+          cache_mode: info.cache_mode || "single-instance",
+          key_size: this.toNumber(info.key_size),
+          hit_count: this.toNumber(info.hit_count),
+          miss_count: this.toNumber(info.miss_count),
+          expired_count: this.toNumber(info.expired_count),
+          write_count: this.toNumber(info.write_count)
+        },
+        dbSize: this.toNumber(source.dbSize || info.key_size),
+        commandStats: source.commandStats || []
+      }
+    },
+    normalizeCommandStats(commandStats) {
+      const stats = Array.isArray(commandStats) ? commandStats : []
+      return stats.map((item) => ({
+        name: this.statLabel(item.name),
+        value: this.toNumber(item.value)
+      }))
+    },
+    statLabel(name) {
+      const labelMap = {
+        hit_count: "命中次数",
+        miss_count: "未命中次数",
+        expired_count: "过期清理次数",
+        write_count: "写入次数"
+      }
+      return labelMap[name] || name || "未命名统计"
+    },
+    formatCacheType(type) {
+      const typeMap = {
+        IN_MEMORY: "进程内缓存"
+      }
+      return typeMap[type] || type || "-"
+    },
+    formatCacheMode(mode) {
+      const modeMap = {
+        "single-instance": "单实例"
+      }
+      return modeMap[mode] || mode || "-"
+    },
+    formatSampleTime(date) {
+      const current = date || new Date()
+      const pad = (value) => String(value).padStart(2, "0")
+      return `${current.getFullYear()}-${pad(current.getMonth() + 1)}-${pad(current.getDate())} ${pad(current.getHours())}:${pad(current.getMinutes())}:${pad(current.getSeconds())}`
+    },
+    toNumber(value) {
+      const parsedValue = Number(value)
+      return Number.isFinite(parsedValue) ? parsedValue : 0
+    },
+    renderCharts() {
+      if (!this.commandstats) {
+        this.commandstats = echarts.init(this.$refs.commandstats, "macarons")
+      }
+      if (!this.usedmemory) {
+        this.usedmemory = echarts.init(this.$refs.usedmemory, "macarons")
+      }
+      this.commandstats.setOption({
+        tooltip: {
+          trigger: "item",
+          formatter: "{a} <br/>{b} : {c} ({d}%)"
+        },
+        series: [
+          {
+            name: "缓存统计",
+            type: "pie",
+            roseType: "radius",
+            radius: [15, 95],
+            center: ["50%", "38%"],
+            data: this.commandStats,
+            animationEasing: "cubicInOut",
+            animationDuration: 1000
+          }
+        ]
+      })
+      this.usedmemory.setOption({
+        tooltip: {
+          trigger: "axis",
+          axisPointer: {
+            type: "shadow"
+          }
+        },
+        xAxis: {
+          type: "category",
+          data: this.commandStats.map((item) => item.name),
+          axisTick: {
+            alignWithLabel: true
+          }
+        },
+        yAxis: {
+          type: "value",
+          minInterval: 1
+        },
+        series: [
+          {
+            name: "统计次数",
+            type: "bar",
+            barMaxWidth: 48,
+            data: this.commandStats.map((item) => item.value)
+          }
+        ]
+      })
+      if (!this.resizeHandler) {
+        this.resizeHandler = () => {
+          this.commandstats && this.commandstats.resize()
+          this.usedmemory && this.usedmemory.resize()
+        }
+        window.addEventListener("resize", this.resizeHandler)
+      }
     }
   }
 }

ruoyi-ui/src/views/monitor/cache/list.vue

@@ -175,7 +175,10 @@ export default {
     getCacheNames() {
       this.loading = true
       listCacheName().then(response => {
-        this.cacheNames = response.data
+        this.cacheNames = response.data || []
+        this.loading = false
+      }).catch(() => {
+        this.cacheNames = []
         this.loading = false
       })
     },
@@ -188,7 +191,7 @@ export default {
     handleClearCacheName(row) {
       clearCacheName(row.cacheName).then(response => {
         this.$modal.msgSuccess("清理缓存名称[" + row.cacheName + "]成功")
-        this.getCacheKeys()
+        this.getCacheKeys(row)
       })
     },
     /** 查询缓存键名列表 */
@@ -199,7 +202,13 @@ export default {
       }
       this.subLoading = true
       listCacheKey(cacheName).then(response => {
-        this.cacheKeys = response.data
+        this.cacheKeys = response.data || []
+        this.cacheForm = {}
+        this.subLoading = false
+        this.nowCacheName = cacheName
+      }).catch(() => {
+        this.cacheKeys = []
+        this.cacheForm = {}
         this.subLoading = false
         this.nowCacheName = cacheName
       })
@@ -227,13 +236,16 @@ export default {
     /** 查询缓存内容详细 */
     handleCacheValue(cacheKey) {
       getCacheValue(this.nowCacheName, cacheKey).then(response => {
-        this.cacheForm = response.data
+        this.cacheForm = response.data || {}
       })
     },
     /** 清理全部缓存 */
     handleClearCacheAll() {
       clearCacheAll().then(response => {
         this.$modal.msgSuccess("清理全部缓存成功")
+        this.cacheKeys = []
+        this.cacheForm = {}
+        this.nowCacheName = ""
       })
     }
   }

ruoyi-ui/tests/workflow-index-refresh.test.js

@@ -0,0 +1,52 @@
+const assert = require('assert')
+const fs = require('fs')
+const path = require('path')
+const vm = require('vm')
+
+function loadComponentOptions(filePath) {
+  const source = fs.readFileSync(filePath, 'utf8')
+  const scriptMatch = source.match(/<script>([\s\S]*?)<\/script>/)
+
+  if (!scriptMatch) {
+    throw new Error('未找到组件脚本内容')
+  }
+
+  const importNames = []
+  const importPattern = /^import\s+([A-Za-z0-9_]+)\s+from\s+.*$/gm
+  let importMatch = importPattern.exec(scriptMatch[1])
+  while (importMatch) {
+    importNames.push(importMatch[1])
+    importMatch = importPattern.exec(scriptMatch[1])
+  }
+
+  const stubImports = importNames.map(name => `const ${name} = {};`).join('\n')
+  const transformed = `${stubImports}\n${scriptMatch[1]}`
+    .replace(/^import .*$/gm, '')
+    .replace(/export default/, 'module.exports =')
+
+  const sandbox = {
+    module: { exports: {} },
+    exports: {},
+    require,
+    console
+  }
+
+  vm.runInNewContext(transformed, sandbox, { filename: filePath })
+  return sandbox.module.exports
+}
+
+const filePath = path.resolve(__dirname, '../src/views/loanPricing/workflow/index.vue')
+const component = loadComponentOptions(filePath)
+
+assert.strictEqual(typeof component.activated, 'function', '流程列表页应在激活时刷新数据')
+
+let refreshCount = 0
+component.activated.call({
+  getList() {
+    refreshCount += 1
+  }
+})
+
+assert.strictEqual(refreshCount, 1, '流程列表页激活时应调用一次 getList')
+
+console.log('workflow-index-refresh test passed')