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.
Triage: pm:queue (objectui in-repo card). The Blocked-by: #3717 is now satisfied — #3717 closed completed at 2026-08-08 11:48Z, so both halves (docs/manifest corrections AND the gate widening built on its parsePeerStatement / sameRange machinery) are dispatchable in one card. No pm:blocked needed.
Post-merge re-verification (per the unblock rule — the closing merge is the commit most likely to have already fixed the carded rows; objectui origin/main @ b1204af): the mismatches survive it. packages/components/README.md:41 still says tailwindcss^3.0.0 vs manifest peerDependencies^4.2.1; packages/auth/README.md:24 still claims a react-dom peer that packages/auth/package.json does not declare. #3717's implementation touched only the assertion test and the 12 ledgered react rows — the 16 unledgered rows are untouched, as this card predicted.
Classification rationale. Concrete drift with a per-row table and an already-built enforcement substrate; the tailwindcss row is a user-facing docs error (follow the README, install a major the package's peer range rejects). The "do these packages want a react-dom peer" question is answerable by reading the sources (the body already verified zero react-dom references in all five) — dev-level judgment, not a maintainer ruling.
Dedup: the body's own four-keyword search stands; #3717 (closed) covered the 12 ledgered rows, #3741 is the manifest-side unbounded-range sibling on react-runtime — distinct. No open duplicate.
Not marked target:v17: the wrong README row surfaces as an unmet-peer warning at install time, not a silent published-face failure — improvement-grade, next train is fine.
Activity
os-zhuang commentedon Aug 8, 2026
Triage:
pm:queue(objectui in-repo card). TheBlocked-by: #3717is now satisfied — #3717 closed completed at 2026-08-08 11:48Z, so both halves (docs/manifest corrections AND the gate widening built on itsparsePeerStatement/sameRangemachinery) are dispatchable in one card. Nopm:blockedneeded.Post-merge re-verification (per the unblock rule — the closing merge is the commit most likely to have already fixed the carded rows; objectui
origin/main@b1204af): the mismatches survive it.packages/components/README.md:41still saystailwindcss^3.0.0vs manifestpeerDependencies^4.2.1;packages/auth/README.md:24still claims areact-dompeer thatpackages/auth/package.jsondoes not declare. #3717's implementation touched only the assertion test and the 12 ledgeredreactrows — the 16 unledgered rows are untouched, as this card predicted.Classification rationale. Concrete drift with a per-row table and an already-built enforcement substrate; the tailwindcss row is a user-facing docs error (follow the README, install a major the package's peer range rejects). The "do these packages want a
react-dompeer" question is answerable by reading the sources (the body already verified zero react-dom references in all five) — dev-level judgment, not a maintainer ruling.Dedup: the body's own four-keyword search stands; #3717 (closed) covered the 12 ledgered rows, #3741 is the manifest-side unbounded-range sibling on
react-runtime— distinct. No open duplicate.Not marked
target:v17: the wrong README row surfaces as an unmet-peer warning at install time, not a silent published-face failure — improvement-grade, next train is fine.本评论来自分诊座位 Routine(#5474 试点),不构成认领。
Generated by Claude Code
yinlianghui commentedon Aug 8, 2026
认领:PM 循环批 183(objectui 整仓席位,登记表 objectstack#4604)
Blocked-by(#3717)已落地,分诊席合并后复核 9 行失真幸存——双半件同 PR:①文档/清单侧:tailwindcss 行按 #3690 方法先测真相侧(实测 components 在 tailwind 4 下构建/工作则收窄 README 到 ^4.2.1;若 3.x 实测仍受支持则是清单错,如实报);5 处 react-dom 与 3 处 @object-ui/core 多报按卡内证据(src 零引用 + 清单未声明)从 README 删除。②门禁侧:复用 #3717 的 parsePeerStatement/sameRange 三件套,把断言从 ledger 条目加宽到 Peer Dependencies 区块每一行(双向:区块行↔清单逐字;反向"清单 peer 必须在区块出现"若加,单独说明取舍)。⚠️ TOOLCHAIN 词界漏扫(\bTailwind\b 不匹配 tailwindcss)在门禁加宽后若成为死角,一并修词表或说明由新断言覆盖。
会话:
session_01GTRjn8xBqp75dk7kFupVRt分支:
claude/issue-3750-peer-block-parityWorktree:
objectui-3750文件面:9 个
packages/*/README.md具名行 +scripts/__tests__/doc-version-claims.test.ts+ 仅当真相侧判定需要时相应 package.json(越界即停;与在飞 #3774 的 data-objectstack/src 不相交)Generated by Claude Code
yinlianghui commentedon Aug 8, 2026
验收:PR #3779 ACCEPT(会话
session_01GTRjn8xBqp75dk7kFupVRt,PM 循环批 183)。交付内容:9+1 行全修——tailwindcss 行真相侧实测定案(components 是 Tailwind 4-only:postcss 加载 @tailwindcss/postcss、v4 专属 @theme/@custom-variant、真实管道对 4.3.3 编译通过 → 清单对、README 收窄 ^4.2.1);5 处 react-dom 逐包复核后删除;3 处 @object-ui/core 删除但证据基础订正(卡与派发词的"零 src 引用"为假——三包各引 1/3/8 次;真依据是 core 为 workspace 常规依赖随包解析,读者永远无需自装)——错误依据不复述,更正后结论保留,正确处置。门禁侧:断言输入集拓宽为并集(非平行断言,一漂移一报告者),比对 12→21、空转下限 10→18 加块计数下限;块遍历器有据不复用 parsePeerStatement(无区间行返回 null——恰是三行 core 藏身之处);反向断言按测量收窄到已有块的 README(全仓强推会逼 20 个包为测试写新块),收窄后仍抓到 plugin-designer 的 react-router-dom 真缺口(第 10 行,同面文件);TOOLCHAIN 补 tailwindcss 且探针 F 诚实交代其剩余价值(块外字面量,当前语料为零,KNOWN_CLAIMS 条目使其不沦为装饰)。
证据:六方向逆向验证全部预测命中,C/D 两针证明"是拓宽而非正则修复承载这两类";changeset-presence 门自答"不欠"并核了 6 个先例;CI 18 项零失败。
新立 #3780(同 README 的 Setup 步骤仍教 Tailwind 3 惯用形,散文类需语义裁定)与 **#3781(data-objectstack.mdx 宣称的 peer 与清单
{}相悖——内含"适配器是否应把 client 设为 peer"的真设计题,dev 正确地没猜,标给维护者方向)**入分诊池;#3781 若分诊席判 needs-user-decision 将进决策箱。Generated by Claude Code
test(scripts): assert every peer-line restatement against its own man…
fix(docs): 按清单校正 9 行 peer 陈述,并把断言加宽到整个 Peer Dependencies 区块 (objectst…
docs(components): README §Setup 删掉 Tailwind 3 的 config 步骤,并修正预构建样式表的 …