Skip to content

fix(release): backport twenty-one user-facing fixes to 0.12.0 line (s3b3) - #33549

Merged
buluoray merged 21 commits into
release/0.12.0from
crew/slack/0.12.1-s3b3
Nov 9, 2026
Merged

buluoray merged 21 commits into
release/0.12.0from
crew/slack/0.12.1-s3b3

Conversation

@buluoray

@buluoray buluoray commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: 0.12 users get twenty-two user-facing fixes that are on main but not on the 0.12.0 line, in 0.12.1.

Each fix below merged to main and was checked as not on release/0.12.0 (no PR number, no cherry picked from line, no matching patch-id, and the pick still changes the tree). Each is something a 0.12 user hits today.

Why it matters

These are bugs 0.12 users hit now: a deb that will not install on Ubuntu 24.04+, KAS sessions missing from the Usage page, a first reply that stalls after every restart, a cancelled update that leaves its git child running, lost crash dumps, and focus that jumps off buttons while they run. Without a backport they wait for 0.13.

Not a goal

  • Any fix that conflicts in source code, or needs a PR that is not on the release line. Those are listed under "Dropped" below.
  • Rewording or hand-merging spec prose that changed differently on each branch.
  • New features, refactors, CI, test and dev-tool changes.

What changed (motivation → approach → change)

Every commit is git cherry-pick -x of the main merge commit onto release/0.12.0 at 7a89cc18d60f581d994b18afd6a3d0c8ef0b0e23, in main merge order. The commit author is the release line's public identity, as on every other commit on this branch (the repo's leak guard refuses the original author emails); the cherry picked from commit line in each message names the source.

Picked cleanly (16):

PR What users hit
#31572 approve on a collapsed skill candidate is greyed out with no reason
#32295 Escape does not leave a video's fullscreen on desktop
#32448 deb install fails on Ubuntu 24.04+ where libasound2 is replaced by libasound2t64
#32414 multi-line shell commands render as one squashed line in the tool tip
#32501 stdio MCP probe uses a smaller read limit than the runtime, so big servers fail the probe
#32485 a split pane draws its reply twice when history lands mid-stream
#32510 the first reply after a restart stalls while every skill is scanned
#32444 AWS Control keeps a stale probe and hides a failing key's error
#32381 cancelling a starting update leaves its git child running
#32270 a remote-crew desktop window gets local-only bridges
#32251 the browser harness install fails late when pillow cannot build
#32519 retired knowledge keys linger in config after settings saves
#32481 a remote crew pane fails to connect with no reason shown
#26951 the Usage page shows no KAS sessions
#25315 a cron parent's session is not reset after its completion reaches the open tab
#32536 focus jumps off the app migration cleanup buttons while they run

Picked with conflicts only in docs, tests or translation catalogs (5). Each was resolved by keeping release's existing entries and adding only the entries the PR itself adds:

PR What users hit Hand-resolved file
#32332 the MCP Measure button counts servers a pass can never finish docs/decisions/README.md: kept release's rows, added this PR's 2026-11-07 row (the other row main has there belongs to a decision not on this line)
#32315 the Tailscale invite copy implies the email carries a Crew link the 13 website/src/i18n/locales/*.json catalogs: kept release's keys, added this PR's three invite_email_hint* keys
#32545 the ACP hooks and subprocess labels are English in every language website/src/i18n/en.context.json: kept release's entries, added this PR's two ACP label entries
#32865 app pop-out exits, shortcuts and labels misbehave website/src/i18n/locales/en.json: kept release's direct_link_note, added this PR's new shell.nav.appRowPopoutAction block
#32631 Settings search cannot find the Feishu channel's settings src/kiro_crew/docs/ui-index.generated.json (generated): regenerated with npm run gen:ui on the picked source, which adds only the Feishu settings entries

Dropped (not in this PR):

Backwards compatibility

Compatible: each commit is the fix main already ships, with no new keys, routes or settings beyond what its PR added.

Removes nothing: the only removals are those the picked PRs make on main (#32865 replaces its own pop-out catalog keys and code together).

Tests

Run on this branch, one process at a time, no xdist:

  • Python: the 18 test files the kept commits add or change, in a clean Python 3.12 venv (uv pip install -e . --group dev), PYTHONNOUSERSITE=1, one file at a time, -n0: all pass (run on the 22-pick head; after dropping fix: keep the crash dump of a gateway that died without a clean exit #32205 the slack gateway, update-apply and sub-agent injection files were re-run and pass).
  • Vitest: the 18 website test files the kept commits add or change, plus src/i18n: 71 files, 1197 tests pass.
  • Electron: node --require ./test/_preload.cjs --test on the 4 touched electron test files: 127 pass.
  • npx tsc -p tsconfig.app.json --noEmit: clean.
  • npm run i18n:check against the release head: 19 checks PASS. node scripts/check-i18n-keys.mjs: all references resolve.

Proof: not provable -- other: a release backport; each fix was proven by its own PR on main

Manual verification

N/A — each fix is the change main already ships and was verified there; the tests above re-run on the release line.

Screenshots / video

Why no screenshot: every UI change here is a backport of a main PR that carried its own screenshots, and the backport changes nothing beyond it.

Related Issues

Backports #31572, #32295, #32448, #32414, #32501, #32485, #32510, #32444, #32381, #32270, #32251, #32519, #32481, #26951, #25315, #32536, #32332, #32315, #32545, #32865 and #32631 to the 0.12 line. Sibling batches: #33529 and #33530. A rebase may be needed once those land.

Sibling sweep

Siblings: none -- a backport batch; each source PR carried its own sweep on main.

Pattern harvest

Not generalizable: a release backport of fixes already harvested on main.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

Contribution License Agreement

Contributions are accepted under the project's Apache-2.0 license; see the Licensing section of CONTRIBUTING.md.

@buluoray
buluoray requested review from a team and KiroCrewCaptain as code owners November 9, 2026 01:23
@buluoray
buluoray requested review from tim-finnigan and removed request for a team November 9, 2026 01:23
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 9, 2026
@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 7563c2cf2a3e47acd42e0e3f9fd475eb24b5b1ed — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks: the batch backports fixes main already ships, every pick is accounted for, and the platform-specific picks (deb deps, Electron fullscreen) are byte-identical to their verified main PRs.

Notes

[DESIGN-REVIEWED] 7563c2c

Description read

[DESCRIPTION-READ] a56340d678d1675a6ebb15893dbd4ef29fd22690f6a29150c35b3a2c6022737e

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 7563c2cf2a3e47acd42e0e3f9fd475eb24b5b1ed — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

First-Principles-Verdict: PASS

Every item is a cherry-pick of a fix that already merged on main. Each one carries the main PR's own provenance and adds nothing beyond what that PR shipped.

What this change ships

Inventory (10 items) — 10 justified

Intent: 0.12 users get fixes that are already on main in 0.12.1, without waiting for 0.13. This is a FIX (a backport batch). There are 21 picks; the 10 most noticeable are listed here.

  1. The deb installs on Ubuntu 24.04+, where libasound2 has become libasound2t64 (fix(desktop): depend on libasound2t64 before libasound2 in the deb #32448) — justified
  2. The Usage page lists KAS sessions (fix(usage): count KAS sessions on the Usage page #26951) — justified
  3. The first reply after a restart no longer stalls while every skill is scanned (fix: stop the first reply after a restart scanning every skill #32510) — justified
  4. Cancelling an update while it starts also stops its git child (fix(update): kill a starting git-update child's group when cancelled #32381) — justified
  5. Approving a collapsed skill candidate says why the button is greyed out (fix: explain why approve is disabled on a collapsed skill candidate #31572) — justified
  6. Escape leaves a video's fullscreen on desktop (fix(desktop): let Escape end a video's fullscreen instead of sticking #32295) — justified
  7. The stdio MCP probe reads as much as the runtime does, so large servers pass it (fix: probe stdio mcp servers with the runtime read limit #32501) — justified
  8. MCP Measure counts only servers a pass can still finish, with its 2026-11-07 decision row (fix: count only servers a measure pass can still finish #32332) — justified
  9. The app pop-out exits, shortcuts and labels work, including screenshots under temp-screenshots/ (fix: keep app pop-out exits, shortcuts and labels honest #32865) — justified
  10. Settings search finds the Feishu channel's settings, with the UI index regenerated (fix(settings): find the feishu channel's settings in search #32631) — justified

[FIRST-PRINCIPLES-REVIEWED] 7563c2c

Description read

[DESCRIPTION-READ] fccae642824f8aa47d9b6f8a937a8e2ca7827a58e1a38dc907f6a2fe1e55b34c

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS (a BLOCK with no Trigger and no Outcome does not block)

UX-level review of 7563c2cf2a3e47acd42e0e3f9fd475eb24b5b1ed — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

UX-Verdict: PASS

cannot evaluate: missing screenshots of every changed surface except the app pop-out. The three supplied images cover only #32865. The no-visual-delta claim doesn't hold, because this PR adds new visible copy, new tips and new error states, and a screenshot in the source PR on main is not evidence for this release-line revision.

Evidence gaps

  • Tailscale invite: no image of the new invite-email-hint line in any of its three states (invite_email_hint, _off, _unavailable). Close with a screenshot of Settings → invite result for each state.
  • Skills tab: no image of the collapsed Approve button, now dimmed with aria-disabled, or its new HoverTip approve_review_first. Close with a screenshot of the collapsed row with the tip showing.
  • AWS Control: no image of the new per-row probe error notice reconnect-detail in ConsoleView. Close with a screenshot of a failing key's row.
  • Remote crew pane (InstancesViewport): no image of the new failure reason (activeConnectError) in the panel. Close with a screenshot of a refused connect.
  • Tool command tip: no image of multi-line commands now rendered as separate rows, with blank rows kept at full height (min-h-[1.55em]). Close with a screenshot of a heredoc or multi-line command tip.
  • Migration cleanup buttons: no image of the busy state, now shown with aria-disabled and opacity-30. Close with a screenshot while cleanup runs.
  • Usage page: no image of KAS sessions now listed. MCP Measure button: no image of the corrected count. Close with a screenshot of each.

Notes

  • The pop-out title-bar hover text is now "Return to main window and close this popout". The blind reader, who saw the German version, was unsure "whether it closes this window or loses something I have open". The new wording answers that, so keep it.

[UX-REVIEWED] 7563c2c

Description read

[DESCRIPTION-READ] acbdb9b576b5ef77a17e18a1b07af6091831148b1a08abb5277d9ac70959cab6

That sha256 names everything this verdict read: the PR description, plus the 6 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@buluoray buluoray added the posix-only-approved Cross-Platform Portability findings reviewed and accepted as intentionally POSIX-only label Nov 9, 2026
@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 7563c2cf2a3e47acd42e0e3f9fd475eb24b5b1ed and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 7563c2c

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 7563c2cf2a3e47acd42e0e3f9fd475eb24b5b1ed false-positive: <reason, 20 to 500 characters>

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Nov 9, 2026
buluoray and others added 18 commits November 9, 2026 01:53
…31572)

In Skills > Pending review, a collapsed row's Approve was natively
disabled with nothing saying why; on a queue with no flagged candidate
no hint rendered at all. A natively disabled button gets no hover or
focus, so it could not carry one.

The collapsed row now renders Approve aria-disabled and wraps it in the
shared HoverTip, which shows the existing "Review the candidate to
enable Approve." sentence on hover and keyboard focus and exposes it as
the button's description. The click handler refuses while disabled, so
the cached detail of a row that was opened and collapsed again cannot
be approved from the collapsed state. Other disabled reasons keep
native disabled.

Closes #27255

(cherry picked from commit 2a7a21b)
…32448)

On Ubuntu 24.04 libasound2 is only a virtual package, and OSS4's
liboss4-salsa-asound2 provides it too. apt picks that stand-in, which
lacks ALSA symbols the desktop binary links against, so the app
installed from the .deb exits with "undefined symbol:
snd_device_name_get_hint" before it opens a window.

The deb now depends on "libasound2t64 | libasound2 (>= 1.0.17)". Naming
the real t64 library first fixes a clean install; the version keeps an
already-installed stand-in, whose Provides carries no version, from
satisfying the dependency. Releases without libasound2t64, such as
22.04, fall through to their real libasound2 as before.

The deb smoke step also checks that no ALSA symbol of the installed
binary is unresolved, and the packaging test pins the entry.

Builds on #28115.

Closes #27964

(cherry picked from commit 9f2bf27)
The collapsed tool-call preview sent any command containing a newline to
the verbatim fallback, so a heredoc or a script showed as plain text
while a one-line command in the same session kept its colours.

Lay each physical line out as its own row. A heredoc body shows as typed
text up to its delimiter, blank lines kept at full height; a line ending
in a backslash goes on in a row of its own as the same command; the
operator a line ends on leads the next command row; a # comment is
plain text. A quote or substitution left open across a newline keeps
the verbatim fallback.

Builds on #25782.

Closes #25769

Co-authored-by: Lê Bảo Duy <lebaoduy1993@gmail.com>
(cherry picked from commit 7fdaa45)
The Connections page probe spawned stdio MCP servers with a fixed
1 MiB asyncio read limit, so a server whose tools/list reply is one
longer line probed as an error with "Separator is not found, and chunk
exceed the limit", although the MCP gateway reads the same server with
its configured ceiling (64 MiB by default).

The probe now takes its limit from resolve_read_buffer_limit(),
the gateway's own resolver (KIROCREW_MCP_READ_LIMIT, then
mcp_gateway.read_buffer_limit_bytes, then the default), on every probe.
A test drives a real stdio child with a 2 MiB tools/list line at the
default ceiling and at a 1 MiB env ceiling, and the MCP architecture doc
says the probe follows the same ceiling.

Closes #30309

(cherry picked from commit 0a2010c)
…#32485)

A split-view pane whose one-time history page arrives after the live
chunks of the turn it shows kept two copies of the reply: the page's
streaming row and the one the live chunks built. When the slot runs and
the page's row reaches at least the slot's chunk floor, the pane's live
row now takes the page's text in place of a second copy, keeping its
place under any reasoning, and the floor rises to the page as the other
snapshot readers raise it.

Closes #29707

(cherry picked from commit d25b0b2)
With any app disabled (most built-ins ship disabled), the first catalog
pass of a new process asked each flat skill for its app: line. No walk
had vetted the stored rows yet, so every one of those reads ran the
full unvetted-path check, and both owner roots were resolved again per
skill. At 1,500 skills that added seconds to the first reply.

Until a walk vets the stored rows, the gate now caches a flat row's
saved metadata as its frontmatter while the file's stat fingerprint
still matches, the same check and cache list_skills already applies,
so only files the index holds no current row for are read. The apps
and builtins roots are resolved once per catalog TTL instead of once
per skill. The saved-metadata read now treats a cell nested past the
JSON decoder's depth like any other undecodable cell, since the gate
reads it too.

Closes #29801

(cherry picked from commit dd16b79)
…32444)

The Accounts and Overview Refresh buttons refetched GET /accounts,
which the backend answers from a five-minute probe snapshot, so a key
fixed after the page loaded kept its failure. Refresh now asks for
?refresh=1 and writes the answer into the list's one cache entry. That
re-probe also skips the identity probe's 30-second cache, so a key
fixed seconds before Refresh is checked again; ordinary reads keep
both caches.

A failing key showed only a warning badge and Reconnect, never the
probe's own error. Reconnect now leads with that error (already
redacted server-side) through AwsErrorNotice, so the cause is on
screen wherever Reconnect is offered.

Closes #29229

(cherry picked from commit 8373101)
…32381)

A cancel landing inside the spawn await of the git auto-update's reset,
kiro-cli update or core-dep pip install made asyncio SIGKILL the leader
pid alone, so the child's process group kept running against the
install. These three spawns now start through update_provider's
_start_installer, which keeps the spawn running past the cancel, waits
for it under the update stop's bound, then stops the child. A new stop=
keyword lets these children use _kill_and_reap, since they have no TERM
trap to honour.

Closes #26795

(cherry picked from commit 136c4cc)
…32270)

A desktop window opened on a configured Remote Crew (client mode, local
gateway off) still exposed the crash-report, WSL, file-open, folder,
terminal, first-run, pane-cache and update-governance bridges, so the
remote dashboard called channels the shell then refused and logged on
every load.

The window now passes --kc-remote-gateway to its preload, decided by
the same per-window predicate the main-process gate reads, and the
preload withholds exactly the channels that gate refuses. The gate is
unchanged and stays the authority.

Builds on #16566.

(cherry picked from commit 31a47a0)
On a Linux host with a glibc older than 2.27 (Amazon Linux 2: 2.26),
the locked pillow==12.3.0, which browser-harness pins exactly, has no
wheel, so pip builds its sdist. Without a C compiler, Python.h, zlib.h
or jpeglib.h that build fails, and the install error keeps only pip's
tail, "Failed to build pillow", which names no cause. Check for them
first, from the filesystem, and refuse at the preparing stage, before
the marker or the venv is touched, naming what is missing and the yum
or apt-get command that installs it. A venv that already holds the
locked pillow is not checked.

Closes #32241

(cherry picked from commit d3aff60)
…2519)

The retired knowledge folder-discovery keys were dropped only by save().
The Settings PATCH and PUT and `kirocrew config set` edit config.json
directly, and the raw-write drop helper covered just the two retired keys
that warn at load, so the five knowledge keys stayed in the file forever.

The drop map is split into its RENAMED and RETIRED halves, the helper
drops every RETIRED key (a renamed spelling is still read, so it stays),
and `config set` calls it too.

Closes #30337

(cherry picked from commit ba92caf)
* fix(usage): count KAS sessions on the Usage page

The Session Activity card and Daily History table read only kiro-cli's
sessions/cli transcripts. The KAS harness writes each session to
sessions/<id>/sess_<uuid>/messages.jsonl in another row format, so an
install on the KAS backend showed almost no sessions and no messages or
tool calls, while the same days showed real credit spend.

The parse now also lists the KAS records beside the cli directory and
counts their user rows, Say assistant rows and tool_call rows. A KAS
record without a messages file is skipped, not reported as a failed
load. Each transcript's counts are kept keyed on its mtime and size,
so a refresh reads only the transcripts that changed.

* fix(usage): list Windows cloud-files and dedup session folders

Pin the KAS root and sessions/cli with links_only, as the upload path
does, so a cloud-files or dedup folder is listed instead of read as
missing or unreadable. KAS record directories opened through the root
pin inherit links_only, so they are listed too. Links and junctions
are still refused.

Co-authored-by: Ray Xu <buluoray@gmail.com>

---------

Co-authored-by: Ray Xu <buluoray@gmail.com>
(cherry picked from commit 4182398)
(cherry picked from commit 91bc37b)

# Conflicts:
#	docs/decisions/README.md
(cherry picked from commit ab349e1)

# Conflicts:
#	website/src/i18n/locales/bn.json
#	website/src/i18n/locales/de.json
#	website/src/i18n/locales/en-XA.json
#	website/src/i18n/locales/en.json
#	website/src/i18n/locales/es.json
#	website/src/i18n/locales/fr.json
#	website/src/i18n/locales/hi.json
#	website/src/i18n/locales/it.json
#	website/src/i18n/locales/ja.json
#	website/src/i18n/locales/ko.json
#	website/src/i18n/locales/pt.json
#	website/src/i18n/locales/ru.json
#	website/src/i18n/locales/zh-CN.json
The ACP provider's hooksSection ("ACP Agent Hooks") and sessionProcess
("ACP subprocess") labels were fixed English literals shown in or
inside translated copy: the Hooks page section heading, its aria-label
and its load-failure and empty-state titles, and the Agent Config tab
tip. Every other language showed the English words.

Both labels are now getters that read a catalog key at use time, as
pluginRegistryName already does, translated in all 12 locales. The
Hooks page no longer lower-cases the section name, which turned the
ACP acronym into "acp" and is wrong for translated nouns.

(cherry picked from commit c3b50d3)

# Conflicts:
#	website/src/i18n/en.context.json
Follow-ups from the review of the app pop-out window.

- The sidebar's pop-out action no longer stops keydown, so the
  shell's document-level shortcuts fire while it has focus; the rail
  has no keyboard drag sensor that needed the stop.
- An Ask the agent in an app pop-out hands its prompt to the main
  window without committing /chat in the pop-out, so the app is not
  remounted and no /chat entry is left for Forward to replay.
- A POP onto a location that is not the pinned app (a deep link such
  as /apps/foo/extra, a differently cased route, a Forward) settles
  the window on the app without handing anything to main.
- Code Review Sage's "Open shared copy" is a router Link, so in a
  pop-out it opens in the main window instead of loading the
  dashboard in the pop-out.
- The action's tooltip and accessible name are one string per state
  that names the app; the title bar's Return says what it does (go
  back to the main window and close this one), with the artifact
  pop-out's wording and translations. The strings move to their
  components' namespaces.
- The routing, sidebar, error hand-off and pop-out applier specs
  describe the app pop-out.

(cherry picked from commit 3535135)

# Conflicts:
#	website/src/i18n/locales/en.json
Settings search offered no row that opens the Feishu channel. The
Feishu panel is drawn by the shared bot-channel panel, but the
registry extractor fanned that panel's rows out only to Discord,
Telegram and WeCom, and the Feishu spec's App ID / App Secret labels
were never indexed. Fan the shared rows out to Feishu, index the two
credential fields, and drop the coverage waiver that claimed the
fan-out already happened.

(cherry picked from commit 3c1e70c)

# Conflicts:
#	src/kiro_crew/docs/ui-index.generated.json
@buluoray
buluoray force-pushed the crew/slack/0.12.1-s3b3 branch from f69df06 to 7563c2c Compare November 9, 2026 01:56
@buluoray buluoray changed the title fix(release): backport twenty-two user-facing fixes to 0.12.0 line (s3b3) fix(release): backport twenty-one user-facing fixes to 0.12.0 line (s3b3) Nov 9, 2026
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 7563c2cf2a3e47acd42e0e3f9fd475eb24b5b1ed — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 7563c2c

Verdict parsed from the review's SHA-scoped output markers for commit 7563c2cf2a3e47acd42e0e3f9fd475eb24b5b1ed.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 7563c2cf2a3e47acd42e0e3f9fd475eb24b5b1ed false-positive: <reason, 20 to 500 characters>

@buluoray
buluoray merged commit 9f7010e into release/0.12.0 Nov 9, 2026
22 of 41 checks passed
@buluoray
buluoray deleted the crew/slack/0.12.1-s3b3 branch November 9, 2026 03:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

posix-only-approved Cross-Platform Portability findings reviewed and accepted as intentionally POSIX-only readiness: action required A blocking check or review needs attention

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant