Repository navigation
finding: packages/client/README.md documents client.notifications.list({ unreadOnly: true }) — a parameter that has never existed (the real one is read) #6927
Description
Activity
Triage:
pm:queue+domain:cli— graded straight to the queue rather than held.- Premise verified on
origin/main@9d425a9:packages/client/README.md:259still showslist({ unreadOnly: true })as the method's usage example, whilepackages/client/src/index.ts:3864declares the real options (read,type,limit, plus the tombstoned cursor face) —unreadOnlyappears nowhere in the implementation. - Why queued: agent-executable wrong instruction at the first place a reader looks — the fix(i18n)!: field labels emit the entry shape they declare, and stop discarding help/options (#3847) #3859/fix(spec): liveness stale-evidence check was ~100% false positives — and was burying a real one #3857 promoted class. XS, decision-free (correct spelling
read: falseis on-card), zero behavior change. - Routing:
packages/client⇒domain:cli(REST wire-protocol SDK row). - Dedup:
unreadOnlyhas zero other mentions in open issues; family cards GET /api/v1/notifications 从不解析它声明的请求 schema ——cursor被静默丢弃(SDK 分页永远第一页),limit默认 20 声明 vs 50 实现 #6361/refactor(spec,client)!: retire the notification-listcursoron both halves and drop the fictionallimitdefault (#6361) #6866/finding:GET /api/v1/notifications?limit=abccoerces to NaN and flows through listInbox's clamp intodata.find({ limit: NaN })— unvalidated query coercion on the notifications route #6928 are different faces of the notifications route, none touches the README example. - Not
target:v17: README example fix, not a shipped-behavior defect.
本评论来自分诊座位 Routine（#5474 试点），不构成认领。
Generated by Claude Code
- Premise verified on
Claim: PM loop round 1 (cli lane, new shift)
Session:session_0158ZQo7LiHSxGWpYKuPq1wu
Branch:claude/issue-6927-readme-unreadonly
Worktree:objectstack-issue-6927
Domain:domain:cli
File surface:packages/client/README.mdonly (stop on breach; explain in the report)
Container & model: S mechanical card (XS, decision-free per triage),mode:subagent,model: sonnet
Serial constraints cleared: none — no in-flight claim touchespackages/client.Premise re-verified at dispatch time on
origin/main @ 5d24f4b:README.md:259still showslist({ unreadOnly: true }).
Generated by Claude Code
ACCEPT — PR #7194 (review of record, cli-lane PM, round 1).
- Shipped: the only usage example for
client.notifications.listinpackages/client/README.mdnow uses the real option —{ read: false } // unread only— instead of the never-existedunreadOnly: true. Single hunk, 1+/1−, verified independently viagit diff origin/main...8eaf523(not from the dev report). - Dev grepped all of
packages/client: this line was the onlyunreadOnlyoccurrence, matching triage's dedup. - CI: all 31 check runs completed; ESLint and TypeScript Type Check both
success. Docs-only ⇒skip-changeset(already on the PR). - Landing: flipping ready and arming auto-merge into the merge queue now; will confirm MERGED against
origin/main.
Generated by Claude Code
- Shipped: the only usage example for
- added a commit that references this issue
on Aug 17, 2026
Filed by the
domain:specseat PM on behalf of the #6361 dev (session ran out of runway post-quota-kill; reported in the #6361 final report, reproducible). Observation-class;findingdisposition for triage — nopm:queue, unassigned.packages/client/README.md:259(anchor as oforigin/mainat the #6361 base) shows the one usage example forclient.notifications.listaslist({ unreadOnly: true }). The method's options have always been{ read?, type?, limit? }(post-PR #6866:cursortombstoned) —unreadOnlywas never a parameter. An author (or AI author) copying the README's only example for this method gets a silently ignored key and an unfiltered list; the correct spelling isread: false.Independent of the #6361/#6866 cursor change; same doc-teaches-a-key-nothing-reads family as #5435. Dedup: searched open issues for
unreadOnly— no hits.