140 lines
4.3 KiB
Markdown
140 lines
4.3 KiB
Markdown
# Results Overview Backend Implementation Plan
|
|
|
|
> **For agentic workers:** REQUIRED: Use superpowers:subagent-driven-development (if subagents available) or superpowers:executing-plans to implement this plan. Steps use checkbox (`- [ ]`) syntax for tracking.
|
|
|
|
**Goal:** 明确结果总览页面本轮仅实现前端静态页面，不新增任何后端接口、数据库脚本或服务逻辑，并通过边界核验避免误开后端改动。
|
|
|
|
**Architecture:** 本次页面方案基于原型图和本地 mock 数据，继续使用前端 `PreliminaryCheck.vue` 直出静态内容，不依赖 `ccdi-project`、`ruoyi-admin` 或其他 Java 模块提供新接口。后端实施计划的重点不是编码，而是冻结边界、校验现有链路不被误改，并补充“本次无需后端实施”的记录。
|
|
|
|
**Tech Stack:** Java 21, Spring Boot 3, Maven, Markdown documentation
|
|
|
|
---
|
|
|
|
### Task 1: 核定本次需求不涉及后端开发
|
|
|
|
**Files:**
|
|
- Modify: `docs/plans/backend/2026-03-19-results-overview-backend-implementation.md`
|
|
- Test: `docs/design/2026-03-19-results-overview-page-design.md`
|
|
|
|
- [ ] **Step 1: Write the failing review checklist**
|
|
|
|
先写出边界检查清单，锁定本轮不得出现以下后端诉求：
|
|
|
|
```md
|
|
- 不新增 Controller 接口
|
|
- 不新增 Service/Mapper 查询
|
|
- 不新增 SQL 脚本
|
|
- 不修改项目详情后端返回结构
|
|
- 不为静态页面补造 mock 后端接口
|
|
```
|
|
|
|
- [ ] **Step 2: Run boundary review to verify current intent**
|
|
|
|
Run:
|
|
|
|
```bash
|
|
sed -n '1,220p' docs/design/2026-03-19-results-overview-page-design.md
|
|
```
|
|
|
|
Expected:
|
|
|
|
- 设计文档明确写明“本次设计只覆盖前端内容展示，不包含真实接口接入”
|
|
- 若读到任何接口或数据库变更要求，则视为边界失败，需要先回到设计文档修正
|
|
|
|
- [ ] **Step 3: Record the minimal backend decision**
|
|
|
|
在本计划中明确写入后端结论：
|
|
|
|
```md
|
|
## 后端结论
|
|
- 本轮不实施后端开发
|
|
- 后端仓库代码保持不变
|
|
- 若后续从静态页升级为真实数据页，需要重新发起后端设计与实施计划
|
|
```
|
|
|
|
- [ ] **Step 4: Re-run boundary review**
|
|
|
|
Run:
|
|
|
|
```bash
|
|
grep -n "不实施后端开发\\|不新增 Controller 接口\\|不新增 SQL 脚本" docs/plans/backend/2026-03-19-results-overview-backend-implementation.md
|
|
```
|
|
|
|
Expected:
|
|
|
|
- 能检索到明确边界文案
|
|
- 说明后续执行者不会误将该需求扩展成全栈改造
|
|
|
|
- [ ] **Step 5: Commit**
|
|
|
|
```bash
|
|
git add docs/plans/backend/2026-03-19-results-overview-backend-implementation.md
|
|
git commit -m "补充结果总览页面后端实施边界"
|
|
```
|
|
|
|
### Task 2: 补充“无需后端实施”的验证与交接记录
|
|
|
|
**Files:**
|
|
- Create: `docs/tests/records/2026-03-19-results-overview-backend-verification.md`
|
|
- Create: `docs/reports/implementation/2026-03-19-results-overview-backend-implementation.md`
|
|
|
|
- [ ] **Step 1: Write the failing record skeleton**
|
|
|
|
先创建验证记录模板，锁定这次核验的是“无后端改动”而不是“后端功能实现”：
|
|
|
|
```md
|
|
# 结果总览后端验证记录
|
|
|
|
## 验证范围
|
|
- 本轮是否新增后端接口
|
|
- 本轮是否新增数据库脚本
|
|
- 本轮是否修改 Java 模块代码
|
|
```
|
|
|
|
- [ ] **Step 2: Run workspace inspection**
|
|
|
|
Run:
|
|
|
|
```bash
|
|
git diff --name-only HEAD~1..HEAD
|
|
```
|
|
|
|
Expected:
|
|
|
|
- 若当前提交仅涉及设计/计划/前端文件，则满足本轮边界
|
|
- 若出现 `ruoyi-admin`、`ccdi-project`、`sql/` 等后端路径，则需要人工复核是否偏离需求
|
|
|
|
- [ ] **Step 3: Write minimal implementation record**
|
|
|
|
在 `docs/reports/implementation/2026-03-19-results-overview-backend-implementation.md` 中写清：
|
|
|
|
```md
|
|
# 结果总览后端实施记录
|
|
|
|
## 结论
|
|
- 本轮未实施后端代码改动
|
|
- 页面数据由前端本地 mock 驱动
|
|
- 后端仅保留后续真实数据化扩展空间
|
|
```
|
|
|
|
- [ ] **Step 4: Re-run record review**
|
|
|
|
Run:
|
|
|
|
```bash
|
|
sed -n '1,200p' docs/tests/records/2026-03-19-results-overview-backend-verification.md
|
|
sed -n '1,200p' docs/reports/implementation/2026-03-19-results-overview-backend-implementation.md
|
|
```
|
|
|
|
Expected:
|
|
|
|
- 两份文档都明确表达“本轮无后端实施”
|
|
- 后续联调人员可直接据此判断无需等待后端发布
|
|
|
|
- [ ] **Step 5: Commit**
|
|
|
|
```bash
|
|
git add docs/tests/records/2026-03-19-results-overview-backend-verification.md docs/reports/implementation/2026-03-19-results-overview-backend-implementation.md
|
|
git commit -m "补充结果总览页面后端验证记录"
|
|
```
|