You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 4, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 4, 2026. It is now read-only.
Stale-premise check first — all four claims re-measured on origin/main (0cf8f0f, i.e. after #3704 / PR #3714 merged), not in the shared worktree. The card was filed against 36bf20235 and predicted its line numbers would survive that merge. They did:
MetadataManagerPage appears at :858, :862, :868, :999 — the full P1.12.3 spread the card describes;
git grep -l MetadataManagerPage origin/main -- apps/console/src/ ⇒ zero files. The zero-hit is real, not a broken scan: the control probe on the same path (MetadataRedirect in apps/console/src/AppContent.tsx) returns 6 hits, so the scanner reads that tree fine. The component is genuinely gone; the route resolves to MetadataRedirect.
#3704 landing therefore did not incidentally fix this, exactly as the card predicted.
Why promote rather than hold. Two things separate this from the observation-class cards this round is holding:
Cost accrues to readers who act on it.- [x] /system/metadata/:metadataType → MetadataManagerPage (generic, registry-driven) reads as "the console already ships a registry-driven metadata list page you can wire up"; someone plans against a component with zero files behind it. That is the "照做会坏" shape, on a checked-off roadmap line, which is more load-bearing than an unchecked one.
Scope for the claiming dev — deliberately wider than the two lines in the title. The card's own analysis is right that :858 cannot be repaired alone: :862, :868 and :999 describe the same absent component as current, so a single-line patch leaves the section self-contradictory. Fix the whole MetadataManagerPage spread (:858 / :862 / :868 / :999) in one PR.
For :872 (Total: 20) the card is right that "system page tests" is an undefined referent — measured as 13 on the narrow reading and 18 on the wide, neither being 20 — so do not pick a number: follow the :871 precedent from #3704 and rewrite it without a hardcoded count. Planting 13 would just re-arm the same trap.
No domain:* — objectui is a whole-repo seat. Not a transfer candidate: ROADMAP.md is repo-local, no packages/spec face, not cross-repo.
Dedup — searched this repo and both siblings for MetadataManagerPage, ROADMAP drift, P1.12.3, system page tests, open issues and PRs. No duplicate.#3704 is the closed-out parent whose file fence produced this card; #3700 / PR #3705 is the method precedent. ⚠️ Both touch ROADMAP.md, and #3704 has landed, so there is no in-flight conflict on that file right now — but check for a fresh one at claim time, since this file attracts several lanes.
交付内容:MetadataManagerPage 整片(:858/:862/:868/:999)按今日现实就地改写——URL 判为 legacy alias(MetadataRedirect 一跳转发至 metadata-admin 引擎),真实继任者 MetadataResourceListPage/MetadataResourceRegistry 逐条给出实路径;:872 与 :868 均不种计数,且 :872 把"指称未定义"本身写进条目并附「Measure the group you mean instead of trusting a number written down once」——比删数字更进一步,把陷阱的成因钉在了原地。声明式一行扩界(:1000 为 :999 同句后半,不改则自相矛盾)理由成立,PR 正文与 issue 评论均有记录。方法完全循 #3700/#3705 先例:零删除、[x] 保留、错名留锚、裸文本引用、零版本字面量。
Activity
os-zhuang commentedon Aug 8, 2026
Findings triage — verdict: PROMOTE.
finding→pm:queue.Stale-premise check first — all four claims re-measured on
origin/main(0cf8f0f, i.e. after #3704 / PR #3714 merged), not in the shared worktree. The card was filed against36bf20235and predicted its line numbers would survive that merge. They did:ROADMAP.md:858—- [x] \/system/metadata/:metadataType` → MetadataManagerPage (generic, registry-driven)` — present, unchanged;ROADMAP.md:872—- [x] Total: 20 system page tests passing— present, unchanged;MetadataManagerPageappears at:858,:862,:868,:999— the full P1.12.3 spread the card describes;git grep -l MetadataManagerPage origin/main -- apps/console/src/⇒ zero files. The zero-hit is real, not a broken scan: the control probe on the same path (MetadataRedirectinapps/console/src/AppContent.tsx) returns 6 hits, so the scanner reads that tree fine. The component is genuinely gone; the route resolves toMetadataRedirect.#3704 landing therefore did not incidentally fix this, exactly as the card predicted.
Why promote rather than hold. Two things separate this from the observation-class cards this round is holding:
:871one line above. There is no open design question, only the work.- [x] /system/metadata/:metadataType → MetadataManagerPage (generic, registry-driven)reads as "the console already ships a registry-driven metadata list page you can wire up"; someone plans against a component with zero files behind it. That is the "照做会坏" shape, on a checked-off roadmap line, which is more load-bearing than an unchecked one.Scope for the claiming dev — deliberately wider than the two lines in the title. The card's own analysis is right that
:858cannot be repaired alone::862,:868and:999describe the same absent component as current, so a single-line patch leaves the section self-contradictory. Fix the wholeMetadataManagerPagespread (:858/:862/:868/:999) in one PR.For
:872(Total: 20) the card is right that "system page tests" is an undefined referent — measured as 13 on the narrow reading and 18 on the wide, neither being 20 — so do not pick a number: follow the:871precedent from #3704 and rewrite it without a hardcoded count. Planting 13 would just re-arm the same trap.No
domain:*— objectui is a whole-repo seat. Not a transfer candidate:ROADMAP.mdis repo-local, nopackages/specface, not cross-repo.Dedup — searched this repo and both siblings for⚠️ Both touch
MetadataManagerPage,ROADMAP drift,P1.12.3,system page tests, open issues and PRs. No duplicate. #3704 is the closed-out parent whose file fence produced this card; #3700 / PR #3705 is the method precedent.ROADMAP.md, and #3704 has landed, so there is no in-flight conflict on that file right now — but check for a fresh one at claim time, since this file attracts several lanes.本评论来自分诊座位 Routine(#5474 试点),不构成认领。
Generated by Claude Code
yinlianghui commentedon Aug 8, 2026
认领:PM 循环批 179(objectui 整仓席位,登记表 objectstack#4604)
会话:
session_01GTRjn8xBqp75dk7kFupVRt分支:
claude/issue-3712-roadmap-p1123-driftWorktree:
objectui-3712文件面:
ROADMAP.md单文件(越界即停,报告说明)按发现分诊晋级裁定执行:整片 MetadataManagerPage 铺(:858/:862/:868/:999)一次修,不做单行补丁;:872 不种新计数,循 :871 / PR #3705 先例改写为不含硬编码数字的表述。已核当前在飞 PR(仅 #3727,ledger/plugin-report)不触 ROADMAP.md,dev 动手前按惯例再核一次。
Generated by Claude Code
yinlianghui commentedon Aug 8, 2026
实现完成,草稿 PR #3732(
claude/issue-3712-roadmap-p1123-drift,ROADMAP.md单文件,6 增 6 删,CI 全绿)。前提复核:成立,且比标题更宽。在
origin/main@4e93e40d7(单据基线36bf20235与分诊复核点0cf8f0f7均已走远)逐条实测:MetadataManagerPage在apps/console/src/下零文件零引用;/system/metadata/:metadataType的 route element 是MetadataRedirect;:999 所指的ObjectManagerListAdapter与listComponent两个载体名字全仓都不存在(连带MetadataTypeConfig、MetadataDetailPage、pageSchemaFactory亦零命中),不只是换了实现。:872 的两个数字也复现:窄读 13、宽读 18,皆非 20。按裁定落地。 :858 / :862 / :868 / :999 就地按现实改写,
[x]保留、错误名留作纠错锚、只挂裸文本编号。:872 未种任何计数(既没写 13 也没写 18),循 :871 / PR #3705 先例改为不含硬编码数字、并把「指称本身没定义」写进条目本身。越界一行,已声明: 连改了紧邻的 :1000。其原文
listComponent extension point on MetadataTypeConfig…与 :999 是同一句话的后半、同一个零命中符号,只改 :999 会让它紧接着自相矛盾 —— 正是裁定第 1 条列为不可接受的形态。越界范围严格限于ROADMAP.md内这 1 行。版本号 prose 门禁:
scripts/__tests__/doc-version-claims.test.ts:112的SCAN_ROOTS = ['content/docs', 'packages/*/README.md']——ROADMAP.md不在其扫描面上(即该门禁自述的 residual hole)。仍按规则未写入任何版本号字面量。ROADMAP.md在check-doc-links.mjs的 disk 面上(:397),故只用裸文本编号、不新增链接。两个门禁测试实跑 2 files / 88 tests 全绿;check-control-bytesOK 并另做了超出门禁的自扫。Changeset:无 —— 对齐 PR #3714 / PR #3705(两者
--stat均只含ROADMAP.md)。围栏外发现,只报不改,已立单(均未认领):
documentation+finding,观察类)—— P1.12.3 的 :861 / :863 / :864 / :866、:1001,以及 P1.16 的 Metadata Manager Grid Mode 整块 :987-:990(metadataTypeRegistry、listMode、MetadataGrid、MetadataTypeConfig全仓零命中)。sys-datasources改指规范路由,却漏了同一数组里紧挨上一行的sys-objects,加上QuickActions.tsx:39,共三个调用点仍发出 legacy 别名/apps/setup/system/metadata/object,每次点击多绕一跳。Generated by Claude Code
Generated by Claude Code
yinlianghui commentedon Aug 8, 2026
验收:PR #3732 ACCEPT(会话
session_01GTRjn8xBqp75dk7kFupVRt,PM 循环批 179)。交付内容:MetadataManagerPage 整片(:858/:862/:868/:999)按今日现实就地改写——URL 判为 legacy alias(MetadataRedirect 一跳转发至 metadata-admin 引擎),真实继任者 MetadataResourceListPage/MetadataResourceRegistry 逐条给出实路径;:872 与 :868 均不种计数,且 :872 把"指称未定义"本身写进条目并附「Measure the group you mean instead of trusting a number written down once」——比删数字更进一步,把陷阱的成因钉在了原地。声明式一行扩界(:1000 为 :999 同句后半,不改则自相矛盾)理由成立,PR 正文与 issue 评论均有记录。方法完全循 #3700/#3705 先例:零删除、[x] 保留、错名留锚、裸文本引用、零版本字面量。
证据:ROADMAP.md 单文件 6/6;check-doc-links 7 根全绿(ROADMAP 在其 disk 面上,故全用裸文本引用);:872 所指两读数如实测得(窄 13/宽 18)但仅入报告不入文档;逆向验证如实报"散文改动无可反演谓词",以 triage 同款零命中对照探针(MetadataRedirect 6 命中 vs MetadataManagerPage 0)替代——处置正确。CI 14 成功 0 失败。无 changeset,与 PR #3705/#3714 先例一致(--stat 已核)。
premise 加宽被证实::999 五个具名载体(ObjectManagerListAdapter/listComponent/MetadataTypeConfig/MetadataDetailPage/pageSchemaFactory)全仓零命中,非改名而是整体退役。dev 另立 #3738(围栏外九条同章节漂移,观察级)与 #3739(具体缺陷:#3660 修 sys-datasources 时漏了同数组上一行的 sys-objects,三处内部导航仍走 legacy alias 多付一跳重定向+重渲染——AppSidebar.tsx:329 / UnifiedSidebar.tsx:335 / QuickActions.tsx:39)入分诊池。
Generated by Claude Code
docs(ROADMAP): P1.12/P1.16 的 MetadataManagerPage 铺与 Total 计数按现实改写 (ob…
docs(ROADMAP): P1.12.3 / P1.16 九条同源漂移按现实改写 (objectstack-ai#3738) (obj…
ci(release): drop the duplicate test run and stop concurrency discard…
ci(release): drop the duplicate test run and stop concurrency discard…