docs(seal): 2026-09-30 封版验收判定与证据入库 + 台账假事实更正

代码封版点仍是 a0328a6;本提交只含验收证据与文档,用于把台账
§0 的「未达可判验收通过(唯一阻断 AUTH-D1)」改判为「封版通过
(含例外清单)」。

补齐 sealed 树上从未跑过的 5 项门禁并如实记录非全绿:
- 全站 check:axe EXIT=0(34 路由 × 双引擎 × 双主题,violation=0)
- 产物安全头 EXIT=0(每头单次,WARN 仅 HSTS 边缘注入)
- 生产目标 E2E 91 passed / 1 failed(唯一红 = firefox 并发墙钟,
  隔离与 4-project 复跑均绿;dev.db 指纹前后一致,未写库)
- 视觉只读 94 passed / 31 failed(20 缺参照 + 11 已过时参照,
  逐条归因;未写任何基线)
- check:motion EXIT=1 / 23 处(与周期 2 同数,未新增)

更正 4 处文档假事实:DEC-N21b(/admin 实有服务端 gating,入口是
src/proxy.ts 而非 middleware.ts)、视觉基线「85 张未提交」(实测
107 张全在库)、「无需重跑 db:seed」(seed 改过 modelCode 而
permissions 精确匹配)、lint 105→104。
This commit is contained in:
zhangxiang committed 2026-09-30 23:41:22 +08:00
1 parent a0328a623f
commit 1b8ffd5486
21 files changed
+5693 -12

No files matched your search

+2 -1
View File
@@ -31,12 +31,13 @@
- [x] CMS 全覆盖:法律页、新闻、团队、案例、服务、方案、产品、独立产品、首页运营位(ContentZone)、RBAC/工作流/媒体/通知全部从 CMS 读取并启用 ISR(3600s)
- [x] CMS 管理后台:角色权限界面(`/admin/roles`)、内容模型 × 操作权限矩阵、super_admin 锁定
- [x] 全量测试体系:单元 **134 suites / 1697 例** / 功能 E2E **1080 例**(270 例 × chromium + chromium-mobile + firefox + webkit 四个 project)/ 视觉回归 **125 例**(25 例 × 桌面·平板·移动·firefox·webkit 五个 project)/ 用户旅程 UJ-01~UJ-11 / Lighthouse / k6 负载压力 / 安全扫描,全部通过。**计数为 2026-09-23 本树复跑实测**(`npm run test:coverage` ⇒ `Test Suites: 134 passed` / `Tests: 1697 passed` / EXIT=0;`cd e2e && npx playwright test --list` ⇒ `Total: 1205 tests in 22 files` = 1080 + 125),非估算;计数随树漂移,引用请附复算命令
- [x] 全量测试体系:单元 **134 suites / 1697 例** / 功能 E2E **1080 例**(270 例 × chromium + chromium-mobile + firefox + webkit 四个 project)/ 视觉回归 **125 例**(25 例 × 桌面·平板·移动·firefox·webkit 五个 project)/ 用户旅程 UJ-01~UJ-11 / Lighthouse / k6 负载压力 / 安全扫描。**本条不再声明「全部通过」**:单元与真库集成层在封版树 `a0328a6` 上全绿(`npm run test:coverage`、`npm run test:integration:real`),但**视觉回归在封版树上实测 94 passed / 31 failed**(20 张缺参照 + 11 张已过时参照,属 AUTH-D3 追认范围,已逐条归因,非像素级产品缺陷),生产目标 E2E 实测 **91 passed / 1 failed**(唯一红为 firefox 并发墙钟)。**计数一律不在此复制**:以 `npm run test:coverage`、`cd e2e && npx playwright test --list`、`docs/acceptance/2026-09-30-seal/final-verdict.md` §1 表为现取入口
- [x] **官网产品模块定位(IHG/字节式品牌矩阵,2026-08-19)**:官网品牌宣传为主,产品矩阵页为聚合入口;成熟产品 `externalUrl` 外链独立站(NovaVis → novavis.p.novalon.cn);未成熟产品详情页占位,独立站上线后切换外链
- [x] **结构性文案全站 CMS 化(2026-08-19)**:新增 `page-copy` 内容模型承载全部营销页面章节标题/眉标/描述/CTA/空状态(首页 + 服务/方案/产品/案例/新闻列表页),「CMS 优先 + 硬编码兜底」不白屏;seed 写入 6 条,本地 db:seed 已生效
- [x] **信任证据补齐·阶段 0(成立 <1 年策略,2026-08-20)**:信任策略从「结果证据」转向「可验证的过程 + 能力 + 治理证据」——首页「首批客户共创计划」板块(共创进行中/产品内测中/成果授权公开三档如实状态 + 招募 CTA)+ 关于页资质「建设中」如实空态,零编造
- [x] **生产部署上线(2026-08-20)**:`deploy.sh deploy`(本地 dist → 远端容器重建)+ 生产库 seed(page-copy/methodology 数据)完成;生产目录 Drizzle 残留源码归档清理;站点全路由 200、生产库 Prisma 结构
- [x] **数字口径结构强制(2026-09-20,critique P0 收尾)**:共享数字样式渲染的指标(`metrics`/`outcomes`/`dataProofs`)统一携带 `basis: target|team-history|verified`,渲染端自动附口径角注、未声明保守回落 `target`;CMS 新增 `basis` select 录入字段;删除产品详情页「每一项指标都源自真实客户案例」「经实际场景验证」等虚构佐证并补注角注;`metrics-basis.test.ts` 机械校验声明完整性并拦截虚构佐证禁词
- [x] **五轮系统性 QA 封版(2026-09-21…28 修复,2026-09-30 封版)**:Q-1…Q-10 / S-1…S-24 共 30 处缺陷修复入库(假登出清服务端令牌、登录 IP 限流、停用令牌 fail-closed 收口、workflow 状态+审计交互式 `$transaction` 原子化、编辑器 richtext 防换行静默损毁、`StaggerReveal` 吞网格类致详情页塌成单列、首页 CMS 数组逐条守卫、about/contact/erp-upgrade 补 ISR=3600 等),每处带判别性 RED→GREEN 测试。跨周期台账 `docs/acceptance/qa-tracker.md`(§8 为现行判定),封版判定书与全部原始门禁输出见 `docs/acceptance/2026-09-30-seal/`。**判定 = 封版通过(含例外清单)**:例外均为「待业务口径」(4 条互斥 SLA、erp-upgrade 无 basis 数字)或「待授权的测试装配追认」(视觉基线、写库 E2E、全量变异),非代码质量问题
- [ ] **信任证据补齐·阶段 1/2(待内测/试点客户素材)**:如实披露「共创中/内测中/已交付」三档 + 经授权客户(脱敏);有交付成果后经授权公示可量化结果(零编造原则)——口径字段与 admin 录入口已就绪,待真实数据把 `basis` 从 `target` 升级为 `verified`
## 技术栈
File diff suppressed because it is too large. Load diff
@@ -0,0 +1,240 @@
🚀 启动 standalone 服务 :3100 ...
✅ 服务就绪,路由清单生成中...
> ruixin-website-react@1.0.0-phase1 check:axe:routes
> node scripts/accessibility/crawl-routes.mjs
crawled visited=34 reachable=33 urls=34 manifestExtra=16 skippedInternalDocs=1 -> /tmp/axe-routes-0930.xml
/
/_not-found
/about
/about/brand
/cases
/contact
/methodology
/news
/news/company-founded
/news/digital-transformation-solution
/privacy
/products
/products/bi
/products/cms
/products/crm
/products/erp
/products/erp-upgrade
/products/erp-upgrade-v3
/products/oa
/products/sds
/services
/services/consulting
/services/data
/services/software
/services/solutions
/solutions
/solutions/education
/solutions/finance
/solutions/healthcare
/solutions/logistics
/solutions/manufacturing
/solutions/retail
/team
/terms
AXE_ROUTES_EXIT=0
> ruixin-website-react@1.0.0-phase1 check:axe
> node scripts/accessibility/axe-node-count.mjs
chromium/light / status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /_not-found status=404 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /about status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /about/brand status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /cases status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /contact status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /methodology status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /news status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /news/company-founded status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /news/digital-transformation-solution status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /privacy status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /products status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /products/bi status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /products/cms status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /products/crm status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /products/erp status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /products/erp-upgrade status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /products/erp-upgrade-v3 status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /products/oa status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /products/sds status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /services status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /services/consulting status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /services/data status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /services/software status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /services/solutions status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /solutions status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /solutions/education status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /solutions/finance status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /solutions/healthcare status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /solutions/logistics status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /solutions/manufacturing status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /solutions/retail status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /team status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/light /terms status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark / status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /_not-found status=404 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /about status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /about/brand status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /cases status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /contact status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /methodology status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /news status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /news/company-founded status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /news/digital-transformation-solution status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /privacy status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /products status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /products/bi status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /products/cms status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /products/crm status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /products/erp status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /products/erp-upgrade status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /products/erp-upgrade-v3 status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /products/oa status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /products/sds status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /services status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /services/consulting status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /services/data status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /services/software status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /services/solutions status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /solutions status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /solutions/education status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /solutions/finance status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /solutions/healthcare status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /solutions/logistics status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /solutions/manufacturing status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /solutions/retail status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /team status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
chromium/dark /terms status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light / status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /_not-found status=404 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /about status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /about/brand status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /cases status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /contact status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /methodology status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /news status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /news/company-founded status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /news/digital-transformation-solution status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /privacy status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /products status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /products/bi status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /products/cms status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /products/crm status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /products/erp status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /products/erp-upgrade status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /products/erp-upgrade-v3 status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /products/oa status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /products/sds status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /services status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /services/consulting status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /services/data status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /services/software status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /services/solutions status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /solutions status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /solutions/education status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /solutions/finance status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /solutions/healthcare status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /solutions/logistics status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /solutions/manufacturing status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /solutions/retail status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /team status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/light /terms status=200 theme=light bg=rgb(255, 255, 255) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark / status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /_not-found status=404 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /about status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /about/brand status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /cases status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /contact status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /methodology status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /news status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /news/company-founded status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /news/digital-transformation-solution status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /privacy status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /products status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /products/bi status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /products/cms status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /products/crm status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /products/erp status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /products/erp-upgrade status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /products/erp-upgrade-v3 status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /products/oa status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /products/sds status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /services status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /services/consulting status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /services/data status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /services/software status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /services/solutions status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /solutions status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /solutions/education status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /solutions/finance status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /solutions/healthcare status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /solutions/logistics status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /solutions/manufacturing status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /solutions/retail status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /team status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
firefox/dark /terms status=200 theme=dark bg=rgb(10, 14, 20) rules=0 nodes=0 contrast=0 extra=0/3/3
SUMMARY {
"chromium/light": {
"pages": 34,
"themeMismatch": 0,
"bgMismatch": 0,
"contrastNodes": 0,
"violationNodes": 0,
"extraRuleNodes": 0,
"extraRulePagesUnderCovered": 0,
"extraRuleCoveragePairs": 102,
"non2xxResponses": 1,
"okResponses": 33,
"unexpectedStatus": 0
},
"chromium/dark": {
"pages": 34,
"themeMismatch": 0,
"bgMismatch": 0,
"contrastNodes": 0,
"violationNodes": 0,
"extraRuleNodes": 0,
"extraRulePagesUnderCovered": 0,
"extraRuleCoveragePairs": 102,
"non2xxResponses": 1,
"okResponses": 33,
"unexpectedStatus": 0
},
"firefox/light": {
"pages": 34,
"themeMismatch": 0,
"bgMismatch": 0,
"contrastNodes": 0,
"violationNodes": 0,
"extraRuleNodes": 0,
"extraRulePagesUnderCovered": 0,
"extraRuleCoveragePairs": 102,
"non2xxResponses": 1,
"okResponses": 33,
"unexpectedStatus": 0
},
"firefox/dark": {
"pages": 34,
"themeMismatch": 0,
"bgMismatch": 0,
"contrastNodes": 0,
"violationNodes": 0,
"extraRuleNodes": 0,
"extraRulePagesUnderCovered": 0,
"extraRuleCoveragePairs": 102,
"non2xxResponses": 1,
"okResponses": 33,
"unexpectedStatus": 0
}
}
PASSED = true
AXE_EXIT=0
SCRIPT_EXIT=0
@@ -0,0 +1,93 @@
> ruixin-website-react@1.0.0-phase1 build:clean
> rm -rf .next dist && next build
▲ Next.js 16.3.0 (Turbopack)
- Environments: .env.local, .env.production, .env
⚠ Warning: Next.js ignored package-lock.json in /Users/zhangxiang because it is outside the current Git repository (/Users/zhangxiang/Codes/Novalon/novalon-website).
To use this directory, set `turbopack.root` in your Next.js config.
✓ Running next.config.mjs took 308ms
- Experiments (use with caution):
· clientTraceMetadata
· optimizePackageImports
Creating an optimized production build ...
✓ Compiled successfully in 7.1s
Running next.config.js provided runAfterProductionCompile ...
[@sentry/nextjs - After Production Compile] Info: Sending telemetry data on issues and performance to Sentry. To disable telemetry, set `options.telemetry` to `false`.
[@sentry/nextjs - After Production Compile] Warning: No auth token provided. Will not create release. Please set the `authToken` option. You can find information on how to generate a Sentry auth token here: https://docs.sentry.io/api/auth/
[@sentry/nextjs - After Production Compile] Warning: No auth token provided. Will not upload source maps. Please set the `authToken` option. You can find information on how to generate a Sentry auth token here: https://docs.sentry.io/api/auth/
✓ Completed runAfterProductionCompile in 1012ms
Running TypeScript ...
Finished TypeScript in 6.4s ...
Collecting page data using 7 workers ...
Generating static pages using 7 workers (0/62) ...
Generating static pages using 7 workers (15/62)
Generating static pages using 7 workers (30/62)
Generating static pages using 7 workers (46/62)
✓ Generating static pages using 7 workers (62/62) in 249ms
Finalizing page optimization ...
Route (app) Revalidate Expire
┌ ○ / 1h 1y
├ ○ /_not-found
├ ○ /about 1h 1y
├ ○ /about/brand
├ ○ /admin
├ ƒ /admin/content/[modelCode]
├ ƒ /admin/content/[modelCode]/[itemId]
├ ○ /admin/login
├ ○ /admin/media
├ ○ /admin/notifications
├ ○ /admin/roles
├ ○ /admin/users
├ ○ /admin/zones
├ ƒ /api/admin/items
├ ƒ /api/admin/items/[id]/workflow
├ ƒ /api/admin/media
├ ƒ /api/admin/models
├ ƒ /api/admin/notifications
├ ƒ /api/admin/notifications/[id]/read
├ ƒ /api/admin/notifications/read-all
├ ƒ /api/admin/notifications/unread-count
├ ƒ /api/admin/roles
├ ƒ /api/admin/stats
├ ƒ /api/admin/users
├ ƒ /api/admin/zones
├ ƒ /api/auth/login
├ ƒ /api/auth/logout
├ ƒ /api/auth/me
├ ƒ /api/auth/refresh
├ ƒ /api/cms/draft/disable
├ ƒ /api/cms/draft/enable
├ ƒ /api/cms/revalidate
├ ƒ /api/contact
├ ○ /cases 1h 1y
├ ● /cases/[slug]
├ ○ /contact 1h 1y
├ ○ /methodology 1h 1y
├ ○ /news 1h 1y
├ ƒ /news/[slug]
├ ○ /privacy 1h 1y
├ ○ /products 1h 1y
├ ƒ /products/[id]
├ ○ /products/erp-upgrade 1h 1y
├ ○ /products/erp-upgrade-v3
├ ● /products/standalone/[id]
├ ○ /robots.txt
├ ○ /services 1h 1y
├ ƒ /services/[id]
├ ○ /sitemap.xml
├ ○ /solutions 1h 1y
├ ƒ /solutions/[id]
├ ○ /team 1h 1y
└ ○ /terms 1h 1y
ƒ Proxy (Middleware)
○ (Static) prerendered as static content
● (SSG) prerendered as static HTML (uses generateStaticParams)
ƒ (Dynamic) server-rendered on demand
@@ -0,0 +1,73 @@
> ruixin-website-react@1.0.0-phase1 check:motion
> tsx scripts/utils/check-motion-constraints.ts
🎬 动效契约检查(时长档位 + 缓动曲线)
契约:入场 180–280ms · 反馈 100ms · 上限 700ms · ease-ink [0.22, 1, 0.36, 1]
出处:CONTEXT.md:76 / :77 / :82(N-29:此前无任何脚本约束)
令牌层允许曲线:[0.000, 0.000, 0.200, 1.000] [0.220, 1.000, 0.360, 1.000] [0.400, 0.000, 0.200, 1.000] [0.400, 0.000, 1.000, 1.000] [0.650, 0.000, 0.350, 1.000]
❌ [easing-palette] src/app/(marketing)/news/[slug]/NewsDetailClient.tsx:14 const EASE = [0.25, 1, 0.5, 1]
曲线 [0.250, 1.000, 0.500, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/app/(marketing)/template.tsx:16 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/app/(marketing)/template.tsx:24 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [entrance-cap] src/app/globals.css:268 1000ms
--transition-gentle = 1000ms 超过 700ms 入场硬上限
❌ [css-transition-token] src/app/globals.css:1457 0.6s
transition 写了裸时长字面量,应改用 var(--transition-*)
❌ [easing-palette] src/components/sections/challenge-section.tsx:43 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/sections/cta-section.tsx:44 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/sections/hero-section-v2.tsx:13 const EASE = [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/sections/methodology-section.tsx:22 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/sections/product-matrix-section.tsx:20 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/sections/social-proof-section.tsx:43 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/sections/social-proof-section.tsx:59 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/sections/social-proof-section.tsx:70 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/sections/social-proof-section.tsx:98 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/sections/why-us-section.tsx:62 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/sections/why-us-section.tsx:86 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/sections/why-us-section.tsx:137 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/sections/why-us-section.tsx:154 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/ui/brand-visuals.tsx:66 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/ui/brand-visuals.tsx:95 ease: [0.16, 1, 0.3, 1]
曲线 [0.160, 1.000, 0.300, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/ui/page-transition.tsx:20 ease: [0.25, 1, 0.5, 1]
曲线 [0.250, 1.000, 0.500, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [easing-palette] src/components/ui/page-transition.tsx:76 ease: [0.25, 1, 0.5, 1]
曲线 [0.250, 1.000, 0.500, 1.000] 不在令牌层 --ease-* 允许集合内(默认应为 ease-ink [0.220, 1.000, 0.360, 1.000])
❌ [css-transition-token] src/lib/constants/design-system.ts:76 0.3s
内联 transition 串写了裸时长字面量,CSS 变量在 style 串里同样可用:var(--transition-*)
📊 检查摘要
扫描源码文件: 264(.ts/.tsx,已排除测试与 _archive)
扫描令牌/配置: CSS 1 · config 1
判定分母: CSS 声明 46 · 时长字面量 290 · 贝塞尔字面量 66 · --transition-* 令牌 6 · --ease-* 令牌 6
违规处数: 23
📋 分规则计数
token-band: 0 —— R1 令牌时长带:instant==100ms、fast/normal ∈ 180–280ms(CONTEXT.md:76)
entrance-cap: 1 —— R2 时长硬上限:任何动效时长不得超过 700ms(infinite 循环动画除外)(CONTEXT.md:82)
css-transition-token: 2 —— R3 令牌间接层:transition 声明的时长必须走 var(--transition-*)(CONTEXT.md:76(令牌层是时长的唯一事实来源))
easing-palette: 20 —— R4 缓动曲线:写死的 cubic-bezier 必须等于 --ease-* 令牌集,且 --ease-ink 必须是 [0.22,1,0.36,1](CONTEXT.md:77)
修复方向示例(easing-palette):改用 var(--ease-*) / ease-* 类,或把曲线值改回令牌层已声明的那条
❌ 存在动效契约违反!
@@ -0,0 +1,329 @@
=== BEFORE dev.db fingerprint (inode size mtime) ===
prisma/dev.db 398998151 1114112 1790137717
prisma/dev.db-wal 484282668 0 1790138992
prisma/dev.db-shm 484282669 32768 1790780040
(node:56718) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Running 92 tests using 4 workers
(node:56827) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:56825) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:56828) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:56826) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
✓ 1 [chromium] › ga4-event-tracking.spec.ts:121:7 › GA4 事件追踪验证 › TC-GA4-001: 页面浏览追踪 - 首屏由应用发出唯一一次 config @analytics @regression @critical (932ms)
✓ 4 [chromium] › ga4-event-tracking.spec.ts:234:7 › GA4 事件追踪验证 › TC-GA4-004: 页面浏览追踪 - 客户端路由跳转触发带 page_path 的 config @analytics @regression @critical (1.3s)
✓ 3 [chromium] › ga4-event-tracking.spec.ts:141:7 › GA4 事件追踪验证 › TC-GA4-002: 联系表单提交触发 form_submit 和 conversion 事件 @analytics @regression @critical (2.6s)
Desktop viewport detected, navigating directly to: /solutions
Desktop viewport detected, navigating directly to: /products
✓ 2 [chromium] › ga4-event-tracking.spec.ts:199:7 › GA4 事件追踪验证 › TC-GA4-003: 同意横幅「接受所有」点击触发 button_click 事件 @analytics @regression @critical (4.1s)
✓ 8 [chromium] › mobile-user-journeys.spec.ts:323:7 › UJ-05 Mobile: 案例浏览者筛选旅程(列表 → 筛选 → 详情) › @mobile @journey @regression 客户访问案例页,零案例种子下经共创空态转化到联系页 (2.4s)
✓ 7 [chromium] › mobile-user-journeys.spec.ts:272:7 › UJ-04 Mobile: 新闻读者浏览旅程(列表 → 详情 → 返回) › @mobile @journey @regression 读者从新闻列表浏览到详情页并返回 (4.5s)
✓ 10 [chromium] › nav-dropdown.spec.ts:8:5 › 主导航产品下拉菜单可在 hover 时展开 @smoke (579ms)
✓ 11 [chromium] › nav-dropdown.spec.ts:28:5 › 主导航解决方案下拉菜单可在 hover 时展开 @smoke (640ms)
✓ 12 [chromium] › p6-missing-paths.spec.ts:184:7 › 关键用户路径 - 首页 → 产品 → 详情 › 从首页导航到产品列表页 @smoke @regression (2.9s)
✓ 6 [chromium] › mobile-user-journeys.spec.ts:193:7 › UJ-02 Mobile: 行业客户浏览解决方案到产品的旅程 › @mobile @journey @regression 客户从解决方案浏览到产品详情 (10.6s)
✓ 13 [chromium] › p6-missing-paths.spec.ts:209:7 › 关键用户路径 - 首页 → 产品 → 详情 › 从产品列表页进入产品详情页 @smoke @regression (2.4s)
UJ-08: 访问首页
UJ-01 Mobile route hit: true
✓ 5 [chromium] › mobile-user-journeys.spec.ts:81:7 › UJ-01 Mobile: 潜在客户从首页到联系表单的完整旅程 › @mobile @journey @regression 访客从首页浏览产品并提交联系表单 (12.9s)
UJ-09: 开始产品深度浏览旅程
✓ 9 [chromium] › mobile-user-journeys.spec.ts:360:7 › UJ-10 Mobile: 深度搜索者旅程(分类浏览 → 逐篇阅读 → 内容发现) › @mobile @journey @regression 用户通过分类筛选浏览多篇文章并发现相关内容 (7.7s)
✓ 14 [chromium] › p6-missing-paths.spec.ts:230:7 › 关键用户路径 - 首页 → 产品 → 详情 › 从产品详情页可跳转回产品列表 @smoke @regression (2.5s)
UJ-09: 产品列表页标题: 自研产品矩阵支撑企业数字化核心系统
UJ-09: 产品卡片数量: 12
UJ-09: 点击第一个产品链接: /products/erp
UJ-08: 首页 Hero 区域可见
UJ-08: 从导航进入服务列表页
✓ 17 [chromium] › uj-11-home-conversion.spec.ts:40:7 › UJ-11a: 首屏说服链路(Hero → 信任 → 叙事 → CTA) › @journey @critical 首页首屏产品视觉、单一 CTA、数据条渲染正常 (2.7s)
✓ 18 [chromium] › uj-11-home-conversion.spec.ts:66:7 › UJ-11a: 首屏说服链路(Hero → 信任 → 叙事 → CTA) › @journey @critical 首页信任层展示可验证信号与来源标注 (2.7s)
UJ-09: 第一个产品详情页 URL: http://localhost:3000/products/erp
UJ-09: 第一个产品标题: 睿新ERP管理系统
UJ-09 L2: 找到价值区域关键词: 核心功能
UJ-09 L3: 找到信任区域关键词: 客户案例
UJ-09 L4: CTA 链接可见
UJ-08: 已导航到服务列表页
UJ-08: 服务列表页页面标题: 服务 - 睿新致远 | 四川睿新致远科技有限公司
UJ-08: 找到服务链接数量: 8
UJ-08: 点击第一个服务链接
UJ-08: 服务链接地址: /services/consulting
✓ 19 [chromium] › uj-11-home-conversion.spec.ts:86:7 › UJ-11a: 首屏说服链路(Hero → 信任 → 叙事 → CTA) › @journey @critical 首页叙事区按 01/02/03 章节呈现问题→方法→结果 (2.7s)
UJ-09: 通过 goto 返回产品列表
UJ-09: 已返回产品列表页
UJ-09: 第二轮产品卡片数量: 12
UJ-09: 点击第二个产品链接: /products/crm
✓ 20 [chromium] › uj-11-home-conversion.spec.ts:112:7 › UJ-11b: 信任验证旅程(共创标签 → 转化) › @journey @critical 首页首批客户共创标签引导至联系转化 (2.8s)
UJ-08: 已导航到服务详情页
UJ-08: 服务详情页标题: 战略咨询明确数字化转型方向,避免盲目投入
UJ-08: 服务详情页 main 内容长度: 1134
UJ-08: 找到核心价值区域: 解决什么问题
UJ-08: 找到信任证明区域: 客户案例
UJ-08: CTA 链接可见
UJ-08: 导航到联系页面
UJ-09: 第二个产品详情页 URL: http://localhost:3000/products/crm
UJ-09: 第二个产品标题: 睿新客户关系管理系统
UJ-09: 第二个产品详情页 CTA 链接可见
UJ-09: 产品深度浏览旅程完成
✓ 16 [chromium] › uj-09-product-browsing.spec.ts:31:7 › UJ-09: 产品深度浏览旅程 › @journey @regression 用户从产品列表浏览多个产品详情并验证四层叙事结构 (8.0s)
✓ 21 [chromium] › uj-11-home-conversion.spec.ts:131:7 › UJ-11b: 信任验证旅程(共创标签 → 转化) › @journey @critical 空案例区呈现共创内容块而非裸空态 (2.7s)
(node:58399) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
✓ 22 [chromium] › uj-11-home-conversion.spec.ts:153:7 › UJ-11c: 移动端首屏转化旅程 › @mobile @journey @critical 移动端 CTA 首屏可见且无横向滚动 (2.7s)
UJ-08: 联系页面标题: 随时欢迎聊一聊
UJ-08: 表单字段可见
UJ-08: 表单字段已正确填写
(node:58451) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
UJ-08: 提交按钮可见且可点击: 发送消息
UJ-08: 服务探索者旅程测试完成
✓ 15 [chromium] › uj-08-service-journey.spec.ts:42:7 › UJ-08: 服务探索者旅程(服务列表 → 服务详情 → 联系表单) › @journey @regression 访客从服务列表浏览到详情页并填写联系表单 (10.4s)
(node:58500) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
✓ 23 [chromium] › uj-11-home-conversion.spec.ts:172:7 › UJ-11c: 移动端首屏转化旅程 › @mobile @journey @critical 移动端信任层与叙事区单列堆叠无溢出 (2.8s)
(node:58517) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
✓ 24 [chromium-mobile] › ga4-event-tracking.spec.ts:121:7 › GA4 事件追踪验证 › TC-GA4-001: 页面浏览追踪 - 首屏由应用发出唯一一次 config @analytics @regression @critical (2.6s)
✓ 27 [chromium-mobile] › ga4-event-tracking.spec.ts:234:7 › GA4 事件追踪验证 › TC-GA4-004: 页面浏览追踪 - 客户端路由跳转触发带 page_path 的 config @analytics @regression @critical (2.8s)
✓ 25 [chromium-mobile] › ga4-event-tracking.spec.ts:141:7 › GA4 事件追踪验证 › TC-GA4-002: 联系表单提交触发 form_submit 和 conversion 事件 @analytics @regression @critical (2.8s)
✓ 26 [chromium-mobile] › ga4-event-tracking.spec.ts:199:7 › GA4 事件追踪验证 › TC-GA4-003: 同意横幅「接受所有」点击触发 button_click 事件 @analytics @regression @critical (6.1s)
✓ 30 [chromium-mobile] › mobile-user-journeys.spec.ts:272:7 › UJ-04 Mobile: 新闻读者浏览旅程(列表 → 详情 → 返回) › @mobile @journey @regression 读者从新闻列表浏览到详情页并返回 (5.0s)
✓ 31 [chromium-mobile] › mobile-user-journeys.spec.ts:323:7 › UJ-05 Mobile: 案例浏览者筛选旅程(列表 → 筛选 → 详情) › @mobile @journey @regression 客户访问案例页,零案例种子下经共创空态转化到联系页 (3.0s)
✓ 33 [chromium-mobile] › nav-dropdown.spec.ts:8:5 › 主导航产品下拉菜单可在 hover 时展开 @smoke (1.3s)
✓ 34 [chromium-mobile] › nav-dropdown.spec.ts:28:5 › 主导航解决方案下拉菜单可在 hover 时展开 @smoke (1.3s)
✓ 29 [chromium-mobile] › mobile-user-journeys.spec.ts:193:7 › UJ-02 Mobile: 行业客户浏览解决方案到产品的旅程 › @mobile @journey @regression 客户从解决方案浏览到产品详情 (12.1s)
✓ 35 [chromium-mobile] › p6-missing-paths.spec.ts:184:7 › 关键用户路径 - 首页 → 产品 → 详情 › 从首页导航到产品列表页 @smoke @regression (3.7s)
UJ-01 Mobile route hit: true
✓ 28 [chromium-mobile] › mobile-user-journeys.spec.ts:81:7 › UJ-01 Mobile: 潜在客户从首页到联系表单的完整旅程 › @mobile @journey @regression 访客从首页浏览产品并提交联系表单 (13.3s)
UJ-08: 访问首页
✓ 32 [chromium-mobile] › mobile-user-journeys.spec.ts:360:7 › UJ-10 Mobile: 深度搜索者旅程(分类浏览 → 逐篇阅读 → 内容发现) › @mobile @journey @regression 用户通过分类筛选浏览多篇文章并发现相关内容 (9.2s)
UJ-09: 开始产品深度浏览旅程
✓ 36 [chromium-mobile] › p6-missing-paths.spec.ts:209:7 › 关键用户路径 - 首页 → 产品 → 详情 › 从产品列表页进入产品详情页 @smoke @regression (3.3s)
✓ 37 [chromium-mobile] › p6-missing-paths.spec.ts:230:7 › 关键用户路径 - 首页 → 产品 → 详情 › 从产品详情页可跳转回产品列表 @smoke @regression (3.1s)
UJ-08: 首页 Hero 区域可见
UJ-08: 从导航进入服务列表页
UJ-09: 产品列表页标题: 自研产品矩阵支撑企业数字化核心系统
UJ-09: 产品卡片数量: 12
UJ-09: 点击第一个产品链接: /products/erp
UJ-08: 已导航到服务列表页
UJ-08: 服务列表页页面标题: 服务 - 睿新致远 | 四川睿新致远科技有限公司
UJ-08: 找到服务链接数量: 8
UJ-08: 点击第一个服务链接
UJ-08: 服务链接地址: /services/consulting
✓ 40 [chromium-mobile] › uj-11-home-conversion.spec.ts:40:7 › UJ-11a: 首屏说服链路(Hero → 信任 → 叙事 → CTA) › @journey @critical 首页首屏产品视觉、单一 CTA、数据条渲染正常 (3.3s)
UJ-09: 第一个产品详情页 URL: http://localhost:3000/products/erp
UJ-09: 第一个产品标题: 睿新ERP管理系统
UJ-09 L2: 找到价值区域关键词: 核心功能
UJ-09 L3: 找到信任区域关键词: 客户案例
UJ-09 L4: CTA 链接可见
✓ 41 [chromium-mobile] › uj-11-home-conversion.spec.ts:66:7 › UJ-11a: 首屏说服链路(Hero → 信任 → 叙事 → CTA) › @journey @critical 首页信任层展示可验证信号与来源标注 (3.3s)
UJ-08: 已导航到服务详情页
UJ-08: 服务详情页标题: 战略咨询明确数字化转型方向,避免盲目投入
UJ-08: 服务详情页 main 内容长度: 1134
UJ-08: 找到核心价值区域: 解决什么问题
UJ-08: 找到信任证明区域: 客户案例
UJ-08: CTA 链接可见
UJ-08: 导航到联系页面
UJ-09: 通过 goto 返回产品列表
UJ-09: 已返回产品列表页
UJ-09: 第二轮产品卡片数量: 12
UJ-09: 点击第二个产品链接: /products/crm
✓ 42 [chromium-mobile] › uj-11-home-conversion.spec.ts:86:7 › UJ-11a: 首屏说服链路(Hero → 信任 → 叙事 → CTA) › @journey @critical 首页叙事区按 01/02/03 章节呈现问题→方法→结果 (3.4s)
✓ 43 [chromium-mobile] › uj-11-home-conversion.spec.ts:112:7 › UJ-11b: 信任验证旅程(共创标签 → 转化) › @journey @critical 首页首批客户共创标签引导至联系转化 (3.4s)
UJ-09: 第二个产品详情页 URL: http://localhost:3000/products/crm
UJ-09: 第二个产品标题: 睿新客户关系管理系统
UJ-09: 第二个产品详情页 CTA 链接可见
UJ-09: 产品深度浏览旅程完成
✓ 39 [chromium-mobile] › uj-09-product-browsing.spec.ts:31:7 › UJ-09: 产品深度浏览旅程 › @journey @regression 用户从产品列表浏览多个产品详情并验证四层叙事结构 (8.8s)
UJ-08: 联系页面标题: 随时欢迎聊一聊
UJ-08: 表单字段可见
UJ-08: 表单字段已正确填写
UJ-08: 提交按钮可见且可点击: 发送消息
UJ-08: 服务探索者旅程测试完成
✓ 38 [chromium-mobile] › uj-08-service-journey.spec.ts:42:7 › UJ-08: 服务探索者旅程(服务列表 → 服务详情 → 联系表单) › @journey @regression 访客从服务列表浏览到详情页并填写联系表单 (10.4s)
(node:59916) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
✓ 44 [chromium-mobile] › uj-11-home-conversion.spec.ts:131:7 › UJ-11b: 信任验证旅程(共创标签 → 转化) › @journey @critical 空案例区呈现共创内容块而非裸空态 (3.4s)
(node:59930) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
✓ 45 [chromium-mobile] › uj-11-home-conversion.spec.ts:153:7 › UJ-11c: 移动端首屏转化旅程 › @mobile @journey @critical 移动端 CTA 首屏可见且无横向滚动 (3.5s)
✓ 46 [chromium-mobile] › uj-11-home-conversion.spec.ts:172:7 › UJ-11c: 移动端首屏转化旅程 › @mobile @journey @critical 移动端信任层与叙事区单列堆叠无溢出 (3.6s)
(node:59950) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:59976) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
✓ 47 [firefox] › ga4-event-tracking.spec.ts:121:7 › GA4 事件追踪验证 › TC-GA4-001: 页面浏览追踪 - 首屏由应用发出唯一一次 config @analytics @regression @critical (2.1s)
✓ 48 [firefox] › ga4-event-tracking.spec.ts:141:7 › GA4 事件追踪验证 › TC-GA4-002: 联系表单提交触发 form_submit 和 conversion 事件 @analytics @regression @critical (3.1s)
✓ 50 [firefox] › ga4-event-tracking.spec.ts:234:7 › GA4 事件追踪验证 › TC-GA4-004: 页面浏览追踪 - 客户端路由跳转触发带 page_path 的 config @analytics @regression @critical (2.5s)
Desktop viewport detected, navigating directly to: /products
Desktop viewport detected, navigating directly to: /solutions
✓ 49 [firefox] › ga4-event-tracking.spec.ts:199:7 › GA4 事件追踪验证 › TC-GA4-003: 同意横幅「接受所有」点击触发 button_click 事件 @analytics @regression @critical (6.6s)
✓ 53 [firefox] › mobile-user-journeys.spec.ts:272:7 › UJ-04 Mobile: 新闻读者浏览旅程(列表 → 详情 → 返回) › @mobile @journey @regression 读者从新闻列表浏览到详情页并返回 (7.0s)
✓ 54 [firefox] › mobile-user-journeys.spec.ts:323:7 › UJ-05 Mobile: 案例浏览者筛选旅程(列表 → 筛选 → 详情) › @mobile @journey @regression 客户访问案例页,零案例种子下经共创空态转化到联系页 (5.3s)
✓ 56 [firefox] › nav-dropdown.spec.ts:8:5 › 主导航产品下拉菜单可在 hover 时展开 @smoke (2.3s)
✓ 57 [firefox] › nav-dropdown.spec.ts:28:5 › 主导航解决方案下拉菜单可在 hover 时展开 @smoke (1.4s)
UJ-01 Mobile route hit: true
✓ 51 [firefox] › mobile-user-journeys.spec.ts:81:7 › UJ-01 Mobile: 潜在客户从首页到联系表单的完整旅程 › @mobile @journey @regression 访客从首页浏览产品并提交联系表单 (16.8s)
✓ 52 [firefox] › mobile-user-journeys.spec.ts:193:7 › UJ-02 Mobile: 行业客户浏览解决方案到产品的旅程 › @mobile @journey @regression 客户从解决方案浏览到产品详情 (14.8s)
✓ 58 [firefox] › p6-missing-paths.spec.ts:184:7 › 关键用户路径 - 首页 → 产品 → 详情 › 从首页导航到产品列表页 @smoke @regression (3.4s)
UJ-08: 访问首页
✓ 59 [firefox] › p6-missing-paths.spec.ts:209:7 › 关键用户路径 - 首页 → 产品 → 详情 › 从产品列表页进入产品详情页 @smoke @regression (2.8s)
✓ 60 [firefox] › p6-missing-paths.spec.ts:230:7 › 关键用户路径 - 首页 → 产品 → 详情 › 从产品详情页可跳转回产品列表 @smoke @regression (2.5s)
UJ-09: 开始产品深度浏览旅程
✓ 55 [firefox] › mobile-user-journeys.spec.ts:360:7 › UJ-10 Mobile: 深度搜索者旅程(分类浏览 → 逐篇阅读 → 内容发现) › @mobile @journey @regression 用户通过分类筛选浏览多篇文章并发现相关内容 (10.0s)
UJ-09: 产品列表页标题: 自研产品矩阵支撑企业数字化核心系统
UJ-09: 产品卡片数量: 12
UJ-09: 点击第一个产品链接: /products/erp
UJ-08: 首页 Hero 区域可见
UJ-08: 从导航进入服务列表页
✓ 63 [firefox] › uj-11-home-conversion.spec.ts:40:7 › UJ-11a: 首屏说服链路(Hero → 信任 → 叙事 → CTA) › @journey @critical 首页首屏产品视觉、单一 CTA、数据条渲染正常 (3.6s)
✓ 64 [firefox] › uj-11-home-conversion.spec.ts:66:7 › UJ-11a: 首屏说服链路(Hero → 信任 → 叙事 → CTA) › @journey @critical 首页信任层展示可验证信号与来源标注 (3.5s)
UJ-09: 第一个产品详情页 URL: http://localhost:3000/products/erp
UJ-09: 第一个产品标题: 睿新ERP管理系统
UJ-09 L2: 找到价值区域关键词: 核心功能
UJ-09 L3: 找到信任区域关键词: 客户案例
UJ-09 L4: CTA 链接可见
UJ-08: 已导航到服务列表页
UJ-08: 服务列表页页面标题: 服务 - 睿新致远 | 四川睿新致远科技有限公司
UJ-08: 找到服务链接数量: 8
UJ-08: 点击第一个服务链接
UJ-08: 服务链接地址: /services/consulting
UJ-09: 通过 goto 返回产品列表
✓ 65 [firefox] › uj-11-home-conversion.spec.ts:86:7 › UJ-11a: 首屏说服链路(Hero → 信任 → 叙事 → CTA) › @journey @critical 首页叙事区按 01/02/03 章节呈现问题→方法→结果 (3.5s)
UJ-08: 已导航到服务详情页
UJ-08: 服务详情页标题: 战略咨询明确数字化转型方向,避免盲目投入
UJ-08: 服务详情页 main 内容长度: 1134
UJ-08: 找到核心价值区域: 解决什么问题
UJ-08: 找到信任证明区域: 客户案例
UJ-08: CTA 链接可见
UJ-08: 导航到联系页面
✓ 66 [firefox] › uj-11-home-conversion.spec.ts:112:7 › UJ-11b: 信任验证旅程(共创标签 → 转化) › @journey @critical 首页首批客户共创标签引导至联系转化 (3.5s)
UJ-08: 联系页面标题: 随时欢迎聊一聊
UJ-08: 表单字段可见
UJ-08: 表单字段已正确填写
UJ-08: 提交按钮可见且可点击: 发送消息
UJ-08: 服务探索者旅程测试完成
✓ 61 [firefox] › uj-08-service-journey.spec.ts:42:7 › UJ-08: 服务探索者旅程(服务列表 → 服务详情 → 联系表单) › @journey @regression 访客从服务列表浏览到详情页并填写联系表单 (10.7s)
✓ 67 [firefox] › uj-11-home-conversion.spec.ts:131:7 › UJ-11b: 信任验证旅程(共创标签 → 转化) › @journey @critical 空案例区呈现共创内容块而非裸空态 (3.6s)
(node:61992) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
✓ 68 [firefox] › uj-11-home-conversion.spec.ts:153:7 › UJ-11c: 移动端首屏转化旅程 › @mobile @journey @critical 移动端 CTA 首屏可见且无横向滚动 (3.5s)
(node:62045) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
✓ 70 [webkit] › ga4-event-tracking.spec.ts:121:7 › GA4 事件追踪验证 › TC-GA4-001: 页面浏览追踪 - 首屏由应用发出唯一一次 config @analytics @regression @critical (1.8s)
✓ 71 [webkit] › ga4-event-tracking.spec.ts:141:7 › GA4 事件追踪验证 › TC-GA4-002: 联系表单提交触发 form_submit 和 conversion 事件 @analytics @regression @critical (2.0s)
✓ 69 [firefox] › uj-11-home-conversion.spec.ts:172:7 › UJ-11c: 移动端首屏转化旅程 › @mobile @journey @critical 移动端信任层与叙事区单列堆叠无溢出 (4.2s)
(node:62176) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
✓ 73 [webkit] › ga4-event-tracking.spec.ts:234:7 › GA4 事件追踪验证 › TC-GA4-004: 页面浏览追踪 - 客户端路由跳转触发带 page_path 的 config @analytics @regression @critical (1.3s)
Desktop viewport detected, navigating directly to: /solutions
✓ 72 [webkit] › ga4-event-tracking.spec.ts:199:7 › GA4 事件追踪验证 › TC-GA4-003: 同意横幅「接受所有」点击触发 button_click 事件 @analytics @regression @critical (5.2s)
Desktop viewport detected, navigating directly to: /products
✘ 62 [firefox] › uj-09-product-browsing.spec.ts:31:7 › UJ-09: 产品深度浏览旅程 › @journey @regression 用户从产品列表浏览多个产品详情并验证四层叙事结构 (21.3s)
(node:62353) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
✓ 76 [webkit] › mobile-user-journeys.spec.ts:272:7 › UJ-04 Mobile: 新闻读者浏览旅程(列表 → 详情 → 返回) › @mobile @journey @regression 读者从新闻列表浏览到详情页并返回 (4.5s)
✓ 77 [webkit] › mobile-user-journeys.spec.ts:323:7 › UJ-05 Mobile: 案例浏览者筛选旅程(列表 → 筛选 → 详情) › @mobile @journey @regression 客户访问案例页,零案例种子下经共创空态转化到联系页 (2.9s)
✓ 79 [webkit] › nav-dropdown.spec.ts:8:5 › 主导航产品下拉菜单可在 hover 时展开 @smoke (865ms)
✓ 75 [webkit] › mobile-user-journeys.spec.ts:193:7 › UJ-02 Mobile: 行业客户浏览解决方案到产品的旅程 › @mobile @journey @regression 客户从解决方案浏览到产品详情 (10.9s)
✓ 80 [webkit] › nav-dropdown.spec.ts:28:5 › 主导航解决方案下拉菜单可在 hover 时展开 @smoke (891ms)
[WebServer] ⨯ Error: The destination stream closed early.
[WebServer]  at ignore-listed frames {
[WebServer]  digest: '595075872'
[WebServer] }
UJ-01 Mobile route hit: true
✓ 74 [webkit] › mobile-user-journeys.spec.ts:81:7 › UJ-01 Mobile: 潜在客户从首页到联系表单的完整旅程 › @mobile @journey @regression 访客从首页浏览产品并提交联系表单 (13.2s)
✓ 82 [webkit] › p6-missing-paths.spec.ts:209:7 › 关键用户路径 - 首页 → 产品 → 详情 › 从产品列表页进入产品详情页 @smoke @regression (2.7s)
✓ 81 [webkit] › p6-missing-paths.spec.ts:184:7 › 关键用户路径 - 首页 → 产品 → 详情 › 从首页导航到产品列表页 @smoke @regression (3.3s)
UJ-08: 访问首页
UJ-09: 开始产品深度浏览旅程
✓ 78 [webkit] › mobile-user-journeys.spec.ts:360:7 › UJ-10 Mobile: 深度搜索者旅程(分类浏览 → 逐篇阅读 → 内容发现) › @mobile @journey @regression 用户通过分类筛选浏览多篇文章并发现相关内容 (7.9s)
✓ 83 [webkit] › p6-missing-paths.spec.ts:230:7 › 关键用户路径 - 首页 → 产品 → 详情 › 从产品详情页可跳转回产品列表 @smoke @regression (2.9s)
UJ-09: 产品列表页标题: 自研产品矩阵支撑企业数字化核心系统
UJ-09: 产品卡片数量: 12
UJ-09: 点击第一个产品链接: /products/erp
UJ-08: 首页 Hero 区域可见
UJ-08: 从导航进入服务列表页
UJ-09: 第一个产品详情页 URL: http://localhost:3000/products/erp
UJ-09: 第一个产品标题: 睿新ERP管理系统
UJ-09 L2: 找到价值区域关键词: 核心功能
UJ-09 L3: 找到信任区域关键词: 客户案例
UJ-09 L4: CTA 链接可见
✓ 86 [webkit] › uj-11-home-conversion.spec.ts:40:7 › UJ-11a: 首屏说服链路(Hero → 信任 → 叙事 → CTA) › @journey @critical 首页首屏产品视觉、单一 CTA、数据条渲染正常 (3.7s)
UJ-08: 已导航到服务列表页
UJ-08: 服务列表页页面标题: 服务 - 睿新致远 | 四川睿新致远科技有限公司
UJ-08: 找到服务链接数量: 8
UJ-08: 点击第一个服务链接
UJ-08: 服务链接地址: /services/consulting
✓ 87 [webkit] › uj-11-home-conversion.spec.ts:66:7 › UJ-11a: 首屏说服链路(Hero → 信任 → 叙事 → CTA) › @journey @critical 首页信任层展示可验证信号与来源标注 (3.8s)
UJ-09: 通过 goto 返回产品列表
UJ-09: 已返回产品列表页
UJ-09: 第二轮产品卡片数量: 12
UJ-09: 点击第二个产品链接: /products/crm
UJ-08: 已导航到服务详情页
UJ-08: 服务详情页标题: 战略咨询明确数字化转型方向,避免盲目投入
UJ-08: 服务详情页 main 内容长度: 1134
UJ-08: 找到核心价值区域: 解决什么问题
UJ-08: 找到信任证明区域: 客户案例
UJ-08: CTA 链接可见
UJ-08: 导航到联系页面
UJ-09: 第二个产品详情页 URL: http://localhost:3000/products/crm
UJ-09: 第二个产品标题: 睿新客户关系管理系统
UJ-09: 第二个产品详情页 CTA 链接可见
UJ-09: 产品深度浏览旅程完成
✓ 85 [webkit] › uj-09-product-browsing.spec.ts:31:7 › UJ-09: 产品深度浏览旅程 › @journey @regression 用户从产品列表浏览多个产品详情并验证四层叙事结构 (8.3s)
✓ 88 [webkit] › uj-11-home-conversion.spec.ts:86:7 › UJ-11a: 首屏说服链路(Hero → 信任 → 叙事 → CTA) › @journey @critical 首页叙事区按 01/02/03 章节呈现问题→方法→结果 (3.7s)
✓ 89 [webkit] › uj-11-home-conversion.spec.ts:112:7 › UJ-11b: 信任验证旅程(共创标签 → 转化) › @journey @critical 首页首批客户共创标签引导至联系转化 (3.8s)
UJ-08: 联系页面标题: 随时欢迎聊一聊
UJ-08: 表单字段可见
UJ-08: 表单字段已正确填写
UJ-08: 提交按钮可见且可点击: 发送消息
UJ-08: 服务探索者旅程测试完成
✓ 84 [webkit] › uj-08-service-journey.spec.ts:42:7 › UJ-08: 服务探索者旅程(服务列表 → 服务详情 → 联系表单) › @journey @regression 访客从服务列表浏览到详情页并填写联系表单 (10.6s)
✓ 90 [webkit] › uj-11-home-conversion.spec.ts:131:7 › UJ-11b: 信任验证旅程(共创标签 → 转化) › @journey @critical 空案例区呈现共创内容块而非裸空态 (3.6s)
✓ 91 [webkit] › uj-11-home-conversion.spec.ts:153:7 › UJ-11c: 移动端首屏转化旅程 › @mobile @journey @critical 移动端 CTA 首屏可见且无横向滚动 (3.7s)
✓ 92 [webkit] › uj-11-home-conversion.spec.ts:172:7 › UJ-11c: 移动端首屏转化旅程 › @mobile @journey @critical 移动端信任层与叙事区单列堆叠无溢出 (3.7s)
1) [firefox] › uj-09-product-browsing.spec.ts:31:7 › UJ-09: 产品深度浏览旅程 › @journey @regression 用户从产品列表浏览多个产品详情并验证四层叙事结构
Error: expect(page).toHaveURL(expected) failed
Expected pattern: /\/products\/?$/
Received string: ""
Timeout: 15000ms
Call log:
 - Expect "toHaveURL" with timeout 15000ms
 - waiting for" http://localhost:3000/products" navigation to finish...
122 |
123 | // 验证已返回产品列表页
> 124 | await expect(page).toHaveURL(/\/products\/?$/);
| ^
125 | console.log('UJ-09: 已返回产品列表页');
126 |
127 | // === Step 8: 点击第二个产品链接进入详情页 ===
at /Users/zhangxiang/Codes/Novalon/novalon-website/e2e/uj-09-product-browsing.spec.ts:124:24
attachment #1: screenshot (image/png) ──────────────────────────────────────────────────────────
test-results/uj-09-product-browsing-UJ--31963-on-用户从产品列表浏览多个产品详情并验证四层叙事结构-firefox/test-failed-1.png
────────────────────────────────────────────────────────────────────────────────────────────────
Error Context: test-results/uj-09-product-browsing-UJ--31963-on-用户从产品列表浏览多个产品详情并验证四层叙事结构-firefox/error-context.md
1 failed
[firefox] › uj-09-product-browsing.spec.ts:31:7 › UJ-09: 产品深度浏览旅程 › @journey @regression 用户从产品列表浏览多个产品详情并验证四层叙事结构
91 passed (2.0m)
E2E_PROD_EXIT=1
=== AFTER dev.db fingerprint ===
prisma/dev.db 398998151 1114112 1790137717
prisma/dev.db-wal 484282668 0 1790138992
prisma/dev.db-shm 484282669 32768 1790780941
=== :3000 released? ===
3000 CLEAR
WRAPPER_EXIT=1
@@ -0,0 +1,98 @@
# 封版验收判定书 · 2026-09-30
- 封版对象:分支 `qa/seal-2026-09-28`,代码封版点 **`a0328a6`**(第五轮 QA 三笔提交),本判定书与其后的**纯文档封版提交 S** 一起构成 `seal/2026-09-30`。
- 判定:**封版通过(含例外清单)**。技术面无未闭环缺陷;例外均为「需业务口径」或「需单独授权的测试装配追认」,不是代码质量问题。
- 与台账 §0 旧判定的关系:旧判定「未达可判验收通过——唯一阻断 AUTH-D1(未入库)」**已失效**,AUTH-D1 于 2026-09-28 实质完成(三笔提交已推 `origin/qa/seal-2026-09-28`),本轮补齐从未在 sealed 树上跑过的门禁并据此改判。
## 1. 本轮补证结果(sealed tree `a0328a6`,2026-09-30 实测)
| # | 门禁 | 命令 | 退出码 | 实测数字 |
|---|---|---|---|---|
| 1 | 干净重建 + 装配 | `npm run build:clean && npm run postbuild` | 0 / 0 | `dist` **377M**(清理前 2.5G,其中 `dist/dev` 2.1G 是 `next dev` 与 build 共用 `distDir` 留下的开发缓存);`dist/standalone/{server.js,dist/static,public}` 齐备 |
| 2 | 全站 axe 节点计数 | `BASE=http://127.0.0.1:3100 SITEMAP=… OUT=docs/acceptance/2026-09-30-seal/axe npm run check:axe` | **0** | `PASSED=true`;34 路由 × (chromium,firefox) × (light,dark) = 136 页;`violationNodes=0`、`contrastNodes=0`、`bgMismatch=0`、`themeMismatch=0`;规则覆盖对 102/组合、总 408=408。**唯一 non-2xx = `/_not-found`(Next 内部路由,404 属设计,`unexpectedStatus=0`)** |
| 3 | 安全头(打本地产物) | `npx tsx scripts/utils/check-security-headers.ts --url http://localhost:3100/` | **0** | 8 项:7 PASS / 1 WARN / **0 FAIL**;WARN 是 HSTS(由 nginx/CDN 边缘注入,http 目标本就不下发)。**每个头各出现 1 次** ⇒ 线上重复下发确系 nginx 与 `next.config.mjs` 两层叠加,与产物无关 |
| 4 | 生产目标 E2E(排除写库 spec) | `E2E_TARGET=production playwright --grep '@smoke\|@critical\|@journey' --grep-invert 'cms-workflow\.spec\.ts\|user-journey\.spec\.ts'` × 4 project | **1** | **91 passed / 1 failed**(2.0m)。失败项与定性见 §2.1。`prisma/dev.db` 跑前跑后 inode/size/mtime 完全一致(`398998151 / 1114112 / 1790137717`)⇒ 该子集确实未写库 |
| 5 | 视觉只读比对 | `playwright test visual-regression.spec.ts --update-snapshots=none` | **1** | **94 passed / 31 failed**(5.1m)= 20 缺基线 + 11 像素差异;逐条定性见 §2.2。`git status e2e/visual-snapshots` 全程为空 ⇒ 未写任何基线 |
| 6 | 动效契约 | `npm run check:motion` | **1** | **23 处违规** = easing-palette 20 + css-transition-token 2 + entrance-cap 1。与周期 2 §3.5 计数的 23 **同数、未新增**;provenance 见 §2.3 |
| 7 | Lint | `npm run lint` | **0** | 0 error / **104 warning** ⇒ `AGENTS.md` §5 与台账 §7.4 记的「105」已过期(台账 `:152` 的 104 才是现值) |
| 8 | 类型检查 | `npm run type-check` | **0** | 全程序 tsc,0 error |
沿用 2026-09-28 §7.4 且本轮未重跑(代码未变,见 §3 不变式):`test:coverage` 143 套件 / 1772 例、`test:integration:real` 23 例、`check:a11y` 三件套、`lighthouse` 27 run。
## 2. 三处判红的逐条定性(不用 retry 或放宽阈值「修」)
### 2.1 `[firefox] uj-09-product-browsing.spec.ts:124` —— 并发墙钟族,非代码回归
- 症状:`await expect(page).toHaveURL(/\/products\/?$/)` 收到 `""`,15s 超时,等待的是「返回 /products」的导航完成。
- 取证:同一批次 chromium / chromium-mobile / webkit **三引擎全绿**;隔离单跑 firefox **1 passed(11.5s)**;该文件 4-project 并发复跑 **两次各 4 passed**。⇒ 只在 92 例满并发(多 worker 打同一台 standalone)时飘红。
- 归类:台账 §2.4 已知不稳定清单同族(N-28:同一代码三轮失败数 8→1→5)。**诚实披露:本轮 E2E 不是「92 例全绿」,是 91/1。**
### 2.2 视觉 31 红 = 20 缺基线 + 11 像素差异,全部可归因
- **20 缺基线**(4 subject × 5 project):`/products/erp-upgrade` 全页、`/about/brand` 全页、L2「卡片组件」(`product-card`)、L2「表单输入框」(`input-default`)。这 4 个 subject 在任何 project 下都从未有过参照 ⇒ 属 AUTH-D3 的追认范围。
- ⚠ 更正:台账 §2.3 `:91` 记「`erp-upgrade`/`about/brand`/`cases/[slug]` 三路由从无基线」不准——`/cases` 与 `/cases/[slug]` **根本不在 `VISUAL_TEST_PAGES`(`e2e/visual-regression.spec.ts:26-43`)里**,属覆盖缺口而非缺参照;真正缺参照的是上列 4 个 subject。
- ⚠ 自我更正:本轮中途我一度采信「只差 10 张基线」,实测是 **20 张**,台账原记的「20 例缺参照」是对的。
- **10 像素差异 = Q-5/S-2 网格修复的预期结果**:`/products/erp` 与 `/solutions/manufacturing` 各 5 project。差异签名是**页面变矮**(2548×18422→14388、1280×9211→7194、1668×16326→14426,ratio 0.22–0.24),而移动端几乎不变(1170 宽,+30/+21px,ratio 0.03)——正是「单子元素吞掉网格类导致塌成单列」被修好后、卡片恢复多列的必然版面收缩。
- 真实浏览器实证(`grid-structure-report.json`,1440 视口):`/products/erp` 的 5 个网格容器 `computedCols` = **3 / 2 / 4 / 4 / 12**,`directChildren` = 6 / 2 / 6 / 3 / 5;修复前这些容器的直接子元素恒为 1。
- 目视复核:`visual-check/products-erp-grid-1.png`(实施步骤 4 列 × 2 行、6 项,文字完整无重叠)、`visual-check/solutions-manufacturing-grid-2.png`(页脚 12 列四栏正常)。
- **1 像素差异 = 基线早于测试装配修正**:`[visual-chromium-mobile] button-default`,期望 186×96、实得 132×132。132×132 恰是 44×44 CSS 盒在 DPR 3 下的像素尺寸,而 `error-context.md` 的可访问性树里被拍元素是 `button "打开菜单"` ——即 `6bb7c55` 引入 N-15(c) `:visible` 选择器修正后**应当**拍到的目标(见 `e2e/visual-regression.spec.ts:96-110` 的诊断注释)。旧基线拍的是按设计隐藏的桌面导航钮 ⇒ 新图是对的,基线是旧的。
### 2.3 `check:motion` 23 处:既存债,但落在本轮改过的文件里
- 计数与周期 2 一致(20 曲线 + 2 裸时长 + 1 上限),本轮**未新增**。
- 但 4 个违规文件(`why-us-section.tsx`、`brand-visuals.tsx`、`page-transition.tsx`、`design-system.ts`)确在 `origin/dev..a0328a6` 的改动清单内:改动内容是品牌令牌收敛(`text-[var(--color-brand)]`→`text-brand-ink`)与时长归带,**非令牌缓动曲线被原样搬动**。⇒ 表述应为「计数零新增,但违规行出现在本轮 diff 中」,不宜简化成「本轮无涉动效」。
- 属 DEC-P2-motion 待裁定项(改代码 or 承认设计例外),封版轮不动。
## 3. 封版不变式(为何无需重跑全套门禁)
纯文档封版提交 S 只允许动文档;代码封版点仍是 `a0328a6`。机械核验:
```bash
git diff --name-only a0328a6..HEAD # 结果必须全部落在 docs/** 与 *.md 内
```
该命令的输出与结论记录在本文件末尾「§6 封版提交」。凡 §1 表中在 `a0328a6` 上出的数,对 S 恒等成立(S 无 `src/`、无 `e2e/` 变更)。
## 4. 例外登记(明写「未做」,不得被读成「已通过」)
| ID | 事项 | 现状与后果 |
|---|---|---|
| AUTH-D3 | 视觉基线追认 | 20 张缺参照 + 11 张已过时参照未更新。`npm run test:visual:all` 在封版树上必判红 31 例;**上线不受影响**(像素变化随 src 一起生效,基线只是测试真相未追认) |
| AUTH-D4 | 写库 E2E 11 例(`cms-workflow` + `user-journey`) | 从未执行 ⇒ 后台 draft→review→publish 全链路与多角色旅程无 E2E 凭据(仅有单测层) |
| AUTH-D2 | `db:seed` | 本轮发布计划内含**生产**重 seed;本地 `dev.db` 权限行仍旧 ⇒ 本地后台的非 super_admin 行为与生产不一致 |
| AUTH-D9 | Sentry 实投递 | 接线在码(`src/instrumentation*.ts` + `withSentryConfig`),但无真实 DSN 的事件与 source map 上传未验证 |
| AUTH-D10 | 全量变异测试 | 未跑;97.06 那个分数只覆盖 `utils.ts`,**不得当全站分数引用** |
| DEC-N30 | 四条互斥 SLA 同时在线(工作日 2h / <4h / 48h / <2h·7×24) | **业务已裁定:按例外照常上线,文案不动**。访客可见的自相矛盾承诺仍在站内 |
| DEC-D5 | `/products/erp-upgrade` 的 `99.2%`/`100%`/「从5天到1天」无 basis 无角注 | 同上,按例外上线;且该路由本身无视觉基线(见 AUTH-D3) |
| DEC-P2-motion | 动效契约 23 处判红 | 未改代码,门禁 `check:motion` 不在 `test:all` 内 ⇒ 不会拦停,但它是红的 |
| 覆盖缺口 | `/cases`、`/cases/[slug]` 不在视觉 spec 内;`check:axe` 矩阵无 webkit;`@regression`/`@mobile`/`@accessibility`/`@performance` 不在任何自动门禁内 | 登记为长期缺口,本轮不扩面 |
| 并发族 | firefox UJ-09/UJ-10、`website-acceptance:111`、4 例 webkit `@accessibility` | 墙钟/并发敏感,禁止用 retry 或放宽阈值掩盖 |
## 5. 发布相关事实(供部署与回滚决策,非验收判定)
1. `npm run deploy` 投递的是**本工作树的 `dist/`**,与 git 分支无关 ⇒ 合并 `main` 是追溯性动作,产物真伪取决于本地树是否等于封版提交。
2. 必带 `--clean`:`cmd_build` 在 `CLEAN_BUILD=1` 时走 `build:clean`(`rm -rf .next dist`),否则会把 `dist/dev` 的 2.1G 开发缓存一起 rsync。清理后 payload **377M**。
3. `deploy:rollback` **不是完整恢复路径**(`scripts/deploy.sh:330-385`):只恢复 `dist` + reload nginx,不重建容器、不恢复 `public/`,镜像恒为 `:latest` 被覆写。真正的恢复锚点是合并后打的 `prod/*` tag + 重新部署。
4. `scripts/deploy.sh status` 不报磁盘 ⇒ 预演须单独取远程 `df -h`(历史记录 88% 占用 / 2.4G 可用,而备份保留 3 份)。
5. 线上安全头重复下发(`X-Frame-Options: DENY` 后跟 `SAMEORIGIN`、`nosniff`×2、CSP×2…)是 nginx 与 `next.config.mjs` 两层叠加;仓库内 `nginx-static-production.conf` 已修但 `deploy.sh` 从不投递 nginx 配置,须单独 scp + `nginx -t` + reload。
6. 无待执行 Prisma migration(最新 `20260717044101`,`schema.prisma` 迁移后仅加过 `binaryTargets`);但 `prisma/seed.ts` 与 `prisma/seeds/*` 在本分支改过(`team→team-page`、`legal→legal-page`、`+contact-page`、`+shellReadModels`),`src/lib/permissions.ts:26` 按 `modelCode` 精确匹配 ⇒ 不重 seed 则生产非 super_admin 角色持失效授予且缺 `content-model`/`content-zone` 读权。
7. `.pr-seal-2026-09-28.md:26` 那句「无需重跑 `db:seed`」是**假事实**,与第 6 条冲突,本轮已按实况更正。
8. `rsync -az --delete public/`(`deploy.sh:286`)会删远端 `public/` 下本地没有的条目;生产上传件走 `./uploads:/app/public/uploads` 卷挂载(`docker-compose.server.yml:20-23`)⇒ 部署前必须核实二者不重叠,否则会清掉 CMS 上传资产。
## 6. 封版提交
- 代码封版点:`a0328a6`(`fix(qa)` `a366bd1` + `test(qa)` `6bb7c55` + `chore(qa)` `a0328a6`)。
- 纯文档封版提交 S 的 sha = `git rev-parse seal/2026-09-30^{commit}`(tag 即指向 S);不变式核验在**提交前**执行,命令与结果:
```bash
git diff --name-only a0328a6 # 已跟踪的改动
git status --porcelain # 含未跟踪
# 结果:M README.md / M docs/acceptance/qa-tracker.md / M docs/development/quality-gates.md
# / M docs/lessons-learned.md / ?? docs/acceptance/2026-09-30-seal/
# ⇒ 全部落在 docs/** 与 *.md 内,无 src/、无 e2e/、无 config/、无 package.json
```
- 封版 tag:`seal/2026-09-30`。
## 7. 本轮的方法论收获(已同步到 `docs/lessons-learned.md` §5.32)
1. **「机制不存在」是高危断言**:台账 DEC-N21b 用「无 `middleware.ts`」推出「`/admin` 无服务端 gating」,而 Next 16 早已把该约定改名为 `src/proxy.ts`,且**本仓 `CLAUDE.md:108` 明确写着这件事**,`npm run build` 的路由表也会打印 `ƒ Proxy (Middleware)`。按记忆中的文件名搜索、而不是按能力搜索,会造出与自家文档直接冲突的假缺陷。
2. **文档里的文件计数必须现取**:「85 张基线 modified 未提交 / 视觉通过依赖未提交状态」在 `git ls-files` 前不成立(107 张全在库、树干净)。
3. **本轮我自己也犯过一次**:中途采信「视觉只差 10 张基线」的乐观估计,实测是 20 张缺参照 + 11 张过时 ⇒ 台账原记「20 例缺参照」是对的。子代理的「已修正」结论同样要复测。
4. **后台任务的 exit 0 不是门禁的 exit 0**:本轮两次「通知说 0、日志里是 1」(E2E 与视觉),根因都是我把命令包在 `...; echo EXIT=$?` 的包装里 ⇒ 包装自身成功即返回 0。判绿必须读日志内的 `*_EXIT` 行。
5. **判红要先分层再定性**:视觉 31 红拆成「缺参照 / 版面按预期变化 / 基线早于装配修正」三类,各自处置不同(追认、目视复核、认定新图正确);混成一句「UI 坏了」会既误报又漏掉真正该看的 mobile button。
@@ -0,0 +1,84 @@
[
{
"page": "products-erp",
"gridCount": 5,
"grids": [
{
"cls": "grid md:grid-cols-2 lg:grid-cols-3 gap-px",
"directChildren": 6,
"w": 1270,
"h": 295,
"computedCols": 3
},
{
"cls": "grid lg:grid-cols-2 gap-20",
"directChildren": 2,
"w": 1270,
"h": 507,
"computedCols": 2
},
{
"cls": "grid md:grid-cols-2 lg:grid-cols-4 gap-px",
"directChildren": 6,
"w": 1270,
"h": 547,
"computedCols": 4
},
{
"cls": "grid md:grid-cols-2 lg:grid-cols-4 gap-px",
"directChildren": 3,
"w": 1270,
"h": 465,
"computedCols": 4
},
{
"cls": "grid grid-cols-2 md:grid-cols-4 lg:grid-cols-12 gap-10 lg:gap-12",
"directChildren": 5,
"w": 1270,
"h": 796,
"computedCols": 12
}
]
},
{
"page": "solutions-manufacturing",
"gridCount": 5,
"grids": [
{
"cls": "grid lg:grid-cols-2 gap-20",
"directChildren": 2,
"w": 1270,
"h": 563,
"computedCols": 2
},
{
"cls": "grid md:grid-cols-2 gap-px",
"directChildren": 4,
"w": 1270,
"h": 419,
"computedCols": 2
},
{
"cls": "grid md:grid-cols-3 gap-px",
"directChildren": 3,
"w": 1270,
"h": 298,
"computedCols": 3
},
{
"cls": "grid sm:grid-cols-2 lg:grid-cols-4 gap-4 sm:gap-6",
"directChildren": 4,
"w": 1270,
"h": 343,
"computedCols": 4
},
{
"cls": "grid grid-cols-2 md:grid-cols-4 lg:grid-cols-12 gap-10 lg:gap-12",
"directChildren": 5,
"w": 1270,
"h": 796,
"computedCols": 12
}
]
}
]
+347
View File
@@ -0,0 +1,347 @@
> ruixin-website-react@1.0.0-phase1 lint
> eslint
/Users/zhangxiang/Codes/Novalon/novalon-website/docs/acceptance/2026-09-21-gates/probe/probe-browser-name.spec.ts
8:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
/Users/zhangxiang/Codes/Novalon/novalon-website/prisma/seed.ts
182:5 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
187:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
190:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
203:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
206:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
321:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
356:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
358:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
361:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
616:5 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
620:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
640:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
642:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
648:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
650:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
668:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
670:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
672:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
674:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
722:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
724:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
726:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
728:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
730:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
732:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
734:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
737:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
768:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
771:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
807:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
809:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
852:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
854:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
890:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
892:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
913:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
915:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
938:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
940:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
949:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
951:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
999:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
1001:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
1062:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
1065:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
1067:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
1074:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
1075:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
1076:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
1077:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
1078:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
/Users/zhangxiang/Codes/Novalon/novalon-website/sentry.server.config.ts
40:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/(marketing)/home-content-v15.tsx
120:36 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
156:29 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
272:60 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
509:78 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
510:61 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
512:40 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
515:29 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
552:32 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
555:38 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
555:59 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
562:74 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
562:90 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
636:69 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
714:77 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
789:85 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
828:120 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
930:73 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
954:29 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
955:26 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
956:26 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
957:29 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/(marketing)/methodology/methodology-content.tsx
20:24 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/(marketing)/news/[slug]/NewsDetailClient.tsx
79:17 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
113:29 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/(marketing)/news/news-content-v3.tsx
37:13 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/(marketing)/news/news-detail-content-v3.tsx
29:13 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
105:17 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/admin/content/[modelCode]/[itemId]/page.tsx
652:15 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/admin/content/[modelCode]/page.tsx
106:15 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/admin/content/[modelCode]/page.tsx:106:15
104 | return;
105 | }
> 106 | if (user) fetchItems();
| ^^^^^^^^^^ Avoid calling setState() directly within an effect
107 | }, [user, authLoading, router, fetchItems]);
108 |
109 | const openDeleteDialog = (id: string) => { react-hooks/set-state-in-effect
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/admin/media/page.tsx
59:15 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/admin/media/page.tsx:59:15
57 | return;
58 | }
> 59 | if (user) fetchMedia();
| ^^^^^^^^^^ Avoid calling setState() directly within an effect
60 | }, [user, authLoading, router]);
61 |
62 | const handleUpload = async (e: React.ChangeEvent<HTMLInputElement>) => { react-hooks/set-state-in-effect
159:17 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/admin/notifications/page.tsx
112:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/admin/notifications/page.tsx:112:7
110 | }
111 | if (user) {
> 112 | fetchNotifications();
| ^^^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
113 | fetchUnreadCount();
114 | }
115 | }, [user, authLoading, router, fetchNotifications, fetchUnreadCount]); react-hooks/set-state-in-effect
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/admin/roles/page.tsx
77:15 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/admin/roles/page.tsx:77:15
75 | return;
76 | }
> 77 | if (user) fetchRoles();
| ^^^^^^^^^^ Avoid calling setState() directly within an effect
78 | }, [user, authLoading, router, fetchRoles]);
79 |
80 | const selectedRoleInfo = roles.find((r) => r.code === selectedRole); react-hooks/set-state-in-effect
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/admin/users/page.tsx
138:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/admin/users/page.tsx:138:7
136 | }
137 | if (user) {
> 138 | fetchUsers();
| ^^^^^^^^^^ Avoid calling setState() directly within an effect
139 | fetchRoles();
140 | }
141 | }, [user, authLoading, router, fetchUsers, fetchRoles]); react-hooks/set-state-in-effect
/Users/zhangxiang/Codes/Novalon/novalon-website/src/app/global-error.tsx
57:13 warning Do not use an `<a>` element to navigate to `/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages @next/next/no-html-link-for-pages
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/admin/auth-context.tsx
45:9 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/admin/auth-context.tsx:45:9
43 | if (savedToken && savedUser) {
44 | try {
> 45 | setToken(savedToken);
| ^^^^^^^^ Avoid calling setState() directly within an effect
46 | setUser(JSON.parse(savedUser));
47 | } catch {
48 | localStorage.removeItem('novalon_admin_token'); react-hooks/set-state-in-effect
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/analytics/GlobalErrorTracker.tsx
74:7 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/analytics/GoogleAnalytics.test.tsx
34:12 warning Synchronous scripts should not be used. See: https://nextjs.org/docs/messages/no-sync-scripts @next/next/no-sync-scripts
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/detail/detail-product-value.tsx
79:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/detail/detail-product-value.tsx:79:7
77 | if (!isInView) return;
78 | if (isNaN(numericValue)) {
> 79 | setDisplayValue(value);
| ^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
80 | return;
81 | }
82 | let frame = 0; react-hooks/set-state-in-effect
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/detail/detail-trust-section.tsx
30:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/detail/detail-trust-section.tsx:30:7
28 | const numericValue = parseFloat(value.replace(/[^0-9.]/g, ''));
29 | if (isNaN(numericValue)) {
> 30 | setDisplayValue(value);
| ^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
31 | return;
32 | }
33 | react-hooks/set-state-in-effect
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/detail/product-card.test.tsx
42:5 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/layout/footer.test.tsx
23:5 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/layout/header.test.tsx
30:5 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/ui/loading-state.tsx
44:9 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/ui/loading-state.tsx:44:9
42 |
43 | if (!isLoading) {
> 44 | setShowSkeleton(false);
| ^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
45 | return;
46 | }
47 | react-hooks/set-state-in-effect
158:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/ui/loading-state.tsx:158:7
156 | useEffect(() => {
157 | if (!isLoading) {
> 158 | setShouldShow(false);
| ^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
159 | return;
160 | }
161 | react-hooks/set-state-in-effect
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/ui/page-transition.tsx
41:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/zhangxiang/Codes/Novalon/novalon-website/src/components/ui/page-transition.tsx:41:5
39 |
40 | useEffect(() => {
> 41 | setMounted(true);
| ^^^^^^^^^^ Avoid calling setState() directly within an effect
42 | }, []);
43 |
44 | // SSR 和首次 hydration 阶段直接渲染子内容,避免 framer-motion DOM 差异导致 hydration mismatch react-hooks/set-state-in-effect
/Users/zhangxiang/Codes/Novalon/novalon-website/src/hooks/use-count-up.ts
30:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders
Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
/Users/zhangxiang/Codes/Novalon/novalon-website/src/hooks/use-count-up.ts:30:7
28 | useEffect(() => {
29 | if (!enabled) {
> 30 | setValue(end);
| ^^^^^^^^ Avoid calling setState() directly within an effect
31 | return;
32 | }
33 | react-hooks/set-state-in-effect
/Users/zhangxiang/Codes/Novalon/novalon-website/src/hooks/use-reduced-motion.ts
34:61 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
35:63 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
49:19 warning Unexpected any. Specify a different type @typescript-eslint/no-explicit-any
/Users/zhangxiang/Codes/Novalon/novalon-website/src/instrumentation-client.ts
88:3 warning Unexpected console statement. Only these console methods are allowed: warn, error no-console
✖ 104 problems (0 errors, 104 warnings)
@@ -0,0 +1,32 @@
🔒 安全响应头检查 — http://localhost:3100/
安全头检查结果:
┌────────────────────────────────────┬────────┬────────────────────────────────────────┬────────────────────────────────────────┐
│ Header │ Status │ Expected │ Actual │
├────────────────────────────────────┼────────┼────────────────────────────────────────┼────────────────────────────────────────┤
│ Content-Security-Policy │ ✅ PASS │ 存在(需包含合理策略) │ default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://ssl.google-analytics.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://www.google-analytics.com https://ssl.google-analytics.com https://www.googletagmanager.com; font-src 'self'; connect-src 'self' https://www.google-analytics.com https://ssl.google-analytics.com https://www.googletagmanager.com; frame-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; │
│ X-Content-Type-Options │ ✅ PASS │ nosniff │ nosniff │
│ X-Frame-Options │ ✅ PASS │ DENY 或 SAMEORIGIN │ DENY │
│ Strict-Transport-Security │ ⚠️ WARN │ 存在(需包含 max-age) │ (未设置) │
│ Referrer-Policy │ ✅ PASS │ 存在(如 strict-origin-when-cross-origin) │ strict-origin-when-cross-origin │
│ Permissions-Policy │ ✅ PASS │ 存在(需配置合理权限) │ camera=(), microphone=(), geolocation=(), interest-cohort=() │
│ X-XSS-Protection │ ✅ PASS │ 存在(0 或 1; mode=block) │ 1; mode=block │
│ Access-Control-Allow-Origin │ ✅ PASS │ 无(不暴露 CORS 头) │ (未设置) │
└────────────────────────────────────┴────────┴────────────────────────────────────────┴────────────────────────────────────────┘
🍪 Cookie 安全标记: 无 Cookie 设置
📝 说明:
• [⚠️] Strict-Transport-Security: 强制 HTTPS 连接,防止 SSL Strip 攻击
📊 检查摘要
安全头检查:
总计: 8
✅ 通过: 7
⚠️ 警告: 1
❌ 失败: 0
✅ 所有关键安全头检查通过!
@@ -0,0 +1,4 @@
> ruixin-website-react@1.0.0-phase1 type-check
> tsc --noEmit
Binary file not shown.

After

Width:  |  Height:  |  Size: 63 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 62 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 43 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 37 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 56 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 137 KiB

File diff suppressed because it is too large. Load diff
+36 -11
View File
@@ -1,7 +1,7 @@
# QA 问题跟踪台账(系统性质量保障 · 单一真源)
- 分支:`refactor/optimize-ui` HEAD:`f543e47`(**本台账所引用的全部修复仍只存在于工作树,未提交**)
- 工作树状态(2026-09-25 实测):`git status --porcelain` = **363 条**(47 条未跟踪)
- 分支:`qa/seal-2026-09-28` HEAD:`a0328a6`(**第三/四/五轮全部修复已于 2026-09-28 分三笔入库并推到 `origin/qa/seal-2026-09-28`;AUTH-D1 就此闭合**)
- 工作树状态(2026-09-30 实测):`git status --porcelain` = 仅 `.pr-seal-2026-09-28.md`、`deliverables/` 两条未跟踪 ⇒ **代码树干净**,本台账引用的修复全部在提交历史里
- 上游报告:
- 周期 1:`docs/acceptance/2026-09-23-gates/final-verdict.md`(发现 N-1…N-33;对 2026-09-21 阻断 A-*/R-*/B-* 的闭环)
- 周期 2:`docs/acceptance/2026-09-23-cycle2/final-verdict.md`(新增表现层/领域层轴:A-1…A-4、C-1、P-*、D-1(defect)、L-1…L-5、Sentry 接线;决策清单 D-1…D-11)
@@ -16,11 +16,13 @@
| 2 测试 | 门禁实测表(周期 1 §1 / 周期 2 §0)+ `docs/testing.md` | **已达成**(可自主执行的门禁全部出数;写库/基线/线上/全量变异等需授权项见 §3) |
| 3 修复 + 跟踪机制 | 本台账(单一真源) | **机制已建立**;修复的**可复现性未达成**(未入库) |
| 4 优化 | 性能(Lighthouse 9/9=100、a11y 节点计数、限流键、死资源清理)+ 安全(提权/XSS/越权/令牌/开放重定向) | **已达成**,余留项见 §2/§3 |
| 5 验收确认 | 本报告 + 门禁凭据 | **未达「可判验收通过」**——唯一阻断为交付形态(AUTH-D1 未入库),非代码质量 |
| 5 验收确认 | 本报告 + 门禁凭据 | **封版通过(含例外清单)**——AUTH-D1 已闭合,2026-09-30 补齐从未在 sealed 树上跑过的 4 项门禁;判定书见 `docs/acceptance/2026-09-30-seal/final-verdict.md`,例外见其 §4 |
> **结论不变**(承接周期 1「有条件通过」/周期 2「未达可判验收通过」):技术面已闭环并有实测凭据;验收不能判完成的**唯一实质原因**是 §3 AUTH-D1(约 363 条改动未提交,评审者/CI/下一位开发者无法复现本台账任何结论)。
> **【2026-09-30 改判 · 现行判定】封版通过(含例外清单)**。AUTH-D1 已于 2026-09-28 闭合(三笔提交入 `qa/seal-2026-09-28`,`a0328a6`);本轮补齐 sealed 树上从未跑过的全站 `check:axe`、生产目标 E2E、视觉只读比对、产物安全头、`check:motion` 五项,三处判红已逐条定性。判定书:`docs/acceptance/2026-09-30-seal/final-verdict.md`。**下面两条历史结论仅作过程留痕,不再代表现状。**
>
> **2026-09-28 更新**:第三/四/五轮(§4/§5/§7)在此结论上继续累积修复(第五轮再修 S-21/S-22/Q-10②/S-3 两个 P2 + 12 个 P3,全带判别测试与门禁凭据),未提交的工作树现 **394 条**——AUTH-D1 仍是唯一硬阻断。
> ~~**结论不变**~~(历史,2026-09-30 作废;承接周期 1「有条件通过」/周期 2「未达可判验收通过」):技术面已闭环并有实测凭据;验收不能判完成的**唯一实质原因**是 §3 AUTH-D1(约 363 条改动未提交,评审者/CI/下一位开发者无法复现本台账任何结论)。
>
> ~~**2026-09-28 更新**~~(历史:该轮改动随后即入库):第三/四/五轮(§4/§5/§7)在此结论上继续累积修复(第五轮再修 S-21/S-22/Q-10②/S-3 两个 P2 + 12 个 P3,全带判别测试与门禁凭据),未提交的工作树现 **394 条**——AUTH-D1 仍是唯一硬阻断。
## 1. 本台账建立时的独立复核(trust-but-verify,2026-09-25)
@@ -73,7 +75,7 @@
|---|---|---|---|
| REG-C1 | P3(**已复核,非活跃缺陷**) | C-1 归一在 `cases/[slug]/client.tsx:22,30-35`(唯一 importer),位置**正确**:恰在未受信任的 CMS 强转 `item.data as unknown as CaseStudyData` 边界处 `?? ''`/`?? []` 一次归一,`case-detail-page.tsx` 消费已定型 props 可信任(无第二个真实调用方)。周期 2 报告把它记在组件文件属**归属笔误**,非漏洞;**不**在组件内加冗余守卫(违反"不为不可能发生的场景加校验") | 仅更正周期 2 §1.2 的 file:line 归属 |
| DEC-N21 | P2→潜伏 | `'content-item'` 幻影 modelCode:周期 2 §5.3 以源码推翻「越权」定性,实为 **fail-closed**;真风险是将来被补进种子即成跨模型读取闸口。建议「缺 modelCode ⇒ 400」 | `admin/items/route.ts:79` |
| DEC-N21b | P2 | `/admin` 无服务端 gating(仅客户端跳转),HTML 外壳无会话也下发;数据 API 已守卫 | 无 `middleware.ts` |
| DEC-N21b | ~~P2~~ **2026-09-30 撤销该定性(原为假事实)** | 原文称「`/admin` 无服务端 gating、HTML 外壳无会话也下发,入口=无 `middleware.ts`」——**不成立**:Next 16 已把该约定文件更名为 `src/proxy.ts`(在 HEAD 内、已跟踪,`2297f01` 迁入),`:77-105` 对 `matcher: ['/admin/:path*']` 做 Edge HS256 校验并在缺令牌/验签失败时重定向登录页 ⇒ 服务端 gating **存在**。**改登记两条真残留**:① 只验签名与 `exp`、**不查 `User.status`** ⇒ 停用令牌的持有者仍能拿到 `/admin` 外壳 HTML(数据面由 Q-4 的 `authenticateActiveRequest` fail-closed 兜住);② `src/proxy.ts` **零测试**(`git ls-files` 无任何 proxy 测试) | `src/proxy.ts:77-105` |
| DEC-N30 | P1 | 四条互斥 SLA(工作日 2h / <4h / 48h / <2h·7×24)留哪一条 | 周期 1 §8.2 / 周期 2 §5.2 |
| DEC-D5 | P1 | `/products/erp-upgrade` 在线数字(`99.2%`/`40%+`/`从5天到1天`)在**活组件** `erp-upgrade-content-v2.tsx:63,69,77`,无 basis 无 MetricsBasisNote,且该路由无视觉基线 | 周期 2 §5.1 |
| DEC-D7 | P2 | news 正文字段声明 `richtext` 而 `renderField` 无该分支(能力缺口) | 周期 2 §5.3 |
@@ -86,9 +88,9 @@
### 2.3 待授权动作(阻塞验收;须逐项明文批准)
| ID | 动作 | 命令 | 为何阻塞 |
|---|---|---|---|
| **AUTH-D1** | **入库 / PR(验收唯一硬阻断)** | 先 `git fetch origin dev` 取真值 → 裁定双向分叉(周期 1 记 30↔31,两端同标题异 hash)重复提交对 → 按 5 组分笔提交 → Gitea PR(过 `check-pr-checklist.sh`) | 约 363 条改动只在工作树 ⇒ 本台账/两份报告结论均不可复现。**⚠ 分叉非快进整理,须先 fetch 再判** |
| AUTH-D2 | 重跑 seed | `npm run db:seed` | 使 L-2(seed 权限过期)修复对数据生效;现网 `dev.db` 仍为旧权限行 |
| AUTH-D3 | 视觉基线写入 | `npx playwright test visual-regression.spec.ts --update-snapshots` | 20 例缺参照恒红 + `erp-upgrade`/`about/brand`/`cases/[slug]` 三路由从无基线;追认现状需人工核看 85 张差异 |
| **AUTH-D1** | ~~入库 / PR(验收唯一硬阻断)~~ **已闭合(2026-09-28)** | 三笔提交 `a366bd1`/`6bb7c55`/`a0328a6` 已入 `qa/seal-2026-09-28` 并推到 origin;工作树现仅 2 条未跟踪(PR 描述文件、`deliverables/`) | 原「363 条只在工作树 ⇒ 不可复现」的前提消失。**分叉真相已查明(2026-09-30 复核)**:内容层面 `git diff --name-status f543e47 origin/dev` = **15 文件全为新增(A)、+2092/−0**,即 origin/dev 是本链 rebase 后版本 + 一条 `chore(infra)`;但拓扑层面 `f543e47` **仍不是** `origin/dev` 的祖先(`rev-list --left-right` = 30↔31,同标题异 hash 的 rebase 残留)。⇒ 上面「须逐笔裁定冲突」的配方对本轮不再适用:实际做法是从 `origin/dev` 新切分支 + cherry-pick 三笔,PR diff 只含本轮 QA |
| AUTH-D2 | 重跑 seed | `npm run db:seed` | **2026-09-30 用户已裁定本轮含「生产库重 seed」**(前置硬条件:先 `cp data/prod.db prod.db.bak-<ts>` 快照——现网**无任何 DB 备份机制**)。必要性已升级:本分支改过 `prisma/seed.ts` 与 `prisma/seeds/*`(`team→team-page`、`legal→legal-page`、`+contact-page`、`+shellReadModels`),而 `src/lib/permissions.ts:26` 按 `modelCode` **精确匹配** ⇒ 不重 seed 则生产非 super_admin 角色继续持失效授予且缺 `content-model`/`content-zone` 读权(`admin/models`、`admin/stats`、`zones` 三处消费)。本地 `dev.db` 同样仍旧权限行 |
| AUTH-D3 | 视觉基线写入 | `npx playwright test visual-regression.spec.ts --update-snapshots` | **2026-09-30 实测口径(只读比对:94 passed / 31 failed)**:31 = **20 缺参照**(4 subject × 5 project:`/products/erp-upgrade` 全页、`/about/brand` 全页、L2 `product-card`、L2 `input-default`)+ **11 张已过时参照**(`/products/erp` ×5、`/solutions/manufacturing` ×5 = Q-5/S-2 网格修复的预期版面收缩,真实浏览器实证 computed 3/4/12 列;chromium-mobile `button-default` ×1 = 基线早于 N-15(c) `:visible` 选择器修正)。**两处更正**:① 原记「85 张 modified 未提交、视觉通过依赖未提交状态」**已失效**——107 张基线全部在库(`git ls-files e2e/visual-snapshots`),工作树干净;② 原记「`cases/[slug]` 从无基线」不准——`/cases` 与 `/cases/[slug]` **根本不在 `VISUAL_TEST_PAGES`(`e2e/visual-regression.spec.ts:26-43`)内**,属覆盖缺口而非缺参照 |
| AUTH-D4 | 写库 E2E | 完整 `npm run test` / `test:e2e:prod`(差 `cms-workflow`+`user-journey` 共 11 例) | 真写 `prisma/dev.db`;只读边界已实证,此 11 例是唯一未执行的功能层 |
| AUTH-D9 | Sentry 实投递 | 真实 DSN 起服务验证事件与 source map 上传 | 接线惰性有码路证据已足,但投递未线上验证 |
| AUTH-D10 | 全量变异测试 | 去 `--inPlace`(config 默认沙箱)跑 `mutate` 全集 | 成本/磁盘(峰值 1.7G 曾致 ENOSPC,周期 2 §3.9);须 ≥2G 余量与无并发门禁窗口 |
@@ -96,6 +98,7 @@
### 2.4 已知不稳定清单(**禁止用 retry / 放宽阈值「修」**)
- `mobile-user-journeys` UJ-10(firefox,隔离复跑通过)、`website-acceptance:111` 响应式(隔离通过)、`@accessibility` webkit 四例(周期 1 N-32,隔离不复现)。同属**并发 / 墙钟**族(周期 1 N-28:同一代码三轮失败数 8→1→5)。墙钟型用例(`p4:31`、`p4:68`)不该进共享并发门禁。
- **2026-09-30 新增同族实例**:`[firefox] uj-09-product-browsing.spec.ts:124` 在生产目标 92 例满并发批次里判红(`toHaveURL(/\/products\/?$/)` 收到 `""`,15s 等「返回 /products」的导航没完成),而**同批次另三引擎全绿、隔离单跑 1 passed(11.5s)、该文件 4-project 并发复跑两次各 4 passed**。⇒ 定性为并发/墙钟族而非代码回归;本轮 E2E 诚实口径是 **91 passed / 1 failed**,不得写成「92 例全绿」。取证:`docs/acceptance/2026-09-30-seal/e2e-production-writefree.txt`。
## 3. 提交前强制提醒(承接 memory 纪律)
- 提交只加自己的路径,**勿 `git add -A`**:`prisma/dev.db-shm`/`-wal` 未被 `.gitignore` 覆盖(周期 1 §7),`git add -A` 会把 SQLite 边车与陈旧 `dev.db`/`data.db`(周期 2 §3.9)扫入。
@@ -189,7 +192,7 @@
### 6.2 本会话门禁证据(最终树,全部 EXIT=0,见 §4.4 表)
`test:unit` **142 套件/1760 例** · `test:coverage`(阈值未下调,新 lib 100%)· `test:integration:real`(23,`dev.db` 指纹未变)· 完整 `check:a11y`(contrast 44/44 · headings 10/10 · brand-token 0 违规)· `npm run build`+standalone 装配 · `npm run lighthouse`(9 URL×3)· `type-check` · `lint` 0 error/104 warning。
### 6.3 工作树披露(最高优先,勿静默留给下一个人)
### 6.3 工作树披露(最高优先,勿静默留给下一个人)〔本节数字为 2026-09-25/28 当时实况,**已被 §8 封版记录取代**〕
`git status --porcelain` = **378 条**(54 未跟踪),HEAD 仍 `f543e47`。⇒ 两轮 + 本会话全部修复**只在工作树**,未提交/未 PR ⇒ 不可审、不可复现、不可 CI 验证。**这是 objective 阶段5「可交付」未达成的唯一实质原因。**
> **2026-09-28 第五轮后刷新**:`git status --porcelain` = **394 条**(55 未跟踪),HEAD 仍 `f543e47`。本轮净增 16 条改动/新文件(含新测试文件 `src/app/__tests__/cms-page-revalidate.test.ts`)。结论不变。
@@ -236,9 +239,31 @@ S-3(about/contact/erp-upgrade 无 revalidate + revalidateTag no-op,涉渲染
| 门禁 | 结果 |
|---|---|
| type-check | EXIT=0(一次 tsc 报错为 Q-6 测试 mock 类型断言丢失 `.mock`,已修后复跑绿) |
| lint | 0 error / 105 warning(与 AGENTS.md 口径一致 ⇒ 本轮零新增债) |
| lint | 0 error / **104 warning**(2026-09-30 在 sealed 树 `a0328a6` 复测仍为 104;本表 §4.4 记 104、此处曾记 105,且 `AGENTS.md` §5 亦记 105 并给出「分项相加=105」的自洽说明 ⇒ **现值以 104 为准**,105 口径已过期。本轮零新增债) |
| test:coverage | EXIT=0,**143 套件 / 1772 例全通过**(较 §6.2 净增 1 套件 12 例,全为本轮判别测试) |
| test:integration:real | EXIT=0,4 套件 / 23 例,dev.db/data.db inode+size+mtime 守卫通过(workflow `$transaction` 改动在真 SQLite 无回归) |
| check:contrast / brand-token / headings | 44/44 · 0 违规 · 10/10 页,均 EXIT=0 |
| build + standalone 装配 | EXIT=0,ASSEMBLY_OK;`prerender-manifest` 实证三页 ISR=3600(S-3 产物级) |
| lighthouse | EXIT=0,9 URL × 3 次 = 27 run 全部断言通过(lhci autorun 自起 standalone :3200) |
## 8. 封版记录(2026-09-30,现行判定)
**判定:封版通过(含例外清单)。** 代码封版点 = `a0328a6`;完整判定书、逐条判红定性与例外登记见 **`docs/acceptance/2026-09-30-seal/final-verdict.md`**,原始门禁输出同目录(`axe/`、`e2e-production-writefree.txt`、`visual-readonly.txt`、`security-headers-artifact.txt`、`check-motion.txt`、`lint.txt`、`type-check.txt`、`grid-structure-report.json`、`visual-check/*.png`)。
本轮在 sealed 树上补齐的 6 项(前几轮从未跑过):
| 门禁 | 退出码 | 结果 |
|---|---|---|
| `build:clean` + `postbuild` 装配 | 0 | `dist` 377M(清理前 2.5G,含 `dist/dev` 2.1G 开发缓存);standalone 三件套齐备 |
| 全站 `check:axe` | **0** | `PASSED=true`,34 路由 × (chromium,firefox) × (light,dark)=136 页,`violationNodes/contrastNodes/bgMismatch` 全 0;唯一 non-2xx = `/_not-found`(设计如此) |
| 产物安全头(`--url http://localhost:3100/`) | **0** | 7 PASS / 1 WARN(HSTS 边缘注入) / 0 FAIL,**每头单次** ⇒ 线上重复头确系 nginx+Next 两层叠加 |
| 生产目标 E2E(排除两个写库 spec) | **1** | **91 passed / 1 failed**;唯一红为 firefox UJ-09 并发墙钟(§2.4),`dev.db` 指纹跑前后一致 ⇒ 未写库 |
| 视觉只读比对(`--update-snapshots=none`) | **1** | **94 passed / 31 failed** = 20 缺参照 + 11 已过时参照(全部可归因,见 §2.3 AUTH-D3);未写任何基线 |
| `check:motion` | **1** | 23 处(20 曲线 + 2 裸时长 + 1 上限),与周期 2 同数未新增;属 DEC-P2-motion 待裁定 |
| `npm run lint` / `npm run type-check` | 0 / 0 | 0 error / **104 warning**(105 口径作废);tsc 0 error |
**封版不变式(为何不重跑全套)**:本轮唯一新提交是纯文档提交 S,`git diff --name-only a0328a6..S` 全部落在 `docs/**` 与 `*.md` 内 ⇒ `a0328a6` 上的绿灯对 S 恒等成立。S 的 sha 与清单见 `final-verdict.md` §6。
**本轮同步更正的台账假事实**(均为「文档写了但当场复核不成立」,已就地标注):§0 判定与 `:3-4` 的 HEAD/工作树状态、§2.2 **DEC-N21b**(`/admin` 其实有服务端 gating,入口是 `src/proxy.ts` 而非 `middleware.ts`;真残留=不查 `User.status` + 零测试)、§2.3 **AUTH-D1**(已闭合)、**AUTH-D3**(107 张基线全在库、缺参照实为 20 张、`/cases` 属覆盖缺口)、**AUTH-D2**(本轮含生产重 seed 及其权限依据)、§7.4 lint 104。
**发布侧未闭环(不属验收判定,见判定书 §5)**:`deploy:rollback` 不回滚容器/`public/`;`deploy.sh status` 不报磁盘;`rsync --delete public/` 与 `./uploads` 卷的关系部署前必须核实;nginx 安全头去重须单独投递。
+7
View File
@@ -156,6 +156,13 @@ Closes #123
**结论**:以 `npm run test` 的绿灯宣称"GA4/生产头已验证"属口径错误;引用时必须指明目标。
#### 6.1 产物口径的三条实操陷阱(2026-09-30 封版轮在 `a0328a6` 上实测)
1. **`test:e2e:prod` 默认集合会写真库**:它的 grep 是 `@smoke|@critical|@journey`,**不排除** `e2e/cms-workflow.spec.ts`(`@critical`)与 `e2e/user-journey.spec.ts`(`@journey`),二者对 `/api/admin/items|media` 发真实写请求 ⇒ "prod" 不等于"只读安全"。要拿写库-free 凭据必须自己加:
`--grep-invert 'cms-workflow\.spec\.ts|user-journey\.spec\.ts'`(`--grep-invert` 匹配的是含**文件路径**的 title path,先 `--list` 自证排除生效再实跑)。封版树实测:排除后 **92 例 → 91 passed / 1 failed**,`prisma/dev.db` 的 inode/size/mtime 跑前后完全一致。唯一红是 `[firefox] uj-09:124` 的并发墙钟(隔离与 4-project 复跑均绿),已登记 `docs/acceptance/qa-tracker.md` §2.4。
2. **视觉比对必须显式关写入**:`--update-snapshots` 不带值时 Playwright 取 `missing`,会**静默创建**缺失参照。只读比对写 `--update-snapshots=none`,并先确认 `:3000` 无残留服务(`reuseExistingServer` 在 dev 目标下为 true,会静默复用旧构建)。封版树实测 **94 passed / 31 failed = 20 缺参照 + 11 已过时参照**,逐条归因见 `docs/acceptance/2026-09-30-seal/final-verdict.md` §2.2。
3. **安全头不必打线上**:`scripts/utils/check-security-headers.ts:28-35` 支持 `--url`,因此可以对着本分支产物跑(`--url http://localhost:3100/` ⇒ 实测 7 PASS / 1 WARN / 0 FAIL,WARN 是 HSTS,由 nginx/CDN 边缘注入,http 目标本就不下发)。只有 `test:all` 的默认值指向 `https://novalon.cn`,那条在分支产物上结构上不可能全绿,两者不可混用。
### 7. 一键门禁 `npm run test:all`
`type-check` → `lint` → `test:coverage` → **`test:integration:real`** → **`check:a11y`** → `test:e2e:fast` → `test:security:headers`(`package.json:48` 原文即此七段,勿凭记忆省略 `test:integration:real`)。注意最后一项 E2E 仍是 **dev 目标**(`@smoke|@critical`),GA4 的 16 个实例同样 skipped,故 `test:all` 绿之后仍需按 §6 补 `test:e2e:prod`。
+17
View File
@@ -492,6 +492,22 @@ Object.defineProperty(window, 'requestAnimationFrame', { configurable: true, val
**来源**:`scripts/utils/check-security-headers.ts:60-68`(原 `status: 'pass' as const`)、`:137`(原同分支三元)、`:284`(原 `hasFailures` 只看 headerChecks)、`:34`(默认线上 URL)、`package.json:48,56`、`Jenkinsfile:293-294`、`next.config.mjs`(HSTS 不在应用头里)、`scripts/accessibility/crawl-routes.mjs`(正确的空输入写法)、`docs/acceptance/2026-09-23-gates/final-verdict.md` N-22/N-23/N-24。
### 5.32 「按文件名推断机制不存在」写出的假事实,本仓自己的文档已经否定过它
**事故**:`docs/acceptance/qa-tracker.md` §2.2 的 DEC-N21b 长期记着「`/admin` 无服务端 gating(仅客户端跳转),HTML 外壳无会话也下发」,证据栏写的是**「无 `middleware.ts`」**。2026-09-30 封版复核:该文件不存在,但 Next 16 已把该约定**更名为 `src/proxy.ts`**(在 HEAD 内、已跟踪、`2297f01` 迁入),`:77-105` 对 `matcher: ['/admin/:path*']` 做 Edge HS256 校验并在缺令牌/验签失败时重定向登录页 ⇒ 所谓缺陷的**前提不成立**。
三条本可当场拦住的证据,登记时都没被用:
1. **本仓 `CLAUDE.md:108` 白纸黑字写着**「中间件命名为 `proxy.ts`(Next 16 起 `middleware.ts` 更名)」——假事实与自家权威文档直接冲突。
2. **构建产物会自报**:`npm run build` 的路由表末尾打印 `ƒ Proxy (Middleware)`,等于服务自己声明有这个装配。
3. **文件名不是搜索键**:按能力找(`matcher`、`NextResponse.redirect`、`/admin`),而不是按记忆中的文件名找。
**同族第二例(同轮发现)**:台账与 `AGENTS.md` 记「磁盘上 85 张视觉基线相对 HEAD 处于 modified、'视觉通过'依赖未提交状态」。实况是 `git ls-files e2e/visual-snapshots` = **107 张全部已入库、工作树干净**;真实缺口是 20 张缺参照 + 11 张已过时参照。**文档里的文件计数与「是否已提交」必须以 `git ls-files` / `git status` 现取**,不能沿用上一轮的叙述。
**规则**:任何「某机制不存在 / 某能力缺失」的断言,落笔前必须给三样东西——① 该框架版本对应该机制的**当前约定文件名**(版本改名是常态);② 一次按**能力关键词**的检索结果;③ 一条产物级或运行时的正向证据。三者缺一,就只能写成「待复核」,不得写成缺陷。
**来源**:`src/proxy.ts:77-105`、`CLAUDE.md:108`、`docs/acceptance/qa-tracker.md` §2.2(DEC-N21b,2026-09-30 已就地更正)、§2.3(AUTH-D1/AUTH-D3 数字更正)、`docs/acceptance/2026-09-30-seal/final-verdict.md` §2.2。
## 6. 代码组织
### 6.1 组件版本膨胀
@@ -544,3 +560,4 @@ Object.defineProperty(window, 'requestAnimationFrame', { configurable: true, val
| 2026-09-23 | 增加 §5.28(`/contact` 的 CSP 违规定位三坑:① 同一缺陷对 `errors-in-console`(1/0 items)与 `inspector-issues`(0/1 item)一显一隐,issue 通道不进控制台;② 自造 Playwright 探针采到「0」但正向对照同为 0——CDP 注入的代码不受 `'unsafe-eval'` 判定,而 `connect-src`/`script-src-elem` 类经校准证明确可采,故**正向对照须同类**、未经对照的 0 记为「未证」;③ 真凶为 Zod 4.4.3 `allowsEval` 的 `new Function` 探测(库源码注释自述该现象),以带类型的公开开关 `z.config({jitless:true})` 修掉并经 `inspector-issues` 同仪器 A/B 确认 BP 96→100,同时排除「`www.google.com/g/collect` 被拦」的假定因——GA4 实测三条 hit 全落在已放行的 `www.google-analytics.com` 且返回 204)| 2026-09-23 收尾复测 N-11/N-13(`docs/acceptance/2026-09-23-gates/final-verdict.md` §3、`lighthouse-reports/contact-2026_09_23_04_54_06.report.json` 与修复后重跑)|
| 2026-09-23 | 增加 §5.29(视觉回归只读比对 21 例恒红的四类装配坑:① 宽松选择器 `input[type=text],input[type=email]` + `.first()` 命中按设计隐藏的**反垃圾蜜罐** ⇒ 期望隐藏字段可见,5/5 project 必失败且基线从未创建;② `[class*="card"]` 在 /products 零匹配,`element(s) not found` 被误读成 UI 回归;③ `VISUAL_TEST_PAGES` 列了 `/products/erp-upgrade`、`/about/brand` 但 5 个 project 全无 PNG ⇒ 只读判红、默认模式静默创建;④ 后台命令组 `{ cmd; echo X=$?; date; }` 的退出码取自 `date`,框架报 exit 0 而真实门禁 EXIT=1。管理归零:失败先按断言/参照/渲染三层分类,`0 例像素不符`即可否掉 UI 假设;不能复验的门禁脚本只记录精确修法不动手 | 2026-09-23 视觉回归只读比对(EXIT=1,21 failed / 104 passed)+ N-15 取证 |
| 2026-09-23 | 增加 §5.30(覆盖率门禁 `collectCoverageFrom` 不含 `src/app/**` ⇒ route handler 全在棘轮外,专项审查找出 3 个 P1:`admin/stats` 只验会话即返回跨模型草稿标题、`checkUserPermission` 从不读 User 行使停用账号旧令牌 24h 内仍可用、B-6 的 `isInternalRedirect` 定义成私有函数致姊妹路由 `draft/disable` 开放重定向复活。管理归零:安全抽象必须可导入、修完要 grep 函数名看命中数是否等于应有数、每处修复做「临时移除 guard ⇒ 用例判红 ⇒ 恢复转绿」的 RED 实测、改共享鉴权函数打爆测试桩是信号不是障碍 | 2026-09-23 `src/app/**` 盲区专项审查(N-17..N-21)+ 三项修复与 RED 探针 |
| 2026-09-30 | 增加 §5.32(「按文件名推断机制不存在」写出的假事实:DEC-N21b 记「无 middleware.ts ⇒ /admin 无服务端 gating」,实况是 Next 16 已改名 `src/proxy.ts` 且 `CLAUDE.md:108` 早已写明;同族第二例是「85 张基线未提交」而 `git ls-files` 实测 107 张全在库) | `src/proxy.ts:77-105`、`docs/acceptance/2026-09-30-seal/final-verdict.md` |