Skip to content

fix: backport 0.12.1 late batch 2 (42 fixes merged after 11-07 22:00Z) - #33025

Merged
buluoray merged 39 commits into
release/0.12.0from
crew/slack/0.12.1-late-2
Nov 8, 2026
Merged

buluoray merged 39 commits into
release/0.12.0from
crew/slack/0.12.1-late-2

Conversation

@buluoray

@buluoray buluoray commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Bring 39 fixes merged on main after 2026-11-07 22:00 UTC onto release/0.12.0 for 0.12.1, one commit each, in a PR of its own.

Why it matters

Each fix changes behaviour a 0.12.0 user can hit today: wrong or missing UI text and focus, refused or stuck actions, lost dictation, cron, sub-agent, task-runner and channel bugs, KAS sign-in and certificate problems, crash-dump and diagnostics gaps, and Windows publish retries. They are the user-facing fix: rows merged on main in the last day, freeze 2026-11-08 16:00Z.

Not a goal

  • No fix that is not already merged on main; nothing is changed only here.
  • No version bump, no tag, no CHANGELOG.md change.
  • No feature, CI, test-only, docs-only, refactor, perf or internal dev-tooling change.
  • No row that needs a prerequisite feature or a hand port of production code; those are listed under What changed.

What changed (motivation → approach → change)

Each main squash commit was cherry-picked onto release/0.12.0 @ ec9e31b334, in merge order on main, one commit each, with the (cherry picked from commit …) trailer. The repository's leak guard requires the public identity, so every commit is authored as Ray Xu and names its original author on an Original author: line.

This batch is built on release/0.12.0 after the other batch (#33024) merged.

# PR Original author main release
1 #32816 keep every .env line setup --slack does not own @CrysisDeu ec11b37750 22e9e65bae
2 #32579 retry a failed broker start until the broker comes up @bolichen97 76b166432e 4eaeb7d34b
3 #32468 name the missing library when chromium cannot start @bolichen97 908add827e 1c6301f455
4 #32367 keep the key when redacting an authorization bearer header @bolichen97 3a5c452a4a a0ec16683c
5 #32872 keep focus on sessions page new session while it creates @RohanK6 60431a6d92 b476818609
6 #32848 narrow the Bot suggestions line so Bots still draw non-progress widgets @iamwhatever b16b196ee8 7c13edbbb7
7 #32873 show CRITICAL log lines at every level on the Logs page @RohanK6 6b6aaee59a a884079d3d
8 #32879 keep focus on the sessions stale-rows Retry while it runs @RohanK6 cc681932dc cb68872007
9 #32020 let an app's own projectless chat search its skills @Pearcekieser 35fddd9eff a08e07e5b0
10 #32832 give pre-bind port readers the served port under --port auto @CrysisDeu 8236d73a69 2afa6fa29f
11 #32890 join the folded spend row's names by language @RohanK6 d5895ad26d 0307bc9577
12 #31495 give subagent and task-runner spec hooks the session id @bolichen97 f222dbcdd1 68b04168ff
13 #31159 replace the host name in diagnostics bundle members @bolichen97 70fcc4e038 b49caaed4b
14 #32611 let the create api make room at the cap like the panel @bolichen97 e1c206dca7 a2445d4896
15 #32458 count only kept rows in a session's message total @bolichen97 6ce61454ae bd0b0e373e
16 #32638 show a rejected nested spawn in the root chat after a reconnect @bolichen97 c513c148cb de70033a43
17 #32608 say why a connection with a stored sign-in shows not connected @bolichen97 a3956da377 d1aca1b192
18 #32571 let the splash's close window work behind a failure dialog @bolichen97 2caa69b7a6 d722ee36d0
19 #32914 keep focus on the md notebook connect button while it runs @RohanK6 1aea792e9a 0025986bbc
20 #32790 show each regenerated reply's own model, credits and time @bolichen97 652d578a57 a2a6d4e899
21 #32905 stop one degraded session list shrinking the model cache @bolichen97 0983357a28 ab43d08f8c
22 #32527 name an unreadable mcp.json in the session-start notice @bolichen97 2f60cf0e00 d56ab4c7aa
23 #32906 replace emoji instead of crashing on an ASCII-only stdout @bolichen97 d9a472ff85 609013153d
24 #32612 offer install when kiro's chromium is not downloaded @bolichen97 752c0b9c89 40d95063f0
25 #32877 keep focus when a posture list's show more leaves @RohanK6 7de2532b17 bccf1871e9
26 #32880 keep focus on the usage tab try again buttons @RohanK6 e26b1aa353 8150872da6
27 #32828 a subprocess timeout ends the child's whole tree @CrysisDeu 5d4fbc0adf 5b040be611
28 #32924 clear a removed crewmate's thread session record @bolichen97 bed3c8af7e 5ad1ac6c8b
29 #32934 run a new channel conversation's sub-agent on its parent's agent @bolichen97 0a60009098 5b3a27f35e
30 #32134 let people turn off a registered theme's overlays @bolichen97 2ebb1d1629 a505f81d3b
31 #32929 say "removed" for an out-of-band pending-skill removal @bolichen97 36fb266976 28c908c9dd
32 #29890 show a card with the reason and Retry when a preview fails to load @buluoray 7505d96c1c 854ce5db76
33 #29354 keep a shown card when a scroll moves its link @buluoray f8e25741f5 150c5a8684
34 #32505 keep a code block indented under a list item inside it @bolichen97 1dde2fb14f f733ab5010
35 #32916 name the file tree's git badge by its status word @RohanK6 93a9c7faf9 d840144849
36 #32507 stop logging an oversized folder file as an error @bolichen97 0c34a4285c 5a0679305b
37 #32513 drop a quoted session-directive marker from the saved reply @bolichen97 1091827c88 0193349e71
38 #31731 warn, not fail, on a kas engine the first chat downloads @bolichen97 d549bec81c 94f6e47aff
39 #32938 answer 404 when a named workspace's directory is missing @CrysisDeu cad0ff4dcd 5e213e2459

Hand-resolved hunks:

The left-out list for the whole set is in #33024. Left out of this batch as well:

PR Why
#32205 GPT 6.1 Review blocked it on this batch: update_schedule.py marks the crash dump clean before the final shutdown drain, so a SIGKILL during that drain makes the next start delete the dump as a clean exit. Kept on main only. #31159, which went in as its prerequisite, stays: it is a fix on its own.
#32933 GPT 6.1 Review blocked it on this batch: taskrunner.py takes a Resume's agent only for a planned run, so a paused run saved by 0.12.0 (no agent field) resumes on the default agent instead of the one selected. Kept on main only.
#32486 Source-build frontend staging step (dev tooling).

Backwards compatibility

None: each fix keeps its main PR's compatibility notes; nothing here changes stored data or config beyond what those PRs already shipped on main.

Tests

Proof: not provable -- other: a backport of main commits whose proofs ran on their own PRs

  • CI does not run the backend suite on PRs into release/*, so the related set ran here, one pytest process at a time with no xdist: every Python test file the batch changes plus the two hook test files (64 files), 4,927 passed, 1 skipped and 1 failed. The failure is test_acp_harness_contract.py::test_a_missing_self_served_binary_names_its_install_command[copilot], which fails the same way on a clean release/0.12.0 on this host.
  • Frontend: vitest on the 19 changed test files, one file at a time, 404 passed. tsc -p tsconfig.app.json --noEmit passes.
  • flake8 passes on the changed Python files. check_file_line_cap fails only on dashboard/chat_api/resume.py, which is already 2,008 lines on release.

Manual verification

N/A - each fix was verified on its own main PR. The 0.12.1 RC soak is the end-to-end check.

Screenshots / video

Why no screenshot: the frontend picks carry the same rendered change as their main PRs, which show it.

Related Issues

Backport to the 0.12 line for 0.12.1 of #32816, #32579, #32468, #32367, #32872, #32848, #32873, #32879, #32020, #32832, #32890, #31495, #31159, #32611, #32458, #32638, #32608, #32571, #32914, #32790, #32905, #32527, #32906, #32612, #32877, #32880, #32828, #32924, #32934, #32134, #32929, #29890, #29354, #32505, #32916, #32507, #32513, #31731, #32938.

Sibling sweep

Siblings: none -- each source PR carried its own sibling sweep; this PR only carries those fixes.

Pattern harvest

Not generalizable: this PR only carries fixes already on main. The source PRs have their own harvest.

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 8, 2026 07:54
@buluoray
buluoray requested review from Zedmor and removed request for a team November 8, 2026 07:54
@github-actions

github-actions Bot commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

Sensitive Change Review

Sensitive files changed:

  • src/kiro_crew/hook_runtime/hook_dispatch.py

  • src/kiro_crew/sandbox_rlimit.py

  • src/kiro_crew/security/redaction.py

  • src/kiro_crew/security/redaction_patterns.py

  • src/kiro_crew/security_posture.py

  • No reasoning template for 5e213e2 yet.

How to clear this check:

  1. The PR author posts the template below as a PR comment, with
    every field filled (N/A needs a reason). Keep the
    Head commit line: it must name the current head SHA.
  2. The check turns green within a minute, with no push.
  3. A new push resets this check: post it again for the new head.

Only the author's comment counts this way. A reviewer can instead
paste the filled template into an "Approve" review on this head.
Merging still needs a reviewer's approval.

## Sensitive change review
- Head commit: 5e213e24592409e5c75d5cb025c9d5a3d2bb065b
- What rule changed:
- Before -> after (what was allowed/blocked, now):
- Worst case if wrong (breaks commands / leaks secret / locks user out):
- Evidence checked (which sandbox result proves it):
- No regression:
  - Tools still work (which tools/commands were run, result):
  - Backward compatible (old config / old data / old callers still work, how checked):
  - Existing tests (which suites passed on this head):
- How to undo:

@github-actions github-actions Bot added readiness: checking Automated validation is still running merge conflict Branch has merge conflicts with its base — author must resolve before merge labels Nov 8, 2026
@buluoray
buluoray force-pushed the crew/slack/0.12.1-late-2 branch from ee53ec1 to ae92990 Compare November 8, 2026 08:09
@github-actions

github-actions Bot commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 5e213e24592409e5c75d5cb025c9d5a3d2bb065b and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 5e213e2

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

@github-actions

github-actions Bot commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 5e213e24592409e5c75d5cb025c9d5a3d2bb065b — 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

This PR only backports fixes already merged on main. Every row in the table maps to a listed main commit, and nothing appears in the diff that the table doesn't account for.

What this change ships

Inventory (10 items) — 10 justified

Intent: give 0.12.0 users 39 fixes already merged on main as the 0.12.1 point release (FIX; the change list has more than 10 items, so this list stops at the 10 a person is most likely to notice).

  1. Setup, broker start, chromium start and the kiro-chromium install offer recover or name what failed (fix(setup): keep every .env line setup --slack does not own #32816, fix(mcp-gateway): retry a failed broker start until the broker comes up #32579, fix(browser): name the missing library when chromium cannot start #32468, fix(settings): offer install when kiro's chromium is not downloaded #32612) — justified
  2. Keyboard focus stays on the sessions, stale-row Retry, md-notebook connect, posture show-more and usage try-again controls while they run (fix: keep focus on sessions page new session while it creates #32872, fix(system): keep focus on the sessions stale-rows Retry while it runs #32879, fix(a11y): keep focus on the md notebook connect button while it runs #32914, fix(settings): keep focus when a posture list's show more leaves #32877, fix(a11y): keep focus on the usage tab try again buttons #32880) — justified
  3. Logs page shows CRITICAL lines; spend row names joined by language; git badge named by its status word (fix(website): show CRITICAL log lines at every level on the Logs page #32873, fix(dashboard): join the folded spend row's names by language #32890, fix(a11y): name the file tree's git badge by its status word #32916) — justified
  4. A registered theme's overlays get an Off switch, on by default, with the decision recorded by maintainer @bolichen97 (fix: let people turn off a registered theme's overlays #32134) — justified
  5. A subprocess timeout ends the child's whole process tree; git calls in the file editor and diff go through the tree-kill helper, while POSIX sandbox spawns keep subprocess.run (fix(windows): a subprocess timeout ends the child's whole tree #32828) — justified
  6. The create API makes room at the terminal cap the way the panel does (fix(terminal): let the create api make room at the cap like the panel #32611) — justified
  7. Subagent and task-runner spec hooks receive the session id (fix(hooks): give subagent and task-runner spec hooks the session id #31495) — justified
  8. Diagnostics bundles replace the host name, and an authorization bearer header keeps its key when redacted (fix: replace the host name in diagnostics bundle members #31159, fix: keep the key when redacting an authorization bearer header #32367) — justified
  9. Fixes to regenerated-reply stats, the model cache, nested spawns, crewmate thread records and channel sub-agent agents (fix: show each regenerated reply's own model, credits and time #32790, fix(models): stop one degraded session list shrinking the model cache #32905, fix: show a rejected nested spawn in the root chat after a reconnect #32638, fix: clear a removed crewmate's thread session record #32924, fix: run a new channel conversation's sub-agent on its parent's agent #32934) — justified
  10. Pin budgets raised to match the ported lines: _PACKAGE_LINE_BUDGET goes up by 4 and _BASE_SHAPE_DIGEST is updated; both are stated under hand-resolved hunks — justified

[FIRST-PRINCIPLES-REVIEWED] 5e213e2

Description read

[DESCRIPTION-READ] 888817117d1173bc27062b22a9762f5a188799a954617f1aa590b680ec86fd9f

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 8, 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 5e213e24592409e5c75d5cb025c9d5a3d2bb065b — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

UX-Verdict: PASS

cannot evaluate: missing screenshots. The blind read was not performed because this backport changes user-visible dashboard controls and copy, and its description has no images and it commits none.

Evidence gaps

Notes

  • Attaching the screenshots that came with each original main PR to this description, one per row above, closes these gaps without new captures.

[UX-REVIEWED] 5e213e2

Description read

[DESCRIPTION-READ] 0d2e92280ff8d8baf61153a8a39b37e3cc8c739028b6b6e5ac254503a50b478c

That sha256 names everything this verdict read: the PR description, plus the 3 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 8, 2026 •

Copy link
Copy Markdown
Contributor

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

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

Design-Verdict: PASS

cannot evaluate: missing screenshots of the new link-preview failure card and the registered-theme Overlays toggle as they render on this branch. Both surfaces are new under website/src/, and the evidence list shows no images or recordings.

Blockers

New user-visible surfaces with no rendered evidence of this revision
Trigger: #34 "show a card with the reason and Retry when a preview fails to load" adds a host-drawn card in website/src/linkPreview/LinkPreviewLayer.tsx. #31 adds an Overlays toggle for registered themes in ThemeExperienceSettings.tsx (const registered = !installed && !!getThemeBranding(colorTheme)?.overlays?.length). design-evidence.txt lists 0 attachments and 0 committed images.
Outcome: the surfaces are cherry-picked onto release/0.12.0, where hand-resolved hunks and different neighbouring code apply → screenshots on the original main PRs show main, not this branch → the shape of what 0.12.1 users will see cannot be checked.
Fix: attach screenshots taken from a release/0.12.0-based build of this head.
Clears when: the description carries github.com/user-attachments screenshots, taken on this branch, of the preview failure card with Retry and close, and of Settings → Theme showing the Overlays toggle for a registered theme.

Notes

  • ## Backwards compatibility reads "None: each fix keeps its main PR's compatibility notes" and lists no readers. That is acceptable only because each take-away was already checked on its original PR; the hand-resolved _PACKAGE_LINE_BUDGET and _BASE_SHAPE_DIGEST edits are release-only and deserve a one-line reason each.
  • The description was cut off at 8000 bytes, so the end of the Tests section was not seen.

[DESIGN-REVIEWED] 482e23b

Description read

[DESCRIPTION-READ] b7125db7628510915c6dd05ceecf75019d2773301f7603931fb4a65076d312c1

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 removed the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 8, 2026
@github-actions

github-actions Bot commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

Security Scope Review -- 🔴 could not complete (fails closed)

No scope verdict for 5e213e24592409e5c75d5cb025c9d5a3d2bb065b (the review produced no [SCOPE-REVIEWED] marker for this head). This lane fails CLOSED: an unmeasured tightening must not read as "nothing newly refused". See the job logs, then re-run -- or record /ai-review override scope 5e213e24592409e5c75d5cb025c9d5a3d2bb065b <class>: <reason> if a human has judged the scope by hand.


Security scope review -- adjudicated candidates

  • macos-latest (platform posix): 7 classified, 0 newly refused, 7 still allowed.
  • ubuntu-latest (platform posix): 7 classified, 0 newly refused, 7 still allowed.
  • windows-latest (platform windows): 8 classified, 0 newly refused, 8 still allowed.

No candidate flipped from allowed to refused.

[SCOPE-REVIEWED] 5e213e2

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: checking Automated validation is still running labels Nov 8, 2026
@buluoray
buluoray force-pushed the crew/slack/0.12.1-late-2 branch from ae92990 to 200d2dd Compare November 8, 2026 08:43
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Nov 8, 2026
@buluoray
buluoray force-pushed the crew/slack/0.12.1-late-2 branch from 200d2dd to 482e23b Compare November 8, 2026 08:48
@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Nov 8, 2026
@buluoray
buluoray force-pushed the crew/slack/0.12.1-late-2 branch from 482e23b to 7e92025 Compare November 8, 2026 09:15
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Nov 8, 2026
The Slack step rebuilt .env from its KEY=VALUE pairs, so each save
deleted every comment and blank line, re-spaced unrelated keys, and
read an indented '# KEY=value' comment as a key named '# KEY'.

It now saves through the dashboard writer's locked line rewrite, which
replaces only the Slack app token, bot token and owner ID lines (every
spelling of each) and keeps all other lines byte for byte. The reader
strips each line before the comment test, as the boot parser does.

Fixes #32675

(cherry picked from commit ec11b37)

Original author: @CrysisDeu
…up (#32579)

GatewayManager arms its watchdog only on a start that spawned or
adopted a daemon, and _init_mcp_gateway had no branch for a start that
returned False. Any failed start (a daemon owned by another live
gateway, a draining incumbent, a slow or failed spawn, the election
rounds spent) left the gateway without a broker until it restarted,
with every stubbed server on per-session exec.

On a failed start the gateway keeps the manager in
_mcp_gateway_pending and starts mcp-gateway-start-retry, which awaits
start() on the same manager after each L4 ladder delay (1s doubling to
a 60s cap, jittered, no attempt cap) and publishes the broker through
the helper a boot start uses, including the dashboard handle that was
wired at boot with no broker. Reusing the manager keeps its lifetime
stand-down budget and election gates across attempts.

_stop_mcp_broker cancels the retry first and shuts the pending manager
down as well, so a daemon an attempt spawned cannot outlive the
gateway, and the sharing toggle stops a pending retry before it builds
a new manager. The lifecycle spec said the watchdog retried after a
refused start; it names the gateway's retry instead.

(cherry picked from commit 76b1664)

Original author: @bolichen97
…2468)

A Kiro's Chromium that cannot load a shared library exits 127 at once,
but its stderr went to /dev/null and the start only watched the Harness
daemon, so the person waited about 60 s for "the Harness daemon did not
start in time" with no hint of the cause.

On macOS and Linux the browser's stderr now goes to a pipe the gateway
drains for the browser's life, keeping its newest 4 KiB in memory. The
daemon wait also watches the browser: one that exits fails the start at
once with its exit code and its last stderr lines, redacted, which for a
missing library is the loader's own line naming it.

Closes #30312

(cherry picked from commit 908add8)

Original author: @bolichen97

Hand-resolved: added the TYPE_CHECKING import of Callable that main carries from an earlier commit, so the new published_stderr_tail annotation resolves on release.
…log (#32571)

The gateway-failure dialog opened as a modal child of the window it is
about. On Windows and Linux a modal child disables its parent, so while
the dialog waited (for example "port 5476 already in use") the splash's
Close window button, and the window's own captions, did nothing.

Open it as a plain child on Windows and Linux: it still stays above its
window, and the window can be closed to the tray while it waits. macOS
keeps the modal sheet. The desktop-app doc says so.

(cherry picked from commit 2caa69b)

Original author: @bolichen97
…#32914)

The MD Notebook connect screen's Clone / Attach button set native
`disabled` while busy. A disabled button leaves the tab order, so a
keyboard user who pressed it lost focus to the page for the whole
clone. It now uses `aria-disabled` plus an in-handler guard while
busy, and stays natively disabled only for an empty field.

(cherry picked from commit 1aea792)

Original author: @RohanK6
Switching between regenerated replies swapped the text but left the
turn stats footer showing the newest reply's model, credits and time.
A variant now keeps its reply's turn stats, and a switch puts them back
on the row its turn stamped, so each reply shows its own figures.

Builds on #22749 by @LuckVd.

Closes #22724

(cherry picked from commit 652d578)

Original author: @bolichen97
…#32905)

A session/new model list is entitlement-filtered, and a session born
while an entitlement lookup races a token refresh can advertise a
degraded subset. refresh_advertised_models replaced the cross-session
cache with it and persisted it to provider_models.json, so the degrade
seeded every later session and the cold picker until a healthy session
rewrote it.

Both session/new callers now pass confirm_shrink=True: a list that drops
a cached id is held in memory instead of applied, the cache keeps its
ids and takes only the list's additions, and reading the same list
again replaces the cache, so a real downgrade still narrows it one
session later. The kiro --list-models catalog keeps plain replace.

Builds on #28617 by @cruisercohen.

Fixes #22344

(cherry picked from commit 0983357)

Original author: @bolichen97
…32906)

Under LANG=C with UTF-8 mode off, the first emoji print raised
UnicodeEncodeError and killed kirocrew setup, service install and
service uninstall. ensure_utf8_console() now switches a POSIX
stdout/stderr that cannot encode those glyphs to errors="replace",
keeping its ASCII encoding.

Closes #29741

Co-authored-by: Cary Wu <41397851+cwu98@users.noreply.github.com>
(cherry picked from commit d9a472f)

Original author: @bolichen97
…32612)

Settings > Browser read "Not connected · Connect" when the engine was
installed but Kiro's Chromium, the browser it would launch, was not on
disk. Connect could only fail with "install it in Settings", and the
card then offered only Retry. The card's state looked at the engine
alone and never at chromium.downloaded.

An install is now needed when the engine is missing, or when the
browser is Kiro's Chromium and it is not downloaded. The card offers
Install for that case, and a failed install there is the card's to
show rather than the Engine row's under More.

Closes #30385

(cherry picked from commit 752c0b9)

Original author: @bolichen97
)

In Settings, Security, an expanded posture row with more than 25 items
shows a Show N more button that is removed once pressed. Keyboard focus
then fell to the page body. Focus now moves to the first row the press
revealed, so a keyboard or screen reader user continues where the new
rows begin.

(cherry picked from commit 7de2532)

Original author: @RohanK6
The spend chart's Try again rendered only while its query held an
error, which React Query clears when a query with nothing cached
refetches, so the chart swapped to its skeleton and the pressed button
unmounted. The harness notice's Try again stayed mounted but was
natively disabled while it read. Either way keyboard focus fell to the
page. Hold the chart's last error message through a first-load retry so
the notice and button stay up, mark both busy buttons with
aria-disabled plus a click guard, and label them Retrying while they
read so the retry is visibly running.

(cherry picked from commit e26b1aa)

Original author: @RohanK6
On Windows, CPython's subprocess.run kills only the direct child on TimeoutExpired and then calls communicate() with no timeout, so a launcher's child (Git for Windows' cmd\git.exe, a .cmd or exe shim) holding the pipes keeps the call open until it exits. Add platform_compat.run_killing_tree_on_timeout, which on Windows kills the tree with kill_popen_tree, drains under a 5 s bound and re-raises the same TimeoutExpired. Route run_limited, no_index_diff, api_file_diff's git calls and doctor's kiro-cli --version and node -v probes through it. POSIX is unchanged.

Fixes #32755

Fixes #32742

Fixes #32703

(cherry picked from commit 5d4fbc0)

Original author: @CrysisDeu (picked by hand: conflict only in docs/system-specs/modules/cli.md docs/system-specs/modules/learn-cron-dashboard.md)
Deleting a crewmate tore down its config row, crew log, avatar, goal
check-ins, worktrees and private template copy, but never its pinned
thread's session_map.json entry. A bad dashboard:member-<slug> record
then outlived the crewmate, and nothing else could clear it.

The shared removal teardown now destroys the thread's keys through the
gateway's session manager, which also ends a live process for the
thread: the V1 key, the current store's key and earlier store
generations on the exact .memory- boundary. A slug another live crew
still derives keeps its entries, and a failure never fails the delete.
The dashboard delete and both prunes pass the manager; the CLI delete
has none and leaves the map alone.

Builds on #28613 by @cruisercohen.

Co-authored-by: Matt Cohen <1832296+cruisercohen@users.noreply.github.com>
(cherry picked from commit bed3c8a)

Original author: @bolichen97
…#32934)

POST /api/spawn built its own execution context for a parent session
with no execution record and always passed it as _execution_context,
so the manager's fallback to the parent's live selection never ran.
A channel conversation has no record until its first turn is saved,
so a sub-agent spawned in that turn ran kirocrew and lost the parent
agent's prompt, tools, hooks and MCP servers, while the same request
from a dashboard chat inherited the parent's agent.

The fallback moves into execution_context.recordless_parent_execution,
which resolve_spawn_execution and the route both call. When the parent
has no record and the request names no agent, the route reads the
parent's live selection (SessionManager.get_agent_selection) and
admits the child from it. A parentless request and a parent on the
default template keep kirocrew. An unusable selection is refused with
409 member_identity_unavailable, as spawn_async refuses it, rather
than run as kirocrew. The availableAgents policy for such a parent is
unchanged.

Test doubles that send a recordless parent give a concrete
get_agent_selection tuple, as testing-conventions.md requires.

Closes #32798

(cherry picked from commit 0a60009)

Original author: @bolichen97
A theme registered through the branding seam mounts its overlays (the
Bikini Bottom mascot, for one) with no way to hide them, because the
Experience section's Overlays switch only exists for installed packs.
Give such a theme that same switch, on the same per-theme record, on by
default, and skip its overlays in the shell while it is off.

Closes #20542

(cherry picked from commit 2ebb1d1)

Original author: @bolichen97 (picked by hand: conflict only in docs/decisions/README.md)
…32929)

The pending-skills panel's not-found notices reused "dismissed" for a
candidate that left the queue in another window or through the agent,
so the same word named the user's own Dismiss button and something that
happened elsewhere. The five out-of-band values now say "removed": the
two settled variants (candidate_no_longer_pending_dismissed,
approve_failed_not_found_dismissed_named) and the three hedges
(approve_failed_not_found, approve_failed_not_found_named,
candidate_no_longer_pending), in all 12 catalogs plus en-XA. Key names
are unchanged.

SkillsTabValidationReason pins the new copy on every not-found approve
and dismiss path, and the approve-validation capture script waits on
the new settled sentence.

Builds on #22679 by @dodgeblaster.

Co-authored-by: Gary Jennings <garysjennings@gmail.com>
(cherry picked from commit 36fb266)

Original author: @bolichen97 (picked by hand: conflict only in website/src/test/SkillsTabValidationReason.test.tsx; took main's version, which release now matches up to this change)
…ew fails to load (#29890)

Closes #29855

(cherry picked from commit 7505d96)

Original author: @buluoray
…9354)

A streaming reply auto-scrolls the transcript. When it moved the link under
the pointer, the layer hid every unpinned card on scroll, so a card the user
was reading closed by itself.

A card that is already open now stays where it is on such a scroll. The
pointer-out the browser fires for the scroll is ignored; the first real
pointer move outside the card and the link sends the usual leave, so the
app's own leave grace still decides when it closes. A show still in its
hover delay is still cancelled by a scroll that moves its link. Escape,
blur, another provider's hover and pinned cards are unchanged.

(cherry picked from commit f8e2574)

Original author: @buluoray
A file tree row is a button whose name is its text, so a modified file
read as "app.py M": the badge letter is sighted shorthand with no
meaning to a screen reader and no way to translate it. Hide the letter
from assistive tech and give the row a visually hidden status word
(modified, untracked, added, deleted, renamed, or "git status <code>"
for any other code) from the catalog, in every locale.

(cherry picked from commit 93a9c7f)

Original author: @RohanK6
…2507)

A file over knowledge.max_ingest_file_mb in a watched folder is an
expected skip: the ingestion pipeline logs it as a WARNING naming the
config key and raises FileTooLargeError. The folder scan caught that
in its generic handler and logged it again with logger.exception, so
every scan added an ERROR line and a traceback for a file the user
only has to raise the cap for.

The scan now skips the error log for FileTooLargeError and records the
row exactly as before: status 'failed' with the raise-the-cap message,
so the Knowledge page still shows the file with its reason and Retry.

Closes #30347

(cherry picked from commit 0c34a42)

Original author: @bolichen97
#32513)

A directive tool's result reaches the model with its internal
[[KIROCREW_SESSION_DIRECTIVE]] marker line, so a reply that repeats the
result carried that line into the chat bubble and the stored
transcript. The marker is applied from the tool row, never from the
reply.

The segment flush now drops each reply line that is only a marker
reading as a directive, or only the refusal tag, and keeps every other
line; sentinel bytes inside a sentence or in code stay as written.

(cherry picked from commit 1091827)

Original author: @bolichen97
…#31731)

On a host with no kiro-cli, KAS takes Kiro Crew's own engine on the
automatic route, and the gateway downloads the pinned engine at the
first chat. kirocrew doctor printed a missing pin there as a warning
but also put it in its issue list, so a healthy fresh install ended
with "Fix these issues" and exit 1.

On the automatic route a missing pin now keeps its warning row and
download hint, and is an issue only when the gateway will not install
it on this host (an unsupported platform or glibc, or a version
override it does not install unattended); the row then says so instead
of promising a download. An operator who turned
agent.kas_bundle on, an incomplete pinned directory and an unreadable
engines directory still count as issues.

(cherry picked from commit d549bec)

Original author: @bolichen97 (picked by hand: conflict only in docs/system-specs/modules/cli.md)
…ssing (#32938)

A request naming ?workspace= whose directory was absent fell through to the
default roots and returned another directory's files with an empty root.
Answer it like a missing ?project= root instead: 404 workspace_not_found.

Fixes #32846

(cherry picked from commit cad0ff4)

Original author: @CrysisDeu
@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 8, 2026
@buluoray
buluoray force-pushed the crew/slack/0.12.1-late-2 branch from 7e92025 to 5e213e2 Compare November 8, 2026 09:42
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Nov 8, 2026
@buluoray
buluoray merged commit dc384c6 into release/0.12.0 Nov 8, 2026
27 of 49 checks passed
@buluoray
buluoray deleted the crew/slack/0.12.1-late-2 branch November 8, 2026 10:05
@github-actions github-actions Bot removed the readiness: checking Automated validation is still running label Nov 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant