|
20139
|
1
|
5
|
10
|
18
|
0
|
0
|
refs/heads/pc-260818
|
0
|
{"Commits":[{"Sha1":"c82e81c72 {"Commits":[{"Sha1":"c82e81c72dd613315f20412513139ce9d8dea8a7","Message":"员工预定码业绩报表\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-07-31T11:28:22+08:00"}],"HeadCommit":{"Sha1":"c82e81c72dd613315f20412513139ce9d8dea8a7","Message":"员工预定码业绩报表\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-07-31T11:28:22+08:00"},"CompareURL":"vodtest/pc/compare/7d5d79677347f853f40390608be09d5536fa3050...c82e81c72dd613315f20412513139ce9d8dea8a7","Len":1}...
|
1785468519
|
Edit
Delete
|
|
20140
|
3
|
5
|
10
|
18
|
0
|
0
|
refs/heads/pc-260818
|
0
|
{"Commits":[{"Sha1":"c82e81c72 {"Commits":[{"Sha1":"c82e81c72dd613315f20412513139ce9d8dea8a7","Message":"员工预定码业绩报表\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-07-31T11:28:22+08:00"}],"HeadCommit":{"Sha1":"c82e81c72dd613315f20412513139ce9d8dea8a7","Message":"员工预定码业绩报表\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-07-31T11:28:22+08:00"},"CompareURL":"vodtest/pc/compare/7d5d79677347f853f40390608be09d5536fa3050...c82e81c72dd613315f20412513139ce9d8dea8a7","Len":1}...
|
1785468519
|
Edit
Delete
|
|
20141
|
4
|
5
|
10
|
18
|
0
|
0
|
refs/heads/pc-260818
|
0
|
{"Commits":[{"Sha1":"c82e81c72 {"Commits":[{"Sha1":"c82e81c72dd613315f20412513139ce9d8dea8a7","Message":"员工预定码业绩报表\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-07-31T11:28:22+08:00"}],"HeadCommit":{"Sha1":"c82e81c72dd613315f20412513139ce9d8dea8a7","Message":"员工预定码业绩报表\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-07-31T11:28:22+08:00"},"CompareURL":"vodtest/pc/compare/7d5d79677347f853f40390608be09d5536fa3050...c82e81c72dd613315f20412513139ce9d8dea8a7","Len":1}...
|
1785468519
|
Edit
Delete
|
|
20142
|
7
|
5
|
10
|
18
|
0
|
0
|
refs/heads/pc-260818
|
0
|
{"Commits":[{"Sha1":"c82e81c72 {"Commits":[{"Sha1":"c82e81c72dd613315f20412513139ce9d8dea8a7","Message":"员工预定码业绩报表\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-07-31T11:28:22+08:00"}],"HeadCommit":{"Sha1":"c82e81c72dd613315f20412513139ce9d8dea8a7","Message":"员工预定码业绩报表\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-07-31T11:28:22+08:00"},"CompareURL":"vodtest/pc/compare/7d5d79677347f853f40390608be09d5536fa3050...c82e81c72dd613315f20412513139ce9d8dea8a7","Len":1}...
|
1785468519
|
Edit
Delete
|
|
20143
|
8
|
5
|
10
|
18
|
0
|
0
|
refs/heads/pc-260818
|
0
|
{"Commits":[{"Sha1":"c82e81c72 {"Commits":[{"Sha1":"c82e81c72dd613315f20412513139ce9d8dea8a7","Message":"员工预定码业绩报表\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-07-31T11:28:22+08:00"}],"HeadCommit":{"Sha1":"c82e81c72dd613315f20412513139ce9d8dea8a7","Message":"员工预定码业绩报表\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-07-31T11:28:22+08:00"},"CompareURL":"vodtest/pc/compare/7d5d79677347f853f40390608be09d5536fa3050...c82e81c72dd613315f20412513139ce9d8dea8a7","Len":1}...
|
1785468519
|
Edit
Delete
|
|
20144
|
11
|
5
|
10
|
18
|
0
|
0
|
refs/heads/pc-260818
|
0
|
{"Commits":[{"Sha1":"c82e81c72 {"Commits":[{"Sha1":"c82e81c72dd613315f20412513139ce9d8dea8a7","Message":"员工预定码业绩报表\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-07-31T11:28:22+08:00"}],"HeadCommit":{"Sha1":"c82e81c72dd613315f20412513139ce9d8dea8a7","Message":"员工预定码业绩报表\n","AuthorEmail":"yangruilin888@gmail.com","AuthorName":"linyangrui","CommitterEmail":"yangruilin888@gmail.com","CommitterName":"linyangrui","Timestamp":"2026-07-31T11:28:22+08:00"},"CompareURL":"vodtest/pc/compare/7d5d79677347f853f40390608be09d5536fa3050...c82e81c72dd613315f20412513139ce9d8dea8a7","Len":1}...
|
1785468519
|
Edit
Delete
|
|
427
|
1
|
5
|
1
|
18
|
0
|
0
|
refs/heads/pc-testnew
|
0
|
|
1774346978
|
Edit
Delete
|
|
428
|
9
|
5
|
1
|
18
|
0
|
0
|
refs/heads/pc-testnew
|
0
|
|
1774346978
|
Edit
Delete
|
|
429
|
7
|
5
|
1
|
18
|
0
|
0
|
refs/heads/pc-testnew
|
0
|
|
1774346978
|
Edit
Delete
|
|
430
|
8
|
5
|
1
|
18
|
0
|
0
|
refs/heads/pc-testnew
|
0
|
|
1774346978
|
Edit
Delete
|
|
431
|
1
|
5
|
1
|
18
|
0
|
0
|
refs/heads/pc-testnew
|
0
|
{"Commits":[{"Sha1":"310cf8f88 {"Commits":[{"Sha1":"310cf8f888a6a5f74d38e4c65f97d47ccdac9822","Message":"新分支提交\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-24T18:08:55+08:00"}],"HeadCommit":{"Sha1":"310cf8f888a6a5f74d38e4c65f97d47ccdac9822","Message":"新分支提交\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-24T18:08:55+08:00"},"CompareURL":"vodtest/pc/compare/eebbf9c6cc4410101110485c69af70f2e5133592...310cf8f888a6a5f74d38e4c65f97d47ccdac9822","Len":1}...
|
1774346978
|
Edit
Delete
|
|
432
|
9
|
5
|
1
|
18
|
0
|
0
|
refs/heads/pc-testnew
|
0
|
{"Commits":[{"Sha1":"310cf8f88 {"Commits":[{"Sha1":"310cf8f888a6a5f74d38e4c65f97d47ccdac9822","Message":"新分支提交\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-24T18:08:55+08:00"}],"HeadCommit":{"Sha1":"310cf8f888a6a5f74d38e4c65f97d47ccdac9822","Message":"新分支提交\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-24T18:08:55+08:00"},"CompareURL":"vodtest/pc/compare/eebbf9c6cc4410101110485c69af70f2e5133592...310cf8f888a6a5f74d38e4c65f97d47ccdac9822","Len":1}...
|
1774346978
|
Edit
Delete
|
|
433
|
7
|
5
|
1
|
18
|
0
|
0
|
refs/heads/pc-testnew
|
0
|
{"Commits":[{"Sha1":"310cf8f88 {"Commits":[{"Sha1":"310cf8f888a6a5f74d38e4c65f97d47ccdac9822","Message":"新分支提交\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-24T18:08:55+08:00"}],"HeadCommit":{"Sha1":"310cf8f888a6a5f74d38e4c65f97d47ccdac9822","Message":"新分支提交\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-24T18:08:55+08:00"},"CompareURL":"vodtest/pc/compare/eebbf9c6cc4410101110485c69af70f2e5133592...310cf8f888a6a5f74d38e4c65f97d47ccdac9822","Len":1}...
|
1774346978
|
Edit
Delete
|
|
434
|
8
|
5
|
1
|
18
|
0
|
0
|
refs/heads/pc-testnew
|
0
|
{"Commits":[{"Sha1":"310cf8f88 {"Commits":[{"Sha1":"310cf8f888a6a5f74d38e4c65f97d47ccdac9822","Message":"新分支提交\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-24T18:08:55+08:00"}],"HeadCommit":{"Sha1":"310cf8f888a6a5f74d38e4c65f97d47ccdac9822","Message":"新分支提交\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-24T18:08:55+08:00"},"CompareURL":"vodtest/pc/compare/eebbf9c6cc4410101110485c69af70f2e5133592...310cf8f888a6a5f74d38e4c65f97d47ccdac9822","Len":1}...
|
1774346978
|
Edit
Delete
|
|
319
|
1
|
5
|
1
|
17
|
0
|
0
|
refs/heads/pctest
|
0
|
|
1773989952
|
Edit
Delete
|
|
320
|
2
|
5
|
1
|
17
|
0
|
0
|
refs/heads/pctest
|
0
|
|
1773989952
|
Edit
Delete
|
|
321
|
1
|
5
|
1
|
17
|
0
|
0
|
refs/heads/pctest
|
0
|
{"Commits":[{"Sha1":"e31b1c088 {"Commits":[{"Sha1":"e31b1c088fcbd1c19c3ca487fe550697bfa9bdd6","Message":"测试2222333\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T14:58:36+08:00"}],"HeadCommit":{"Sha1":"e31b1c088fcbd1c19c3ca487fe550697bfa9bdd6","Message":"测试2222333\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T14:58:36+08:00"},"CompareURL":"juhai/pctest/compare/78427a51eb7bd5a7de532a80ec9e94f265930824...e31b1c088fcbd1c19c3ca487fe550697bfa9bdd6","Len":1}...
|
1773989952
|
Edit
Delete
|
|
322
|
2
|
5
|
1
|
17
|
0
|
0
|
refs/heads/pctest
|
0
|
{"Commits":[{"Sha1":"e31b1c088 {"Commits":[{"Sha1":"e31b1c088fcbd1c19c3ca487fe550697bfa9bdd6","Message":"测试2222333\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T14:58:36+08:00"}],"HeadCommit":{"Sha1":"e31b1c088fcbd1c19c3ca487fe550697bfa9bdd6","Message":"测试2222333\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T14:58:36+08:00"},"CompareURL":"juhai/pctest/compare/78427a51eb7bd5a7de532a80ec9e94f265930824...e31b1c088fcbd1c19c3ca487fe550697bfa9bdd6","Len":1}...
|
1773989952
|
Edit
Delete
|
|
325
|
1
|
5
|
1
|
17
|
0
|
0
|
refs/heads/pctest
|
0
|
{"Commits":[{"Sha1":"b23272882 {"Commits":[{"Sha1":"b23272882d68e0b61ab119ff0f670c4dbbe7a652","Message":"修改单个文件测试\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T15:04:08+08:00"}],"HeadCommit":{"Sha1":"b23272882d68e0b61ab119ff0f670c4dbbe7a652","Message":"修改单个文件测试\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T15:04:08+08:00"},"CompareURL":"juhai/pctest/compare/e31b1c088fcbd1c19c3ca487fe550697bfa9bdd6...b23272882d68e0b61ab119ff0f670c4dbbe7a652","Len":1}...
|
1773990288
|
Edit
Delete
|
|
326
|
2
|
5
|
1
|
17
|
0
|
0
|
refs/heads/pctest
|
0
|
{"Commits":[{"Sha1":"b23272882 {"Commits":[{"Sha1":"b23272882d68e0b61ab119ff0f670c4dbbe7a652","Message":"修改单个文件测试\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T15:04:08+08:00"}],"HeadCommit":{"Sha1":"b23272882d68e0b61ab119ff0f670c4dbbe7a652","Message":"修改单个文件测试\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T15:04:08+08:00"},"CompareURL":"juhai/pctest/compare/e31b1c088fcbd1c19c3ca487fe550697bfa9bdd6...b23272882d68e0b61ab119ff0f670c4dbbe7a652","Len":1}...
|
1773990288
|
Edit
Delete
|
|
329
|
1
|
5
|
1
|
17
|
0
|
0
|
refs/heads/pctest
|
0
|
{"Commits":[{"Sha1":"7fbec3ef9 {"Commits":[{"Sha1":"7fbec3ef95a3856eef25ceabf266030d5ca445e4","Message":"修改单个文件测试2\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T15:22:59+08:00"}],"HeadCommit":{"Sha1":"7fbec3ef95a3856eef25ceabf266030d5ca445e4","Message":"修改单个文件测试2\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T15:22:59+08:00"},"CompareURL":"juhai/pctest/compare/b23272882d68e0b61ab119ff0f670c4dbbe7a652...7fbec3ef95a3856eef25ceabf266030d5ca445e4","Len":1}...
|
1773991404
|
Edit
Delete
|
|
330
|
2
|
5
|
1
|
17
|
0
|
0
|
refs/heads/pctest
|
0
|
{"Commits":[{"Sha1":"7fbec3ef9 {"Commits":[{"Sha1":"7fbec3ef95a3856eef25ceabf266030d5ca445e4","Message":"修改单个文件测试2\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T15:22:59+08:00"}],"HeadCommit":{"Sha1":"7fbec3ef95a3856eef25ceabf266030d5ca445e4","Message":"修改单个文件测试2\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T15:22:59+08:00"},"CompareURL":"juhai/pctest/compare/b23272882d68e0b61ab119ff0f670c4dbbe7a652...7fbec3ef95a3856eef25ceabf266030d5ca445e4","Len":1}...
|
1773991404
|
Edit
Delete
|
|
333
|
1
|
5
|
1
|
17
|
0
|
0
|
refs/heads/pctest
|
0
|
{"Commits":[{"Sha1":"12a4a4ad4 {"Commits":[{"Sha1":"12a4a4ad441e2edf19328cb83a4d1532f1985c69","Message":"修改单个文件测试3\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T15:26:46+08:00"}],"HeadCommit":{"Sha1":"12a4a4ad441e2edf19328cb83a4d1532f1985c69","Message":"修改单个文件测试3\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T15:26:46+08:00"},"CompareURL":"juhai/pctest/compare/7fbec3ef95a3856eef25ceabf266030d5ca445e4...12a4a4ad441e2edf19328cb83a4d1532f1985c69","Len":1}...
|
1773991753
|
Edit
Delete
|
|
334
|
2
|
5
|
1
|
17
|
0
|
0
|
refs/heads/pctest
|
0
|
{"Commits":[{"Sha1":"12a4a4ad4 {"Commits":[{"Sha1":"12a4a4ad441e2edf19328cb83a4d1532f1985c69","Message":"修改单个文件测试3\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T15:26:46+08:00"}],"HeadCommit":{"Sha1":"12a4a4ad441e2edf19328cb83a4d1532f1985c69","Message":"修改单个文件测试3\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-20T15:26:46+08:00"},"CompareURL":"juhai/pctest/compare/7fbec3ef95a3856eef25ceabf266030d5ca445e4...12a4a4ad441e2edf19328cb83a4d1532f1985c69","Len":1}...
|
1773991753
|
Edit
Delete
|
|
495
|
1
|
5
|
1
|
17
|
0
|
0
|
refs/heads/pctest
|
0
|
{"Commits":[{"Sha1":"6a1850c0a {"Commits":[{"Sha1":"6a1850c0a6b2b9a5c6f910af5ddecbf2d99c8a96","Message":"ce1\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-25T09:54:45+08:00"},{"Sha1":"2946098562291d2b86473d4cf7d127331e99ac43","Message":"ce\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-25T09:53:55+08:00"}],"HeadCommit":{"Sha1":"6a1850c0a6b2b9a5c6f910af5ddecbf2d99c8a96","Message":"ce1\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-25T09:54:45+08:00"},"CompareURL":"juhai/pctest/compare/12a4a4ad441e2edf19328cb83a4d1532f1985c69...6a1850c0a6b2b9a5c6f910af5ddecbf2d99c8a96","Len":2}...
|
1774403728
|
Edit
Delete
|
|
496
|
2
|
5
|
1
|
17
|
0
|
0
|
refs/heads/pctest
|
0
|
{"Commits":[{"Sha1":"6a1850c0a {"Commits":[{"Sha1":"6a1850c0a6b2b9a5c6f910af5ddecbf2d99c8a96","Message":"ce1\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-25T09:54:45+08:00"},{"Sha1":"2946098562291d2b86473d4cf7d127331e99ac43","Message":"ce\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-25T09:53:55+08:00"}],"HeadCommit":{"Sha1":"6a1850c0a6b2b9a5c6f910af5ddecbf2d99c8a96","Message":"ce1\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-25T09:54:45+08:00"},"CompareURL":"juhai/pctest/compare/12a4a4ad441e2edf19328cb83a4d1532f1985c69...6a1850c0a6b2b9a5c6f910af5ddecbf2d99c8a96","Len":2}...
|
1774403729
|
Edit
Delete
|
|
499
|
1
|
5
|
1
|
17
|
0
|
0
|
refs/heads/pctest
|
0
|
{"Commits":[{"Sha1":"e03027962 {"Commits":[{"Sha1":"e03027962aed59b0c87ce41b201b6905760521d6","Message":"ce12\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-25T10:22:54+08:00"}],"HeadCommit":{"Sha1":"e03027962aed59b0c87ce41b201b6905760521d6","Message":"ce12\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-25T10:22:54+08:00"},"CompareURL":"juhai/pctest/compare/6a1850c0a6b2b9a5c6f910af5ddecbf2d99c8a96...e03027962aed59b0c87ce41b201b6905760521d6","Len":1}...
|
1774405382
|
Edit
Delete
|
|
500
|
2
|
5
|
1
|
17
|
0
|
0
|
refs/heads/pctest
|
0
|
{"Commits":[{"Sha1":"e03027962 {"Commits":[{"Sha1":"e03027962aed59b0c87ce41b201b6905760521d6","Message":"ce12\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-25T10:22:54+08:00"}],"HeadCommit":{"Sha1":"e03027962aed59b0c87ce41b201b6905760521d6","Message":"ce12\n","AuthorEmail":"121158035@qq.com","AuthorName":"zhangjunnan","CommitterEmail":"121158035@qq.com","CommitterName":"zhangjunnan","Timestamp":"2026-03-25T10:22:54+08:00"},"CompareURL":"juhai/pctest/compare/6a1850c0a6b2b9a5c6f910af5ddecbf2d99c8a96...e03027962aed59b0c87ce41b201b6905760521d6","Len":1}...
|
1774405382
|
Edit
Delete
|
|
12573
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
|
1781524152
|
Edit
Delete
|
|
12574
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"247d57ffd {"Commits":[{"Sha1":"247d57ffdf2ba9ba3e2f8023f7f140cbcc1bbd29","Message":"feat(frontend-react): Capacitor 安卓打包与模拟器部署链路\n\n将 frontend-react 经 Capacitor 7.6.6 打包为原生安卓 App 并在模拟器跑通：\n- 新增 android 原生工程（compileSdk/targetSdk 35，gradle 8.11.1）\n- capacitor.config.ts 启用 CapacitorHttp + cleartext + allowMixedContent，\n 让 WebView 内 axios 走原生网络层，绕过混合内容/CORS 直连本机后端\n- AndroidManifest 加 usesCleartextTraffic + network_security_config，\n 放行模拟器回环 10.0.2.2 的明文 HTTP\n- .env.android 指向 http://10.0.2.2:3000/v1（模拟器访问宿主后端）\n- root/frontend-react package.json 增加 android/ios 打包脚本\n- scripts/android、scripts/ios 提供 gradle/emulator helper\n- .gitignore 忽略 .local-tools/jdks 与 gradle 缓存\n- 补齐迁移分支缺失的 ar-ledger/Detail、opportunities/DetailHeader\n 两个 .module.scss（否则 vite build 直接失败）\n- docs 补 Android/iOS runbook，记录 JDK21 要求、CapacitorHttp 连通前提、\n default 系统镜像选型与故障对照表\n\n验证：模拟器(API 34)登录 admin@juhi.com 后工作台仪表盘加载，\n后端单次进入 100+ 个 200 请求（/dashboard、/stats、/todos 等）。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-06-15T04:45:09-07:00"},{"Sha1":"bfc67c2712903f1da5b77de5f89347be1ecdaf84","Message":"fix(rls): safe-rls-inject.sql 对齐 canonical 策略口径\n\n原脚本用 app.current_tenant_id（legacy 变体），与运行态 rls-extension.ts\n注入的 set_config('app.tenant_id',...) 不匹配，误用会导致本租户合法读被\nRLS 全过滤；且只有 USING 无 WITH CHECK，跨租户写不受拦。\n\n对齐迁移真源：app.tenant_id + current_setting(...,true) 兜底 + NULLIF 空串\n保护 + 补 WITH CHECK。已对测试库幂等实跑验证策略可建、USING/WITH CHECK\n均绑定 app.tenant_id。\n\nCo-Authored-By: Claude Opus 4.8 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-06-14T07:26:30-07:00"},{"Sha1":"18c752c4fa928ecfa8b9b99188545f9ed939315b","Message":"chore(react-migration): pnpm dev 默认前端切到 React（接管规范端口 5173）\n\n本地 dev cutover：start-all.sh FRONTEND_DIR 默认指向 frontend-react，\nReact 接管规范端口 5173，healthcheck/docker-compose/nginx 自然指向 React。\nVue 降级为显式 opt-in（dev:frontend:vue / dev:vue / FRONTEND_APP_DIR=frontend）。\n\n- start-all.sh: FRONTEND_DIR 默认 frontend-react，保留 FRONTEND_APP_DIR 回退口\n- frontend-react/package.json: 补 dev:bg(--port 5173)/dev:bg:https/dev:cert/dev:https\n- frontend-react/vite.config.ts: 加 HTTPS dev 证书解析，与 Vue 同口径复用 generate-dev-cert\n- 根 package.json: dev:frontend→React，新增 Vue opt-in 脚本\n\n生产/容器构建仍为 Vue，生产 cutover 受 17 项治理门禁约束，未在此变更。\n\nCo-Authored-By: Claude Opus 4.8 (1M context) \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-06-14T06:55:23-07:00"},{"Sha1":"4715abdbac750e073f17409c46ee9c1b27dcc9ef","Message":"chore(react-migration): refresh cutover readiness ledger\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"laoluojuhai","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"laoluojuhai","Timestamp":"2026-06-14T21:14:03+08:00"},{"Sha1":"b9000ffd475e71c448e0ab6afc283fe88b1117a6","Message":"chore(react-migration): refresh e2e readiness evidence\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"laoluojuhai","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"laoluojuhai","Timestamp":"2026-06-14T21:05:07+08:00"}],"HeadCommit":{"Sha1":"247d57ffdf2ba9ba3e2f8023f7f140cbcc1bbd29","Message":"feat(frontend-react): Capacitor 安卓打包与模拟器部署链路\n\n将 frontend-react 经 Capacitor 7.6.6 打包为原生安卓 App 并在模拟器跑通：\n- 新增 android 原生工程（compileSdk/targetSdk 35，gradle 8.11.1）\n- capacitor.config.ts 启用 CapacitorHttp + cleartext + allowMixedContent，\n 让 WebView 内 axios 走原生网络层，绕过混合内容/CORS 直连本机后端\n- AndroidManifest 加 usesCleartextTraffic + network_security_config，\n 放行模拟器回环 10.0.2.2 的明文 HTTP\n- .env.android 指向 http://10.0.2.2:3000/v1（模拟器访问宿主后端）\n- root/frontend-react package.json 增加 android/ios 打包脚本\n- scripts/android、scripts/ios 提供 gradle/emulator helper\n- .gitignore 忽略 .local-tools/jdks 与 gradle 缓存\n- 补齐迁移分支缺失的 ar-ledger/Detail、opportunities/DetailHeader\n 两个 .module.scss（否则 vite build 直接失败）\n- docs 补 Android/iOS runbook，记录 JDK21 要求、CapacitorHttp 连通前提、\n default 系统镜像选型与故障对照表\n\n验证：模拟器(API 34)登录 admin@juhi.com 后工作台仪表盘加载，\n后端单次进入 100+ 个 200 请求（/dashboard、/stats、/todos 等）。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-06-15T04:45:09-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/1ae44a161007d2352abbc9000239e9a603240dfc...247d57ffdf2ba9ba3e2f8023f7f140cbcc1bbd29","Len":10}...
|
1781524152
|
Edit
Delete
|
|
12575
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"03d1e228d {"Commits":[{"Sha1":"03d1e228ddabedbfc97f6c2a3da75c952c522d9e","Message":"docs(frontend-react): 补记 Capacitor iOS 打包脚手架（说明 247d57ffdf）\n\n上一提交 247d57ffdf 信息仅写「安卓打包」，但实际同时纳入了 iOS 打包脚手架，\n此处在历史中补记，避免信息与内容不符：\n\n- @capacitor/ios 7.6.6 依赖 + build:ios / ios:add|sync|run|open 脚本\n （含根级 frontend-react:ios:* 转发脚本）\n- frontend-react/.env.ios（iOS 模拟器走 localhost:3000，区别于 Android 的 10.0.2.2）\n- scripts/ios/frontend-react-cap.sh（pod 命令 PATH 兜底包装，标准 PATH 优先）\n- frontend-react/capacitor.config.ts、docs/operations/frontend-react-ios-capacitor.md\n\n本提交为空，仅补充历史说明。CocoaPods 1.12.1 安装于本机用户 gem 目录\n（~/.gem/ruby/2.6.0），属本机环境不入仓库；ios/ 原生工程待安装 Xcode 后\n执行 pnpm run ios:add 生成。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-06-15T04:52:37-07:00"}],"HeadCommit":{"Sha1":"03d1e228ddabedbfc97f6c2a3da75c952c522d9e","Message":"docs(frontend-react): 补记 Capacitor iOS 打包脚手架（说明 247d57ffdf）\n\n上一提交 247d57ffdf 信息仅写「安卓打包」，但实际同时纳入了 iOS 打包脚手架，\n此处在历史中补记，避免信息与内容不符：\n\n- @capacitor/ios 7.6.6 依赖 + build:ios / ios:add|sync|run|open 脚本\n （含根级 frontend-react:ios:* 转发脚本）\n- frontend-react/.env.ios（iOS 模拟器走 localhost:3000，区别于 Android 的 10.0.2.2）\n- scripts/ios/frontend-react-cap.sh（pod 命令 PATH 兜底包装，标准 PATH 优先）\n- frontend-react/capacitor.config.ts、docs/operations/frontend-react-ios-capacitor.md\n\n本提交为空，仅补充历史说明。CocoaPods 1.12.1 安装于本机用户 gem 目录\n（~/.gem/ruby/2.6.0），属本机环境不入仓库；ios/ 原生工程待安装 Xcode 后\n执行 pnpm run ios:add 生成。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-06-15T04:52:37-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/247d57ffdf2ba9ba3e2f8023f7f140cbcc1bbd29...03d1e228ddabedbfc97f6c2a3da75c952c522d9e","Len":1}...
|
1781524367
|
Edit
Delete
|
|
13720
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"989e54a1f {"Commits":[{"Sha1":"989e54a1f18193e7e19b620bf93c71c29508f2f9","Message":"feat(react-migration): wire dashboard actions and design tokens\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-06-22T20:27:43-07:00"}],"HeadCommit":{"Sha1":"989e54a1f18193e7e19b620bf93c71c29508f2f9","Message":"feat(react-migration): wire dashboard actions and design tokens\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-06-22T20:27:43-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/03d1e228ddabedbfc97f6c2a3da75c952c522d9e...989e54a1f18193e7e19b620bf93c71c29508f2f9","Len":1}...
|
1782185301
|
Edit
Delete
|
|
15249
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"04eb1a902 {"Commits":[{"Sha1":"04eb1a9023e244277b620d25d83ab7fe3e1e7c3e","Message":"fix: 修复采购拒收/提成备注/供应商表单/选址提交时间 4 处前后端契约断链\n\n- Rejections.tsx：前端类型/表单/列表全面对齐后端真实契约\n （reasonType/reasonDetail/handlingStatus/handlingResult，purchaseOrder/\n supplier/rejector 改嵌套对象）；POST /rejections、/rejections/:id/handle\n 补上此前完全缺失的 Zod 校验；listRejections 的 supplierId 筛选此前被\n 静默忽略，现通过 purchase_orders 关联真正实现；handlingStatus 命名对齐。\n- commission_records/commission_settlements：前端 remark 字段统一改为\n notes 对齐后端真实列；顺带把\"生成结算单\"备注功能真正打通\n （generateSettlementSchema 此前没有该字段，前端填了会被 Zod 直接丢弃）。\n- supplier_applications/supplier_contracts：移除一批被 Zod 校验通过却\n 从未写入数据库的死字段（city/province/companyProfile/bankAccountName/\n applyReason/subCategory/confidentialityClause/productScope/deliveryTerms/\n penaltyClause/territory）——这批列已在 schema 清理中被物理删除，\n 修复方向是去掉前后端\"填了也存不进去\"的死字段，而非把列加回来。\n- location_assessments.submitted_at：该列物理上一直存在（建表迁移即有），\n 只是 Prisma schema 未声明；补上字段声明后 submit() 真正写入该列，\n 前端已有的渲染逻辑无需改动即可生效，prisma migrate status 确认无 drift。\n\ntype-check 全绿（前端+后端），受影响 6 个模块 219 个单测通过（新增 7 个\n拒收记录测试锁定 supplierId 过滤、字段写入行为）。\n\nCo-Authored-By: Claude Sonnet 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-01T03:40:54-07:00"},{"Sha1":"0dda7b57e47411ea4a044d5966c888a9336242a7","Message":"chore(schema): 388 项破坏性 schema 变更全文级复核，清理本地库 243 项确认孤儿对象\n\n背景：dual-tenant-risk-ledger R-P0-2 记录的 388/375 项 dropTable+dropColumn\n迁移序列外破坏性变更，此前 0 owner 签字、无法追溯裁定依据。\n\n本轮工作：\n1. 产出结构化清单（schema-destructive-changes-inventory-2026-07-01.md），\n 对 375 项逐条做全文级代码引用复核（非邻近窗口字符串初筛）。\n2. 279 项收敛为\"确认可安全清理\"，其中 25 项 supplier 域列被证实是\"改名复用\"\n （如 risk_name→title、contract_name→title），从候选中排除避免真删数据；\n 58 项（supplier_jbps/supplier_scorecards）候选列名与当前 schema 完全不匹配，\n 标记为\"清单来源存疑\"暂不裁定。\n3. 对确认安全的 279 项先跑数据存在性预检，36 列有非空计数（抽查证实均为\n DEFAULT 值噪声，非真实业务数据）保守排除，最终 243 项（30 张表 CASCADE +\n 213 列）已在本地开发库执行验证，过程中发现并安全清理了 service_tickets\n 上两条指向废弃工单工作流表的死外键。\n\nscripts/audit-same-tenant-references.ts 同步移除已删除的 ticket-operations.service.ts\n引用。type-check 全绿，受影响 6 个模块 215 个单测通过。staging/生产未触碰，\n需 owner 签字后按文档流程重新执行数据预检再放行。\n\nCo-Authored-By: Claude Sonnet 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-01T03:40:19-07:00"},{"Sha1":"4d854c3be9851ddb8af27e9bea5cb231c33a7a03","Message":"fix(tickets): 补齐状态机死守卫，删除零引用的死代码平行实现\n\ncanStart/canResolve 守卫补线：未指派处理人的工单不能开始处理或标记已解决\n（此前状态机拓扑允许 new/in_progress 直接流转，未指派工单可静默进入处理中）。\n\n删除 ticket-operations.service.ts：其导出的 12 个函数\n（startTicket/resolveTicket/pauseTicket 等）在全仓库只被自己的测试文件引用，\ncontroller/路由层实际走的是 TicketService 类方法，是完全未接线的死代码平行实现。\n测试文件中对应的 7 个 describe 块改写为测试真实类方法，过程中一并修正了\nmock 调用次数（updateInTx 内部还有一次存在性校验 findFirst）和\ncanTransitionTicket 全局 mock 恒 true 导致拓扑拒绝路径测不到的问题。\n\n43/43 单测通过。\n\nCo-Authored-By: Claude Sonnet 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-01T03:39:23-07:00"},{"Sha1":"33a3248f092a239094ad920d12fb0c5dc0c730ca","Message":"fix(governance): 补录 53 个孤儿模块到 modules.ts 登记表\n\n后端 281 个模块目录里有 53 个已挂载路由但从未在 MODULE_REGISTRY 登记，\n权限码从各模块真实 requirePermission 调用中提取补录（非编造）；system\n模块补充为聚合门面条目（无独立路由，见 system.routes.ts 注释）。\nai-manifest-registry 确认是 Phase 0 基础设施桩代码而非业务模块，未强行注册。\n\naudit:modules 复核无回归。\n\nCo-Authored-By: Claude Sonnet 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-01T03:38:57-07:00"},{"Sha1":"e2cacfb34e40fb700f3c2b03039deb9db20fd603","Message":"fix(rls): 修复分区子表 RLS 绕过并把运行态扫描接入棘轮门禁\n\naudit_logs/event_logs/im_messages 的 81 张月度分区子表此前 relrowsecurity=false，\n父表 RLS policy 不被子表继承，无租户上下文直查子分区可读到全租户数据（本地实测\naudit_logs_2026_05 泄露 21375 行）。新增迁移给存量子表 backfill RLS+policy，\n并把 create_monthly_partitions() 改成新分区随建随启 RLS，已在本地库验证泄露归零、\n合法访问不受影响。\n\n同时补上审计盲区：generate-rls-policies.ts 新增运行态扫描（直连 pg_inherits/\npg_class），不再只看 Prisma model 静态清单；harness report.ts 把分区子表缺口计入\ndashboard HIGH；CLAUDE.md 新增两条棘轮断言并通过 baseline-reconcile 校验。\n\nCo-Authored-By: Claude Sonnet 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-01T03:38:15-07:00"}],"HeadCommit":{"Sha1":"04eb1a9023e244277b620d25d83ab7fe3e1e7c3e","Message":"fix: 修复采购拒收/提成备注/供应商表单/选址提交时间 4 处前后端契约断链\n\n- Rejections.tsx：前端类型/表单/列表全面对齐后端真实契约\n （reasonType/reasonDetail/handlingStatus/handlingResult，purchaseOrder/\n supplier/rejector 改嵌套对象）；POST /rejections、/rejections/:id/handle\n 补上此前完全缺失的 Zod 校验；listRejections 的 supplierId 筛选此前被\n 静默忽略，现通过 purchase_orders 关联真正实现；handlingStatus 命名对齐。\n- commission_records/commission_settlements：前端 remark 字段统一改为\n notes 对齐后端真实列；顺带把\"生成结算单\"备注功能真正打通\n （generateSettlementSchema 此前没有该字段，前端填了会被 Zod 直接丢弃）。\n- supplier_applications/supplier_contracts：移除一批被 Zod 校验通过却\n 从未写入数据库的死字段（city/province/companyProfile/bankAccountName/\n applyReason/subCategory/confidentialityClause/productScope/deliveryTerms/\n penaltyClause/territory）——这批列已在 schema 清理中被物理删除，\n 修复方向是去掉前后端\"填了也存不进去\"的死字段，而非把列加回来。\n- location_assessments.submitted_at：该列物理上一直存在（建表迁移即有），\n 只是 Prisma schema 未声明；补上字段声明后 submit() 真正写入该列，\n 前端已有的渲染逻辑无需改动即可生效，prisma migrate status 确认无 drift。\n\ntype-check 全绿（前端+后端），受影响 6 个模块 219 个单测通过（新增 7 个\n拒收记录测试锁定 supplierId 过滤、字段写入行为）。\n\nCo-Authored-By: Claude Sonnet 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-01T03:40:54-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/989e54a1f18193e7e19b620bf93c71c29508f2f9...04eb1a9023e244277b620d25d83ab7fe3e1e7c3e","Len":6}...
|
1782902472
|
Edit
Delete
|
|
15479
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"7942f4d38 {"Commits":[{"Sha1":"7942f4d3803ea963e31be6aef86cd52dbd564635","Message":"chore(react-migration): publish audit evidence and extraction bundles\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-02T00:54:32-07:00"}],"HeadCommit":{"Sha1":"7942f4d3803ea963e31be6aef86cd52dbd564635","Message":"chore(react-migration): publish audit evidence and extraction bundles\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-02T00:54:32-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/04eb1a9023e244277b620d25d83ab7fe3e1e7c3e...7942f4d3803ea963e31be6aef86cd52dbd564635","Len":1}...
|
1782978900
|
Edit
Delete
|
|
15969
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"da76fc5e9 {"Commits":[{"Sha1":"da76fc5e9fcbc3f937fa2bee7743931f9b60e4db","Message":"docs(governance): 沉淀契约断链深挖战役经验（两个 bug 家族 + live 复现纪律）\n\nbaseline-and-experience.md 置顶新增 2026-07-01~07-03 战役经验块：\n- 核心发现：静态审计停在 Zod 边界，语义断链全在 Zod 之后（casing 错位/\n 缺列/mapper 错映射/绕守卫/路由遮蔽），深挖口径为追「Zod→prisma 写入」\n 与「筛选参数→where」两条真实链的断点。\n- Bug 家族 1「controller 绕守卫走裸 batchAction」：11 模块命中、真断链 4、\n 三查判定法（updateStatus 覆写/update 覆写/batchAction 覆写）豁免 5。\n- Bug 家族 2「静态路由被参数化路由遮蔽」：16 文件 32 处死路由全收口，\n 防回潮探测器 audit:route-shadowing 已入仓。\n- live 复现铁律：子代理 5 个「最强候选」全是假阳性（死 controller/\n BaseService 自动筛选/crud fallback 静默丢弃），改前必正负两向真请求复现。\n- 修复分类法（六种证据形态→修法映射表）、状态词汇多源漂移多数决收敛法、\n 测试防剧场增补（mock FieldMapper 须应用真实映射表）、环境坑增补\n （rogue next 遮蔽 3000/Prisma client 重启/非交互迁移纪律）。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-03T02:46:55-07:00"},{"Sha1":"1329d688e027093bb5a1157466cef5cfdfa0513f","Message":"fix(routes): 全仓收口 32 处路由遮蔽死路由，新增 route-shadowing 审计防回潮\n\n承接 supply-chain 采购单批量路由被 /:id 吞掉的发现（fb706e38d6），写模拟\nExpress 顺序匹配的扫描器全仓核查：同一 routes 文件内，先注册的参数化路由\n（/:id...）会吞掉后注册的静态段路由（/batch、/export、/stats、/calendar、\n/today、/templates 等），使其永远不可达——调用方拿到的是详情 handler 的\nPRISMA_P2023/404（静态段被当 UUID 传给 findFirst）。\n\n实测 16 个文件 32 处真死路由（live 抽验 today/stats/calendar 均复现 P2023），\n覆盖：ad-campaigns 批量启停、campaign-targets/contract-templates/tickets/\npartner-customers/social-interactions 批量删除、knowledge-capture 批量审批+\n规则统计、lead-qualification 批量评分/认定、livestream-schedules 日历/今日、\nmarketing 归因 5 个报表端点、satisfaction 响应导出、social-posts 日历/批量\n发布、cash-flow 高风险付款行为、geo-keywords 导出、inventory 盘点行批量、\nsupply-chain 供应商批量删除。\n\n修复：全部静态路由前移到对应参数化路由之前（纯注册顺序移动，handler/权限/\nvalidate schema 一律未动），每处补中文注释说明顺序约束。\n\n防回潮：新增 scripts/audit-route-shadowing.ts（pnpm run audit:route-shadowing），\n模拟 Express 逐段匹配、已处理 :id(regex) 约束段（UUID 正则不吞 batch，剔除\n7 处假阳性）；任何新增遮蔽退出码 1，报告写 reports/route-shadowing-audit.latest.json。\n暂未注册 audit-registry（避免触发 reports-missing-zero，接入棘轮由治理口径决定）。\n\n验证：重扫 361 个 routes 文件 0 遮蔽；backend type-check 全绿；live 抽验 10\n端点全部复活（3 处 P2023→success、attribution 5 端点 200、2 个 export 200）；\nroute-registration 审计重复挂载 0。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-03T02:39:19-07:00"},{"Sha1":"fb706e38d6ba2c08bcea5e43c0da60db2b328e7c","Message":"fix(sn/supply-chain/content-templates): 全仓收口「controller 绕守卫走裸 batchAction」bug 家族\n\n承接 content-creation（ad0aff1667）后全仓扫描 batchAction('update_status')\n家族（11 模块命中），逐模块三查（updateStatus 覆写守卫 / update 覆写守卫 /\nbatchAction 覆写）+ live 复现判责，真断链 3 处全部修复：\n\n- serial-numbers（与 content-creation 完全同族）：activate/return/scrap/\n batch-activate 四个动作走裸 batchAction，绕过 assertTransition 守卫（红线 2），\n 且 activate 的 customerId/orderId/activatedAt 被丢弃（客户绑定/激活时间静默\n 丢失、无生命周期事件）；带守卫的 service.activate/restockReturned/\n scrapSerialNumber 全是死代码。现全部接回守卫实现。\n live：activate 带 customerId/activatedAt 真落库并读回；activated→return\n 被守卫 400 拦截。新增 4 个 controller 回归锁定测试（断言走守卫方法且\n batchAction 未被调用）。\n- supply-chain 采购单批量确认/取消：两层断链叠加——\n ① batch 路由注册在 /:id/confirm、/:id/cancel 之后，Express 把 \"batch\" 当\n :id，前端 POST /purchase-orders/batch/confirm|cancel 恒 400（批量确认/取消\n 一直是假功能）；已把三条 batch 路由前移到 /:id/* 之前。\n ② handler 走裸 batchAction 绕过 canTransitionPurchaseOrder；已改为逐单走\n confirmOrder/cancelOrder 守卫方法并汇总 successCount/failedIds。\n live 混合场景：created 单→confirmed 放行、cancelled 单保持原状进 failedIds。\n- content-templates 记录使用：POST /:id/use 走 batchAction(metadata:{lastUsedAt})\n ——metadata 被忽略、status 为 undefined，什么都不写，前端列表「使用次数」\n 恒 0（死指标）。现实现 service.recordUse（usage_count 自增 + 租户守卫）。\n live：连打两次 usageCount 0→2。顺手修齐既存测试漂移（getTemplateStats 断言\n inactive→archived，对齐 service 真实返回键）。\n\n已核实豁免（live/码面证据，防误改）：leads（update 覆写带 canTransitionLead，\n批量状态未绕守卫）、alliance-merchants/products（update 覆写带守卫）、\ncontent-library（batchAction 覆写已专门处理 metadata.categoryId → 真实\nbatchMoveCategory）、marketing-automation（paused 开关型无拓扑）。\n\nbackend type-check 全绿；serial-numbers/supply-chain/content-templates 测试\n93/93 通过；route-registration 审计重复挂载 0。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-03T02:02:40-07:00"},{"Sha1":"ad0aff1667f4426638d853309430b89468af8966","Message":"fix(content-creation): 视图驱动补全提交审核链路，接回被绕过的状态机守卫\n\n深挖发现该模块存在三层叠加断链：\n1. 红线 2 违反：controller 的 start/submit/complete/cancel/assign 全部绕过\n service 守卫方法，走裸 batchAction('update_status')——状态机从未拦截过任何\n 非法转换（live 实测 draft→pending_review 任意跳转全通）；submit 的 req.body\n 被塞进 batchAction 忽略的 metadata payload，content/outputUrls/note 全部丢弃；\n assign 连 status 都不传（等于什么都不干）。带守卫+流程启动的 service.submit\n 是零调用死代码（与 tickets 4d854c3a 同一 bug 家族）。\n2. 状态词汇三源漂移：machine/statuses.ts 用 pending/assigned/submitted/revision\n （纸面定义、库中从未有数据），运行态（DB 31 行、service 写链、前端\n CONTENTDRAFT_STATUS_MAP）用 draft/in_progress/pending_review/completed/\n cancelled；schema 的 CREATION_STATUS 还混有第三套 review/approved/active 死值\n （其注释宣称的\"控制器实写 review/approved\"经核对与代码不符）。\n3. 数据模型缺位：submitCreationSchema 接受的 content(max 100000)/outputUrls/note\n 无处持久化——content 无列、outputUrls 被 mapper 错映射到 UUID 列\n output_item_id（该列为 ai-assist context-provider 真实读取，不得占用）、\n note 无写链。\n\n修复（按红线 4 视图驱动：视图需求→字段提取→数据模型→迁移→全栈实现）：\n- 状态机收敛到运行态词汇（红线 0）：machine 拓扑/XState states/statuses.ts/\n schema 枚举统一为 draft→in_progress→pending_review→completed（+cancelled、\n 审核退回 pending_review→in_progress）；assign 只设 assigned_to 不再是独立状态。\n- 迁移 20260703030000：content_creations 补 content TEXT / output_urls JSONB\n default [] / submit_note VARCHAR(1000)；mapper 修正 outputUrls→output_urls、\n 新增 submitNote→submit_note，解除对 output_item_id 的错误占用。\n- service.submit 持久化三字段并流转 pending_review（勿用 BUSINESS_STATUS.\n PENDING_APPROVAL='pending_approval' 错词）；补 complete/cancel 守卫方法；\n controller 五个动作全部接回 service 守卫链。\n- 前端 Index：in_progress 行新增「提交审核」Modal（正文必填/成果链接多行 URL/\n 提交说明），完成按钮收窄到 pending_review 行、取消按钮排除 pending_review\n （旧条件在新守卫下会 400）。\n\n真实端到端验证（运行中后端 + 真实 DB）：\n- 修复前：submit 200 但 content/outputUrls/note 全丢（DB 直证 metadata={}）、\n draft 直接 submit 也 200（守卫失效）。\n- 修复后：draft→submit 正确 400（错误信息含合法目标）、pending_review→cancel\n 正确 400；start→submit 后 content/output_urls/submit_note API+DB 双证落库、\n output_item_id 未污染；complete 落 completedAt。\n\n测试：machine 测试重写 17/17；service 测试补 submit 持久化锁定（mock mapper\n改为应用真实映射表，锁 outputUrls→output_urls 配置本身）7/7；前端 RTL 补提交\n审核 Modal 用例并同步行按钮断言 2/2。前后端 type-check 全绿；sm-drift 审计\ndivergent/duplicate/topology 全 0、unresolved 9 未涨；enum/formrules/\nfield-payload/prisma-zod 审计全绿。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-03T01:36:49-07:00"},{"Sha1":"9ff572ee948d646916ba12fb3b3f084f2bd05a30","Message":"fix(crm-activities): 落地文档承诺的幂等能力，同 idempotencyKey 不再重复建活动\n\ncrm-activities create 的 Zod schema 接受 idempotencyKey、docs 明确宣称\n「支持幂等性（通过 idempotencyKey 字段）」，但此前无列无逻辑：字段经 crud\nfallback 静默丢弃（不 500，也不去重），相同 key 重复提交会产生多条活动记录——\n契约/文档与实现不符（假契约）。\n\n修复（落地承诺，补列+接线）：\n- 迁移 20260703020000：crm_activities 补 idempotency_key VARCHAR(100) +\n 租户内唯一索引 (tenant_id, idempotency_key)；Postgres 多 NULL 互异，\n 存量行不冲突；folder 真源 + schema.prisma 镜像同步。\n- service.create：命中既有 idempotency_key 直接返回既有活动（去重）；\n 并发下唯一约束触发 P2002 时兜底重取既有，避免竞态重复。\n\n真实端到端验证（运行中后端 + 真实 DB）：\n- 修复前同 key 两次得两条不同记录（去重失效复现）。\n- 修复后同 key 两次返回同一 id，DB 仅 1 行且 idempotency_key 落库。\n\n新增回归锁定单测：相同 idempotencyKey 命中既有则返回既有、断言 create 未被调用。\ncrm-activity.service.test.ts 9/9 通过；backend type-check 全绿；\nprisma-zod 契约审计 PASS。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-03T01:07:46-07:00"}],"HeadCommit":{"Sha1":"da76fc5e9fcbc3f937fa2bee7743931f9b60e4db","Message":"docs(governance): 沉淀契约断链深挖战役经验（两个 bug 家族 + live 复现纪律）\n\nbaseline-and-experience.md 置顶新增 2026-07-01~07-03 战役经验块：\n- 核心发现：静态审计停在 Zod 边界，语义断链全在 Zod 之后（casing 错位/\n 缺列/mapper 错映射/绕守卫/路由遮蔽），深挖口径为追「Zod→prisma 写入」\n 与「筛选参数→where」两条真实链的断点。\n- Bug 家族 1「controller 绕守卫走裸 batchAction」：11 模块命中、真断链 4、\n 三查判定法（updateStatus 覆写/update 覆写/batchAction 覆写）豁免 5。\n- Bug 家族 2「静态路由被参数化路由遮蔽」：16 文件 32 处死路由全收口，\n 防回潮探测器 audit:route-shadowing 已入仓。\n- live 复现铁律：子代理 5 个「最强候选」全是假阳性（死 controller/\n BaseService 自动筛选/crud fallback 静默丢弃），改前必正负两向真请求复现。\n- 修复分类法（六种证据形态→修法映射表）、状态词汇多源漂移多数决收敛法、\n 测试防剧场增补（mock FieldMapper 须应用真实映射表）、环境坑增补\n （rogue next 遮蔽 3000/Prisma client 重启/非交互迁移纪律）。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-03T02:46:55-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/7942f4d3803ea963e31be6aef86cd52dbd564635...da76fc5e9fcbc3f937fa2bee7743931f9b60e4db","Len":9}...
|
1783072038
|
Edit
Delete
|
|
15970
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"c4a1b8ebc {"Commits":[{"Sha1":"c4a1b8ebcc54d4a222aa030b845818ad365b950d","Message":"fix(sn/contracts): bind 接回守卫实现 + 六模块死字段契约清理批\n\n一、serial-numbers bind 接回 bindSerialNumber（bug 家族第 5 处收口）\n语义核实修正：bindSerialNumber 服务函数的 where 条件 status:'in_stock' 是\n乐观锁前置，data 实写 status:'shipped'——即「绑定即随单发货」，与 controller\n语义一致，非此前疑似的语义漂移，无需产品决策。差别是 controller 裸写版本\n缺订单/明细/客户存在性校验、缺 in_stock+未绑定乐观锁、缺 sn_bound 事件，\n且守卫实现是零调用死代码。修复：\n- controller.bind 接回 bindSerialNumber；路由挂 validate(bindSerialNumberSchema)\n （orderId/customerId 必填）。\n- 前端 api bind 签名对齐后端契约（orderId/customerId 必填 + orderItemId/\n shipmentId 可选），删除后端无写链的 contractId/assetId 死字段。\n- live 四向验证：缺 orderId→400、假订单→404 订单不存在、真绑定→200 且\n DB 直证 shipped+bound_order_id+bound_customer_id 落库、重复绑定→conflict\n 乐观锁拦截；验证后经 /return 恢复（顺带复验 restockReturned 清绑定生效）。\n- 新增 controller 回归锁定测试（断言走 bindSerialNumber 且裸 update 未被调）。\n\n二、契约清理批（六项，Zod 收下但永不落库/错位的死契约）\n① inventory 仓库：create/update schema 删 contactName/contactPhone/notes\n （warehouses 无列、mapper 显式忽略、前端不收集），mapper 忽略条目一并清。\n② opportunities：create body 删 phone/email/province/city/address/industry/\n contact_name/contact_phone 八个死字段（service 自动建客户只写 name、无\n customer_contacts 写链、前端走客户选择器不发送）；update 派生自动净化；\n IM intent-analyzer 调用点同步清 undefined 占位死参数。live：带 phone 创建\n 被 strict 400 拒绝（Unrecognized key）。\n③ opportunities list startDate/endDate 接线（此前被 allowedFilterFields\n 白名单静默忽略）：落创建时间区间。live：全量 317 → 未来起点 0/过去终点 0。\n④ targets update 删 milestones（sales_targets 无标量列、update 无子表写链，\n 透传会触发 Prisma Unknown argument；create 子表写链保留）；前端\n toUpdateWire/UpdateTargetRequest 同步删。\n⑤ rma：diagnose/complete 两处 Zod + docs 删 service 从不读取的 eventInsights；\n 前端 diagnose 签名对齐后端唯一持久化键 diagnosisResult（旧\n diagnosis/faultType/severity 与后端完全错位、会被静默剥离）。\n⑥ livestream createSchedule 删冗余必填死字段 scheduledStartAt/scheduledEndAt\n （service 只读 scheduledStart/scheduledEnd，旧契约强迫调用方双发同值且第二\n 份被丢）；前端读 DTO 类型同步对齐 scheduledStart/scheduledEnd（旧 *At 键\n DTO 从不返回，恒 undefined）。live：不带 *At 创建过 Zod 进入业务校验。\n\n验证：前后端 type-check 全绿；opportunities/targets/rma/livestream/inventory/\nserial-numbers 测试 192/192 通过；formrules-zod errors 0、field-payload 0/0、\nenum-consistency 无新增。\n\nBacklog 登记：rma complete 前端发送 resolution/refundAmount/returnShipping*\n与后端 completeRmaSchema(returnedItem) 错位（Detail 仅发硬编码文案，无用户\n数据损失），待定接线或清理方向。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-03T03:06:13-07:00"}],"HeadCommit":{"Sha1":"c4a1b8ebcc54d4a222aa030b845818ad365b950d","Message":"fix(sn/contracts): bind 接回守卫实现 + 六模块死字段契约清理批\n\n一、serial-numbers bind 接回 bindSerialNumber（bug 家族第 5 处收口）\n语义核实修正：bindSerialNumber 服务函数的 where 条件 status:'in_stock' 是\n乐观锁前置，data 实写 status:'shipped'——即「绑定即随单发货」，与 controller\n语义一致，非此前疑似的语义漂移，无需产品决策。差别是 controller 裸写版本\n缺订单/明细/客户存在性校验、缺 in_stock+未绑定乐观锁、缺 sn_bound 事件，\n且守卫实现是零调用死代码。修复：\n- controller.bind 接回 bindSerialNumber；路由挂 validate(bindSerialNumberSchema)\n （orderId/customerId 必填）。\n- 前端 api bind 签名对齐后端契约（orderId/customerId 必填 + orderItemId/\n shipmentId 可选），删除后端无写链的 contractId/assetId 死字段。\n- live 四向验证：缺 orderId→400、假订单→404 订单不存在、真绑定→200 且\n DB 直证 shipped+bound_order_id+bound_customer_id 落库、重复绑定→conflict\n 乐观锁拦截；验证后经 /return 恢复（顺带复验 restockReturned 清绑定生效）。\n- 新增 controller 回归锁定测试（断言走 bindSerialNumber 且裸 update 未被调）。\n\n二、契约清理批（六项，Zod 收下但永不落库/错位的死契约）\n① inventory 仓库：create/update schema 删 contactName/contactPhone/notes\n （warehouses 无列、mapper 显式忽略、前端不收集），mapper 忽略条目一并清。\n② opportunities：create body 删 phone/email/province/city/address/industry/\n contact_name/contact_phone 八个死字段（service 自动建客户只写 name、无\n customer_contacts 写链、前端走客户选择器不发送）；update 派生自动净化；\n IM intent-analyzer 调用点同步清 undefined 占位死参数。live：带 phone 创建\n 被 strict 400 拒绝（Unrecognized key）。\n③ opportunities list startDate/endDate 接线（此前被 allowedFilterFields\n 白名单静默忽略）：落创建时间区间。live：全量 317 → 未来起点 0/过去终点 0。\n④ targets update 删 milestones（sales_targets 无标量列、update 无子表写链，\n 透传会触发 Prisma Unknown argument；create 子表写链保留）；前端\n toUpdateWire/UpdateTargetRequest 同步删。\n⑤ rma：diagnose/complete 两处 Zod + docs 删 service 从不读取的 eventInsights；\n 前端 diagnose 签名对齐后端唯一持久化键 diagnosisResult（旧\n diagnosis/faultType/severity 与后端完全错位、会被静默剥离）。\n⑥ livestream createSchedule 删冗余必填死字段 scheduledStartAt/scheduledEndAt\n （service 只读 scheduledStart/scheduledEnd，旧契约强迫调用方双发同值且第二\n 份被丢）；前端读 DTO 类型同步对齐 scheduledStart/scheduledEnd（旧 *At 键\n DTO 从不返回，恒 undefined）。live：不带 *At 创建过 Zod 进入业务校验。\n\n验证：前后端 type-check 全绿；opportunities/targets/rma/livestream/inventory/\nserial-numbers 测试 192/192 通过；formrules-zod errors 0、field-payload 0/0、\nenum-consistency 无新增。\n\nBacklog 登记：rma complete 前端发送 resolution/refundAmount/returnShipping*\n与后端 completeRmaSchema(returnedItem) 错位（Detail 仅发硬编码文案，无用户\n数据损失），待定接线或清理方向。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-03T03:06:13-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/da76fc5e9fcbc3f937fa2bee7743931f9b60e4db...c4a1b8ebcc54d4a222aa030b845818ad365b950d","Len":1}...
|
1783073192
|
Edit
Delete
|
|
15971
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"06c1676e4 {"Commits":[{"Sha1":"06c1676e4e8d18d0a3797df1323ed4d768d3bee8","Message":"fix(rma): complete 契约错位收口——resolution 真落库、completed_at 从死写复活\n\n前端 rmaApi.complete 发送 resolution/refundAmount/returnShippingNo/\nreturnShippingCarrier 四字段，而后端 completeRmaSchema 只收 returnedItem——\n全部被 Zod 静默剥离；且 completeRma 的 updateMany 从不写 completed_at，\n详情 timeline 依赖 completed_at 生成的「完成」节点永不出现（死节点）。\n\n修复（接线 + 契约收敛双向）：\n- 后端：completeRmaSchema 补 resolution（max 2000，可选）；completeRma 写入\n completed_at + 将 resolution 并入 logistics_json（与 diagnose 的 diagnosis\n 键同构，保留既有 JSON 键）；controller 透传。\n- 前端 api：complete 签名收敛为 { resolution, returnedItem? }——删除后端无\n 写链的 refundAmount/returnShippingNo/returnShippingCarrier 死字段（退款\n 金额属财务域真源，不在 RMA JSON 记第二份）。\n- 前端 Detail（视图驱动闭环）：完成确认框升级为受控 Modal 真收集处理结论\n （默认「已完成处理」，与既有拒绝原因 Modal 同构）；Descriptions 新增\n 「诊断结论」「处理结论」两行读 logisticsJson.diagnosis/resolution，\n 写入的信息在详情页真正查得回。\n\n真实端到端验证（运行中后端 + 真实 DB）：\n- created→receive→process→complete 带 resolution：status=completed、\n completedAt 落库（timeline 完成节点复活）、logisticsJson.resolution\n API 读回与 DB 直证一致。\n- 顺带补验上一提交的 diagnose 对齐链：receive→diagnose 带 diagnosisResult，\n DB 直证 logistics_json.diagnosis 落库。\n\n新增回归锁定单测：断言 updateMany 写 completed_at + logistics_json 合并\nresolution 且保留既有 diagnosis 键。rma.service.test.ts 34/34 通过；\n前后端 type-check 全绿。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-03T03:16:05-07:00"}],"HeadCommit":{"Sha1":"06c1676e4e8d18d0a3797df1323ed4d768d3bee8","Message":"fix(rma): complete 契约错位收口——resolution 真落库、completed_at 从死写复活\n\n前端 rmaApi.complete 发送 resolution/refundAmount/returnShippingNo/\nreturnShippingCarrier 四字段，而后端 completeRmaSchema 只收 returnedItem——\n全部被 Zod 静默剥离；且 completeRma 的 updateMany 从不写 completed_at，\n详情 timeline 依赖 completed_at 生成的「完成」节点永不出现（死节点）。\n\n修复（接线 + 契约收敛双向）：\n- 后端：completeRmaSchema 补 resolution（max 2000，可选）；completeRma 写入\n completed_at + 将 resolution 并入 logistics_json（与 diagnose 的 diagnosis\n 键同构，保留既有 JSON 键）；controller 透传。\n- 前端 api：complete 签名收敛为 { resolution, returnedItem? }——删除后端无\n 写链的 refundAmount/returnShippingNo/returnShippingCarrier 死字段（退款\n 金额属财务域真源，不在 RMA JSON 记第二份）。\n- 前端 Detail（视图驱动闭环）：完成确认框升级为受控 Modal 真收集处理结论\n （默认「已完成处理」，与既有拒绝原因 Modal 同构）；Descriptions 新增\n 「诊断结论」「处理结论」两行读 logisticsJson.diagnosis/resolution，\n 写入的信息在详情页真正查得回。\n\n真实端到端验证（运行中后端 + 真实 DB）：\n- created→receive→process→complete 带 resolution：status=completed、\n completedAt 落库（timeline 完成节点复活）、logisticsJson.resolution\n API 读回与 DB 直证一致。\n- 顺带补验上一提交的 diagnose 对齐链：receive→diagnose 带 diagnosisResult，\n DB 直证 logistics_json.diagnosis 落库。\n\n新增回归锁定单测：断言 updateMany 写 completed_at + logistics_json 合并\nresolution 且保留既有 diagnosis 键。rma.service.test.ts 34/34 通过；\n前后端 type-check 全绿。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-03T03:16:05-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/c4a1b8ebcc54d4a222aa030b845818ad365b950d...06c1676e4e8d18d0a3797df1323ed4d768d3bee8","Len":1}...
|
1783073771
|
Edit
Delete
|
|
15972
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"7212bb0f7 {"Commits":[{"Sha1":"7212bb0f7d8f202759b9ddb0e2204b3745825847","Message":"chore(harness): route-shadowing 审计接入 audit-registry（红线 9 注册即执行）\n\n将 scripts/audit-route-shadowing.ts 正式注册进 AUDIT_REGISTRY（第 72 项）：\n- trigger: backend/src/modules/**/*.routes.ts 变更时选跑（gate: smart）\n- reportFile: reports/route-shadowing-audit.latest.json（已在仓、当前 shadowed=0）\n- 硬阻塞语义在审计脚本自身（新增遮蔽退出码 1）；harness 侧经 report.ts 的\n adaptGeneric fallback 消化 findings（无 severity 默认 INFO，不污染\n dashboard high/medium），符合「脚本硬门禁 + dashboard INFO 记录」棘轮口径。\n\n接入验证：registry 解析 OK（72 项）、report.ts:3450 按 reportFile 文件名\n自动路由 adaptGeneric 成立、报告新鲜且 0 遮蔽。至此「静态路由被参数化路由\n遮蔽」bug 家族（1329d688e0 收口的 32 处死路由）具备防回潮机器门禁。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-03T03:20:52-07:00"}],"HeadCommit":{"Sha1":"7212bb0f7d8f202759b9ddb0e2204b3745825847","Message":"chore(harness): route-shadowing 审计接入 audit-registry（红线 9 注册即执行）\n\n将 scripts/audit-route-shadowing.ts 正式注册进 AUDIT_REGISTRY（第 72 项）：\n- trigger: backend/src/modules/**/*.routes.ts 变更时选跑（gate: smart）\n- reportFile: reports/route-shadowing-audit.latest.json（已在仓、当前 shadowed=0）\n- 硬阻塞语义在审计脚本自身（新增遮蔽退出码 1）；harness 侧经 report.ts 的\n adaptGeneric fallback 消化 findings（无 severity 默认 INFO，不污染\n dashboard high/medium），符合「脚本硬门禁 + dashboard INFO 记录」棘轮口径。\n\n接入验证：registry 解析 OK（72 项）、report.ts:3450 按 reportFile 文件名\n自动路由 adaptGeneric 成立、报告新鲜且 0 遮蔽。至此「静态路由被参数化路由\n遮蔽」bug 家族（1329d688e0 收口的 32 处死路由）具备防回潮机器门禁。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-03T03:20:52-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/06c1676e4e8d18d0a3797df1323ed4d768d3bee8...7212bb0f7d8f202759b9ddb0e2204b3745825847","Len":1}...
|
1783074059
|
Edit
Delete
|
|
15973
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"04d57d74d {"Commits":[{"Sha1":"04d57d74d0373aea967c831c21a1c4526095da1d","Message":"chore(governance): route-shadowing 接入棘轮门禁全链（受控块断言 + harness:check + 对账）\n\n承接 registry 注册（7212bb0f7d），完成红线 9「注册即执行」的剩余三件套：\n- CLAUDE.md GOVERNANCE-BASELINE 受控块新增断言\n route-shadowing-zero | route-shadowing-audit.latest.json | summary.shadowedRoutes | == | 0\n （零阈值：32 处死路由已全收口，任何回潮立即 drift 阻塞）\n- package.json harness:check 链尾接入 audit-route-shadowing 实跑\n- 重跑 baseline-reconcile + harness dashboard：新断言实测 0==0 ✓；\n dashboard critical 0 / high 0 / medium 11（\u003c= 51 ceiling）、\n reports missing/stale/invalid 全 0。\n\n对账说明：reconcile 仅存的 2 条 VALUE_DRIFT 为既有真实红线\n（production-release-gate/actions 两条 *-overdue-zero 实测 10——10 条 P0\n上线阻断 dueDate 过期，受控块注释明确故意保持 ==0 不得凑绿，须真实完成\n或指挥官重排 due date 清除），与本次接入无关、未触碰。\n\n至此「静态路由被参数化路由遮蔽」bug 家族防回潮闭环：\n审计脚本（退出码 1 硬阻塞）→ registry 选跑触发 → harness:check 全量链 →\n受控块零阈值对账，四层锁死。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-03T03:22:21-07:00"}],"HeadCommit":{"Sha1":"04d57d74d0373aea967c831c21a1c4526095da1d","Message":"chore(governance): route-shadowing 接入棘轮门禁全链（受控块断言 + harness:check + 对账）\n\n承接 registry 注册（7212bb0f7d），完成红线 9「注册即执行」的剩余三件套：\n- CLAUDE.md GOVERNANCE-BASELINE 受控块新增断言\n route-shadowing-zero | route-shadowing-audit.latest.json | summary.shadowedRoutes | == | 0\n （零阈值：32 处死路由已全收口，任何回潮立即 drift 阻塞）\n- package.json harness:check 链尾接入 audit-route-shadowing 实跑\n- 重跑 baseline-reconcile + harness dashboard：新断言实测 0==0 ✓；\n dashboard critical 0 / high 0 / medium 11（\u003c= 51 ceiling）、\n reports missing/stale/invalid 全 0。\n\n对账说明：reconcile 仅存的 2 条 VALUE_DRIFT 为既有真实红线\n（production-release-gate/actions 两条 *-overdue-zero 实测 10——10 条 P0\n上线阻断 dueDate 过期，受控块注释明确故意保持 ==0 不得凑绿，须真实完成\n或指挥官重排 due date 清除），与本次接入无关、未触碰。\n\n至此「静态路由被参数化路由遮蔽」bug 家族防回潮闭环：\n审计脚本（退出码 1 硬阻塞）→ registry 选跑触发 → harness:check 全量链 →\n受控块零阈值对账，四层锁死。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-03T03:22:21-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/7212bb0f7d8f202759b9ddb0e2204b3745825847...04d57d74d0373aea967c831c21a1c4526095da1d","Len":1}...
|
1783074148
|
Edit
Delete
|
|
16977
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"78a500f04 {"Commits":[{"Sha1":"78a500f04042e394b04075c3823e4431ed58b463","Message":"fix(governance): 2026-07-09 契约治理四轮收口——query 布尔 coerce 清零、snake 死键修复、假筛选裁定与断链深挖\n\n- query 布尔参数 coerce 全仓收口：218 处/76 文件归零，新增 scripts/audit-query-boolean.ts 棘轮审计并接入 registry（query-boolean-violations-zero == 0）\n- query snake 死键收口：39 处真死键修复（9 模块），豁免/双读/preprocess 三类假死判据落盘\n- 假筛选群收口：12 键三分法裁定，filter-truth UNSUPPORTED 22→10，后端补消费按 schema+controller 白名单+service where 三点齐\n- 契约断链二轮深挖：renewals 非互逆映射、duplicate 丢名、partner-customers 键名不对称等 10 组用户可见断链修复\n- 新增迁移：rma_type_reason_columns、ad_audiences_add_data_source\n- 全域视图审计矩阵报告（a1~a9 九域）、契约断链/深对齐审计报告、代码导出 PDF\n- 同步 reports/*.latest.json 基线与 CLAUDE.md GOVERNANCE-BASELINE 受控块\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-09T19:18:14-07:00"},{"Sha1":"e6db8812d3c3c7a2c0bdae632c2f1b3f2e9b4fe8","Message":"test(campaigns): 对齐 goals_json 合并读后的 findFirst 调用链，修复 10 个存量假红用例\n\ncommit 4a6c61fc35 将 CampaignService.update 的 goals_json 合并分支触发条件\n扩到 goalsJson/storeScopeMode/storeIds 后，complete/attribute/schedule/selectTools\n路径的 update 多出一次 findFirst({ select: goals_json })合并读（4 次→5 次）。\n测试 mock 队列未同步：\n- marketing.service.test.ts completeCampaign 用例第 5 次调用兜底到前序用例\n 遗留的持久 mockResolvedValue（status=draft），报 expected 'draft' to be 'completed'\n- campaign.service.enhanced.test.ts 使用 mockReset，队列耗尽返回 undefined→404，\n 9 个状态机生命周期用例失败\n\n按 assertion-theater-guard 口径裁定：实现无 bug（合并语义为有意行为且带\ntenant_id），仅在各 mock 队列第 2 位插入合并读返回值并更新链路注释，\n未改动/弱化任何断言。marketing 23/23、campaigns 59/59 全绿。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-09T18:51:30-07:00"},{"Sha1":"9023c1468b7cbd83719f42c6a5521a42813848e7","Message":"fix(governance): tighten service contracts and route validation\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-06T22:32:22-07:00"},{"Sha1":"1f15101e932088234cf16f0606e6dc9227f018e3","Message":"Tighten alliance API tests and order action fallback\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-04T01:04:30-07:00"},{"Sha1":"c892b8637c2fdb10b1246caa149a7e353c442aa6","Message":"Refine governance and frontend workflows\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-04T00:59:39-07:00"}],"HeadCommit":{"Sha1":"78a500f04042e394b04075c3823e4431ed58b463","Message":"fix(governance): 2026-07-09 契约治理四轮收口——query 布尔 coerce 清零、snake 死键修复、假筛选裁定与断链深挖\n\n- query 布尔参数 coerce 全仓收口：218 处/76 文件归零，新增 scripts/audit-query-boolean.ts 棘轮审计并接入 registry（query-boolean-violations-zero == 0）\n- query snake 死键收口：39 处真死键修复（9 模块），豁免/双读/preprocess 三类假死判据落盘\n- 假筛选群收口：12 键三分法裁定，filter-truth UNSUPPORTED 22→10，后端补消费按 schema+controller 白名单+service where 三点齐\n- 契约断链二轮深挖：renewals 非互逆映射、duplicate 丢名、partner-customers 键名不对称等 10 组用户可见断链修复\n- 新增迁移：rma_type_reason_columns、ad_audiences_add_data_source\n- 全域视图审计矩阵报告（a1~a9 九域）、契约断链/深对齐审计报告、代码导出 PDF\n- 同步 reports/*.latest.json 基线与 CLAUDE.md GOVERNANCE-BASELINE 受控块\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-09T19:18:14-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/04d57d74d0373aea967c831c21a1c4526095da1d...78a500f04042e394b04075c3823e4431ed58b463","Len":20}...
|
1783653434
|
Edit
Delete
|
|
17042
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"101858c06 {"Commits":[{"Sha1":"101858c06a69a0ecf99c3366f5034de2786d0495","Message":"Fix RMA contract drift and tighten cleanup/runtime governance\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-09T23:29:51-07:00"},{"Sha1":"495ebd9d6db6af72c778e70ffe22cf9c6b467ff9","Message":"fix(governance): 收口跨域运行真源与验收门禁\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-09T23:04:48-07:00"}],"HeadCommit":{"Sha1":"101858c06a69a0ecf99c3366f5034de2786d0495","Message":"Fix RMA contract drift and tighten cleanup/runtime governance\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-09T23:29:51-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/78a500f04042e394b04075c3823e4431ed58b463...101858c06a69a0ecf99c3366f5034de2786d0495","Len":2}...
|
1783665486
|
Edit
Delete
|
|
17081
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"9646e9036 {"Commits":[{"Sha1":"9646e903603f789cc51ec4b32200b70b3ccf2cff","Message":"docs(api): 重新生成 OpenAPI 契约与全量 API 参考（React 单前端真源口径）\n\n- openapi.json / openapi.yaml 按当前 Zod-First 真源全量重生成\n- 新增 all-api-reference.md 与 generate-api-reference.mjs 生成入口\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-10T01:32:29-07:00"},{"Sha1":"7b8988454f47c83a3fd319e7dc8f9a7cfeb5d649","Message":"fix(architecture): 后端架构边界治理——跨模块调用收口公开入口 + 依赖图基线门禁\n\n- commissions/revenue/treasury/assets/channel-analytics 等跨域直接依赖改走目标模块 index.* 公开入口\n- 新增 backend-module-dependencies 依赖图审计基线（存量 INFO 冻结，基线外新增硬阻断）与测试\n- 补 event-outbox-helper / password 单元测试；vitest workspace/coverage 配置对齐\n- 附 2026-07-09 菜单 292 能力真源分析报告与三份架构治理作战卡\n- 验收：pnpm -C backend run type-check 通过\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-10T01:32:19-07:00"},{"Sha1":"20c082f55e0c4be2105dedce9069420e2750d3fa","Message":"chore(frontend): Vue 前端物理退役——frontend/ 与 mobile/ 全面删除，React 单一真源收口\n\n- 物理删除 frontend/（1876 文件）与 mobile/（197 文件）Vue/Vant 工程，历史仅由 Git 追溯\n- pnpm workspace、启动链、CI、Harness、E2E view-governance、审计扫描根全部切换到 frontend-react/\n- 删除 Vue-only 治理脚本 13 个与旧 view-governance 快照/生成器/验证器\n- dev docker-compose frontend 服务切换为根 context + frontend-react/Dockerfile（对齐 prod），映射 5173:80\n- 新增 React 生产镜像链：frontend-react/Dockerfile、Dockerfile.prebuilt、nginx.conf、.env.example\n- check-env.sh / start-dev.sh / quick-start.sh 与 DOCKER.md / START-HERE.md / 部署与启动指南死命令收口为 frontend-react\n- 删除 Vue 时代死脚本 run_tsc.sh / generate_smoke_tests.py / debug-blank-page.html\n- CLAUDE.md / AGENTS.md / README.md / GEMINI.md / QWEN.md 同步单一前端真源口径\n- 验收：pnpm -C frontend-react run type-check 通过、docker compose config 通过、主树 .vue=0、运行链残留扫描=0\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-10T01:30:05-07:00"}],"HeadCommit":{"Sha1":"9646e903603f789cc51ec4b32200b70b3ccf2cff","Message":"docs(api): 重新生成 OpenAPI 契约与全量 API 参考（React 单前端真源口径）\n\n- openapi.json / openapi.yaml 按当前 Zod-First 真源全量重生成\n- 新增 all-api-reference.md 与 generate-api-reference.mjs 生成入口\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-10T01:32:29-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/101858c06a69a0ecf99c3366f5034de2786d0495...9646e903603f789cc51ec4b32200b70b3ccf2cff","Len":3}...
|
1783672582
|
Edit
Delete
|
|
17085
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"c39315b6c {"Commits":[{"Sha1":"c39315b6c9e556d9dfa9fa55cc933d6b5d74d2a6","Message":"fix(governance): 治理数字对账收口——MEDIUM 清零 + stale 报告刷新 + release-gate 滞后阻断消除\n\n- users 重置密码前端规则对齐后端 Zod：min 6→8，补大小写字母+数字 pattern（真实契约 bug，7 RTL 用例通过）\n- frontend-source-adapter 新增视图子树→真实模块重映射：ai-agents/skill-library 归 ai-agent-skills\n （表单实走 ai-agent-skills API，description max 4000 与 Zod 一致，消除目录名误配假告警）\n- 重跑 10 个超期 stale 审计（ai-assist 系列/migration-safety/time-analysis/workflow/process-definition 等）\n- census e2e.specFiles 基线重冻 294→338（随治理波次提交的真实增长）\n- 重跑 production-release-gate/actions：滞后的 harness-high-zero 阻断消除，11→10 条真实 P0 阻断\n- 终态：dashboard C=0/H=0/M=0、stale=0、formrules WARNING=0；\n baseline-reconcile 242 条断言 drift 10→2，剩余 2 条为受控块明文保留的 overdue 真实红线\n （10 条 P0 上线阻断逾期，只能真完成或指挥官重排 due date，不得改绿）\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-10T02:05:45-07:00"}],"HeadCommit":{"Sha1":"c39315b6c9e556d9dfa9fa55cc933d6b5d74d2a6","Message":"fix(governance): 治理数字对账收口——MEDIUM 清零 + stale 报告刷新 + release-gate 滞后阻断消除\n\n- users 重置密码前端规则对齐后端 Zod：min 6→8，补大小写字母+数字 pattern（真实契约 bug，7 RTL 用例通过）\n- frontend-source-adapter 新增视图子树→真实模块重映射：ai-agents/skill-library 归 ai-agent-skills\n （表单实走 ai-agent-skills API，description max 4000 与 Zod 一致，消除目录名误配假告警）\n- 重跑 10 个超期 stale 审计（ai-assist 系列/migration-safety/time-analysis/workflow/process-definition 等）\n- census e2e.specFiles 基线重冻 294→338（随治理波次提交的真实增长）\n- 重跑 production-release-gate/actions：滞后的 harness-high-zero 阻断消除，11→10 条真实 P0 阻断\n- 终态：dashboard C=0/H=0/M=0、stale=0、formrules WARNING=0；\n baseline-reconcile 242 条断言 drift 10→2，剩余 2 条为受控块明文保留的 overdue 真实红线\n （10 条 P0 上线阻断逾期，只能真完成或指挥官重排 due date，不得改绿）\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-10T02:05:45-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/9646e903603f789cc51ec4b32200b70b3ccf2cff...c39315b6c9e556d9dfa9fa55cc933d6b5d74d2a6","Len":1}...
|
1783674369
|
Edit
Delete
|
|
17104
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"cff2a7743 {"Commits":[{"Sha1":"cff2a7743a4472a541e5b285f5ce5e079be71d07","Message":"fix(governance): 菜单审计假阴性修复 + 14 条孤儿路由收口\n\n「内容与社媒工作台/视频内容/视频发布/视频数据/供应链工作台/系统导入/\n后台中心 无对应 API 或壳入口」经端点级 FE↔BE diff 逐条核查为污染前提，\n根因是 audit-menu-inventory 三处旧判定：\n\n- hasView 按同名 views/ 目录判 → 改为路由真源解析（lazyView import 的\n 视图文件存在性），同名目录仅兜底；\n- hasApi 按同名 api/modules/\u003cpath\u003e.ts 判 → 改为视图文件真实 @/api import\n 判定（共享 owner 映射，含目录 Index 薄壳一层转发），同名文件仅兜底；\n- 孤儿检测解析 Vue 时代 meta: 块（React 树全用 handle:，orphanRoutes=0\n 假绿）→ 改为 handle: 块窗口解析 + menu.ts 全部 path 字面量保守对比。\n\n修后揭示的 14 条真孤儿路由同轮收口：\n- /marketing-workflows 为指向 /marketing-automation 的兼容重定向壳，\n 补 hideInMenu: true；\n- 其余 13 条（store-agency / customer-balance / payment-analytics /\n disbursements / finance-periods / finance-os 支出与风险 3 项 /\n fulfillment 5 项）按路由 handle 声明的中心与分组补录进 menu.ts。\n\n证据与终态：menu-inventory 291→304 项全绿率 100%、孤儿 14→0；\nview-governance menuVisibleCount 293→306 基线同步，audit:view-governance\n复跑全绿；frontend-react tsc --noEmit 零错误，Sidebar/guards 测试 8 用例全绿。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-11T20:48:16-07:00"}],"HeadCommit":{"Sha1":"cff2a7743a4472a541e5b285f5ce5e079be71d07","Message":"fix(governance): 菜单审计假阴性修复 + 14 条孤儿路由收口\n\n「内容与社媒工作台/视频内容/视频发布/视频数据/供应链工作台/系统导入/\n后台中心 无对应 API 或壳入口」经端点级 FE↔BE diff 逐条核查为污染前提，\n根因是 audit-menu-inventory 三处旧判定：\n\n- hasView 按同名 views/ 目录判 → 改为路由真源解析（lazyView import 的\n 视图文件存在性），同名目录仅兜底；\n- hasApi 按同名 api/modules/\u003cpath\u003e.ts 判 → 改为视图文件真实 @/api import\n 判定（共享 owner 映射，含目录 Index 薄壳一层转发），同名文件仅兜底；\n- 孤儿检测解析 Vue 时代 meta: 块（React 树全用 handle:，orphanRoutes=0\n 假绿）→ 改为 handle: 块窗口解析 + menu.ts 全部 path 字面量保守对比。\n\n修后揭示的 14 条真孤儿路由同轮收口：\n- /marketing-workflows 为指向 /marketing-automation 的兼容重定向壳，\n 补 hideInMenu: true；\n- 其余 13 条（store-agency / customer-balance / payment-analytics /\n disbursements / finance-periods / finance-os 支出与风险 3 项 /\n fulfillment 5 项）按路由 handle 声明的中心与分组补录进 menu.ts。\n\n证据与终态：menu-inventory 291→304 项全绿率 100%、孤儿 14→0；\nview-governance menuVisibleCount 293→306 基线同步，audit:view-governance\n复跑全绿；frontend-react tsc --noEmit 零错误，Sidebar/guards 测试 8 用例全绿。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-11T20:48:16-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/c39315b6c9e556d9dfa9fa55cc933d6b5d74d2a6...cff2a7743a4472a541e5b285f5ce5e079be71d07","Len":1}...
|
1783828105
|
Edit
Delete
|
|
17105
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"3d0a44a9c {"Commits":[{"Sha1":"3d0a44a9c8d654139f4027f66c65b83a9ab64f0f","Message":"fix(field-contract): 契约断链深挖收口——12 真缺陷修复 + filter-truth/prisma-zod 审计治理归真\n\n深挖 filter-truth/update三态/list-detail/response未消费四探针 2100+ 候选，逐条 live 代码追踪对抗验证，\n修复真实缺陷并把两个喂 HARD gate 的审计从「stale/坏工具掩盖」拉回真实。\n\n假筛选/数据丢失（8）:\n- groupbuy-reviews: replyStatus(reply列)/sentiment(rating派生) 接线\n- hr payroll: periodCode 接线 + grades search→canonical keyword(删死型 GradeListParams.search)\n- groupbuy-platforms: authStatus 走 extraWhere 接线(列实在·原被白名单排除)\n- ad-placement placement.service.ts:441 end_date `?? null`→`undefined`(与 running 分支对齐,消非对称清空)\n- livestream-schedule coverUrl/coverImage/cover_image `.max(2000)`→`.max(500)`(收敛 cover_url VarChar(500))\n\nowner 决策项（3）:\n- groupbuy-reviews.source: 增 source 列(migration 20260711235453,default 'manual')+全栈接线,formatReview 桩 'meituan'→真列\n- customers check-duplicate: 增 contact_name 查重维度(真源 customer_contacts.name,纯 service 层)\n- social-analytics.industry: 增 social_accounts.industry 列(migration 20260712000950)+getIndustryBenchmark 真实聚合\n (按 tenant+platform+industry 筛账号→单查询聚合 social_analytics 最新快照,无数据 dataAvailable=false,不再伪 'average')\n\n审计工具治理:\n- audit-filter-truth.ts: 修复因 Vue 物理退役(frontend/ 删除)导致的 typescript 解析 anchor 失效,审计复活\n- audit-prisma-zod-contract.ts: 为 6 个静态盲区 FP(superRefine/service-fill/bizCode)加受控豁免+核验理由,归真 PASS\n- filter-truth UNSUPPORTED 18→10 三轮重冻,GOVERNANCE-BASELINE ceiling 同步下调\n\n验证: 双端 type-check 绿;backend 8783 tests(+8 负断言);前端 social-accounts RTL 4/4;\nn1=0;prisma-zod PASS;schema 镜像一致;reconcile 零新增 drift(仅剩 2 个 pre-existing overdue 意图红线)。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-12T00:27:30-07:00"}],"HeadCommit":{"Sha1":"3d0a44a9c8d654139f4027f66c65b83a9ab64f0f","Message":"fix(field-contract): 契约断链深挖收口——12 真缺陷修复 + filter-truth/prisma-zod 审计治理归真\n\n深挖 filter-truth/update三态/list-detail/response未消费四探针 2100+ 候选，逐条 live 代码追踪对抗验证，\n修复真实缺陷并把两个喂 HARD gate 的审计从「stale/坏工具掩盖」拉回真实。\n\n假筛选/数据丢失（8）:\n- groupbuy-reviews: replyStatus(reply列)/sentiment(rating派生) 接线\n- hr payroll: periodCode 接线 + grades search→canonical keyword(删死型 GradeListParams.search)\n- groupbuy-platforms: authStatus 走 extraWhere 接线(列实在·原被白名单排除)\n- ad-placement placement.service.ts:441 end_date `?? null`→`undefined`(与 running 分支对齐,消非对称清空)\n- livestream-schedule coverUrl/coverImage/cover_image `.max(2000)`→`.max(500)`(收敛 cover_url VarChar(500))\n\nowner 决策项（3）:\n- groupbuy-reviews.source: 增 source 列(migration 20260711235453,default 'manual')+全栈接线,formatReview 桩 'meituan'→真列\n- customers check-duplicate: 增 contact_name 查重维度(真源 customer_contacts.name,纯 service 层)\n- social-analytics.industry: 增 social_accounts.industry 列(migration 20260712000950)+getIndustryBenchmark 真实聚合\n (按 tenant+platform+industry 筛账号→单查询聚合 social_analytics 最新快照,无数据 dataAvailable=false,不再伪 'average')\n\n审计工具治理:\n- audit-filter-truth.ts: 修复因 Vue 物理退役(frontend/ 删除)导致的 typescript 解析 anchor 失效,审计复活\n- audit-prisma-zod-contract.ts: 为 6 个静态盲区 FP(superRefine/service-fill/bizCode)加受控豁免+核验理由,归真 PASS\n- filter-truth UNSUPPORTED 18→10 三轮重冻,GOVERNANCE-BASELINE ceiling 同步下调\n\n验证: 双端 type-check 绿;backend 8783 tests(+8 负断言);前端 social-accounts RTL 4/4;\nn1=0;prisma-zod PASS;schema 镜像一致;reconcile 零新增 drift(仅剩 2 个 pre-existing overdue 意图红线)。\n\nCo-Authored-By: Claude Opus 4.8 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-12T00:27:30-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/cff2a7743a4472a541e5b285f5ce5e079be71d07...3d0a44a9c8d654139f4027f66c65b83a9ab64f0f","Len":1}...
|
1783841295
|
Edit
Delete
|
|
17106
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"b6ca4eb97 {"Commits":[{"Sha1":"b6ca4eb97fca5dff7fe33490df662865134b08d2","Message":"fix(field-contract): 断链深挖三批收口——attribution 读模型重塑 + customers 查重富化 + cash-flow 对齐文档真源 + 筛选键 500 硬炸修复\n\n响应侧（前端声明字段后端从未返回 / 键名形状错位）：\n- attribution 五报告全部对齐前端契约：model-comparison 重塑嵌套 comparison + models 假筛选真消费；\n overall stats 补 revenue/coverage 真实指标并删硬编码假数；channel/campaign/path 三报告修\n 键名错位与渲染崩溃隐患（creditPercent.toFixed / path.join），统一\"最近计算批次\"防重算翻倍；\n docs 三套幻想 schema 归真；multi-touch CSV 消费键同步\n- customers check-duplicate：match 补 phone/email/industry/primaryContact 四死字段；\n customer 与 matches[0] 深拷贝隔离（修共享引用被序列化为 \"[Circular]\" 的存量缺陷）\n- cash-flow 整模块对齐后端文档级 DTO（owner 矩阵裁定）：统计卡/风险预警接真实端点，\n 列表/详情/编辑三视图重写（删 NaN%/静默丢弃/永不可达区块），detail 补回 notes 回读；\n 详情页真实消费 canonical /:id/items 明细子资源\n\n请求侧（live 复现实锤的运行时 500 与假筛选）：\n- tickets 列表 9 个 schema 声明筛选键全部真消费（assigneeName/日期区间/多选/isOverdue/\n isEscalated/tags），teamId 无物理列显式吞掉防透传；修复前任意携带即整页 500\n- payments records：min/maxAmount 接 paid_amount 区间真消费，start/endDate 剔除透传\n- targets：end_date 区间补真实消费（此前从未实现），四日期键剔除透传\n\n治理配套：\n- 删除 attribution-models/attribution-reports 两个孤岛遗留 API 测试（打已删模块恒红）\n- acquisition 模块补 module-contract 单测（陈旧基线暴露的 D 级收口，A=282/D=0）\n- 49 条 CONFIRMED 分诊台账落盘 reports/field-contract-triage-2026-07-12.md\n （响应侧 5 域 42 条 + 请求侧 7 条，含共性根因与修复范式）\n\n证据：双端类型检查干净；后端单测 640 文件/8795 全绿（attribution-report 新增 7 用例、\ncustomers 引用隔离守卫）；cash-flow RTL 19/19 重写；attribution/customers/multi-touch/\ncash-flow/targets API 真打 DB 全绿；三组筛选修复 live curl 收敛性断言（tickets 327→162/80/30、\npayments 177→0、targets 33→0）；audit:tenant/response-columns/filter-truth/module-coverage\n全部达标且受控块零漂移。tickets/payments 两 API 套件失败经 stash 判责为存量债（vitest CJS\n加载/fixture 清理链），已记录台账。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-12T06:13:37-07:00"}],"HeadCommit":{"Sha1":"b6ca4eb97fca5dff7fe33490df662865134b08d2","Message":"fix(field-contract): 断链深挖三批收口——attribution 读模型重塑 + customers 查重富化 + cash-flow 对齐文档真源 + 筛选键 500 硬炸修复\n\n响应侧（前端声明字段后端从未返回 / 键名形状错位）：\n- attribution 五报告全部对齐前端契约：model-comparison 重塑嵌套 comparison + models 假筛选真消费；\n overall stats 补 revenue/coverage 真实指标并删硬编码假数；channel/campaign/path 三报告修\n 键名错位与渲染崩溃隐患（creditPercent.toFixed / path.join），统一\"最近计算批次\"防重算翻倍；\n docs 三套幻想 schema 归真；multi-touch CSV 消费键同步\n- customers check-duplicate：match 补 phone/email/industry/primaryContact 四死字段；\n customer 与 matches[0] 深拷贝隔离（修共享引用被序列化为 \"[Circular]\" 的存量缺陷）\n- cash-flow 整模块对齐后端文档级 DTO（owner 矩阵裁定）：统计卡/风险预警接真实端点，\n 列表/详情/编辑三视图重写（删 NaN%/静默丢弃/永不可达区块），detail 补回 notes 回读；\n 详情页真实消费 canonical /:id/items 明细子资源\n\n请求侧（live 复现实锤的运行时 500 与假筛选）：\n- tickets 列表 9 个 schema 声明筛选键全部真消费（assigneeName/日期区间/多选/isOverdue/\n isEscalated/tags），teamId 无物理列显式吞掉防透传；修复前任意携带即整页 500\n- payments records：min/maxAmount 接 paid_amount 区间真消费，start/endDate 剔除透传\n- targets：end_date 区间补真实消费（此前从未实现），四日期键剔除透传\n\n治理配套：\n- 删除 attribution-models/attribution-reports 两个孤岛遗留 API 测试（打已删模块恒红）\n- acquisition 模块补 module-contract 单测（陈旧基线暴露的 D 级收口，A=282/D=0）\n- 49 条 CONFIRMED 分诊台账落盘 reports/field-contract-triage-2026-07-12.md\n （响应侧 5 域 42 条 + 请求侧 7 条，含共性根因与修复范式）\n\n证据：双端类型检查干净；后端单测 640 文件/8795 全绿（attribution-report 新增 7 用例、\ncustomers 引用隔离守卫）；cash-flow RTL 19/19 重写；attribution/customers/multi-touch/\ncash-flow/targets API 真打 DB 全绿；三组筛选修复 live curl 收敛性断言（tickets 327→162/80/30、\npayments 177→0、targets 33→0）；audit:tenant/response-columns/filter-truth/module-coverage\n全部达标且受控块零漂移。tickets/payments 两 API 套件失败经 stash 判责为存量债（vitest CJS\n加载/fixture 清理链），已记录台账。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-12T06:13:37-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/3d0a44a9c8d654139f4027f66c65b83a9ab64f0f...b6ca4eb97fca5dff7fe33490df662865134b08d2","Len":1}...
|
1783862034
|
Edit
Delete
|
|
17107
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"34599f92f {"Commits":[{"Sha1":"34599f92fc238176604126d3b0af3ac05efe051a","Message":"fix(field-contract): P0 批次八条收口——券码链崩溃/分配假失败/SLA 违规表/流转反馈/翻页/编辑丢字段/搜索失效\n\n响应侧：\n- groupbuy-redemptions 券码链：listVouchers/getVoucher/findByPhone 三端点接 adaptVoucher\n 归一（此前直连 canonical 形状致 row.code undefined 渲染 TypeError 崩溃、核销入口\n 永不出现、手机号核销必失败）；adaptVoucher/adaptRedemption 补 metadata 双读\n （buyerName/buyerPhone/orderAmount，金额一直在此前恒 ¥0）；formatVoucherCode 空值\n 守卫；reversed 状态不再折叠为 unused\n- leads 分配链：后端 assign 返回补 assignedTo（成功分配此前被前端 TypeError 报成\n \"分配失败\"）；分配预览 null 守卫（无可分配人显示告警 Tag 而非崩溃）；shared 类型\n assignedTo nullable 化\n- SLA 违规表：getBreachedClocks 富化工单/客户/策略上下文 + breachedBy 超时分钟计算\n （metric_type 兼容 resolution/first_response 双值域），此前裸时钟 DTO 致 7 列全空\n 且超时列渲染 NaN；单测断言更新为富化契约守卫\n- 工单流转反馈：前端 executeTransition 类型与消费改读后端真源键 toStatus\n （此前读 toStage 恒 undefined，流转成功却无提示不刷新）\n- ap-ledger 列表改标准分页包络 paginated()（此前裸 res.json 致前端 total 恒 0 无法翻页）\n\n请求侧（live 实锤）：\n- tickets 编辑：updateTicketSchema 补 customerId/snId/orderId/projectId 关联键\n （与 create 对称，此前换客户被 Zod 静默剥离假成功）+ service 补同租户引用校验 +\n 前端 update() 白名单映射对称化；联系人字段组确认为无物理列的想象契约，归 P2 裁定\n- payments plans：schema 补 keyword/due_date_from/due_date_to + service 到期区间消费\n （搜索框此前输入无效），内部两调用点同步补键\n\n证据：双端类型检查干净；后端单测 640 文件/8795 全绿（SLA 断言更新为富化契约）；\nap-ledger 3/3、sla 12/12 API 真打 DB；live curl 实锤：工单换客户写读回（已还原）、\nplans keyword 190→0 收敛、ap-ledger 标准包络 meta.pagination；前端 leads/\ngroupbuy-redemptions RTL 17/17；分诊台账 P0 段已标记收口。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-12T06:42:16-07:00"}],"HeadCommit":{"Sha1":"34599f92fc238176604126d3b0af3ac05efe051a","Message":"fix(field-contract): P0 批次八条收口——券码链崩溃/分配假失败/SLA 违规表/流转反馈/翻页/编辑丢字段/搜索失效\n\n响应侧：\n- groupbuy-redemptions 券码链：listVouchers/getVoucher/findByPhone 三端点接 adaptVoucher\n 归一（此前直连 canonical 形状致 row.code undefined 渲染 TypeError 崩溃、核销入口\n 永不出现、手机号核销必失败）；adaptVoucher/adaptRedemption 补 metadata 双读\n （buyerName/buyerPhone/orderAmount，金额一直在此前恒 ¥0）；formatVoucherCode 空值\n 守卫；reversed 状态不再折叠为 unused\n- leads 分配链：后端 assign 返回补 assignedTo（成功分配此前被前端 TypeError 报成\n \"分配失败\"）；分配预览 null 守卫（无可分配人显示告警 Tag 而非崩溃）；shared 类型\n assignedTo nullable 化\n- SLA 违规表：getBreachedClocks 富化工单/客户/策略上下文 + breachedBy 超时分钟计算\n （metric_type 兼容 resolution/first_response 双值域），此前裸时钟 DTO 致 7 列全空\n 且超时列渲染 NaN；单测断言更新为富化契约守卫\n- 工单流转反馈：前端 executeTransition 类型与消费改读后端真源键 toStatus\n （此前读 toStage 恒 undefined，流转成功却无提示不刷新）\n- ap-ledger 列表改标准分页包络 paginated()（此前裸 res.json 致前端 total 恒 0 无法翻页）\n\n请求侧（live 实锤）：\n- tickets 编辑：updateTicketSchema 补 customerId/snId/orderId/projectId 关联键\n （与 create 对称，此前换客户被 Zod 静默剥离假成功）+ service 补同租户引用校验 +\n 前端 update() 白名单映射对称化；联系人字段组确认为无物理列的想象契约，归 P2 裁定\n- payments plans：schema 补 keyword/due_date_from/due_date_to + service 到期区间消费\n （搜索框此前输入无效），内部两调用点同步补键\n\n证据：双端类型检查干净；后端单测 640 文件/8795 全绿（SLA 断言更新为富化契约）；\nap-ledger 3/3、sla 12/12 API 真打 DB；live curl 实锤：工单换客户写读回（已还原）、\nplans keyword 190→0 收敛、ap-ledger 标准包络 meta.pagination；前端 leads/\ngroupbuy-redemptions RTL 17/17；分诊台账 P0 段已标记收口。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-12T06:42:16-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/b6ca4eb97fca5dff7fe33490df662865134b08d2...34599f92fc238176604126d3b0af3ac05efe051a","Len":1}...
|
1783863745
|
Edit
Delete
|
|
17108
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"0ebe6fb5c {"Commits":[{"Sha1":"0ebe6fb5c4cc802d6d6f53fba830ec5fbf64f3d7","Message":"fix(field-contract): P1 批次十三条收口——键名/量纲映射级断链修复\n\n响应侧映射修复：\n- campaigns：getCampaignStats 从后端真实 {overview,channels} 派生 summary/channelBreakdown\n （渠道真数据此前被键名错位丢弃恒空）；getStats 分组数组转对象（业务线 Tab 计数恒 0）+\n totalSpent 键对齐\n- leads /:id/score：拆分 controller 回完整评分对象（此前与 /score-details 共用剥壳 handler\n 只回裸数组，评分卡恒 0 分）；shared 类型补 calculatedAt 真源键并重建 dist\n- tickets：stage-history 路由接 ticket_stage_history 真源 handler（此前 alias 到 timeline\n 被旁路，渲染「初始状态：undefined」）；getReplies 补 adapter（回复人恒 '-' 修复）\n- satisfaction /analytics：adapter 归一 responseRate/avgCSAT/avgNPS/npsBreakdown\n （分析页半页恒 '-'）；情感分布/类型统计无后端真源，保持 undefined 失败关闭\n- commissions：my-stats adapter（四张统计卡恒 ¥0）；listRecords/getMyRecords/\n getSettlementById 补 user/rule/settlement/records DTO 映射（含 org_units 部门），\n 顺手修掉 where 层 camel 死键（userId/businessDate 等触发 Prisma 未知列的潜伏 500）\n- financial-reports：KPI 卡读 actualValue/targetValue 真源键（恒 '-' 修复）；\n 逾期率去掉二次 ×100（12.5% 曾显示 1250%）\n- ap-ledger：service 层补 supplier/owner 语义键映射（两列恒 '-'）\n\n请求侧修复：\n- opportunities：statsQuerySchema 补 transform 唯一转换点（snake schema × camel service，\n stats/funnel/forecast 三端点 owner/日期筛选静默失效返回全量口径）\n- sla clocks：schema 补 status（此前被 Zod 剥离）+ service 消费 ticketId/clockType/breached\n （收而不筛的假筛选）\n\n附带：LeadAssignmentResult.assignedTo nullable 化后类型连坐揪出分配历史列第三处\n无守卫消费，一并加守卫。\n\n证据：双端类型检查干净；后端单测 640/8795 全绿；前端六域 RTL 20 文件/72 用例全绿；\nlive curl 实锤：opportunities funnel bogus owner 309→0、stats 2099 区间→0、\nleads score 返回完整对象键、sla clocks bogus status→0、campaigns/commissions wire\n形状确认。分诊台账 P1 段已标记收口。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-12T07:01:41-07:00"}],"HeadCommit":{"Sha1":"0ebe6fb5c4cc802d6d6f53fba830ec5fbf64f3d7","Message":"fix(field-contract): P1 批次十三条收口——键名/量纲映射级断链修复\n\n响应侧映射修复：\n- campaigns：getCampaignStats 从后端真实 {overview,channels} 派生 summary/channelBreakdown\n （渠道真数据此前被键名错位丢弃恒空）；getStats 分组数组转对象（业务线 Tab 计数恒 0）+\n totalSpent 键对齐\n- leads /:id/score：拆分 controller 回完整评分对象（此前与 /score-details 共用剥壳 handler\n 只回裸数组，评分卡恒 0 分）；shared 类型补 calculatedAt 真源键并重建 dist\n- tickets：stage-history 路由接 ticket_stage_history 真源 handler（此前 alias 到 timeline\n 被旁路，渲染「初始状态：undefined」）；getReplies 补 adapter（回复人恒 '-' 修复）\n- satisfaction /analytics：adapter 归一 responseRate/avgCSAT/avgNPS/npsBreakdown\n （分析页半页恒 '-'）；情感分布/类型统计无后端真源，保持 undefined 失败关闭\n- commissions：my-stats adapter（四张统计卡恒 ¥0）；listRecords/getMyRecords/\n getSettlementById 补 user/rule/settlement/records DTO 映射（含 org_units 部门），\n 顺手修掉 where 层 camel 死键（userId/businessDate 等触发 Prisma 未知列的潜伏 500）\n- financial-reports：KPI 卡读 actualValue/targetValue 真源键（恒 '-' 修复）；\n 逾期率去掉二次 ×100（12.5% 曾显示 1250%）\n- ap-ledger：service 层补 supplier/owner 语义键映射（两列恒 '-'）\n\n请求侧修复：\n- opportunities：statsQuerySchema 补 transform 唯一转换点（snake schema × camel service，\n stats/funnel/forecast 三端点 owner/日期筛选静默失效返回全量口径）\n- sla clocks：schema 补 status（此前被 Zod 剥离）+ service 消费 ticketId/clockType/breached\n （收而不筛的假筛选）\n\n附带：LeadAssignmentResult.assignedTo nullable 化后类型连坐揪出分配历史列第三处\n无守卫消费，一并加守卫。\n\n证据：双端类型检查干净；后端单测 640/8795 全绿；前端六域 RTL 20 文件/72 用例全绿；\nlive curl 实锤：opportunities funnel bogus owner 309→0、stats 2099 区间→0、\nleads score 返回完整对象键、sla clocks bogus status→0、campaigns/commissions wire\n形状确认。分诊台账 P1 段已标记收口。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-12T07:01:41-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/34599f92fc238176604126d3b0af3ac05efe051a...0ebe6fb5c4cc802d6d6f53fba830ec5fbf64f3d7","Len":1}...
|
1783864905
|
Edit
Delete
|
|
17109
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"5ae992ef9 {"Commits":[{"Sha1":"5ae992ef927153e78f5d698e12079bcd3c022f39","Message":"fix(field-contract): P2 第四批八条收口——占位统计真实现 + 无真源 UI 失败关闭\n\n后端补真实现（真源在库、此前占位/分组数组致恒 0）：\n- rma：byType 真实 groupBy（type 列 2026-07-09 已建，stats 注释过期硬编码空数组致\n 「类型分布」卡恒空）\n- contracts：统计卡 active/expiringSoon/totalValue 真算（status 分组 + effective_to\n 30 天到期窗口 + total_amount 合计；live 实测 active=126 / totalValue=90 亿）\n- tickets：统计卡 pending(new+assigned)/processing(in_progress)/breached(SLA 时钟违约\n 且未终态) 真算（live 实测 177/45/0）\n- leads：/stats 补 unassigned（销售看板待办真源，live 实测 398）；assignment/stats 补\n unassigned/todayAssigned + topAssignees.userName 人员姓名回填（分配页 UUID 直显修复）\n- sales-dashboard：getTrend 由硬编码空数组占位改真实月度聚合（与 overview 同口径\n won opportunities expected_amount + leads/opportunities 创建计数；live 验证趋势卡\n 出现 2026-05 真实赢单 50000，此前恒「暂无趋势数据」）\n\n前端无真源 UI 失败关闭（数据模型表达不了、禁止造假数）：\n- contract-templates：删「草稿」统计卡（is_active 布尔无 draft 语义，后端字面量 0、\n 点击恒空列表）\n- customer-balance：删「透支额度」虚构列（后端无 overdraft 概念，adapter 硬编码 0）\n- groupbuy-redemptions：删「方式统计」死面板（redeem_method 未持久化，后端诚实空集）\n\n证据：双端类型检查干净；后端单测 640/8795 全绿（contracts/lead-assignment 单测断言\n更新为扁平键回归守卫）；前端六域 RTL 10 文件/39 用例全绿；live curl 六端点真值实锤。\n分诊台账 P2 段拆分为已收口子集与剩余待裁定清单。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-12T07:16:44-07:00"}],"HeadCommit":{"Sha1":"5ae992ef927153e78f5d698e12079bcd3c022f39","Message":"fix(field-contract): P2 第四批八条收口——占位统计真实现 + 无真源 UI 失败关闭\n\n后端补真实现（真源在库、此前占位/分组数组致恒 0）：\n- rma：byType 真实 groupBy（type 列 2026-07-09 已建，stats 注释过期硬编码空数组致\n 「类型分布」卡恒空）\n- contracts：统计卡 active/expiringSoon/totalValue 真算（status 分组 + effective_to\n 30 天到期窗口 + total_amount 合计；live 实测 active=126 / totalValue=90 亿）\n- tickets：统计卡 pending(new+assigned)/processing(in_progress)/breached(SLA 时钟违约\n 且未终态) 真算（live 实测 177/45/0）\n- leads：/stats 补 unassigned（销售看板待办真源，live 实测 398）；assignment/stats 补\n unassigned/todayAssigned + topAssignees.userName 人员姓名回填（分配页 UUID 直显修复）\n- sales-dashboard：getTrend 由硬编码空数组占位改真实月度聚合（与 overview 同口径\n won opportunities expected_amount + leads/opportunities 创建计数；live 验证趋势卡\n 出现 2026-05 真实赢单 50000，此前恒「暂无趋势数据」）\n\n前端无真源 UI 失败关闭（数据模型表达不了、禁止造假数）：\n- contract-templates：删「草稿」统计卡（is_active 布尔无 draft 语义，后端字面量 0、\n 点击恒空列表）\n- customer-balance：删「透支额度」虚构列（后端无 overdraft 概念，adapter 硬编码 0）\n- groupbuy-redemptions：删「方式统计」死面板（redeem_method 未持久化，后端诚实空集）\n\n证据：双端类型检查干净；后端单测 640/8795 全绿（contracts/lead-assignment 单测断言\n更新为扁平键回归守卫）；前端六域 RTL 10 文件/39 用例全绿；live curl 六端点真值实锤。\n分诊台账 P2 段拆分为已收口子集与剩余待裁定清单。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-12T07:16:44-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/0ebe6fb5c4cc802d6d6f53fba830ec5fbf64f3d7...5ae992ef927153e78f5d698e12079bcd3c022f39","Len":1}...
|
1783865808
|
Edit
Delete
|
|
17110
|
5
|
5
|
5
|
6
|
0
|
0
|
refs/heads/react-migration
|
0
|
{"Commits":[{"Sha1":"e005063b4 {"Commits":[{"Sha1":"e005063b444466a70a8b0bc6b257ee2097fac9cb","Message":"fix(field-contract): P2 第五批十五条全量收口——SLA/门店/获客三域整链 + 微修线\n\n三域并行修复（每条裁定附 prisma schema 列证据，范式：有真源后端真算、无真源失败关闭）：\n\nSLA 整链（服务#2/#3）：\n- getDashboardStats 重写为前端嵌套契约：current{running/atRisk/breaching}、last30Days\n 响应/解决达标率（诚实分母：未到期 pending 不计入不造数）、breachedByPriority、\n dailyTrend 近 7 日；保留旧扁平键兼容。live 实锤 running=306、解决达标率 22.7%\n- getComplianceReport 由时钟数组改报告对象（overall/byPriority/byType/daily 逐日骨架），\n 真消费 dateFrom/dateTo（此前完全忽略）；API 测试断言同步归真（旧断言锁定断链形状）\n\n门店域（门店#1-6）：\n- groupbuy-platforms：全局统计/平台列表真算（accounts 计数、settled_amount 合计、\n byPlatform 分桶、authorizedPlatforms 接 auth_status 真列）；店铺硬编码死指标\n （syncStatus/productCount/rating）删除；营收量纲修正（误按分除 100 → 元）；\n totalOrders 全仓无 writer 全线失败关闭；同步任务无持久化表 → tab/API/类型下线\n- livestream-groupbuy-conversion：实时卡 redemptions（conversion_tracks stage='redeemed'）\n 与 avgWatchDuration（viewer_tracks.watch_duration 有列有写链，纠正分诊「无列」误判）\n 真算；peakViewers 死零列失败关闭；关联表补 schedule 名称等 7 个物理列真源，\n 假时间戳/假 status 兜底删除；创建表单想象字段（商品 ID/置顶）删除\n\n获客域（获客#1/#2/#5）：\n- campaigns getDashboardData 扩展 12 键真算（byStatus/byChannel/byBusinessLine groupBy、\n 预算花费聚合、executingCampaigns、recentLeadsCount、dailyTrend 7 日桶）；live 实锤\n totalBudget=134.3 万、recentLeadsCount=31\n- channel-comparison 补 campaigns 计数与 avgRoi（cost=0 失败关闭）；impressions/clicks\n 无真源从前端契约删除\n- campaign-targets 无 Prisma 关系 → 二次查询拼装活动摘要（查不到 null 禁止伪造）；\n currentValue 无列 → 进度列失败关闭 '-'；abm 触点/评分 metadata 无写链 → nullable\n\n微修线（7 条）：\n- 门店系 page 回退 typo ×4（page ?? page_size 误回退，pageSize=50 会跳空页）\n- contracts 排序 order 别名（拦截器映射键此前被 Zod 剥离，升序静默回落 desc）\n- invoices「开票人」死字段三处删除（表无 issued_by 列，条件恒 false）\n- leads 保护期真实现（protect_until 真列 + 分配链真实写入；「保护期管理」由硬编码\n 空 stub 改真查询）；分配历史 protectUntil 假时间戳改读 leads 真值\n- tickets assign/escalate 补 crm_activities 操作日志 writer（activity_type 直映\n timeline type，「指派记录」「升级记录」两个恒空 Tab 从此有真源）\n- cash-flow payment-behaviors 孤儿 schema 删除（零引用死文件）\n- batch8 测试存量断言缺陷补 auth mock（Permission 包裹按钮自 wire 提交起未 mock）\n\n证据：双端类型检查干净；后端单测 640 文件/8803 全绿（三域新增/强化单测：SLA 4 条、\nplatforms/livestream 聚合断言、campaigns dashboard/channel/targets 拼装断言，含\nnot.toHaveProperty 防伪造键回潮守卫）；SLA API 真打 DB 12/12；前端相关域 RTL 全绿\n（含失败关闭断言与 createLink payload 精确匹配防想象字段回潮）；live curl 六端点\n真值/失败关闭行为实锤。分诊台账 P2 段全部标记收口，余 4 项无消费者观察 INFO 备案。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-12T08:08:16-07:00"}],"HeadCommit":{"Sha1":"e005063b444466a70a8b0bc6b257ee2097fac9cb","Message":"fix(field-contract): P2 第五批十五条全量收口——SLA/门店/获客三域整链 + 微修线\n\n三域并行修复（每条裁定附 prisma schema 列证据，范式：有真源后端真算、无真源失败关闭）：\n\nSLA 整链（服务#2/#3）：\n- getDashboardStats 重写为前端嵌套契约：current{running/atRisk/breaching}、last30Days\n 响应/解决达标率（诚实分母：未到期 pending 不计入不造数）、breachedByPriority、\n dailyTrend 近 7 日；保留旧扁平键兼容。live 实锤 running=306、解决达标率 22.7%\n- getComplianceReport 由时钟数组改报告对象（overall/byPriority/byType/daily 逐日骨架），\n 真消费 dateFrom/dateTo（此前完全忽略）；API 测试断言同步归真（旧断言锁定断链形状）\n\n门店域（门店#1-6）：\n- groupbuy-platforms：全局统计/平台列表真算（accounts 计数、settled_amount 合计、\n byPlatform 分桶、authorizedPlatforms 接 auth_status 真列）；店铺硬编码死指标\n （syncStatus/productCount/rating）删除；营收量纲修正（误按分除 100 → 元）；\n totalOrders 全仓无 writer 全线失败关闭；同步任务无持久化表 → tab/API/类型下线\n- livestream-groupbuy-conversion：实时卡 redemptions（conversion_tracks stage='redeemed'）\n 与 avgWatchDuration（viewer_tracks.watch_duration 有列有写链，纠正分诊「无列」误判）\n 真算；peakViewers 死零列失败关闭；关联表补 schedule 名称等 7 个物理列真源，\n 假时间戳/假 status 兜底删除；创建表单想象字段（商品 ID/置顶）删除\n\n获客域（获客#1/#2/#5）：\n- campaigns getDashboardData 扩展 12 键真算（byStatus/byChannel/byBusinessLine groupBy、\n 预算花费聚合、executingCampaigns、recentLeadsCount、dailyTrend 7 日桶）；live 实锤\n totalBudget=134.3 万、recentLeadsCount=31\n- channel-comparison 补 campaigns 计数与 avgRoi（cost=0 失败关闭）；impressions/clicks\n 无真源从前端契约删除\n- campaign-targets 无 Prisma 关系 → 二次查询拼装活动摘要（查不到 null 禁止伪造）；\n currentValue 无列 → 进度列失败关闭 '-'；abm 触点/评分 metadata 无写链 → nullable\n\n微修线（7 条）：\n- 门店系 page 回退 typo ×4（page ?? page_size 误回退，pageSize=50 会跳空页）\n- contracts 排序 order 别名（拦截器映射键此前被 Zod 剥离，升序静默回落 desc）\n- invoices「开票人」死字段三处删除（表无 issued_by 列，条件恒 false）\n- leads 保护期真实现（protect_until 真列 + 分配链真实写入；「保护期管理」由硬编码\n 空 stub 改真查询）；分配历史 protectUntil 假时间戳改读 leads 真值\n- tickets assign/escalate 补 crm_activities 操作日志 writer（activity_type 直映\n timeline type，「指派记录」「升级记录」两个恒空 Tab 从此有真源）\n- cash-flow payment-behaviors 孤儿 schema 删除（零引用死文件）\n- batch8 测试存量断言缺陷补 auth mock（Permission 包裹按钮自 wire 提交起未 mock）\n\n证据：双端类型检查干净；后端单测 640 文件/8803 全绿（三域新增/强化单测：SLA 4 条、\nplatforms/livestream 聚合断言、campaigns dashboard/channel/targets 拼装断言，含\nnot.toHaveProperty 防伪造键回潮守卫）；SLA API 真打 DB 12/12；前端相关域 RTL 全绿\n（含失败关闭断言与 createLink payload 精确匹配防想象字段回潮）；live curl 六端点\n真值/失败关闭行为实锤。分诊台账 P2 段全部标记收口，余 4 项无消费者观察 INFO 备案。\n\nCo-Authored-By: Claude Fable 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-07-12T08:08:16-07:00"},"CompareURL":"luoanwu/juhi-omni-knowledge-hub/compare/5ae992ef927153e78f5d698e12079bcd3c022f39...e005063b444466a70a8b0bc6b257ee2097fac9cb","Len":1}...
|
1783868903
|
Edit
Delete
|