docs(status): correct two stale duplicate Phase 22 ✅ tables disproved by KEEP-VERIFY
STATUS.md contained two duplicate legacy Phase 22 blocks still claiming: - "application.yml 默认配置 ✅ (15个V1.1 flag)" / "application-dev.yml + application-docker.yml 配置 ✅" — verified false: all four yml files (application.yml / -dev / -docker / -production) contain neither a `features:` block nor any flag key; defaults are Java field defaults only. - "P22-T01..T05 ✅" and "P22-T07 ✅" — these are dead config: zero business call sites for the five module toggles, zero references for the private storage bucket flags. Both blocks now carry a "superseded by the 2026-09-18 authoritative section" notice with per-row measured verdicts (T06 remains ✅ as genuinely enforced). No code change; doc-only.
This commit is contained in:
+24
-24
@@ -586,33 +586,33 @@ MinIO: localhost:9003 (凭证由本地环境变量提供)
|
||||
|
||||
**Phase 20(Analytics数据统计扩展)— 已完成** ✅
|
||||
|
||||
### Phase 22 — 部署运维配置扩展 ✅ 已完成
|
||||
| 任务 | 状态 |
|
||||
|------|------|
|
||||
| P22-T01 counselingEnabled flag | ✅ |
|
||||
| P22-T02 premaritalEnabled flag | ✅ |
|
||||
| P22-T03 contentEnabled flag | ✅ |
|
||||
| P22-T04 serviceLocationEnabled flag | ✅ |
|
||||
| P22-T05 localEligibilityEnabled flag | ✅ |
|
||||
| P22-T06 local evidence upload policy | ✅ (maxFiles/maxSizeMB/allowedTypes) |
|
||||
| P22-T07 private storage for counseling attachments | ✅ (private/bucket) |
|
||||
| FeatureFlagController API | ✅ (GET/PUT /operator/feature-flags) |
|
||||
| application.yml 默认配置 | ✅ (15个V1.1 flag) |
|
||||
### Phase 22 — 部署运维配置扩展(历史声明,已被上方 2026-09-18 权威结论取代)
|
||||
> ⚠️ 下表为历史进度声明,**经 KEEP-VERIFY 实测部分不成立**,以本节上方「Phase 22 — 部署运维配置扩展(Feature Flag)✅(KEEP-VERIFY 复验关闭,2026-09-18)」为准。
|
||||
|
||||
| 任务 | 历史声明 | 实测结论 |
|
||||
|------|---------|---------|
|
||||
| P22-T01 counselingEnabled flag | ✅ | ⚠️ 死配置:全仓无业务调用点,不 gate 任何功能 |
|
||||
| P22-T02 premaritalEnabled flag | ✅ | ⚠️ 死配置:同上 |
|
||||
| P22-T03 contentEnabled flag | ✅ | ⚠️ 死配置:同上 |
|
||||
| P22-T04 serviceLocationEnabled flag | ✅ | ⚠️ 死配置:同上 |
|
||||
| P22-T05 localEligibilityEnabled flag | ✅ | ⚠️ 死配置:同上 |
|
||||
| P22-T06 local evidence upload policy | ✅ | ✅ 属实:`LocalEligibilityService` 强制启用开关+数量上限,`PhotoService` 强制 size+类型 |
|
||||
| P22-T07 private storage for counseling attachments | ✅ | ⚠️ 死配置:`counselingAttachmentsPrivate/Bucket` 零引用,存储实走 `object-storage.bucket-private` |
|
||||
| FeatureFlagController API | ✅ | ⚠️ 曾含 D-22-A(仅布尔,7 个非布尔 flag 更新必失败)与 D-22-B(缺 value 静默置 false);已修复并补 7 例守卫 |
|
||||
| application.yml 默认配置(15个 flag) | ✅ | ❌ 不成立:yml 无 `features:` 块,实际为 Java 字段默认值 |
|
||||
|
||||
**Phase 21(账户生命周期增量)— 已完成** ✅
|
||||
|
||||
### Phase 22 — 部署运维配置扩展 ✅ 已完成
|
||||
| 任务 | 状态 |
|
||||
|------|------|
|
||||
| P22-T01 counselingEnabled flag | ✅ |
|
||||
| P22-T02 premaritalEnabled flag | ✅ |
|
||||
| P22-T03 contentEnabled flag | ✅ |
|
||||
| P22-T04 serviceLocationEnabled flag | ✅ |
|
||||
| P22-T05 localEligibilityEnabled flag | ✅ |
|
||||
| P22-T06 local evidence upload policy | ✅ |
|
||||
| P22-T07 private storage for counseling attachments | ✅ |
|
||||
| FeatureFlagController API | ✅ |
|
||||
| application-dev.yml + application-docker.yml 配置 | ✅ |
|
||||
### Phase 22 — 部署运维配置扩展(重复的历史声明块,已作废)
|
||||
> ⚠️ 与上一条为同一 Phase 的重复历史声明,同样已被上方 2026-09-18 权威结论取代,不再逐项重复。
|
||||
|
||||
| 任务 | 实测结论 |
|
||||
|------|---------|
|
||||
| P22-T01~T05 五个模块开关 flag | ⚠️ 死配置(无业务调用点) |
|
||||
| P22-T06 local evidence upload policy | ✅ 属实(真实强制) |
|
||||
| P22-T07 private storage for counseling attachments | ⚠️ 死配置(零引用) |
|
||||
| FeatureFlagController API | ✅ 已修复 D-22-A/D-22-B 并补守卫 |
|
||||
| application-dev.yml + application-docker.yml 配置 | ❌ 不成立:两份 yml 均无 `features:` 块 |
|
||||
|
||||
**Phase 21(账户生命周期增量)— 已完成** ✅
|
||||
|
||||
|
||||
Reference in New Issue
Block a user