补回分割 image-sdk 阶段记录与两份被引用回执 - #61
Merged
Merged
Conversation
上一轮抢救只取回了 reports/segmentation/2026-09-18-feasibility 路径，
同一分支上还有三份被该路径正文按名引用的孤儿文件：
- reports/segmentation/2026-09-18-image-sdk/README.md：保住"严格掩码门槛仍为
failed"这条负面证据（图 204871 的 car 完整原图 IoU 0.978824 < 0.99，
根因为官方把 612×612 截成 611×611、丢失 58 个边缘前景像素）；
- reports/sdk-standard/segmentation-{before,after}.json：standardVersion 1.1.0，
分割仓库由 partial（required 失败 18）收敛到 locally-compliant（0）。
阶段口径与后续口径的差异在文首以 dated 归档说明标注，不改写原文结论。
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
为什么
PR #59 抢救了
reports/segmentation/2026-09-18-feasibility/，但同一死分支（codex/independent-sdk-priority，PR #53 关闭未合并、远端分支已删）上还有三份被那份文档正文按名引用的孤儿文件，此前没人取回：reports/segmentation/2026-09-18-image-sdk/README.md（门户侧阶段记录，不是 SDK 仓库同名目录的副本——SDK 那份是"64图公共SDK真实验收"，字节数 4208 vs 本文 2568，内容不同）。它保住了负面证据：严格掩码门槛当时为 failed，图 204871 的 car 完整原图 IoU 0.978824 < 0.99，根因是官方实现把 612×612 截成 611×611、丢失 58 个边缘前景像素。reports/sdk-standard/segmentation-before.json/segmentation-after.json：standardVersion 1.1.0，web-sdk-PP-Segmentation由partial（required 失败 18）收敛到locally-compliant（0）。文中明写"门户静态规范检查保存在"这两个文件，缺了就是断链。变更
三份文件原样取回；README 顶部加一段 2026-09-26 dated 归档说明，指出"failed"是当日阶段口径、后续改按原图整数尺寸独立参考验收，现状以
pp-segmentation.yaml的 limitations 与2026-09-18-portal-registry/为准。原文结论未改写。验证
git diff HEAD..codex/independent-sdk-priority --name-status --diff-filter=A现为空 → 那条死分支已无任何独有文件，具备删除前置条件。../2026-09-18-feasibility/README.md（抢救分割可行性证据并归档模型型跟踪候选设计 #59 已落地）、reports/sdk-standard/segmentation-{before,after}.json（本 PR）。git grep为空），故不新增.gitattributes行尾规则；git diff --check干净。standards/v1。