Skip to content

Commit 2099656

Browse files
committed
docs(changeset): carry the cloud NOT-MEASURED census bound into the shipping artifact (#13095)
At-tier contract review finding on PR #14120: the changeset said a cross-repo census found zero prefix-branching consumers without naming objectstack-ai/cloud as unmeasured. The PR body and both #8111 comment homes carried the bound; the changeset -- the artifact that feeds release notes and reaches operators -- did not, so its zero read as 'checked everywhere'. The census statement now names the three repos it covered (each with a positive control) and states that cloud was NOT MEASURED and is deliberately not reported as clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UngCYXF98BVpYA9hfz6NYk
1 parent 4ed81ba commit 2099656

1 file changed

Lines changed: 10 additions & 4 deletions

File tree

‎.changeset/rest-passthrough-strips-declared-code-prefix.md‎

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,13 @@ ruling did not move).
4444
`error` (flat `/data` doors) or `error.message` (nested record-share
4545
envelope) on these routes must read the `code` field instead — it has
4646
carried the same token all along, with unregistered spellings demoted to
47-
the `declaredCode` sibling (#9232). A cross-repo census (objectstack,
48-
objectui, hotcrm; re-run 2026-09-01) found zero consumers branching on the
49-
prefix; per #13347's precedent an error-envelope shape change ships as
50-
`minor` with this note.
47+
the `declaredCode` sibling (#9232). The consumer census behind this change
48+
covered `objectstack`, `objectui` and `hotcrm` (re-run 2026-09-01, each
49+
scope with a positive control) and found zero consumers branching on the
50+
prefix. `objectstack-ai/cloud` was NOT MEASURED — it was unreachable from
51+
the implementing session — and is deliberately not reported as clean: the
52+
zero above is a statement about the three repos named, not about every
53+
deployment. An operator whose code parses the leading token off these
54+
routes' error text should locate and update those reads before upgrading.
55+
Per #13347's precedent an error-envelope shape change ships as `minor`
56+
with this note.

0 commit comments

Comments
 (0)