Skip to content

fix: backport 0.12.1 late batch 1 (47 fixes merged after 11-07 22:00Z) - #33024

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

buluoray merged 45 commits into
release/0.12.0from
crew/slack/0.12.1-late-1

Conversation

@buluoray

@buluoray buluoray commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Bring 45 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 @ a0b61daa99, 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.

#32373 sits at the end of this batch, after its prerequisite #32340, which is in it. #29890 (a fix) goes in ahead of #29354, which needs it.

# PR Original author main release
1 #32595 narrow the board-in-panel line so Ultra Mode still draws non-board widgets @iamwhatever 326033c649 e7dcc36a0a
2 #32553 build the new-channel keep/mute prompt as one sentence @RohanK6 aa191fdd50 6aeb67c6e5
3 #32540 keep focus on the workflow Run button while it runs @RohanK6 18ec1282bc b85b66ae06
4 #32585 word three more overview lines as whole sentences @RohanK6 c13765b79f f1d178d3fa
5 #32538 keep focus in the team dialog while a save or delete runs @RohanK6 6a81d5c073 eddfcc8246
6 #32504 say when a store refresh lands on the offline listing @bolichen97 ea26f31c4d 05ea1bdce2
7 #32340 show a failed goal-loop cycle as an error, not a paused line @bolichen97 bc6579b4a4 312a7fd84a
8 #32711 give banner buttons on tinted notices a visible resting fill @bolichen97 a4e1271360 9951c3a7e8
9 #32747 say which team preset is picked in the new channel dialog @RohanK6 58d63679f5 923db3c735
10 #30799 describe Mint Timeout's below-10 fallback in its help text @tim-finnigan 0b4e7fe42e bdbb0b449d
11 #32557 keep focus on the schedule roster retry while it runs @RohanK6 bfc0ef15ba 5025697b0c
12 #32773 keep focus on the prompts and workflows list retry @RohanK6 d3665eea38 245600ac44
13 #32546 read a non-integer installed.json schemaVersion as 1 @RohanK6 75aed024e9 6c9be930d8
14 #32775 word three webhooks page lines as one message each @RohanK6 fe2d88c718 61ce6b4d8f
15 #32650 keep the campaigns database in the app data dir @bolichen97 b42d198acb d8ba5d4b28
16 #32483 keep the steer acknowledgement out of a sub-agent's result @bolichen97 991e33f566 2473b0d588
17 #32543 store the lessons and facts that kirocrew consolidate extracts @bolichen97 8730b41768 1f9aa3977a
18 #32514 tell a host with no AWS profiles to create one @bolichen97 f0984cf223 4cce87ac8a
19 #32774 announce the chosen option in three one-of-N switches @tim-finnigan 273fa43631 4cead57982
20 #32806 start no session for a cron completion whose parent is gone @bolichen97 bc81317d29 c9ba9bd091
21 #32525 refuse plan, execute and retry while task runner is disabled @bolichen97 7ea786ede8 79fa01118a
22 #32517 refuse a malformed knowledge extraction model in config set @bolichen97 6720a047a7 4938b6e39e
23 #32429 say that skill updates always wait for review @bolichen97 3004ea35ab 557e6059e8
24 #32231 save only the repository part of the target url @bolichen97 5941a9c1ac 49552d311a
25 #32523 correct what the file-only app enable message says is live @bolichen97 bf4fc9c0c8 fa57f14341
26 #32298 decide a transport edit's teardown under the lock @bolichen97 69431d53a9 257c434780
27 #32596 give paging right after boot the stall deferral @bolichen97 a3f4e3a096 95e558dcb3
28 #32588 bind an agent whose package twins all declare its name @bolichen97 336b847e54 e9f5a36b66
29 #32821 show a power's name, not its doubled id, on the sign-in card @bolichen97 7951d1f86c 4989eee81e
30 #32829 let touch drag the Older Sessions handle and the Design Tweak splitter @CrysisDeu db353b73d5 0c5c811652
31 #32822 report a missing channel SDK and print pip only where it can install (#32733) @CrysisDeu fab0c85405 fca148316b
32 #32632 warn when a skill sets inclusion: always without always: true @bolichen97 f5b9bdc4bc af19fb484a
33 #32827 retry the SEL prune and four more tmp + rename publishes @CrysisDeu b6419ee8e4 83ccccacb6
34 #32586 let a restart after make live follow the live target again @bolichen97 7458a23e0a 89c0ea9a39
35 #32592 claim deferred session directives under the resource-v2 tool id @bolichen97 c991635762 882f52e750
36 #32815 log a gh auth token that cannot run or exits non-zero @CrysisDeu 48c4454ca8 db28b15ee6
37 #32618 show the report of a run that finishes while open @bolichen97 73377ad278 ba94550007
38 #32614 show the purpose of a deferred tool search call in the pet bubble @bolichen97 e3e6c824fe a7dc5ed8c2
39 #32582 name a yaml plan after its first step, not its agents: line @bolichen97 8103f62035 9e9709de28
40 #32793 word the hooks never-fires labels as one message @RohanK6 b76710537a 59175a3e4e
41 #32474 keep a dictation that returned while chat was away @bolichen97 1718c9cc8f 8370172f2f
42 #32577 name the missing owner id on the slack settings page @bolichen97 eb0ecb9278 e22a5166a0
43 #32587 trust the OS certificate store on the bundle route @iamwhatever 9b5bbfb685 b6b6c22747
44 #32792 never infer an owner from a peer who only messaged the bot @RohanK6 1782ff85d0 6e72df6813
45 #32373 explain two goal-loop pauses the popover showed as bare paused @bolichen97 8e251ac176 4d961fd806

Hand-resolved hunks:

Left out of both batches (code conflicts, with the prerequisite each needs):

PR Why
#32481 Needs #31018 and #32327 first; #31018 itself conflicts on website/src/i18n/en.context.json.
#32473 Needs #29356 (a perf change, not picked) in website/src/store/chat/activity.ts.
#32892 Needs feature #32255 (relay Crews through the local gateway).
#32369 Needs features #17165 and #31139 in dashboard/chat_utils_slots.py.
#32600 Needs #31671 and feature #25347 in acp/harness/kas_cloud.py.
#32834 Needs relay-viewer features #32253 and #31898.
#32889 Needs features #32337 and #31468 in ArtifactsPageGallery.tsx.
#32838 Needs perf changes #32236, #31953 and #31568 in crew_log/emit_runtime.py.
#32907 Needs #32666 (feature), #32035 and #31638 (feature) in dashboard/handlers/usage.py.
#30979 Code conflict in apps/routes_install.py, routes_lifecycle.py, AppDetailPage.tsx; needs 4 earlier commits, two of them features.
#32081 Code conflict in dashboard/chat_fork.py, state_parts/slot_session.py; needs 4 earlier commits, including features #9750 and #17165.
#32524 Code conflict in crew_pause.py, chat_api/continue_turn.py; needs 4 earlier crew-mode commits, one a feature.
#32239 Code conflict in acp/client_transport.py, runtime_wire.py, session_handle_turn.py; needs 5 earlier commits, mostly features.
#32399 Needs #32239 and #32393 (both left out) plus 3 more in messaging/dispatch.py and the channel turn engines.
#32814 Code conflict in cli_server.py; needs 5 earlier commits, two of them features.
#32350 Needs #32473 (left out) and 5 more in website/src/store/chatSlice.ts.
#32554 Needs #32528 (left out) and 5 more in knowledge/SourcesList.tsx.
#32393 Code conflict in dashboard/chat_turn/queue_drain.py; needs 7 earlier commits.
#32459 Needs #32393 (left out) and 7 more in chat_turn/queue_drain.py.
#32649 Needs #32600 (left out), #31671 and feature #29543 in acp/kas_agents.py and the tools-settings readers.
#32831 Code conflict in chat_runner.py, ChatInput.tsx, ContextShelf.tsx; needs 20+ earlier commits.
#32528, #32477, #32469, #32488, #32464, #32865, #32631, #30697 Conflicts in the locale catalogs or generated settings index; each needs many (30 to 120) earlier string changes that release does not have. #32528, #32477 and #32469 also conflict in page code.
#26951 Kept on main only, by decision; not backported to the 0.12 line.
#32583 Code conflict in dashboard/handlers/usage_sessions.py; needs #26951, which stays on main only.
#32484 Picks cleanly, but test_dashboard_chat_turn_wiring.py::test_first_slash_preserves_pending_replay_for_next_prompt (a test it changes) fails on release: the replay mark is set twice.

Not picked by the bar (not a user-facing fix): #32710, #32398, #32236, #32313, #32482, #32590, #32558, #32383, #32627, #32452, #32843, #30652, #32551, #32486 (CI and release scripts, the source-build frontend staging step #32486, prepare-pr and pod/Dev Fleet tooling, a log-only change, perf). Every feat:, test:, docs:, ci: and refactor: PR merged in the window was skipped by type.

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 on the rebased head, one pytest process at a time with no xdist: every Python test file the batch changes plus test_usage.py and test_usage_daily_credits.py (44 files), 2,303 passed.
  • Frontend: vitest on the 36 changed test files, one file at a time, 849 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 #32595, #32553, #32540, #32585, #32538, #32504, #32340, #32711, #32747, #30799, #32557, #32773, #32546, #32775, #32650, #32483, #32543, #32514, #32774, #32806, #32525, #32517, #32429, #32231, #32523, #32298, #32596, #32588, #32821, #32829, #32822, #32632, #32827, #32586, #32592, #32815, #32618, #32614, #32582, #32793, #32474, #32577, #32587, #32792, #32373.

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 tim-finnigan and removed request for a team November 8, 2026 07:54
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 8, 2026
@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 4d961fd806f5d8ff6528bcac13907019adf6b465 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

UX-Verdict: PASS

cannot evaluate: missing screenshots. The PR attaches and commits no images, so the blind read was not performed. Meanwhile the diff changes dozens of user-visible strings, controls and states across the dashboard.

Evidence gaps

Notes

  • These are backports of fixes already merged on main. Attaching the stills from each original PR to this description would close every gap above.

[UX-REVIEWED] 4d961fd

Description read

[DESCRIPTION-READ] dfc4ff16266023363ddd75231fd390bb45b39323faece0a0dcf1f6d4c61996ed

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

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

Design-Verdict: PASS

Nothing blocks: this mechanically cherry-picks 47 fixes that were already reviewed and merged on main. It adds no new design surface.

Notes

[DESIGN-REVIEWED] 4d961fd

Description read

[DESCRIPTION-READ] 82f3c2bab133bfd03d80fde53594054c24d8c92afc64ad7949ea3f6783af1250

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 8, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 4d961fd806f5d8ff6528bcac13907019adf6b465 — 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

Each item is a cherry-pick of a fix already merged on main and kept in step with its main commit. Only one dev-only rider falls outside the Goal.

Notes

What this change ships

Inventory (10 items) — 9 justified

Intent: give 0.12.0 users 47 fixes already merged on main, through 0.12.1. This is a FIX (a backport).

  1. UI wording now says whole sentences (overview, webhooks, hooks, channel prompt, preset, switches) — justified
  2. Focus stays on Run, retry and team-dialog controls while they run — justified
  3. A failed or paused goal-loop cycle shows an error or its reason, not a bare "paused" — justified
  4. Task runner refuses plan, execute and retry while it is disabled; config set refuses a malformed model — justified
  5. Cron and sub-agent bugs: no session for an orphaned completion, no steer ack in the result — justified
  6. KAS bundle route trusts the OS certificate store; the sign-in card shows the power name — justified
  7. Windows tmp + rename publishes retry; a held app archive reads as a local failure — justified
  8. Dictation is kept across chat navigation; touch can drag two handles — justified
  9. Slack/WeCom owner inference fixed; a missing channel SDK is reported — justified
  10. A screenshot capture script is added under website/scripts/ — rides along, outside the Goal

[FIRST-PRINCIPLES-REVIEWED] 4d961fd

Description read

[DESCRIPTION-READ] 50584f1c1d98db4c5e0fbdc26fcbe37d5e32355ce195b3c30d99bf0dfdb9c2eb

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

Opus 5.5 Review — ✅ no blocking findings

Reviewed 4d961fd806f5d8ff6528bcac13907019adf6b465 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 4d961fd

Verdict parsed from the review's SHA-scoped output markers for commit 4d961fd806f5d8ff6528bcac13907019adf6b465.

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

@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 4d961fd806f5d8ff6528bcac13907019adf6b465 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 4d961fd

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 4d961fd806f5d8ff6528bcac13907019adf6b465 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 8, 2026
…on-board widgets (#32595)

(cherry picked from commit 326033c)

Original author: @iamwhatever
The Workflows author view disabled its Run button while the script validated and ran. A disabled button leaves the tab order, so a keyboard user who pressed Run lost focus to the page. Mark it aria-disabled and aria-busy instead, and claim the press in a ref so a second press in the same tick still starts only one run.

(cherry picked from commit 18ec128)

Original author: @RohanK6
The Overview health line, the Usage card's no-usage note and the
WakaTime line each glued catalog fragments around a value in English
order. Hindi and Korean put the uptime last, Japanese put the provider
name after the sentence, and German read the status "Up" as the
direction ("Nach oben"). Render each as one catalog message with
the value in place, reusing the Usage tab's existing no-usage sentence.

(cherry picked from commit c13765b)

Original author: @RohanK6
Create team, Save, the name field and the delete confirm took native
disabled while the request they started was out. Disabling the
focused control blurs it to the body, outside the dialog, so a
keyboard user lost their place before the request answered. Hold
them with aria-disabled (the name field read-only) and refuse a
second send in the handler instead.

Fixes #32407

(cherry picked from commit 6a81d5c)

Original author: @RohanK6
)

Co-authored-by: w <w@k.local>
(cherry picked from commit ea26f31)

Original author: @bolichen97
…2340)

A goal loop whose last cycle could not run (stopped_reason
structural_terminal or session_start_failures) rendered "Paused · the
last cycle could not run" in the same warn-toned status line as a user
pause, so a failure read like an ordinary pause with no alert. That
line now renders through ErrorNotice (alert semantics, no hand-off
beside the unsaved goal fields); every other state keeps the status
line.

Closes #21637

(cherry picked from commit bc6579b)

Original author: @bolichen97
…#32711)

A stock Btn has a transparent fill and a faint --border edge. On the
12% ok/warn tint of a banner that edge falls to about 1.0:1 against
the background, so the Dev Fleet Undo, the job-log Cancel, the
artifact slug-collision Open buttons and the MCP Apply/Discard pair
looked like plain text until hovered.

Give each an opaque --bg-elevated fill and a --border-strong edge, as
#31924 did for Open Approvals. Hover and the danger text stay as they
were. The wider sweep of the same shape is tracked in #32636.

Closes #31903

(cherry picked from commit a4e1271)

Original author: @bolichen97
…xt (#30799)

* fix(config): describe Mint Timeout's below-10 fallback in its help text

The help said "Clamped to [10, 120]", but InstancesConfig.__post_init__
discards a value below 10 and uses the transport default (SSH 30s, SSM
90s), and the loader reads a non-numeric value as 30s. Say what the code
does for each input.

Fixes #30396

* fix(config): say a non-numeric Mint Timeout uses the transport default

validate_config_data drops a non-number before the section builder runs,
so the 30s _safe_float fallback is unreachable on KiroCrewConfig.load().

(cherry picked from commit 0b4e7fe)

Original author: @tim-finnigan
)

The Schedule page agent roster Retry used a native disabled while the
roster reloaded, which takes the focused button out of the tab order
and drops a keyboard user to the page. Make it inert with aria-disabled
and a guard instead, and pin focus and the ignored second press.

(cherry picked from commit bfc0ef1)

Original author: @RohanK6
The Retry under a failed Prompts or Workflow library list read lost
keyboard focus the moment it was pressed. It rendered only while the
query held an error, which React Query clears when a query with no data
refetches, so the pressed button unmounted for the whole retry, and it
was natively disabled while busy. Keep it mounted with queryReadFailed
and mark the busy state with aria-disabled plus a click guard, as the
memory cards do.

(cherry picked from commit d3665ee)

Original author: @RohanK6
Every field in InstalledApp.from_dict is coerced with a no-raise
wrapper so a malformed installed.json degrades to defaults rather than
crashing a reader. schemaVersion was the one exception: int() raises on
a non-numeric string, a list or null, so a corrupted or hand-edited
record crashed from_dict with an uncaught ValueError/TypeError, unlike
every other bad field. _read_installed catches only JSONDecodeError,
UnicodeDecodeError and OSError, so that raise escaped to most callers.

Read schemaVersion through a shared _read_schema_version helper that
mirrors _read_enabled: an unusable value reads as 1 with a warning,
forcing the legacy-migration pass, so the field degrades like the
others instead of raising.

Fixes #32542

(cherry picked from commit 75aed02)

Original author: @RohanK6
…2775)

The confirm-hide button, the stored-context banner note and a token's
agent line were each built from catalog pieces joined in code with an
English space or ': '. Japanese, Korean and Chinese read the button in
English word order, and Japanese and Chinese got an ASCII colon or
space between full-width text. Each line is now one catalog message
with placeholders, in all shipped catalogs. English reads the same.

(cherry picked from commit fe2d88c)

Original author: @RohanK6
…32650)

Research Lab kept campaigns.db beside app.json in
<data home>/apps/auto-research/. An update or an adoption onto the
app's own repository keeps only data/ and .app_secret of that
directory, so moving the app out of core would delete every campaign
row with the retired tree (gap 1 in the app repository's PORTING.md).

The database now lives in data/. On every gateway start, from the
startup hook that runs whether or not the app is enabled and before
any connection opens, a database kept beside app.json is copied in
once through SQLite's online backup (rows still in the -wal come
along), written owner-only under a staging name, checked with
PRAGMA quick_check and published with a hard link, so it never
replaces a database already in data/. Once published the old file and
its sidecars are removed. A link at the old name is an operator's
redirection and stays in use. Until a copy is published db_path keeps
answering the old file, so no row is hidden; a lock someone else holds
on the old file makes the copy give up after a few seconds instead of
holding up the start, and a failed copy is retried at the next start.

Part of #26967

(cherry picked from commit b42d198)

Original author: @bolichen97
A host deny (or a parent's spawn_steer) steers text into a running
sub-agent turn, and kiro-cli has the model acknowledge it with a
[STEERING steer-<id>: ...] line. The run's end-of-turn cleanup stripped
the [OPTIONS: ...] line but not that acknowledgement, so the completion
event and result.txt (which spawn_status reads) both handed it to the
parent as part of the answer.

Strip complete acknowledgements once at the end of the turn, through a
new messaging.driver.strip_steering_markers that reuses the channel
layer's steer-marker parser, fed in bounded slices so its cost stays
linear. sanitize_channel_replay_text now calls the same function.

Closes #29807

(cherry picked from commit 991e33f)

Original author: @bolichen97
…32543)

The CLI built its HistoryConsolidator without a vector store. Without
one a pass drops the lessons and structured facts it extracts, so the
CLI pass drained the tail, printed done, and kept neither. The
gateway's pass, given the store, kept them.

Hand the CLI pass the default VectorMemoryStore and memory.migrated,
as the gateway does, with embeddings wired like a named store's, and
close the store when the command ends. The CLI spec row says what the
pass now stores.

Closes #30339

(cherry picked from commit 8730b41)

Original author: @bolichen97
#32231)

Connect saved the repository link exactly as it was pasted, so anything
pasted after the repository name, a token included, was written to the
app's saved settings in plain text. It now saves only the repository
the link names, so nothing else from a pasted link is kept.

(cherry picked from commit 5941a9c)

Original author: @bolichen97
With no gateway reachable, kirocrew app enable/disable said the change
takes effect at the next gateway start. A gateway that is running anyway
(the CLI cannot reach one on Windows or from a sandboxed shell) re-reads
the app's crons and hooks from the files within a minute, so the enabled
cron was listed and fired at once. Only the backend process waits for a
gateway start. The message, the CLI spec and the App Kit reference say
so, and a test pins the minute to the two poll intervals behind it.

Closes #30328

(cherry picked from commit bf4fc9c)

Original author: @bolichen97
…2298)

The PATCH route read the record before the manager lock and skipped the
teardown when every named transport field matched that read. Another
edit plus a connect landing between the read and the write let a request
that set a field back to its old value skip the teardown, so the record
named one machine while the live forward served another.

reconfigure() takes an optional needs_teardown predicate and runs it
under the lock first. False writes in that same hold and leaves the
tunnel and its self-heal alone; True takes the existing barrier and
teardown. The route passes it for every edit naming a transport field;
a disable still always tears down.

Closes #20991

(cherry picked from commit 69431d5)

Original author: @bolichen97
The watchdog learned the loop thread's id from its first heartbeat,
which lands one interval after start. A stall in that window had no
thread to read major faults from, so a paging loop exited on the plain
budget. start() runs on the loop thread, so record the id there.

(cherry picked from commit a3f4e3a)

Original author: @bolichen97
A package installer writes one copy of a shared agent per dependent
package (<Package>-<name>.json plus a local-<Package>-<name>.json twin),
all declaring the same name. Every crew binding writer (crew create,
both crew-update paths, the locked rebind and the default-agent write)
runs _foreign_private_copy_owner, which refused any name matched by
more than one spec file with 409 lineage_unverifiable. The crew editor
re-sends kiro_agent on every save, so a crew bound to such an agent
could not even be edited.

Lineage is keyed by the declared name, and that name's strict sidecar
read has already found no record by the time the file scan runs. When
every claimant resolves under the target's own name, none of them is a
private copy whichever one a session runs, which is the verdict the
spawn gate already gives the same twins. _AmbiguousTemplateName now
carries the name each match resolves under, and the ownership read
falls through only when that set is exactly the target. A claimant
resolving under another name, such as a <target>.json declaring a
fork-backed name, keeps the fail-closed refusal. Fork, publish, reset
and template create still refuse, since they must pick one file.

The existing ambiguity tests move to that mixed-name shape so the
sentence, masking and file listing stay pinned; new tests cover the
rebind, the generic editor save, the direct ownership read and a
recorded private copy with twins. crew-mode.md says which claimants
the refusal covers and that the session start picks the file through
agent.spec_pins.

(cherry picked from commit 336b847)

Original author: @bolichen97
…rd (#32821)

A Power whose one server shares its name gets the namespaced id
power-<name>-<name> (power-figma-figma), which the MCP sign-in card
printed as-is, in code font, in the sentence and on the button. Show
that name once, capitalized, in normal text. Every other id keeps its
full id and the code font, and the relay still gets the raw id.

Builds on #28532 by munahad.

Closes #28524

Co-authored-by: munahad <344993864+munahad@users.noreply.github.com>
(cherry picked from commit 7951d1f)

Original author: @bolichen97
… can install (#32733) (#32822)

(cherry picked from commit fab0c85)

Original author: @?
…32632)

A skill that sets the steering key inclusion: always stays on demand,
because skills pin only on always: true. The listing ignored the key
silently, so an author who shares one SKILL.md with a tool that reads
inclusion had no signal. The listing now logs one warning per saved
file naming the skill and the always: true key, and the skills doc
lists inclusion as a key skills do not read.

Closes #30773

(cherry picked from commit f5b9bdc)

Original author: @bolichen97
#32827)

The daily SEL prune and four tmp + rename writers (Bot staging, recording
meta, avatar staging, adoption archive) published with a bare os.replace.
On Windows any reader holding the destination fails that rename on the
first attempt. They now rename through atomic_write.replace_with_retry,
which stays a plain rename on POSIX and on the event loop.

The prune caught a failed rewrite in the same except arm as the rotation
lock, so a held rename was logged as a lock skip and never reached the
heartbeat's prune_failed counter. A rewrite failure is now raised after
the lock is released; a lock that cannot be taken still skips as before.

The adoption archive's rename sat inside the download's OSError mapping
and was reported as network_unreachable. A failed local rename is now the
transient stage_io_failed (disk_full for ENOSPC), retried with the same
backoff and shown with the dashboard's "local" remedy copy.

Fixes #32684
Fixes #32683

(cherry picked from commit b6419ee)

Original author: @CrysisDeu
A gateway that exec'd into a live target kept KIROCREW_LIVE_EXECED in
its environment, so every process it spawned inherited it. The
foreground Make live restart is one of those: its detached `kirocrew
restart` brought up a replacement that saw the marker, skipped the
pointer and booted the old checkout again, so the second Make live (and
Switch back) only staged the change.

The exec'd image now pops the marker as it returns, so a gateway it
later starts reads the pointer like any other boot.

Closes #30376

(cherry picked from commit 7458a23)

Original author: @bolichen97
…32592)

A session directive such as monitor_start called through Tool Search
under a resource-v2 tool loader arrives as {"tool_id":
"tool::kirocrew-core::<tool>", "arguments": {...}}. The consumer only
unwrapped the envelope when tool_id was exactly kirocrew-core::<tool>,
so it hashed the whole wrapper, missed the record the MCP server parked
and the directive was never applied.

event_input_digest now accepts both exact spellings for the directive
tool the call already resolved to; any other server, tool or prefix
still hashes the whole envelope. The agent-host contract names the
second spelling.

Closes #30665

(cherry picked from commit c991635)

Original author: @bolichen97
#32614)

On a KAS session, a call that Tool Search deferred carries the agent's
purpose inside the envelope's arguments. The pet's approval bubble read
the purpose from the raw input's top level only, so it showed no purpose
for those calls. It now prefers the tool_purpose the gateway already
puts on the permission row, which is read through the envelope, and
keeps the raw-input read as the fallback.

(cherry picked from commit e3e6c82)

Original author: @bolichen97
)

A plan imported from YAML with no heading comment and no path fell
through auto_name to its first non-empty line, which in every workflow
spec is the top-level `agents:` key. The plan was listed as "agents:"
and exported as agents.yaml. Once the YAML is decomposed, the plan is
named again with its first step's title standing in for that first-line
fallback; a saved workflow's own name, a heading comment and a spec path
still win.

Closes #30364

(cherry picked from commit 8103f62)

Original author: @bolichen97
Two Hooks page names glued translated text together with a hard-coded
English em dash: the unsent-hook badge ("never fires — <reason>") and
the ON switch of a trigger that never fires ("Disable hook — <note>").
Japanese and Chinese screen readers heard a foreign separator
mid-sentence, and no locale could re-punctuate either name.

Move each name into one catalog key with a placeholder,
pages.hooksPage.stored_only_reason and
pages.hooksPage.disable_hook_with_note, so each locale owns its
punctuation. English stays byte-identical.

(cherry picked from commit b767105)

Original author: @RohanK6
A batch transcript that settles while Chat is unmounted is held by the
transcript inbox and handed over when Chat mounts again. The composer's
session effect also redelivered held results synchronously on mount,
inside the composer's own mount effects and before ChatPage's draft
restore, which then overwrote the transcript: the composer came back
empty and the saved draft stayed empty.

The session effect now redelivers only when the session changes; on
mount the inbox's deferred hand-over delivers after the host's mount
effects. The inbox reports when a held result is being delivered, so
the "Dictation added" cue shows on a return as well as on a slot switch.

Closes #29776

(cherry picked from commit 1718c9c)

Original author: @bolichen97
)

With both Slack tokens saved and KIROCREW_OWNER_ID empty, the gateway
keeps Slack off and the settings page only said "Needs setup": the
config reads as not configured, and the panel hid every hint in that
state. The panel now says Slack stays off until an owner is set and
points at the Owner Slack member ID field, in every shipped language.

Closes #30491

(cherry picked from commit eb0ecb9)

Original author: @bolichen97
Crew's own KAS bundle runs Node directly, and Node trusts only its
built-in roots unless NODE_USE_SYSTEM_CA is set. Behind a TLS-inspecting
proxy whose CA lives only in the OS store, every engine call failed on
the bundle route. kiro-cli already defaults the variable to 1 when it
spawns KAS, so the relay route worked.

The bundle spawn now defaults NODE_USE_SYSTEM_CA=1. An operator's own
value, 0 included, is kept, as on kiro-cli. The relay is left to
kiro-cli.

Fixes #32561

(cherry picked from commit 9b5bbfb)

Original author: @iamwhatever
#32792)

Under wecom.allow_all_users, configured_targets() lists every warm peer,
so a stranger who messaged the bot once could be the single available
direct target that sole_direct_target reads as the channel owner. Mark
those peers learned on ConfiguredChannelTarget and have
sole_direct_target skip learned targets, so an owner-DM path names only
a configured userid or owner_id. The dashboard picker still lists them.

(cherry picked from commit 1782ff8)

Original author: @RohanK6
…32373)

A loop a restart caught mid-cycle comes back paused as interrupted_cycle,
which the goal popover rendered as a bare "Paused". A refused turn whose
claim release the store would not take stopped re-arming but stayed
active with nothing armed, so the popover showed a running loop with only
a log line saying why.

The popover now words interrupted_cycle in every locale, and that failed
release stops the loop under claim_unsaved in the same write that records
the claim undelivered. The popover shows that failed save as an error
notice in place of the status line, like a cycle that could not run.

Part of #22831

(cherry picked from commit 8e251ac)

Original author: @bolichen97
@buluoray
buluoray force-pushed the crew/slack/0.12.1-late-1 branch from 7eec2d6 to 4d961fd Compare November 8, 2026 08:43
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Nov 8, 2026
@buluoray
buluoray merged commit ec9e31b into release/0.12.0 Nov 8, 2026
28 of 41 checks passed
@buluoray
buluoray deleted the crew/slack/0.12.1-late-1 branch November 8, 2026 09:04
@github-actions github-actions Bot removed the readiness: action required A blocking check or review needs attention 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