release 18.3.0: #29923's fail-closed type-mismatch refusal shipped in the 18.3.0 packages with no CHANGELOG line (its changeset was not consumed) #29957

domain:server#6 · os-support-ai · session_01WGufzibcN9oHa8kDbTTnL5

Filing gate: ① a release defect with a named landing point. Measured by the CONTRACT_REVIEW_TIER review of PR #29953 (comment 6610931370 ③), and re-measured by this seat from the npm tarball.
Business reason: an operator upgrading to 18.3.0 reads the CHANGELOG and the 18.3 release page to learn what now refuses. #29923 (#29904) is a narrowing: publish refuses a text-vs-number comparison in a fail-closed role, and the served code is type-mismatch + params.outcome: 'fail-closed'. It is in the 18.3.0 packages, but its changelog entry is missing. So 18.3.0 refuses metadata it accepted in 18.2.0, and the release notes never say so.
Reader who acts: the release lane (domain:devx, which compiled the 18.3 page, #29933), plus whoever owns the version-packages flow.
Dedupe (open and closed): 18.3.0 changelog version-packages. Nearest is #29933 (closed: the 18.3 release page), which does not cover a changeset the cut skipped.

Measured

• @objectstack/formula@18.3.0 (npm, published 2026-11-03T15:09:01Z) carries fail-closed in dist/index.d.ts (10 hits) and dist/index.js (3). @objectstack/mcp@18.3.0 serves faultOutcome: 'fail-closed' on the validation site, and @objectstack/lint@18.3.0 ships the fail-closed grading.
• The *@18.3.0 GitHub releases target 83d7e4ae (chore: version packages (#26517)). fix(lint)!: publish refuses a text-vs-number comparison in a validation rule (or another fail-closed predicate) instead of warning, then refusing every write #29923's merge 4c2cd29a is an ancestor.
• .changeset/29904-type-mismatch-fail-closed.md is still pending on main. The version-packages PR chore: version packages #26517 branched before 4c2cd29a and was merged without regenerating, so the three shipped CHANGELOGs mention neither publish gate: a validation rule comparing a text field with a number (record.name > 5) publishes with only a warning that says it "evaluates to null", then every write to the object is refused #29904 nor fix(lint)!: publish refuses a text-vs-number comparison in a validation rule (or another fail-closed predicate) instead of warning, then refusing every write #29923. Any other changeset merged between chore: version packages #26517's branch point and 83d7e4ae is in the same state: list them.

What to fix

1. A docs-only erratum for 18.3.0: a line in the 18.3 release page (content/docs/releases/v18/18-3.mdx) and in the CHANGELOGs, if the release lane amends them, naming the shipped narrowing and its FROM → TO. The pending changeset will be consumed by the next release, where PR fix(lint)!: a type mismatch in a record-triggered flow condition or an advisory validation rule is served a verdict that says what really happens #29953 (expression gate: a type mismatch in a record-triggered flow condition (and in an advisory validation rule) is served a verdict whose text is false for that role #29926) already says the arm shipped in 18.3.0 and renames it.
2. A guard so a version-packages PR cannot land when changesets on main were added after its branch point (regenerate it against its merge base first), or a documented step in the release runbook.