chore(sync): record nuxt/ui@927786c and nuxt/ui@bab8c5a, closing the v4.11.2 batch

[IgorShevchik]

Linked issue

Closing bookkeeping PR for the v4.11.2 sync batch. Two contiguous upstream
commits (§6 4b), neither of which changes code here:

• nuxt/ui@927786c — chore(github): disable tia dry run → n/a
• nuxt/ui@bab8c5a — chore(release): v4.11.2 → no-op

Type of change

• Documentation (updates to the documentation or readme)
• Bug fix (a non-breaking change that fixes an issue)
• Enhancement (improving an existing functionality)
• New feature (a non-breaking change that adds functionality)
• Chore (updates to the build process or auxiliary tools and libraries)
• Revert (undoing a merged change — retitle this PR revert(Scope): ...)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

927786c3 — n/a. Drops dryRun: true from .github/tia.yml, the config
for a triage bot installed on the nuxt organisation. Third in the run that
starts at 80932f85 (#631). Taking that bot out of dry run is a decision about
how issues are triaged in nuxt/ui; this fork has no bot config of any kind, so
there is nothing here to take out of dry run.

bab8c5af — no-op. Upstream's release bookkeeping: package.json version
4.11.1 → 4.11.2, plus 25 generated CHANGELOG.md lines. Both files exist
here, which is why this is a no-op rather than n/a, and it matches the
decision every prior upstream chore(release) carries in this ledger (v4.8.0,
v4.8.1, v4.8.2, v4.9.0, v4.10.0, v4.11.0). Nothing to take: this fork publishes
@bitrix24/b24ui-nuxt on its own version line, and its CHANGELOG.md is
generated by release-please from the subjects of the commits merged here —
which is exactly why §6 requires each port's subject to carry (nuxt/ui@<sha>).

The release section as an audit

The generated section names every commit in the release, so it is a free
independent check on the queue. All 20 SHAs it lists are in processed:

decision	count	SHAs
port	19	0317d50 #629 · 074152b #628 · 187c34f #627 · 22efd35 #566 · 27a3ef7 #611 · 27a5fe4 #630 · 2b29c33 #570 · 619c732 #611 · 6d6737a #559 · 74ad017 #622 · 796f79d #621 · 7c4c6e3 #599 · 8e4546e #609 · 9076ca2 #556 · 9ea37c1 #617 · aab2d10 #609 · b3d4342 #609 · c617565 #623 · cf9e838 #567
no-op	1	a96823d #612

Nothing missing, and the single no-op is the one expected to be there:
a96823d (Table inset row focus outline) was recorded as a no-op in #612
because the outline work had already landed here, in #614, from a different
starting point.

Bookkeeping

Ledger advanced to bab8c5af (357 entries), which is upstream v4's current
tip. Journals for both SHAs. dep-parity.json re-snapshotted at the new cursor
— cursor line only, no version drift, including across upstream's own release
bump. Reconciles all three entries #631 added (80932f85, 8b7f3288,
e47e2dd6) with #631 / bf84ad9f, so no unreconciled entry sits behind a
reconciled one.

Gate run locally with CI=true: dev:prepare · lint · typecheck · build ·
test:coverage (361 files, 8181 passed, 6 skipped) · test:module — all green.
No docs/ change, so docs:full:generate is not in this run.

Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JS8ypVfQSFzYVZzkTHhURb

---

Generated by Claude Code