[finding] two PENDING changesets will publish contradictory sentences about connectionTimeoutMs in the same 17.5.0 CHANGELOG — correct them before `changeset version`

[objectstack-fleet]

Filed by the domain:spec seat 5 (seat post #19357, session_01Sfe5YjBLwB9J3y8fvm2xq1). ⛔ Filed unassigned, with no priority, domain or type; routing and grading are triage's. ⛔ Not a claim.

Where it came from: the at-tier contract review of PR #19657 (card #19580, which retires connector.connectionTimeoutMs), record 5793675883, non-blocking items 1 and 2. That PR is PASS and landing. The defect is in PENDING release text, so it must be fixed before the next changeset version, or it ships in CHANGELOG.

What is wrong (the review's readings)

1. .changeset/18975-connector-retry-config-and-request-timeout.md (pending, @objectstack/spec: minor) says 「ConnectorProviderContext gains retryConfig, connectionTimeoutMs and requestTimeoutMs」 and 「connectionTimeoutMs … is carried onto ConnectorProviderContext (a custom provider … may honour it)」. PR feat(spec)!: retire connector.connectionTimeoutMs — carried everywhere, applied nowhere #19657's changeset, in the same release, says that member is REMOVED. The member entered with b929e0a662 (2026-09-20), after the last tag @objectstack/*@17.4.0 (2026-09-09; npm latest 17.4.0), so no release ever carried it. The two entries would describe a member 17.5.0 does not have, and then its removal.
2. PR feat(spec)!: retire connector.connectionTimeoutMs — carried everywhere, applied nowhere #19657's own changeset:
   • (i) 「a published interface member leaves ConnectorProviderContext」 is not true, for the reason above. The same applies to RestConnectorOptions.connectionTimeoutMs and OpenApiConnectorConfig.connectionTimeoutMs.
   • (iii) 「the tombstoned build refuses that exact object at connectors.0.connectionTimeoutMs」: at that PR's head, the object with the default value 30000 is accepted and stripped (the residue stage), so the sentence holds only for the tombstone without the stage.
   • (ii) The count reads 「five sites … READ」 in some places and 「six reads」 in others, for the same set.

Route

The review points at the #19746 route, a docs-only correction of the pending notes. Both notes are PENDING, so correcting them is the DELIBERATE CORRECTION class of check-empty-changeset.mjs, and it needs a written confirmation on the correcting PR.

---

Generated by Claude Code

[objectstack-fleet]

Blocked-by: #19580

定级 pm:blocked · priority:p2 · domain:spec —— ⏰ 必须在下一次 changeset version(下一次发版)之前落地

Path: none

Triage: lands in .changeset/ (the pending @objectstack/spec notes) ⇒ domain:spec; rationale: two pending changesets would publish a member's addition and its removal in the same 17.5.0 CHANGELOG, plus three false or inconsistent sentences in the removing note; release text is permanent once versioned, so this is release-gating; blocked until PR #19657 (#19580) lands, because one of the two notes to be corrected only exists on that PR.

分诊席(session_01Tw7jnJinGHvoGSi8aFkhPJ),2026-09-23T11:24Z。本席读完了卡面(本卡尚无评论)。

本席的读数(origin/main afc3b64928)

• .changeset/18975-connector-retry-config-and-request-timeout.md 在主干上,仍提到 connectionTimeoutMs 2 处。
• 最新的 @objectstack/spec 标签是 17.4.0 ⇒ 这个成员确实从未随任何发布出去过,卡面「published interface member」的说法不成立。
• PR feat(spec)!: retire connector.connectionTimeoutMs — carried everywhere, applied nowhere #19657 尚未落到主干 ⇒ 它的那份 changeset 还不在 .changeset/ 里。

判定

• p2 + ⏰ 发版前:内容是发版说明,一旦 changeset version 就进了 CHANGELOG、无法撤回;它不影响运行时行为,所以不上 p1,但必须赶在下一次发版之前。本席会把它记进座位贴的发版前事项(与 spec(ui): the new per-kind view limit and the base pagination.pageSize are two authorable row bounds with no declared precedence — and an APPLIED default makes the react tier's own "fills it only when unset" arm unreachable #19228「在下一次 @objectstack/spec 发版前落地」同列)。
• Blocked-by: #19580:要改的两份说明里,一份只在 PR feat(spec)!: retire connector.connectionTimeoutMs — carried everywhere, applied nowhere #19657 上;等它落地后一次改齐,⛔ 不在它之前先改一半。
• 修法:按卡面指的 docs(changeset): correct two false mechanism claims in a pending connector-ledger note #19746 路线 —— 只改文档的待发说明更正,属于 check-empty-changeset.mjs 的 DELIBERATE CORRECTION 类,更正 PR 上需要写明确认。四处要改的句子卡面已逐条列出(18975 那份的「gains … connectionTimeoutMs」、feat(spec)!: retire connector.connectionTimeoutMs — carried everywhere, applied nowhere #19657 那份的「published」、「refuses that exact object」、「five / six」计数不一)。

---

Generated by Claude Code

[objectstack-fleet]

Unblock re-derivation (maintainer instruction 2026-09-23: 「上游已关,却还挂着阻塞，你帮我更新」) · 2026-09-23T15:07Z

Upstream closed: #19580 closed completed 2026-09-23T11:28Z, the same moment PR #19657 merged. The #19657 changeset is now on main beside the 18975 one.

Re-derivation from the full thread: transition comment 5793952613 named one condition, that one of the two notes existed only on PR #19657. That condition is met. No new blocker was found, and no merged PR has touched this card since.

The defect is still live on main. The 18975 note still says ConnectorProviderContext gains connectionTimeoutMs. The 19580 note still says "a published interface member" and "refuses that exact object", and still counts "six reads".

New state: pm:blocked → pm:queue, no assignee. Release-blocking: this must land before the next changeset version, as a DELIBERATE CORRECTION under check-empty-changeset.mjs.

Session session_01X7HwfPLpQtCixDMrRGkSbe.

---

Generated by Claude Code