release text: three pending changesets in the next 18.0.0 pre-release carry sentences that later same-release PRs make false (Hono currentRecord 'held'; the organization_id drop gate 'inventory only')

Filing gate ①, the release-text exception. reach: release text. Each file below is pending in .changeset/ (pre.json: mode pre, tag next, 0 changesets consumed), so it compiles into the next release's CHANGELOGs beside the changeset that makes it false.

Filed by domain:cli seat 2 (#22648) · sunhaolin · session session_01Q9PZ5Pzqcus4woVvTZwWNU. ⛔ Not a claim. Grade and lane are triage's.

The sentences

Pending changeset	Sentence	Made false by
`.changeset/23531-hono-conflict-body.md:15`	"`currentRecord` is held on these two doors until #23586 settles how the protocol reads that row"	PR #23667 (`5bb9a83bd0`), whose `.changeset/23531-hono-conflict-current-record.md` says it supersedes this note
`.changeset/23587-hono-structured-arm-fields.md:14`	"`CONCURRENT_UPDATE`'s `currentRecord` stays held until #23586 settles how the protocol reads that row"	the same PR #23667
`.changeset/23429-v18-boot-refusal.md:20` and `:27`	"refuses to drop `organization_id` from any table in the ceremony's inventory (the D7 tables and the `sys_metadata` family)"; "Only an `os migrate apply --allow-destructive` run that would drop an inventory table's `organization_id` is refused"	PR #23699 (#23684, in review at this stamp; the row stands once it lands): every `organization_id` drop the drift offers is held back, and its changeset's FROM / TO states the change

Why it was not fixed in those PRs

This seat kept each earlier changeset byte for byte in a code PR, as #15953 ruling B (6133232470) did for an earlier slice's unreleased changeset. Each superseding changeset states the change in its own FROM / TO. The result is two contradicting sentences in one release's notes, and a release editor must choose one story.

Reader who acts

Triage routes it to whoever owns release-text review for the next 18.0.0 pre-release. The choice:

(a) amend the three earlier changesets in one release-text PR, before the Version Packages PR consumes them;
(b) leave them, and let the compiled notes carry both, the later one read as the update.

⛔ Not edited by this filing.

Dedupe words: pending changeset superseded same release; currentRecord held changeset; v18-boot-refusal inventory only; release text contradiction 18.0.0-next.

Generated by Claude Code

Triage: first grade · `bug` · `priority:p1` · `target:v18` · `domain:cli` · `pm:queue` · option (a) · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-15T16:55Z

Read fresh. Three pending changesets in the next 18.0.0 prerelease (pre.json: tag next, nothing consumed yet) state things that later same-release PRs make false:

23531-hono-conflict-body.md:15 and 23587-hono-structured-arm-fields.md:14: "currentRecord is held …". PR fix(plugin-hono-server): a Hono door's 409 CONCURRENT_UPDATE carries currentRecord, the caller's own read of the row (#23531) #23667 serves it.
23429-v18-boot-refusal.md:20, :27: "inventory only". PR fix(cli)!: os migrate apply --allow-destructive holds back every organization_id drop until the organization-ownership ceremony verifies (#23684) #23699 (cli: os migrate apply --allow-destructive drops organization_id from a host-declared platform-global object before the organization-ownership ceremony has verified, because the drop gate reads only the platform inventory #23684, open) holds back every drift organization_id drop.

Direction (a), by rule, not a decision: AGENTS.md's packages/*/CHANGELOG.md row says a falsified entry is amended in itself, never by an erratum in a later one. The maintainer confirmed exactly that class on PR #23626 (batch #349, 「确认修正」).

So one release-text PR amends the three files in place, before the Version Packages PR chore: version packages (next) #23481 consumes them.
(b), leaving both stories in one release's notes, is what the rule forbids.

Grade p1 + target:v18: the text of the next 18 prerelease (「发版本优先的都 p1」). It must land before the next.2 cut, or the cut ships contradicting notes.

Lane domain:cli: the filing seat's family; the changesets cover plugin-hono-server, rest and cli.

Scope:

Rows 1–2 now.
Row 3 only once PR fix(cli)!: os migrate apply --allow-destructive holds back every organization_id drop until the organization-ownership ceremony verifies (#23684) #23699 has merged, because the sentence it corrects is true until then. If PR fix(cli)!: os migrate apply --allow-destructive holds back every organization_id drop until the organization-ownership ceremony verifies (#23684) #23699 is not merged when this PR is ready, row 3 rides PR fix(cli)!: os migrate apply --allow-destructive holds back every organization_id drop until the organization-ownership ceremony verifies (#23684) #23699's own changeset as an in-place amendment, and this card says so.
Check Changeset's step 12 will read this as the deliberate-correction class. It needs the maintainer's one-word confirmation, as PR fix(metadata-protocol)!: one sentence for every write over a sealed, package-held name; the inferred create remedy retires #23626 did; this seat lists it for the maintainer when the PR opens.
⛔ No new "supersedes" changeset.

finding leaves on grading.

Claim: PM loop round 21 (#23703: one release-text PR amends, in place, the pending changesets whose sentences later same-release PRs made false — the two Hono "currentRecord is held" notes now, and 23429-v18-boot-refusal.md's "inventory only" once PR #23699 merges) · 2026-10-15T17:05Z
Session: session_01Q9PZ5Pzqcus4woVvTZwWNU
Account: sunhaolin (the seat's linked user as GET /user answers it; the card's assignee from this act)
Branch: claude/issue-23703-release-text-in-place
Worktree: objectstack-issue-23703
Domain: domain:cli
Seat: domain:cli#2 (seat post #22648)
Scope: batch 3, by 「并发恢复3」. #23050 slice 4 (PR #23705) and #23684 (PR #23699, in the merge queue) are in flight; this p1 target:v18 card takes the free slot. #23701 and #23702 (p2) both order after PR #23700, which is a draft.
This seat's correction, in public: the ACCEPTs on PR #23667 (6191403700) and PR #23699 (6197474781) kept the earlier pending changesets byte for byte "per #15953 ruling B", and pointed at a newer changeset that supersedes them. That reading was wrong. AGENTS.md's packages/*/CHANGELOG.md row says a falsified entry is amended in itself, in a dedicated docs-only PR, ⛔ never by an erratum in a later entry. Triage's grade 6197557639 applies exactly that. This card is the amendment.
File surface (read on origin/main f1e21c4f4; stop on a breach and explain it in the report):

Row 1: .changeset/23531-hono-conflict-body.md (:15, the "currentRecord is held" sentence).
Row 2: .changeset/23587-hono-structured-arm-fields.md (:14, the same).
Row 3, only once PR fix(cli)!: os migrate apply --allow-destructive holds back every organization_id drop until the organization-ownership ceremony verifies (#23684) #23699 has merged: .changeset/23429-v18-boot-refusal.md (:20, :27, "inventory only"). If PR fix(cli)!: os migrate apply --allow-destructive holds back every organization_id drop until the organization-ownership ceremony verifies (#23684) #23699 has not merged when the PR is ready, row 3 is left out and this card says so (triage's scope).
The newer changesets' cross-references: only what the amendment makes false.
- .changeset/23531-hono-conflict-current-record.md's "This supersedes the earlier note …" points at a note that will no longer exist.
- .changeset/23684-drop-gate-host-tables.md's FROM, once row 3 is amended.
- ⛔ No new "supersedes" changeset.
⛔ Hold-offs: no code, test or docs page; no packages/*/CHANGELOG.md; no content/docs/releases/; and no skip-changeset (ruling D on [finding] the skip-changeset label suppresses the DELIBERATE-CORRECTION refusal whose own text says 「no label and no diff shape makes that safe」 — declared contract against enforced behaviour #18375: never on a PR that edits an existing changeset).
Container & model: S (release text in up to five pending changeset files), mode:subagent, model: default tier.
Clause-②: no
Responsibility: the release text of @objectstack/plugin-hono-server, @objectstack/hono and @objectstack/cli for the next 18.0.0 pre-release (this lane) | PR #23667 and PR #23699, whose behaviour the text must match, read | every reader of the next.2 CHANGELOGs
Thread-read: 6197557639
Serial constraints cleared:
No open PR edits these five changeset files (read at this act), except PR fix(cli)!: os migrate apply --allow-destructive holds back every organization_id drop until the organization-ownership ceremony verifies (#23684) #23699, which adds .changeset/23684-drop-gate-host-tables.md and is in the merge queue. Row 3 and that file wait for its merge.
Landing: Check Changeset reads this diff as the DELIBERATE CORRECTION class (route 0, red by design). Per landing-operations.md that red does not wait for the maintainer. This seat's ACCEPT confirms it, quoting each amended note before and after.

Generated by Claude Code

os-dev-report
{
"issue": 23703,
"status": "done",
"branch": "claude/issue-23703-release-text-in-place",
"pr": "#23707",
"session": "session_01Q9PZ5Pzqcus4woVvTZwWNU",
"premise_still_valid": true,
"summary": "This PR amends five pending changesets in place so the next 18.0.0 prerelease says what it ships. Rows 1-2: 23531-hono-conflict-body.md:15 and 23587-hono-structured-arm-fields.md:14 no longer say Hono holds currentRecord back; since PR #23667 both doors forward it. Row 3: 23429-v18-boot-refusal.md:20 and :27 say the refusal covers any table, not only the inventory; since PR #23699 every organization_id drop is held back. PR #23699 answered merged:false when rows 1-2 were committed (ff753e1). It merged at 17:18:25Z, before the PR was opened, and REST read merged:true at 17:20:05Z. I then merged origin/main (5737f0f) and added row 3 as a separate commit (4ccf7bc); the PM's mid-task note confirmed this order. PR #23707 is a draft on main, body line 1 Fixes #23703, line 2 Clause-②: no, assignee sunhaolin, with a 12-row before/after table. No new changeset, no erratum, no code/test/docs/CHANGELOG, no labels.",
"files_changed": [
".changeset/23531-hono-conflict-body.md (:11 TO, :15 row 1, :17)",
".changeset/23587-hono-structured-arm-fields.md (:14 row 2)",
".changeset/23531-hono-conflict-current-record.md (:8, :10 FROM, :13, :15 supersedes sentence removed)",
".changeset/23429-v18-boot-refusal.md (:20, :27 row 3)",
".changeset/23684-drop-gate-host-tables.md (:15 FROM, :17 'As before,' removed)"
],
"shipped_reading": {
"pre_json": ".changeset/pre.json on origin/main (f1e21c4 and 6074eaf) is {"mode":"pre","tag":"next"}: it has no changesets key, so no consumed changeset is recorded",
"version_cut": "the newest version commit is 0c52e43 'chore: version packages (next)' (2026-10-14 10:19Z, 18.0.0-next.1). npm dist-tags.next = 18.0.0-next.1 for @objectstack/plugin-hono-server and @objectstack/cli",
"row_1": "23531-hono-conflict-body.md was added at 19c554d (2026-10-15 02:52Z). git merge-base --is-ancestor 0c52e43075 19c554ddc1 exits 0 (added after the cut); the control a87d8be vs 0c52e43 also exits 0. The published @objectstack/plugin-hono-server and @objectstack/hono 18.0.0-next.1 tarball CHANGELOG.md is byte-identical (cmp) to origin/main's; currentRecord counts 0, currentVersion 0, and the control '## 18.0.0-next.1' counts 1. NOT shipped",
"row_2": "23587-hono-structured-arm-fields.md was added at f7cd580 (2026-10-15 07:22Z), after the cut; the same tarball readings apply. NOT shipped",
"newer_23531": "23531-hono-conflict-current-record.md was added at 5bb9a83 (2026-10-15 11:55Z). NOT shipped, so it and row 1 compile into one release",
"row_3": "23429-v18-boot-refusal.md was added at dd29bbe (2026-10-15 06:17Z). git merge-base --is-ancestor 0c52e43075 dd29bbe60d exits 0. The published @objectstack/cli 18.0.0-next.1 CHANGELOG.md is byte-identical to origin/main's; ORGANIZATION_OWNERSHIP_MIGRATION_REQUIRED, refused_organization_ownership_unmigrated and ceremony's inventory count 0 together, and the control counts 1. NOT shipped",
"newer_23684": "23684-drop-gate-host-tables.md was added at 6074eaf (2026-10-15 16:55Z). NOT shipped. At 0c52e43, apply.ts has 0 organization references and organization-ownership-drop-gate.ts is absent, so next.1 held back no organization_id drop"
},
"one_story_resolution": "#23531 pair: the earlier note's TO and :15 state the final body (currentVersion plus currentRecord, the caller's own read). The later note's FROM changes from the intermediate body to the next.1 body (code and message only); its prose describing the intermediate state matches, currentVersion leaves its 'unchanged' list, and the supersedes sentence is gone. Both notes now carry the same FROM/TO pair, from the shipped body to the final one. I preferred this to deleting the later note's pair because it is the smallest change that makes each line true. Drop-gate pair: 23429 says any table. 23684's FROM changes from 'the gate held back only the tables of the platform inventory' to 'held back no organization_id drop', and its TO loses 'As before,'. Kept as true: 23684's title ('not only the platform inventory's'), its 'with the existing refusal' (the refusal 23429 introduces in this same release), and its measurement sentence (taken on a pre-#23699 main tree; its outcome is the FROM's behaviour either way)",
"before_after": [
{
"row": 1,
"at": "23531-hono-conflict-body.md:15",
"before": "currentRecord is held on these two doors until #23586 settles how the protocol reads that row, and the REST server's answer is unchanged.",
"after": "currentRecord rides beside it, as on the REST server: the row as the caller reads it, which the protocol re-reads under the caller's own context on a version mismatch (#23586).",
"read_from": "plugin-hono-server/src/adapter.ts:367, :462-475 (filter :471); types/src/data-error-classification.ts:1046-1053; metadata-protocol/src/protocol.ts:15027-15031; adapters/hono/src/index.ts:554"
},
{
"row": 2,
"at": "23531-hono-conflict-body.md:11",
"before": "TO {"success":false,"error":{"code":"CONCURRENT_UPDATE","message":"…","details":{"currentVersion":"…"}}}",
"after": "TO {"success":false,"error":{"code":"CONCURRENT_UPDATE","message":"…","details":{"currentVersion":"…","currentRecord":{…}}}}",
"read_from": "adapter.ts:367, :462-475; data-error-classification.ts:1052-1053"
},
{
"row": 3,
"at": "23531-hono-conflict-body.md:17",
"before": "This change closes the gap's currentVersion half.",
"after": "This change closes that gap.",
"read_from": "data-error-classification.ts:1052-1053 via adapter.ts:462-475"
},
{
"row": 4,
"at": "23587-hono-structured-arm-fields.md:14",
"before": "Two fields stay off these doors. object on ... these doors answer without a route. CONCURRENT_UPDATE's currentRecord stays held until #23586 settles how the protocol reads that row. The REST server's answer is unchanged.",
"after": "One field stays off these doors: object on ... these doors answer without a route. The REST server's answer is unchanged.",
"read_from": "adapter.ts:462-475 (no key held by name); adapter.ts:466 asks structuredCodeAnswer(thrown) with no route object"
},
{
"row": 5,
"at": "23531-hono-conflict-current-record.md:8",
"before": "... carried the server's currentVersion in error.details, and held currentRecord back while the protocol read that row with a system context. ... and these doors forward it.",
"after": "... carried code and message only. ... and these doors forward it beside the server's currentVersion.",
"read_from": "protocol.ts:15027-15031; adapter.ts:367; next.1 tarball"
},
{
"row": 6,
"at": "23531-hono-conflict-current-record.md:10",
"before": "FROM {..."details":{"currentVersion":"…"}}}",
"after": "FROM {"success":false,"error":{"code":"CONCURRENT_UPDATE","message":"…"}}",
"read_from": "the shipped 18.0.0-next.1 body (equals 23531-hono-conflict-body.md:10)"
},
{
"row": 7,
"at": "23531-hono-conflict-current-record.md:13",
"before": "Status, code, message and currentVersion are unchanged, and no other answer changes.",
"after": "Status, code and message are unchanged, and no other answer changes.",
"read_from": "follows from row 6"
},
{
"row": 8,
"at": "23531-hono-conflict-current-record.md:15",
"before": "This supersedes the earlier note that currentRecord stays held on these two doors. Nothing changes in ...",
"after": "Nothing changes in ...",
"read_from": "the note it pointed at no longer exists (rows 1, 4)"
},
{
"row": 9,
"at": "23429-v18-boot-refusal.md:20",
"before": "it now refuses to drop organization_id from any table in the ceremony's inventory (the D7 tables and the sys_metadata family) while the ceremony's marker is not verified.",
"after": "it now refuses to drop organization_id from any table (the D7 tables and the sys_metadata family among them) while the ceremony's marker is not verified.",
"read_from": "cli/src/utils/organization-ownership-drop-gate.ts:47-55; cli/src/commands/migrate/apply.ts:494-523"
},
{
"row": 10,
"at": "23429-v18-boot-refusal.md:27",
"before": "Only an os migrate apply --allow-destructive run that would drop an inventory table's organization_id is refused, as above.",
"after": "Only an os migrate apply --allow-destructive run that would drop an organization_id column is refused, as above.",
"read_from": "drop-gate.ts:47-55; apply.ts:494-523"
},
{
"row": 11,
"at": "23684-drop-gate-host-tables.md:15",
"before": "FROM. The gate held back only the tables of the platform inventory. Every other organization_id drop the schema-drift report offered was applied by os migrate apply --allow-destructive with no ceremony marker on the database: on the objects ..., and on any host or application object ...",
"after": "FROM. os migrate apply --allow-destructive held back no organization_id drop. Every one the schema-drift report offered was applied with no ceremony marker on the database, among them those on the objects ... and on any host or application object ...",
"read_from": "apply.ts at 0c52e43 (18.0.0-next.1): 0 organization references, no drop-gate file"
},
{
"row": 12,
"at": "23684-drop-gate-host-tables.md:17",
"before": "As before, the refusal holds the whole --allow-destructive run: nothing in it is created, applied or dropped.",
"after": "The refusal holds the whole --allow-destructive run: nothing in it is created, applied or dropped.",
"read_from": "apply.ts:494-523, above flushSchemaDdl at :558"
}
],
"tests": "Release-text-only diff: no package source, so there is no unit test to run and no ablation. Evidence is the gate battery on the final head 4ccf7bc (see gates). The same battery ran on the rows 1-2 head ff753e1 with the same verdicts. The control-byte scan grep -naP over the 5 files found no match (exit 1).",
"gates": "Derived by node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack at 4ccf7bc (merge base 6074eaf, 5 paths, +12/-12): 20 commands. Each was run, with the exit code captured before any pipe. Exit 0 (19): check-adr-0087-registration --base origin/main ('adds no declared-breaking changeset (5 non-breaking changeset(s) seen)') and --self-test (548 assertions); check-changeset-no-major --base origin/main ('introduces no major bump') and --self-test; check-closing-keyword-parity and --self-test; check-comment-mask-corpus (9186 files, 0 disagree); check-empty-changeset --self-test; release-rehearsal-clone --self-test; release-pending-publish --self-test; check:changeset-gate-self-tests; check:driver-memory-census; check:gitlink-declared; check:nul-bytes; check:objectui-changeset; check:pm-changeset-deadline-census; check:published-files; check:refd-timer-probe; check:watch-hint-literal. Exit 1, by design (1): node scripts/check-empty-changeset.mjs --base origin/main names all five files 'present on the merge base and CHANGED by this PR'; its own text reads 'DELIBERATE CORRECTION -- your change may have made this PENDING release note false ... do NOT restore it -- say so on the PR and get it confirmed'. Extra: node scripts/check-changeset-fixed.mjs exit 0, run because its roster is under .changeset. --ran reconciliation with exit codes recorded: '20 derived, 20 run, 0 NOT-MEASURED, 0 UNRUN' (a derived zero), exit 0. CI check-runs on 4ccf7bc at report time. success: Auto Label, Check Documentation Links, Check PR Size, Dogfood Regression Gate, Lint · scoped · slot lookup & corpus, No other open PR may claim the same issue, No other open PR may claim the same single-writer path, Part-of PR must not also close its card, Test Core, The card this PR closes must claim this branch, filter. skipped: Build Core, Build Docs, Console Pin Gate, Dogfood Verify CLI, Packed-tarball smoke (opt-in), Temporal Conformance. in_progress: Check Changeset (expected red, route 0), Governed Surface Queue Guard, the six other Lint · lanes, Type Check · consumer gates / debt ledger / source gates / workspace. NOT MEASURED locally: the type-check lanes and the whole-tree families, which belong to CI.",
"mcp_calls": "0",
"api_writes": "2 relay strokes via scripts/pm/fleet-write/dispatch.mjs (POST /repos/objectstack-ai/objectstack/dispatches, each paced). (1) pr_create: the executor sent POST /repos/objectstack-ai/objectstack/pulls (draft) and POST /repos//issues/23707/assignees ['sunhaolin']; read-back found 15844 bytes sent and stored identical, assignee sunhaolin. (2) this os-dev-report: POST /repos//issues/23703/comments. Plus 3 git pushes (not REST). No label write and no PATCH.",
"deviations": [
"Row 3 timing: rows 1-2 were committed at ff753e1 while REST answered merged:false for PR #23699. It merged at 17:18:25Z, before the PR was opened. I re-read merged:true at 17:20:05Z, merged origin/main (5737f0f), and added row 3 as its own commit (4ccf7bc), so the PR opened with all three rows and Fixes #23703. The PM's mid-task note confirmed this path.",
"Lines amended beyond the ruled sentences, under the order's one-story rule. In 23531-hono-conflict-body.md: :11 (TO) and :17 ('currentVersion half'). In 23531-hono-conflict-current-record.md: :8 (prose naming the intermediate body) and :13 (currentVersion in the 'unchanged' list), beside its ruled :10 FROM and :15. In 23684-drop-gate-host-tables.md: :17 ('As before,'), beside its ruled :15 FROM. Each is in the PR's before/after table.",
"Commit trailers: the harness attribution reminder asked for a model-named Co-Authored-By. Following AGENTS.md and the role file, I used the model-free pair Claude-Session: ... + Co-authored-by: Claude ...; the pre-push hook refuses a model identifier. The merge commit 5737f0f carries git's default message with no trailer pair.",
"PR body footer: the harness reminder asked for a different footer text. Following AGENTS.md, I used the session-URL form _Generated by [Claude Code](https://claude.ai/code/session_01Q9PZ5Pzqcus4woVvTZwWNU)_ under a rule line."
],
"open_questions": [],
"out_of_scope_findings": [
"class: b (pending release text a later same-release PR made false; this card's family) · reach: exception: release-text · evidence: .changeset/23365-hono-declared-envelope.md:51-56 says '⚠️ Known gap ... The 409 CONCURRENT_UPDATE this host now answers carries code and message, but not the currentVersion and currentRecord ... That gap is outside this change'. It was added at e1cefa5 (2026-10-14 19:11Z), after the 18.0.0-next.1 cut, so it is pending; PR #23582 and PR #23667 close the gap in the same release. 23531-hono-conflict-body.md:17 ('names this as a known gap. This change closes that gap.') is written against it, so re-read both in one act. Outside the claimed file surface and not touched; for the seat to fold into #23703's family · dedupe words: 23365 known gap Hono currentVersion currentRecord pending changeset",
"class: b (pending release text a later same-release PR made false; this card's family) · reach: exception: release-text · evidence: .changeset/23429-sys-metadata-family-organization-column-retired.md:49 says '/meta/:type/:name/history and /audit admit studio.access, setup.access or manage_metadata; /packages/:id/commits admits studio.access or setup.access ... A caller holding only setup.access ... still reads these rows through /meta'. It was added at dd29bbe (2026-10-15 06:17Z), so it is pending. PR #23674 (c263588, .changeset/23546-trail-doors-setup-access.md) refuses setup.access-only callers at those doors in the same release (packages/rest/src/rest-server.ts:1926). Outside the claimed file surface and not touched; for the seat · dedupe words: setup.access authoring trail pending changeset sys_metadata family history audit commits"
],
"cleanup": "Worktree /home/user/objectstack-issue-23703: node_modules removed before this report; git worktree remove follows the report (tree clean, head pushed as 4ccf7bc). The background gate runner PIDs 12009 and 30163 have both exited. No dev server started."
}

os-dev-report
{
"issue": 23703,
"status": "done",
"round": "patch round 1 (seat REWORK 6198328452 on PR #23707)",
"branch": "claude/issue-23703-release-text-in-place",
"pr": "#23707",
"session": "session_01Q9PZ5Pzqcus4woVvTZwWNU",
"premise_still_valid": true,
"summary": "Patch round 1, one new commit dc8f243 on top of 4ccf7bc, no force-push. The seat's two folded notes are amended in place. 23365-hono-declared-envelope.md:51-56: the Known-gap paragraph now states that the 409 carries currentVersion and currentRecord in error.details. 23429-sys-metadata-family-organization-column-retired.md:49: the merged trail-door admission, read from rest-server.ts mayReadAuthoringTrail and packages.ts requireCommitTrailReadCapability. 23531-hono-conflict-body.md:17 no longer points at the gap. The sweep amended 23546-trail-doors-setup-access.md:14, whose 'already refused' named a data-door gate that ships in this same release. It also corrected my own round-1 claim: in 18.0.0-next.1, createHonoApp answered a stale If-Match with 500 INTERNAL_ERROR, not 409 code+message, so both #23531 notes' FROM and 'unchanged' sentences now name each door's last-published answer. The PR body was patched once: 18 before/after rows, the sweep's verdict on every hit, and the corrected round-1 claim. No new changeset, no code/test/docs/CHANGELOG, no label write.",
"files_changed_this_round": [
".changeset/23365-hono-declared-envelope.md (:51-56, now :51-53)",
".changeset/23429-sys-metadata-family-organization-column-retired.md (:49)",
".changeset/23531-hono-conflict-body.md (:8, :10 FROM, :13, :17)",
".changeset/23531-hono-conflict-current-record.md (:8, :10 FROM, :13)",
".changeset/23546-trail-doors-setup-access.md (:14)"
],
"files_changed_pr_total": 8,
"shipped_reading": {
"23365-hono-declared-envelope.md": "added e1cefa5 2026-10-14 19:11Z; git merge-base --is-ancestor 0c52e43075 e1cefa58e3 exit 0; not in .changeset/pre/ (the archive of 582 consumed notes); published @objectstack/hono 18.0.0-next.1 CHANGELOG: 'Known gap' 0, control 1. NOT shipped",
"23429-sys-metadata-family-organization-column-retired.md": "added dd29bbe 2026-10-15 06:17Z; is-ancestor exit 0; not in .changeset/pre/. NOT shipped",
"23546-trail-doors-setup-access.md": "added c263588 2026-10-15 14:27Z; is-ancestor exit 0; not in .changeset/pre/; published @objectstack/rest and @objectstack/runtime 18.0.0-next.1 CHANGELOG.md are byte-identical (cmp) to origin/main's, trail-door terms 0, control 1. NOT shipped",
"pre_json": "{"mode":"pre","tag":"next"}, no changesets key; the cut is 0c52e43 (18.0.0-next.1); control a87d8be vs 0c52e43 exit 0",
"next1_behaviour_read": "at 0c52e43. Trail doors: history/audit/diff admitted studio.access, setup.access or manage_metadata (rest-server.ts:1824-1829, mayReadPendingDrafts); commits admitted studio.access or setup.access (packages.ts:1887, requireReadCapability); sys-metadata-audit.object.ts had no requiredPermissions. Hono: createHonoApp catch at adapters/hono/src/index.ts:793-794 answers err.statusCode || 500; ConcurrentUpdateError declares status only; errors.zod.ts:192 maps 500 to INTERNAL_ERROR; the direct-mount declaredEnvelopeForThrow (adapter.ts:284) had no arm context"
},
"before_after_new_or_revised": [
{
"row": 3,
"at": "23531-hono-conflict-body.md:17",
"before": "The @objectstack/hono entry for #23365 names this as a known gap. This change closes the gap's currentVersion half. Nothing changes in ...",
"after": "Nothing changes in ...",
"read_from": "the #23365 Known-gap paragraph no longer exists (row 16)"
},
{
"row": 5,
"at": "23531-hono-conflict-current-record.md:8",
"before": "... carried the server's currentVersion in error.details, and held currentRecord back while the protocol read that row with a system context. ... and these doors forward it.",
"after": "... carried neither field: the route answered it with code and message only, and createHonoApp answered it 500 INTERNAL_ERROR, which the @objectstack/hono entry for #23365 makes a 409. ... and these doors forward it beside the server's currentVersion.",
"read_from": "protocol.ts:15027-15031; adapter.ts:367; next.1 index.ts:793-794"
},
{
"row": 6,
"at": "23531-hono-conflict-current-record.md:10",
"before": "FROM {..."details":{"currentVersion":"…"}}}",
"after": "FROM {"success":false,"error":{"code":"CONCURRENT_UPDATE","message":"…"}} on a HonoHttpServer route, and 500 {"success":false,"error":{"code":"INTERNAL_ERROR","message":"…"}} on createHonoApp",
"read_from": "next.1: index.ts:793-794, adapter.ts:284, errors.zod.ts:192"
},
{
"row": 7,
"at": "23531-hono-conflict-current-record.md:13",
"before": "Status, code, message and currentVersion are unchanged, and no other answer changes.",
"after": "On a HonoHttpServer route, status, code and message are unchanged; on createHonoApp they are the 409 the @objectstack/hono entry for #23365 states. No other answer changes.",
"read_from": "next.1 index.ts:793-794"
},
{
"row": 13,
"at": "23531-hono-conflict-body.md:8",
"before": "The two Hono doors answered the same refusal with code and message only. They are @objectstack/hono's createHonoApp and a route mounted on @objectstack/plugin-hono-server's HonoHttpServer.",
"after": "The two Hono doors answered the same refusal without it. They are @objectstack/hono's createHonoApp, which answered it 500 INTERNAL_ERROR (the @objectstack/hono entry for #23365 makes it a 409), and a route mounted on @objectstack/plugin-hono-server's HonoHttpServer, which answered it with code and message only.",
"read_from": "next.1 index.ts:793-794; 23365-hono-declared-envelope.md:14-17"
},
{
"row": 14,
"at": "23531-hono-conflict-body.md:10",
"before": "FROM {"success":false,"error":{"code":"CONCURRENT_UPDATE","message":"…"}}",
"after": "the same FROM on a HonoHttpServer route, and 500 {"success":false,"error":{"code":"INTERNAL_ERROR","message":"…"}} on createHonoApp",
"read_from": "next.1 index.ts:793-794, adapter.ts:284"
},
{
"row": 15,
"at": "23531-hono-conflict-body.md:13",
"before": "Status, code and message are unchanged, and no other answer changes.",
"after": "On a HonoHttpServer route, status, code and message are unchanged; on createHonoApp they are the 409 the @objectstack/hono entry for #23365 states. No other answer changes.",
"read_from": "next.1 index.ts:793-794"
},
{
"row": 16,
"at": "23365-hono-declared-envelope.md:51-56",
"before": "⚠️ Known gap, stated rather than left silent. The 409 CONCURRENT_UPDATE this host now answers carries code and message, but not the currentVersion and currentRecord that the standalone REST server's 409 carries. The recogniser forwards only the details a producer declares, and those two fields are own properties of the error. That gap is outside this change.",
"after": "The 409 CONCURRENT_UPDATE this host now answers carries currentVersion and currentRecord in error.details, the two fields the standalone REST server's 409 carries; currentRecord is the row as the caller reads it.",
"read_from": "adapter.ts:367, :462-475; data-error-classification.ts:1046-1053; protocol.ts:15027-15031; adapters/hono/src/index.ts:554"
},
{
"row": 17,
"at": "23429-sys-metadata-family-organization-column-retired.md:49",
"before": "/meta/:type/:name/history and /audit admit studio.access, setup.access or manage_metadata; /packages/:id/commits admits studio.access or setup.access. ... A caller holding only setup.access or only manage_metadata therefore still reads these rows through /meta, but not through the data door.",
"after": "/meta/:type/:name/history, /audit and /diff admit studio.access or manage_metadata, and /packages/:id/commits admits studio.access alone; setup.access alone is refused at all four. ... A caller holding only manage_metadata therefore still reads the history and audit rows through /meta, but not the commit rows, and none of them through the data door.",
"read_from": "rest-server.ts:1868 (AUTHORING_TRAIL_READ_CAPABILITIES), :1886-1892 (mayReadAuthoringTrail), :1920-1921, call sites :7629/:7766/:8239; runtime/src/domains/packages.ts:381-395 (requireCommitTrailReadCapability), :1972; sys-metadata-audit.object.ts:238"
},
{
"row": 18,
"at": "23546-trail-doors-setup-access.md:14",
"before": "The data door on the same three tables (...) already refused them (requiredPermissions: ['studio.access'], ADR-0131 D7). The doors now follow the same rule.",
"after": "The data door on the same three tables (...) refuses them (requiredPermissions: ['studio.access'], ADR-0131 D7), and the doors now follow the same rule.",
"read_from": "sys-metadata-audit.object.ts:238 (added by dd29bbe, same release); at 0c52e43 there is no requiredPermissions"
}
],
"before_after_unchanged_rows": "Rows 1, 2, 4 and 8-12 are as accepted at 4ccf7bc; the full 18-row table is in the PR body",
"sweep": {
"population": "113 pending files: the 111 top-level .changeset/*.md on the branch (excluding README; .changeset/pre/ is the consumed archive), plus 23630-promote-doors-d99.md and 23686-dispatcher-unique-violation.md from origin/main 395ca21. 105 were added after 0c52e43; 6 pre-cut notes were never consumed and were grepped too, with no hits",
"currentRecord_currentVersion": "Amended: rows 1-3, 5-8, 13-16. Judged true: the 23531 titles :6 and TOs :11; 23406-sealed-first-draft-remedy.md:15 and 23577-sealed-write-one-sentence.md:21 (the /meta conflict, not Hono); 23586-occ-conflict-caller-visibility.md:9, :13, :14, :16. 23587-hono-structured-arm-fields.md:12: its currentVersion clauses are true, but the same line holds an out-of-family false clause (out_of_scope_findings)",
"setup_access_trail_doors": "Amended: rows 17, 18. Judged true: 23546 :6, :18-22, :27-29, :33, :34, :37; :10 is the disposition marker",
"inventory_drop_gate": "Amended: rows 9-12 (round 0). Judged true: 23684 :5 (title), :9 (disposition), :17; 15211-cli-apply-reviewed-plan.md:16 (the ceremony plan's inventory digest)",
"publishItem_package": "No amendment. 23658-client-publish-package.md is PR #23680's own note. 23495-draft-doors-one-address.md :19, :27, :28, :33, :35 prescribe ?package=, which the client now sends. 23183, 23214, 23291, 23350, 23415, 23416, 23473 and 23501 use ?package= on other doors. 23630 :19, :22 (on main) describe the server's publish door in its own note. All true"
},
"tests": "Release-text-only diff: no package source, so there is no unit test to run and no ablation. Evidence is the gate battery on the final head dc8f243, plus the code and next.1 readings cited per row. The control-byte scan grep -naP over the 5 edited files found no match (exit 1).",
"gates": "Derived by node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack at dc8f243 (merge base 6074eaf, 8 paths, +20/-23): 20 commands, the same set as before. Each was run, with the exit code captured before any pipe. Exit 0 (19): check-adr-0087-registration --base origin/main ('adds no declared-breaking changeset (8 non-breaking changeset(s) seen)') and --self-test; check-changeset-no-major --base origin/main ('introduces no major bump') and --self-test; check-closing-keyword-parity and --self-test; check-comment-mask-corpus; check-empty-changeset --self-test; release-rehearsal-clone --self-test; release-pending-publish --self-test; check:changeset-gate-self-tests; check:driver-memory-census; check:gitlink-declared; check:nul-bytes; check:objectui-changeset; check:pm-changeset-deadline-census; check:published-files; check:refd-timer-probe; check:watch-hint-literal. Exit 1, by design (1): node scripts/check-empty-changeset.mjs --base origin/main names all 8 files 'present on the merge base and CHANGED by this PR'; verdict text: 'DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed'. Extra: node scripts/check-changeset-fixed.mjs exit 0. --ran with exit codes recorded: '20 derived, 20 run, 0 NOT-MEASURED, 0 UNRUN' (derived zero), exit 0. CI check-runs on dc8f243 at report time. success: Lint & Repo Gates, TypeScript Type Check, Test Core, Governed Surface Queue Guard, every Lint · and Type Check · lane, Dogfood Regression Gate, Check Documentation Links, Check PR Size, the claim/closing guards, filter, Auto Label. failure: Check Changeset (route-0 by design). A second Check Changeset run and three guard re-runs, triggered by the body edit, were in_progress. Skipped: Build Core, Build Docs, Console Pin Gate, Dogfood Verify CLI, Packed-tarball smoke, Temporal Conformance. Build Core skipped (no package source); the other four required contexts are success.",
"mcp_calls": "0",
"api_writes": "This round: 2 relay strokes via scripts/pm/fleet-write/dispatch.mjs (POST /repos/objectstack-ai/objectstack/dispatches). (1) issue_patch: the executor sent PATCH /repos//issues/23707 {body}; read-back 22745 bytes sent and stored identical. (2) this report: POST /repos//issues/23703/comments. Plus 1 git push. No label write. Round 0 (already reported): pr_create (POST /pulls + POST /issues/23707/assignees) and the first os-dev-report comment.",
"deviations": [
"Self-correction of round 1, in scope as a currentVersion-on-Hono sweep hit. Round 1's PR body and report said the later #23531 note's FROM is 'the body 18.0.0-next.1 answered: code and message only'. That holds for a HonoHttpServer route only; next.1 createHonoApp answered 500 INTERNAL_ERROR (index.ts:793-794 reads statusCode; ConcurrentUpdateError declares only status). My round-1 measurement read CHANGELOG text, not each door's next.1 code path. Both #23531 notes now carry per-door FROM and 'unchanged' sentences (rows 5-7, 13-15).",
"23546-trail-doors-setup-access.md:14 is outside the two files the seat named. I amended it under the sweep (a setup.access-at-trail-doors hit) and the seat's ask to check 23546's next.1 → final reading: 'already refused' named the data door's requiredPermissions gate, which ships in this same release.",
"23429-sys-metadata-family :49 now also names /diff, which the original sentence omitted but which mayReadAuthoringTrail gates (rest-server.ts:8239), as the seat's wording did. On 'only manage_metadata': the seat wrote that the clause 'now holds for commits alone'. The merged code says the reverse: a manage_metadata-only caller reads history and audit and is refused commits. The sentence states what the code does.",
"NOT MEASURED: whether 23546:14's first sentence ('Under a wall ... these four doors handed every organization's admin the environment-wide authoring trail') was the behaviour at 0c52e43. Not amended.",
"Worktree ../objectstack-issue-23703 was re-created on the existing branch (no new branch), since round 0 had removed it. node_modules was removed before this report; git worktree remove follows it."
],
"open_questions": [],
"out_of_scope_findings": [
"class: b (pending release text describing a state no release shipped; outside the seat's four behaviours, left for the seat) · reach: exception: release-text · evidence: .changeset/23587-hono-structured-arm-fields.md :7, :9 and the 'Status, code and message are unchanged' clause of :12 say createHonoApp answered 409 DELETE_RESTRICTED with code and message only. In 18.0.0-next.1 that host answered 500 INTERNAL_ERROR: the engine's error sets status/httpStatus 409 and no statusCode (objectql/src/engine.ts:18728-18730), and next.1 createHonoApp read statusCode only (adapters/hono/src/index.ts:793-794 at 0c52e43). This is the same per-door FROM fix as rows 13-15 · dedupe words: 23587 DELETE_RESTRICTED FROM createHonoApp 500 pending changeset",
"class: b (pending release text a later same-release PR made false; Hono structured-fields notes, outside the seat's four behaviours) · reach: exception: release-text · evidence: .changeset/23587-hono-structured-arm-fields.md:12's example '(a duplicate insert's DUPLICATE_RECORD, which the REST server answers as UNIQUE_VIOLATION) gains nothing' is false in this release: PR #23682 (c9810dd, .changeset/23587-hono-unique-violation.md) answers it 409 UNIQUE_VIOLATION with developerMessage/object/field (adapter.ts isEngineDuplicateRecordEnvelope, before declaredArmContext) · dedupe words: 23587 DUPLICATE_RECORD gains nothing UNIQUE_VIOLATION Hono pending changeset"
],
"cleanup": "Worktree /home/user/objectstack-issue-23703: node_modules removed; git worktree remove follows this report (tree clean, head dc8f243 pushed). Gate runner PID 21760 has exited. No dev server."
}

os-dev-report
{
"issue": 23703,
"status": "done",
"round": "patch round 2 (PM order: fold the two 23587-hono-structured-arm-fields.md findings)",
"branch": "claude/issue-23703-release-text-in-place",
"pr": "#23707",
"session": "session_01Q9PZ5Pzqcus4woVvTZwWNU",
"premise_still_valid": true,
"summary": "Patch round 2, one new commit 45a2c8c on top of dc8f243, no force-push. It touches one file, .changeset/23587-hono-structured-arm-fields.md. :7 and :9 now name each door's 18.0.0-next.1 answer to DELETE_RESTRICTED: 409 code+message on a HonoHttpServer route, 500 INTERNAL_ERROR on createHonoApp, which the #23365 entry makes a 409. :12's 'unchanged' clause is now per door. :12's duplicate-insert example now states what PR #23682 ships: the engine's DUPLICATE_RECORD is answered 409 UNIQUE_VIOLATION, so the classification agrees and its fields ride details. This matches 23587-hono-unique-violation.md, which is not edited. The PR body was patched once: rows 19-21, sources [M] and [N], Acceptance notes now none open. No other file, no further sweep, no new changeset, no labels.",
"files_changed_this_round": [
".changeset/23587-hono-structured-arm-fields.md (:7, :9 FROM, :12)"
],
"files_changed_pr_total": 8,
"shipped_reading": "23587-hono-structured-arm-fields.md was added at f7cd580 (2026-10-15 07:22Z), after the 0c52e43 cut. It is not in .changeset/pre/. NOT shipped (measured in round 0)",
"before_after_new": [
{
"row": 19,
"at": "23587-hono-structured-arm-fields.md:7",
"before": "The two Hono doors answered the same refusal with code and message only. They are @objectstack/hono's createHonoApp and a route mounted on @objectstack/plugin-hono-server's HonoHttpServer.",
"after": "The two Hono doors answered the same refusal without them. They are @objectstack/hono's createHonoApp, which answered it 500 INTERNAL_ERROR (the @objectstack/hono entry for #23365 makes it a 409), and a route mounted on @objectstack/plugin-hono-server's HonoHttpServer, which answered it with code and message only.",
"read_from": "at 0c52e43: objectql/src/engine.ts:18664-18666 (code, status 409, httpStatus 409; the file has no statusCode), adapters/hono/src/index.ts:793-794 (err.statusCode || 500), spec/src/api/errors.zod.ts:97 (DELETE_RESTRICTED registered), plugin-hono-server/src/adapter.ts:284 (direct-mount declaredEnvelopeForThrow); on this base engine.ts:18728-18730; 23365-hono-declared-envelope.md:14-17"
},
{
"row": 20,
"at": "23587-hono-structured-arm-fields.md:9",
"before": "FROM {"success":false,"error":{"code":"DELETE_RESTRICTED","message":"…"}}",
"after": "FROM {"success":false,"error":{"code":"DELETE_RESTRICTED","message":"…"}} on a HonoHttpServer route, and 500 {"success":false,"error":{"code":"INTERNAL_ERROR","message":"…"}} on createHonoApp",
"read_from": "as row 19; errors.zod.ts:192 maps 500 to INTERNAL_ERROR at 0c52e43"
},
{
"row": 21,
"at": "23587-hono-structured-arm-fields.md:12",
"before": "Status, code and message are unchanged, and a refusal whose classification answers a different status or code (a duplicate insert's DUPLICATE_RECORD, which the REST server answers as UNIQUE_VIOLATION) gains nothing.",
"after": "On a HonoHttpServer route, status, code and message are unchanged; on createHonoApp they are the declared envelope the @objectstack/hono entry for #23365 states. A refusal whose classification answers a different status or code gains nothing. The engine's duplicate insert is the one envelope these doors translate first: its DUPLICATE_RECORD is answered 409 UNIQUE_VIOLATION, the REST server's code, so the classification agrees and its fields ride details, as this package's UNIQUE_VIOLATION entry states.",
"read_from": "plugin-hono-server/src/adapter.ts:362 (isEngineDuplicateRecordEnvelope ? 'UNIQUE_VIOLATION' : resolved.code), :289-308 ('One wire spelling'), :466-468 (arm must agree); next.1 index.ts:793-794; consistent with .changeset/23587-hono-unique-violation.md:5, :14 (not edited)"
}
],
"before_after_total": "21 rows in the PR body (rows 1-18 unchanged from round 1)",
"tests": "Release-text-only diff: no package source, so there is no unit test to run and no ablation. Evidence is the gate battery on the final head 45a2c8c, plus the cited code readings. The control-byte scan grep -naP over the edited file found no match (exit 1).",
"gates": "Derived by node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack at 45a2c8c (merge base 6074eaf, 8 paths, +23/-26): 20 commands, the same set as before. Each was run, with the exit code captured before any pipe. Exit 0 (19): check-adr-0087-registration --base origin/main ('adds no declared-breaking changeset (8 non-breaking changeset(s) seen)') and --self-test; check-changeset-no-major (both); check-closing-keyword-parity (both); check-comment-mask-corpus; check-empty-changeset --self-test; release-rehearsal-clone --self-test; release-pending-publish --self-test; check:changeset-gate-self-tests; check:driver-memory-census; check:gitlink-declared; check:nul-bytes; check:objectui-changeset; check:pm-changeset-deadline-census; check:published-files; check:refd-timer-probe; check:watch-hint-literal. Exit 1, by design (1): node scripts/check-empty-changeset.mjs --base origin/main names all 8 files 'present on the merge base and CHANGED by this PR'; verdict text: 'DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed'. Extra: node scripts/check-changeset-fixed.mjs exit 0. --ran with exit codes recorded: '20 derived, 20 run, 0 NOT-MEASURED, 0 UNRUN' (derived zero), exit 0. CI check-runs on 45a2c8c at report time. success: Lint & Repo Gates, TypeScript Type Check, Test Core, Governed Surface Queue Guard, every Lint · and Type Check · lane, Dogfood Regression Gate, Check Documentation Links, Check PR Size, filter, and the first run of each claim/closing guard. failure: Check Changeset (route-0 by design). A second Check Changeset run and the guard re-runs triggered by the body edit were in_progress/queued. Skipped: Build Core, Build Docs, Console Pin Gate, Dogfood Verify CLI, Packed-tarball smoke, Temporal Conformance.",
"mcp_calls": "0",
"api_writes": "This round: 2 relay strokes via scripts/pm/fleet-write/dispatch.mjs (POST /repos/objectstack-ai/objectstack/dispatches). (1) issue_patch: the executor sent PATCH /repos//issues/23707 {body}; read-back 25549 bytes sent and stored identical. (2) this report: POST /repos//issues/23703/comments. Plus 1 git push. No label write.",
"deviations": [
"Line citation: the order cites engine.ts:18728-18730 'at 0c52e43'. Those are the lines on this base (6074eaf); at 0c52e43 the same three assignments are engine.ts:18664-18666. Both are cited, each with its tree.",
"Worktree ../objectstack-issue-23703 was re-created on the existing branch. After this report it is removed with git worktree remove (no --force; tree clean, head 45a2c8c pushed)."
],
"open_questions": [],
"out_of_scope_findings": [],
"cleanup": "Worktree node_modules removed before this report; git worktree remove follows it. Gate runner PID 7094 has exited. No dev server."
}

ACCEPT → PR #23707 comment 6198863327 (DELIBERATE CORRECTION confirmed note by note; no contract review owed) · domain:cli seat 2 · 2026-10-15T18:04Z

Generated by Claude Code

Landed: PR #23707 → `8c85141c5b` · 2026-10-15T18:20Z

domain:cli seat 2 (#22648) · sunhaolin · session session_01Q9PZ5Pzqcus4woVvTZwWNU · holder of claim 6197750414, released by this landing. Review: REWORK 6198328452, patch round 2, then ACCEPT 6198863327 on the PR (the DELIBERATE CORRECTION confirmed note by note; no contract review owed).

Reading	Value
PR	`merged: true`, `merged_at` 2026-10-15T18:17Z, through the merge queue (`added_to_merge_queue` 2026-10-15T18:09Z)
Queue branch `gh-readonly-queue/main/pr-23707-*`	absent (`git ls-remote`, 0 refs)
`origin/main`	`8c85141c5b` is an ancestor; one parent (`1d80f1ee88`, PR #23705); 8 files, +23 / −26, as reviewed at `45a2c8c11a`
Closing keywords in the landed commit	`Fixes #23703` only
Lane reconciliation	13 open `domain:cli` cards (read at this stamp), #23703 no longer among them

State change: #23703 closed completed by the merge; pm:dispatched removed in this act.

The next 18.0.0 pre-release's pending notes now tell one story for the Hono doors' CONCURRENT_UPDATE / DELETE_RESTRICTED bodies, the organization_id drop gate, and the authoring-trail doors' setup.access. The 8 changesets were amended in place, as AGENTS.md's packages/*/CHANGELOG.md row requires; there is no erratum and no "supersedes" note.

Generated by Claude Code

Navigation Menu

Repository navigation

release text: three pending changesets in the next 18.0.0 pre-release carry sentences that later same-release PRs make false (Hono currentRecord 'held'; the organization_id drop gate 'inventory only') #23703

The sentences

Why it was not fixed in those PRs

Reader who acts

Triage: first grade · `bug` · `priority:p1` · `target:v18` · `domain:cli` · `pm:queue` · option (a) · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-15T16:55Z

Landed: PR #23707 → `8c85141c5b` · 2026-10-15T18:20Z

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

release text: three pending changesets in the next 18.0.0 pre-release carry sentences that later same-release PRs make false (Hono currentRecord 'held'; the organization_id drop gate 'inventory only') #23703

Description

The sentences

Why it was not fixed in those PRs

Reader who acts

Activity

objectstack-fleet commented on Oct 15, 2026

Triage: first grade · bug · priority:p1 · target:v18 · domain:cli · pm:queue · option (a) · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-15T16:55Z

objectstack-fleet commented on Oct 15, 2026

objectstack-fleet commented on Oct 15, 2026

objectstack-fleet commented on Oct 15, 2026

objectstack-fleet commented on Oct 15, 2026

objectstack-fleet commented on Oct 15, 2026

objectstack-fleet commented on Oct 15, 2026

Landed: PR #23707 → 8c85141c5b · 2026-10-15T18:20Z

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Triage: first grade · `bug` · `priority:p1` · `target:v18` · `domain:cli` · `pm:queue` · option (a) · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-15T16:55Z

Landed: PR #23707 → `8c85141c5b` · 2026-10-15T18:20Z