Skip to content

fix: backport 48 fixes to 0.12.1 (batch b1 of 4) - #33974

Merged
bolichen97 merged 50 commits into
release/0.12.0from
hotfix/0.12.1-b1
Nov 9, 2026
Merged

bolichen97 merged 50 commits into
release/0.12.0from
hotfix/0.12.1-b1

Conversation

@bolichen97

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Ship 47 user-facing fixes that merged to main after the 0.12 cut, plus the one test pin they need, to 0.12.1 users (hotfix batch b1 of 4).

These fixes are on main and not on release/0.12.0. Each one is a bug that 0.12 users can hit today. All 48 main commits cherry-pick onto release with no conflict once the earlier picks are in; two release-only commits make two of them build on release's own code, listed below.

Why it matters

0.12 users keep hitting these bugs until a patch release carries the fixes. They cover the CLI (bench, pod, restart, chat), macOS signing and desktop update notes, the dashboard (chat replay, slot close, usage, artifacts, Computer Use, the Strands key focus, Report a problem), crash dumps, task runs and crons, Windows path and credential handling, KAS tool globs, subagent admission and background runtimes, and a dashboard login link, token included, that every service-managed gateway wrote to its log.

Not a goal

What changed (motivation → approach → change)

The 0.12.1 hotfix list was re-reviewed PR by PR against v0.12.0: a bug in released code, not on release yet, and not an app PR. This batch is slices hf1 to hf3 of that list, applied in main merge order, one cherry-pick -x of each main merge commit, on release/0.12.0 at 34898f9795, after the release owner's late-4 (#33742) merged. The whole list was assembled and tested as one staging branch first (see Tests), and each batch is a contiguous slice of it, so every merged batch leaves release at a state that branch already passed through.

# PR Main merge commit What users hit
1 #30153 7b00f4af96 kirocrew bench printed its errors and refusals on stdout, mixed in with its results
2 #30256 b81f3076f8 the security conductor's fix contract check crashed with a traceback on a UTF-16 file (what Windows PowerShell saves) instead of reporting it unreadable
3 #30240 08c052cdc6 kirocrew pod --help named systemd units and a journal on every host, and offered pod restart on Windows, which refuses it
4 #30810 39ccfec70e on Windows every prove.py revert failed with "patch does not apply", because the patch went through a text-mode pipe (fixes #29345)
5 #30860 61a9c6393b the agent was never told that processes it starts end with its runtime, so it offered nohup ... & as a way to outlive a turn
6 #31083 4188c0f348 signing the universal macOS app failed at exec: the sign request body went as one argument larger than the kernel allows
7 #31289 154345004e every universal macOS signing failed with "request entity too large" once the manifest passed the signing service's 102,400 byte limit
8 #31223 c38eec4166 the About page and the update popup showed no release notes for a pending desktop update on any platform (fixes #6521)
9 #30841 360960f2b7 a security conductor test golden path failed a clean run, because pytest's basetemp landed inside the checkout
10 #31401 f490ce1095 the split universal signing was refused at part 1 ("code object is not signed at all"), because the shell entries rode in only one part
11 #31712 486806e138 Report a problem's diagnostics line read "1 secret(s) redacted across 1 file(s)", in English and in four translations (fixes #31707)
12 #31997 5635855f0e a hostname holding eyJ (honeyJar.atlassian.net) was cut in half in logs, refused by the decisions gate and mangled by the dashboard sanitizer as if it were a JWT
13 #31203 73157272ab a cron secret grant whose expected_ts was too large for a float answered 500 instead of 400
14 #29957 1cacf51b35 a transcript row's banner label was checked only for type and length on replay, not with the send path's own banner_meta rules
15 #32218 1ef44e73d0 Settings > Computer Use's Accessibility and Screen Recording rows timed out, because the 5 s probe spent its budget importing the whole CLI (fixes #32193)
16 #32363 67a7bc86f5 kirocrew restart started a detached gateway beside a stopped user unit when a system kirocrew.service alias of another unit hid it (fixes #25979)
17 #32552 52d6e05345 keyboard focus fell to the page from the Strands key Save and Remove buttons while their write ran, and again when it landed
18 #32398 666f96222d where pysqlite3 was installed, a second SQLite library opening a database the gateway held could crash the next read with SIGBUS or "database disk image is malformed"
19 #32482 2eeceb4b07 kirocrew pod up could exit 0 with an empty token, because it minted before the gateway wrote its pid record
20 #32627 d8029998fd the page check left its throwaway browser profile behind when a browser helper wrote into it during removal (fixes #30934)
21 #32486 ddd42be19b on an overlay filesystem kirocrew frontend stage failed with EXDEV and the old build stayed live (fixes #29779)
22 #32814 aa08aa6001 on Windows kirocrew stop and restart did not refuse the desktop app's supervised gateway (fixes #32714)
23 #32484 12a1a7d50f after a dashboard turn streamed output and then failed, every recovery turn re-sent the session history replay (fixes #29535)
24 #32205 0956e6534b the crash dump of a gateway that was killed or crashed without the stall alarm read as a clean exit and was swept at startup (fixes #14724)
25 #32583 86a4fef09b the usage page counted a transcript it could not read in its all-time sessions as well as under could not load
26 #32551 8ad14ca919 a pod failed to boot when kiro-cli kept its engine in its data folder: the sign-in copy hit the 512-file cap and never finished (fixes #30357)
27 #32932 eba4f3b053 kirocrew chat sent the typed text bare, without the session context (custom agent prompt, skill resources) every other surface sends
28 #33150 36deb7c842 a gateway killed during an in-place update restart left a crash dump that read as a clean exit and was deleted at the next boot (fixes #32782)
29 #32457 a1f286a4e0 in the shared default workspace, another data home's task runs showed up in the task list after a restart (fixes #29713)
30 #33188 2eaea3d7ed closing a chat slot could retire the auto-nudge loop and pop the key of a replacement slot that took the name meanwhile (fixes #32903)
31 #33272 8509138a7c kirocrew pod down reported a failed stop for a pod whose gateway took longer than 15 s to exit (fixes #33270)
32 #33334 2bc7c8f190 the artifact page's folder chip read "folder" in English under every other language (fixes #33307)
33 #33508 c5f6643172 the member activity and roster views raised on an activity timestamp past float range, and took inf or nan as a time
34 #33534 6264d9ef0f a message queued mid-turn (a queued "/new") could run as a command instead of text when its replay found the session busy and the turn then ended
35 #33536 0781f8567e a re-armed auto-nudge could not replace a loop stopped on its cycle claim, and a later pause relabelled that stop as manual (fixes #33473)
36 #33571 b1bbe69f64 a script cron could reset the conversation of a chat slot it did not create, past the creator fence and session-control switch its other chat routes keep
37 #33562 18de2125b2 on Windows the gateway PATH carried /opt/homebrew/bin and /usr/local/bin, which resolve to folders on the current drive that any local account can create
38 #33566 3e4a72f85d the skill script sensitive-path scan missed a credential path written with Windows backslashes
39 #33564 33af78eeef on Windows a path spelled with the \\?\ extended-length prefix did not count as inside the provider CLI workspace
40 #33555 ad9a25a7e2 on Windows a credential env name declared in lower case (ssh_auth_sock) reached a pooled MCP backend instead of being scrubbed
41 #33484 d5728edc39 a subagent with a heavy MCP roster was admitted at the default roster's memory price until the host ran out of memory
42 #33443 e1f14081ac the telemetry view paid a full path check for every metrics shard outside its date window, slow on an unpruned folder
43 #33635 caf79f4e46 one session id shape passed the sub-agent result routes' check yet named a folder outside the sessions folder on Windows (fixes #33291)
44 #33544 04e5fa68e8 an allowedTools entry with ? went to KAS, which reads ? as a literal where kiro-cli reads it as any one character
45 #32376 21c57e6977 a displaced background runtime whose busy probe never cleared kept a multi-GB kiro-cli alive until the gateway restarted (fixes #30716)
46 #33663 8f29b1dcf7 every subagent start and restart orphan notice ran two realpath calls on the gateway's event loop, slow on Windows (fixes #32069)
47 #33579 c9b9b1df40 a gateway under systemd, launchd, Docker or a detached spawn wrote its dashboard login link, token included, to a kept log on every boot
48 #33695 044a860a15 test pin for #32376: the pid reader ratchet still counted 8 owner-marked readers, so it failed once #32376 added the ninth

Hand-resolved hunks. One, in a release-only commit. The staging branch carries this commit after #32411 (batch b3), so its context held #32411's lines:

File Hunk Resolution
src/kiro_crew/dashboard/chat_turn/prompt_assembly.py _turn_settle_debts, in "settle a failed replay turn on release's kept-the-prompt rule" drop the 7 lines of #32411's settle_drained_subagent_notices requeue block (they arrive with #32411 in batch b3); keep only this commit's _first_turn_history_delivered hoist and the replay call change

Release-only commits. Written for release, not picked, each needed by a pick in this batch. They sit after the hf2 picks, in front of hf3.

Commit For Why
fix: settle a failed replay turn on release's kept-the-prompt rule (backport assembly) #32484 #32484 calls _kiro_cli_kept_the_prompt, which main moved into turn_stats.py in feat #17165 and release does not have, so a replay-bearing turn that did not land raised NameError (flake8 F821). This settles it on release's own kept-the-prompt rule
fix: read a CLI slash command without the saved-prompt lookup (backport assembly) #32932 #32932 imports quick_prompts.user_quick_prompt from feat #31463 (saved prompts as slash commands), which is not on release, so importing kiro_crew.cli_chat_context raised ImportError. This reads a CLI slash command against QUICK_PROMPTS only

Prerequisites not picked:

App content. #33272 carries a Dev Fleet backend hunk (2 of its 11 files) that reads the new pod stop wait; the core fix is the reviewed change, so its app hunk stays.

File line cap. This batch grows src/kiro_crew/env.py from 2,016 to 2,029 lines (#33562). Release is already over 2,000 lines on acp/kas_agents.py, dashboard/chat_api/resume.py and env.py without a baseline row, and no gate on a release PR runs check_file_line_cap.py. Splitting a file here would be a refactor main never shipped in this form, so the batch ships as is.

Dropped: #30872 (pluralize the Dev Fleet force-remove worktree count). It is an app PR (Dev Fleet strings only), so it is out of scope; it and its release-only revert stay on the staging branch, where they cancel, and neither goes to release.

Backwards compatibility

Compatible: each commit is the main commit unchanged, or, for the two release-only commits, only what one pick needs applied to release's own code. Each main PR states its own compatibility.

Removes nothing: no field, API, key or config is removed beyond what each main PR already shipped and documented.

Tests

Run on the pretest branch at db6479eb12 on a Linux DevSpace. Its tree, 0af3c8270f, is this branch's tree byte for byte: the same 50 commits in the same order, with the same one hand resolution (the resolved prompt_assembly.py blob is d49a5a1e07 on both).

  • Backend: pytest -n 6 --dist loadgroup --max-worker-restart=2 --timeout=120 --no-cov, with an isolated TMPDIR, --basetemp and KIROCREW_HOME, on the 83 backend test files the picks touch plus all 22 test/*ratchet*.py files (104 files after removing duplicates, 5,200 items): 5,165 passed, 35 skipped, 0 failed.
  • The two diff-scoped ratchets (test_flake_pattern_ratchet.py, test_wait_discipline_ratchet.py), measured against release/0.12.0 at 34898f9795, once by base SHA and once in PR mode (GITHUB_BASE_REF=release/0.12.0): 117 passed both times.
  • Frontend: npm ci, then vitest run on the 7 website test files the picks touch, with I18N_BASE_REF=34898f9795: 7 files, 171 tests passed.
  • The staging branch that carries all four batches passed the whole backend suite as the 8 release candidate shards with no failure caused by a pick (the first staging run: 251,896 passed, and each failure also fails on release/0.12.0 or comes from the host), and the website suite (vitest 65,459 passed, electron 3,265 passed).

Proof: not provable -- other: a cherry-pick batch of already-merged main fixes, each proven in its own main PR

Manual verification

N/A: each fix was verified in its own main PR, and this batch carries them unchanged except for the two release-only commits above. The staging build that carries every batch was installed and run on Amazon Linux 2, Amazon Linux 2023 and macOS (install, gateway boot, dashboard, chat, MCP gateway, a scheduled run, restart, stop) with an isolated data home, and the collected bug reports were re-run against it with no regression.

Screenshots / video

Screenshots come from each pick's own main PR; the picked change is the same. Of the four picks that change a dashboard file, #31712, #32218 and #32552 carried no screenshot on main: #31712 changes only the noun and verb forms of one line, #32218's two website/ files change only comments, and #32552 changes only keyboard focus.

#33334 (from its main PR): the artifact toolbar of an artifact in no folder. English is unchanged; German shows Ordner instead of folder.

Before After
English before en after en
German before de after de

Related Issues

0.12.1 hotfix batch b1 of 4 (slices hf1 to hf3): #30153, #30256, #30240, #30810, #30860, #31083, #31289, #31223, #30841, #31401, #31712, #31997, #31203, #29957, #32218, #32363, #32552, #32398, #32482, #32627, #32486, #32814, #32484, #32205, #32583, #32551, #32932, #33150, #32457, #33188, #33272, #33334, #33508, #33534, #33536, #33571, #33562, #33566, #33564, #33555, #33484, #33443, #33635, #33544, #32376, #33663, #33579, #33695.

On the release line this carries the fixes for #29345, #6521, #31707, #32193, #25979, #30934, #29779, #32714, #29535, #14724, #30357, #32782, #29713, #32903, #33270, #33307, #33473, #33291, #30716 and #32069, through the picks named in the table.

Sibling sweep

Siblings: none -- a backport batch; each pick's own PR carried its sweep

Pattern harvest

Not generalizable: a release backport batch, not a new defect fix.

Checklist

  • Each commit is a cherry-pick -x of a main commit with a Conventional Commits title, or a release-only commit listed above
  • 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.

RohanK6 and others added 30 commits November 9, 2026 08:29
…not a traceback (#30256)

Co-authored-by: sim <a@b.c>
(cherry picked from commit b81f307)
…30810)

prove.py reverts each hunk with `git apply -R -` and restores it with
`git apply -`, feeding the patch on stdin with text=True. On Windows a
text-mode pipe writes every \n as \r\n, so the patch no longer matched
LF files and every revert failed with "patch does not apply".

Both calls now go through _git_apply, which encodes the patch with
utf-8/surrogateescape and passes bytes. The _git capture that produces
those diffs had the mirror problem on every platform: text mode reads
with universal newlines, so a CRLF file's diff lost its CRs and could
not be reverted either. _git now captures bytes and decodes without
newline translation.

Fixes #29345

(cherry picked from commit 39ccfec)
…30860)

The agent prompt recommended $KIROCREW_SCRATCH and said it is reclaimed
once the session's processes are gone, but never said those processes
are themselves bounded by the agent runtime. So `nohup ... &` read as
a supported way to outlive a turn, and an agent told a user a training
run "runs by itself in the background" until a runtime recycle stopped
it hours later with nobody told.

The prompt now says a process launched from the shell ends with the
runtime and forbids the "runs by itself" promise. Work that must
outlive the turn goes to a one-shot cron command job when it fits that
job's one-hour timeout, and otherwise to a command the user starts
outside Kiro Crew. The cron guide explains the same limit with a
working example, and the test ties the quoted cap to the cron_add
schema.

(cherry picked from commit 61a9c63)
…#31083)

Co-authored-by: w <w@k.local>
(cherry picked from commit 4188c0f)
The signing service refuses a request body over 102,400 bytes. The
universal app lists every nested Mach-O, and the Feishu SDK libraries
took that body from 96,725 to 136,880 bytes, so every universal macOS
signing failed with "request entity too large".

A manifest under 100,000 bytes is still one request, unchanged. A bigger
one is signed in the order the service documents for nested code: the
regular files go out in parts under 90,000 bytes each against the same
upload, their signed bytes are copied into the app, and a final request
signs the bundle entries and the app over that tree. Cutting the list
and merging the outputs alone would leave the app seal covering one
part only.

Co-authored-by: w <w@k.local>
(cherry picked from commit 1543450)
The About page and the update popup already show a pending update's
notes when the update feed carries them, but the macOS, Linux and
Windows publish lanes write their channel files by hand and never set
releaseNotes, so the notes block stayed empty on every platform.

Each lane now writes releaseNotes from the version's CHANGELOG.md
section, picked the way Settings > Releases picks a build's row and
printed as one JSON string, which is also a one-line YAML scalar. A
version with no section, a nightly in practice, gets empty notes.

Closes #6521

(cherry picked from commit c38eec4)
…tside the checkout (#30841)

A test golden path's pytest basetemp (pytest-of-<user>) landed under the
worktree root because child_env points TMPDIR/TEMP/TMP there. A real
checkout's own rootdir conftest snapshots its root and fails a clean run
that leaves a new entry, so pytest exited 1 and the gate judged an
unchanged clone broken. Point each test row's pytest scratch base outside
the worktree instead; real pass/fail verdicts are unchanged.

Co-authored-by: kirocrew-agent <agent@kirocrew.local>
(cherry picked from commit 360960f)
…g request (#31401)

The first real run of the split universal signing was refused at part 1:
"Electron Framework.framework: code object is not signed at all". Every
signing task, a part included, ends with the service's app pass, which signs
the frameworks under Contents/Frameworks. Part 1 listed only backend files,
so the executables inside those frameworks (Electron's Helpers, Squirrel's
ShipIt) were still unsigned when the pass reached them.

Every request now lists the shell entries (helper apps, frameworks and the
executables inside them), and only the backend files under Contents/Resources
are cut across the parts. The final request signs the shell over the merged
tree; a part's signed shell files are not copied. sign.sh also waits for every
part before it fails, so one run reports each part's answer. A manifest under
100,000 bytes is still one request, unchanged.

Co-authored-by: w <w@k.local>
(cherry picked from commit f490ce1)
…line (#31712)

After Report a problem builds its bundle it says "Diagnostics ready —
{{redactions}} secret(s) redacted across {{files}} file(s)." Both
counts sat in one single-form string, so one secret read "1 secret(s)"
and German, Spanish, French and Portuguese copied the shortcuts.

Read each count from its own plural part, with the verb or preposition
that must agree inside it, and keep the outer sentence one key so each
language still orders the parts. Numbers are locale-formatted.

(cherry picked from commit 486806e)
The JWT spelling matches on shape alone, so a host label holding eyJ
(honeyJar.atlassian.net) was cut in half by the log record filter,
refused as a credential by the decisions gate, and mangled by the
dashboard's sanitizer. The chat scrubber already counted a hit only
when its first segment decodes to a JSON object. The log filter and
the sanitizer now apply that same check, the gate leaves the JWT
spelling to the scrubber, and the check lives in one stdlib-only
module the log filter can import at bootstrap. A JSON object Python
cannot parse still counts, so the check fails closed.

Builds on #16573 by NicholasRBowers.

(cherry picked from commit 5635855)
…31203)

PUT /api/crons/{id}/secrets converted expected_ts with float() on both
the approve and the deny path. A JSON integer has no width limit, and
float() of a very long one raises OverflowError, so the request
answered 500. Refuse it with the route's own 400 invalid_secret_env
before anything is audited or written; the pending request stays.

(cherry picked from commit 7315727)
…32218)

Settings > Computer Use read Accessibility and Screen Recording by
running `kirocrew computer doctor --json` in a child with a 5s budget.
The two TCC calls take milliseconds, but the child first imports the
whole CLI (about 1,700 modules) and, with the feature on, projects the
chat backend's agent spec. That measured 2.9 to 4.6s warm and over 11s
on a cold cache, so on a busy host the probe timed out and both rows
read "Could not check" while both grants were held.

The handler now spawns `python -P -m
kiro_crew.computer_use.permission_probe` under the gateway's own
interpreter. The module asks the same `probe_permissions()` the doctor
asks and prints one JSON object, importing only the driver seam (about
0.5s warm). It stays out of process, so a native fault still costs one
row and not the gateway. A test fails if the module loads
`kiro_crew.cli` or `kiro_crew.agent`.

Closes #32193

(cherry picked from commit 1ef44e7)
…as (#32363)

When /etc/systemd/system/kirocrew.service is an alias of another,
stopped unit and our per-user unit is installed and stopped,
`kirocrew restart` skipped the stopped-service refusal and started a
detached gateway outside the user unit. The refusal now falls back to
the per-user unit when the system file is not ours, so it refuses and
names the user unit instead.

Closes #25979

(cherry picked from commit 67a7bc8)
A Strands key field's Save and the remove confirm's Remove went natively
disabled while their write ran, dropping a keyboard user's focus to the
page, and a refused write left it there. A landed write unmounted the
pressed button, so focus fell again. Both now use aria-disabled with a
guard; a refused remove keeps its confirmation open; and once the field
shows its new state focus moves to Replace after a save, to the empty
input after a remove, or back to a refused dangling Remove, unless the
user already moved it elsewhere.

(cherry picked from commit 52d6e05)
…32398)

Where pysqlite3 is installed, the stdlib sqlite3 is a second SQLite
library in the gateway. Its open of a database the gateway already holds
through _sqlite_compat resets the -shm under that connection, whose next
read fails with SIGBUS or "database disk image is malformed".

Pod sign-in staging snapshotted kiro-cli's data.sqlite3, which the
gateway also reads through _sqlite_compat, with the stdlib driver; it now
uses _sqlite_compat too, as does the test that stands in for kiro-cli.
A new test lists every module that references the stdlib connect with
the database each opens, so the next such open has to say what it opens.

(cherry picked from commit 666f962)
The gateway writes its pid record off its readiness path, seconds after
the credential pod up waited for. The mint proves port ownership from
that record, so a mint right after readiness could not prove it,
withheld the token, and pod up exited 0 with an empty token.

For a pod it started and mints for, pod up's readiness now also waits,
inside the same budget, for the mint's own ownership check to pass.
When the budget ends first the pod is still reported up and the mint
explains the withheld token as before.

(cherry picked from commit 2eeceb4)
#32627)

The page check removed its throwaway browser profile with one
ignore_errors rmtree right after the group kill. A helper the browser
starts in its own session (its crash handler) is not killed with the
group and can add an entry while the tree is removed, so the directory
was left in the temp dir with nothing said. The removal now passes over
the profile again until it is gone, bounded by the reap limit, and logs
a warning when it still cannot.

Closes #30934

(cherry picked from commit d802999)
…32486)

On an overlay filesystem a real static/dist that lives in a lower image
layer cannot be renamed aside: the rename fails with EXDEV, so both the
link and the copy fallback of `kirocrew frontend stage` failed and the
old build stayed live. On EXDEV the directory is now copied aside,
removed and the link moved in; a removal that fails or is interrupted
part-way is undone from the copy, so the old build keeps serving.

Closes #29779

(cherry picked from commit ddd42be)
…tart refuse it (#32814)

On Windows the gateway.lock pid stamp is unreadable under the msvcrt
byte lock, so lock_holder answers LockProbeError(held=True) and
_config_dir_owner returned None: the desktop-supervised refusal from
#25705 never fired. On that one answer, name the holder from the
gateway's fresh run/gateway-<port>.pid record instead.

Fixes #32714

Co-authored-by: Zezhen Xu <zezhexu@amazon.com>
(cherry picked from commit aa08aa6)
…32484)

A dashboard session that owes a history replay re-armed the replay
lease on every exit but a clean landed end_turn. A replay-bearing turn
that streamed output and then failed (a throttle 5xx after the first
chunk, a timeout, any error after output) therefore made every recovery
turn rebuild the whole session context, although the live session
already held it.

Such an exit now notes the replay delivered to the provider's context
incarnation, using the same kept-the-prompt rule the first-turn history
debt settles on. The lease stays armed so close_all keeps the prior
SID, later prompts on that native conversation are not built as a
session start, and the next landed non-slash end_turn promotes the
fresh SID. A respawned process is a new incarnation: a turn admitted
just before the respawn commits nothing, and the next one sends the
replay again.

Closes #29535

(cherry picked from commit 12a1a7d)
…32205)

A loop-stall crash dump holding only its startup header was read as a
clean exit, so startup swept it and rotation sacrificed it first. The
header is written at boot, though, so a gateway that was killed or
crashed without the stall alarm firing leaves the very same file, and
that file was the only trace of the death.

An orderly end now leaves an empty <dump>.clean marker beside its dump,
never touching the dump's bytes: from the gateway's shutdown right
after it disarms the watchdog, and from a pre-exec stop before an
in-place restart, whose exec skips that shutdown. A dump's first header
line carries a token saying its build writes that marker, so a dump an
earlier build wrote still reads as a clean exit after an upgrade. The
sweep deletes a header-only dump of a dead owner, with its marker, only
when it reads as a clean exit. One that does not is kept as an
unexplained exit: rotation sacrifices it after clean exits and before
unreadable files and dumps with stacks, kirocrew doctor shows an
information-only "unclean:" row with the count and the newest, and the
diagnostics bundle leaves markers out and gives these headers only the
crash-dump slots nothing else fills. The dump reader opens without
blocking, so a FIFO named like a dump is refused instead of hanging.

Closes #14724

(cherry picked from commit 0956e65)
…32551)

Pod boot copies kiro-cli's data folder into the pod so the pod is signed
in. kiro-cli 3 also unpacks its engine there, under kas/, and the copy
never finished it: the folder is bigger than the 512-file cap, and the
walk held every folder's descriptors until the end, so under a pod's
1,024-descriptor soft limit it ran out and skipped the rest. kiro-cli
then trusted the partial engine and failed with ERR_MODULE_NOT_FOUND.

kas/ at the store root is no longer copied; kiro-cli unpacks a complete
engine itself on first start. Each folder's descriptors are closed
before the next one opens, in both staging twins.

Closes #30357

(cherry picked from commit 8ad14ca)
kirocrew chat sent the typed text to the provider bare. Every mirror
rules a custom agent's prompt and its skill:// resources withheld on
the premise that both reach the harness in the context message
ContextBuilder.build_message assembles, which the dashboard, channels,
cron and kirocrew run send. So on claude, codex, opencode, goose and
the other mirrored harnesses, `kirocrew chat --agent X` ran the
harness's own default persona with none of X's skills.

On those harnesses the CLI now builds the first message of each
session with build_message, as those surfaces do: the -m message, the
REPL's first turn, and the next turn after a compaction restart, a
typed /clear or /compact, or a changed context_incarnation, since each
of those sessions holds none of it. kiro-cli and KAS load the agent
themselves, so a CLI session on either still sends the typed text
bare, as before. A backend process that exits between turns shows up
only once the send that respawned it changed the incarnation: the
process's own liveness would be a shared runtime's answer, not this
session's.
Later turns are sent as typed. A turn that opens with a slash command
is sent as typed too, because a harness runs a command only when it
opens the prompt, and the context waits for the next ordinary turn. A
build that raises prints one line and sends the typed text; the next
turn tries again.

build_message decides per harness what the message holds. It reads the store resolve_agent_bindings resolved:
a member bound to a named store gets neither memory nor lessons, since
the CLI does not bind that store and Global memory is not the
member's to read. The builder lives in a new cli_chat_context module,
imported inside _chat so other CLI commands do not load the context
stack.

The provider-shutdown tests in test_cli_chat_permission.py stub the
tool gate with a real _ToolGate over a default HookManager, as
production always builds one: _chat hands the gate's hooks to the
context builder before the backend starts.

(cherry picked from commit eba4f3b)
…33150)

The in-place update restart wrote the crash dump's clean-exit marker
before its final, unbounded callback drain. A gateway killed with
SIGKILL while that drain hung kept the marker, so the next boot read
its header-only dump as a clean exit and deleted it, and the doctor's
unclean: row missed that death.

The marker is now written after that drain. A zero-wait look right
after the write catches work that arrived while it was being written:
it withdraws the marker and drains that work first, so a received
message is still never left behind the exec, and no channel-wide
ingress quiesce is needed.

Closes #32782

(cherry picked from commit 36deb7c)
The default workspace root is one folder per OS user, so every data
home with no workspace of its own runs its task runner in the same
taskrunner_main folder and loads and rewrites the same runs.json.
Another home's runs showed up in the task list after a restart.

In a work dir under that shared root, a KIROCREW_HOME override now
keeps its registry in runs-<home digest>.json. The default home, and
every work dir outside the shared root (a pod's own workspace, a
configured taskrunner.workspace_dir), keep runs.json.

Closes #29713

(cherry picked from commit a1f286a)
…#33188)

close_slot waited (for the slot's guarded history write, the app close
hook, the AutoNudge lock) and then acted on the slot's key: it retired
the auto-nudge loop by key and popped the key, asking only at its last
pre-pop check whether the slot still held that key. When another close
popped the slot and a send recreated the key during a wait, the close
stopped the replacement's loop or monitor, or popped the replacement,
and its rollback could not put either back.

After each of those waits the close now checks that the slot still owns
its name and refuses with 409 slot_replaced before the next step that
acts by key, releasing only its own close fence. The tab DELETE route
answers that refusal as a 409, and session_close answers it as its own
target_replaced.

Closes #32903

(cherry picked from commit 2eaea3d)
bolichen97 and others added 2 commits November 9, 2026 08:30
A gateway under systemd, launchd, Docker or a detached spawn wrote its
startup dashboard link, ?token= included, to a kept log on every boot,
and again from the slow-browser auto-open fallback and from kirocrew
restart. Anyone reading that log inside the link's five minute window
could redeem it for a 20 hour dashboard session.

dashboard.urls.login_link_may_print() is true only when stdout is a
terminal, and all three prints ask it. Off a terminal the gateway
prints each URL without its query string plus a kirocrew token hint,
and restart mints no link. A terminal's output is unchanged, and
browser auto-open still receives the link.

(cherry picked from commit c9b9b1d)
The runtime liveness check reads its own root pid for the handle-count
probe and marks the site pid-owner-ok, like the RSS probe beside it.
The pinned owner-marked count still said 8, so the Static Ratchet Gate
fails on main. Pin it at 9.

(cherry picked from commit 044a860)

Backport note: release/0.12.0 pins 7 owner-marked sites (it lacks main's code_review_sage review_pool.py marker), so the #32376 pick's handle-count probe makes 8, not 9. The pin is 8 here.
@bolichen97
bolichen97 requested review from a team and KiroCrewCaptain as code owners November 9, 2026 16:37
@bolichen97
bolichen97 requested review from tim-finnigan and removed request for a team November 9, 2026 16:37
@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Sensitive Change Review

Sensitive files changed:

  • src/kiro_crew/log_redaction.py

  • src/kiro_crew/security/redaction.py

  • src/kiro_crew/security/redaction_patterns.py

  • src/kiro_crew/security/text_redaction.py

  • @bolichen97 posted a complete reasoning template for 4bcbd58.

@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 4bcbd5832e0db1e4b279cbec0f2b4e45437f2b74 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks: each hunk is a cherry-pick of a fix that was already reviewed on main, and none of the dashboard changes adds or reshapes a surface. They change wording, plurals, the folder-chip translation and Strands key focus handling.

Notes

  • The description is cut off at row 36, so its ## Backwards compatibility section and the two release-only commits it mentions were not checked against the diff. Check those two commits by hand, because they are the only code in this PR that main never saw.
  • The releaseNotes: feed line goes into the publish workflows with nothing around it, so it relies on scripts/feed_release_notes.py printing valid YAML (a JSON string or ""). Confirm that script is in this batch, or the release feed job breaks on 0.12.1.

[DESIGN-REVIEWED] 4bcbd58

Description read

[DESCRIPTION-READ] 37e156cedc1fd36e282b3556e812780ec7ac70b60a9d2563dd11285af78ce6f8

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

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

UX-level review of 4bcbd5832e0db1e4b279cbec0f2b4e45437f2b74 — 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 no image, so the blind read was not performed, and three dashboard surfaces this backport changes went unseen.

Evidence gaps

  • Report a problem diagnostics line (ReportProblemModal.tsx): the "Diagnostics ready — {{secrets}} {{where}}." success line now has singular and plural forms. Attach a still of the modal after collecting diagnostics, ideally once with 1 secret / 1 file and once with several.
  • Artifact folder chip (ArtifactDetailPageHeader.tsx, folder_chip_unfiled): the label on an unfiled artifact is now translated. Attach a still of the artifact detail header with no folder set, in a language other than English.
  • Strands Save and Delete buttons while a write runs (StrandsSetupCard.tsx): they now use aria-disabled with aria-disabled:opacity-30 instead of native disabled, which is a new dimmed look. Attach a still of a Strands key field with a save or remove in progress.

Notes

  • Each change is a cherry-pick of a fix already merged on main. A still per surface from the release build closes every gap here.

[UX-REVIEWED] 4bcbd58

Description read

[DESCRIPTION-READ] b05f9f0786bb4e3e68a145921dea037191395194aab61443e48a3c70e577fc2b

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 9, 2026

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 4bcbd5832e0db1e4b279cbec0f2b4e45437f2b74 — 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 reviewed main merge cherry-picked onto the release branch, so no new shape is decided here. One premise can't be read: the intent file is cut off at 8000 bytes before the two release-only commits are listed.

Notes

  • Item 10 — undeclared: the description says "two release-only commits make two of them build on release's own code", but the fetched intent is truncated before they are named, and this diff cannot be told apart from the -x picks. Subtraction: drop anything in those two commits beyond the exact adaptation one pick needs.

What this change ships

Inventory (10 items) — 9 justified

Intent: give 0.12 users the bug fixes that already merged to main, as a patch release. This is a FIX.

  1. bench, pod, restart, stop and chat CLI misbehaviours corrected (fix(cli): write kirocrew bench errors to stderr #30153, fix(pod): name only the host's own mechanism in pod --help #30240, fix: refuse restart beside a stopped user unit hidden by a system alias #32363, fix: name the Windows desktop gateway from its run record so stop/restart refuse it #32814, fix: open each kirocrew chat session with the session context #32932, fix: wait for a pod's whole stop before pod down reports #33272) — justified
  2. macOS universal signing succeeds (argument size, 102,400-byte manifest cap, part split) (fix(signing): send the sign request body on stdin, not as an argument #31083, fix(signing): sign an over-limit universal manifest in parts #31289, fix(signing): carry the shell entries in every part of a split signing request #31401) — justified
  3. Desktop update notes appear on the About page and in the update popup (fix: show release notes for a pending desktop update #31223) — justified
  4. Dashboard fixes: replay, slot close, usage, artifact chip, Computer Use probe, Strands focus, Report a problem — justified
  5. Crash dumps of a killed gateway no longer read as clean and get swept (fix: keep the crash dump of a gateway that died without a clean exit #32205, fix: keep a killed update restart's crash dump from reading as clean #33150) — justified
  6. Hostnames containing eyJ are no longer treated as JWTs in redaction, the decisions gate or the dashboard sanitizer (fix: stop redacting hostnames that contain eyJ as a jwt #31997) — justified
  7. Windows fixes: text-mode patch pipe, supervised-gateway refusal, handle count — justified
  8. Agent prompt now says that processes it starts end with its runtime (fix: say plainly that agent-started processes end with the runtime #30860) — justified
  9. Pod down client timeout raised from 60 s to 120 s, and the bench CI step pipes stderr (2>&1) — justified
  10. Two release-only adaptation commits — undeclared, contents not listed in the fetched intent

[FIRST-PRINCIPLES-REVIEWED] 4bcbd58

Description read

[DESCRIPTION-READ] ffa232d7e3c9e1ecba0e54d630039d630a43e768d15e31647d63f5fd97edf45b

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.

@bolichen97

Copy link
Copy Markdown
Contributor Author

Sensitive change review

  • Head commit: 4bcbd58
  • What rule changed: The JWT spelling in the log record filter (log_redaction.py) and in the credential scan (security/redaction_patterns.py, security/text_redaction.py) now counts an eyJ... hit as a JWT only when its first segment base64url-decodes to a JSON object (kiro_crew/jwt_header.py is_jwt_header), the check the chat scrubber already applied on release. This is fix: stop redacting hostnames that contain eyJ as a jwt #31997 (main 5635855f0e0311118baa479bcc4cc1e1653f11b5), carried by a verbatim cherry-pick -x; no other commit in this batch touches these four files.
  • Before -> after (what was allowed/blocked, now): Before, any eyJ<seg>.<seg>.<seg> shape was masked on shape alone, so a host label holding eyJ (honeyJar.atlassian.net) was cut in half in logs, refused as a credential by the decisions gate, and mangled by the dashboard sanitizer. After, that hostname is left intact; a real JWT (JSON object header) is still masked; a token glued after a rejected hit (honeyJar.<jws>) is rescanned from the next character and still masked; a header holding a second eyJ, or a JSON object Python cannot parse (too deep, or an integer past its digit limit), still counts as a JWT, so the check fails closed.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): leaks secret: a JWT whose first segment is not a base64url JSON object would stay unmasked in a log line. Bounded: every JWS and JWE header is a base64url JSON object by spec, and the chat scrubber already used this same test before this pick.
  • Evidence checked (which sandbox result proves it): N/A for a sandbox result, because no sandbox rule, mask or seal changed; this is a text redactor. The proof is the redaction tests: test/test_jwt_header.py, test/test_log_redaction.py, test/test_redaction_mirror_parity.py, test/test_decisions_gate.py, and the website src/test/sanitizeCredentials.test.ts and src/test/sanitizeCredentialsGlued.test.ts (a real JWT masked, the hostname kept, the glued token masked, Python and TypeScript mirrors in step). All passed on this tree.
  • No regression:
    • Tools still work (which tools/commands were run, result): N/A for a tool run, because no tool, command, permission or approval rule changed; only which strings the redactors mask. The tests above exercise the log filter, the scrubber and the decisions gate directly.
    • Backward compatible (old config / old data / old callers still work, how checked): no config, data format or public API changes. The private helper _is_json_object_segment moved into kiro_crew/jwt_header.py as is_jwt_header; git grep on this head finds no remaining caller of the old name, and every caller imports the new one.
    • Existing tests (which suites passed on this head): the batch pretest on branch db6479eb12, whose tree 0af3c8270f is this head's tree byte for byte: 104 backend files (the 83 the picks touch plus all 22 test/*ratchet*.py), 5,165 passed, 35 skipped, 0 failed; 7 website test files, 171 tests passed.
  • How to undo: git revert the fix: stop redacting hostnames that contain eyJ as a jwt #31997 pick on release/0.12.0; nothing to migrate back, since no stored data or config changes shape.

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Security Scope Review -- ✅ PASS

Which legitimate operations does 4bcbd5832e0db1e4b279cbec0f2b4e45437f2b74 newly refuse? Updated in place on each push. A script-confirmed regression blocks; the model proposes candidates and never decides a refusal.

Verdict basis: adjudicated, zero confirmed regressions.

Security scope review -- adjudicated candidates

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

No candidate flipped from allowed to refused.

Scope-Verdict: PASS

Reason: This diff does not touch the shell deny composite (hooks.py SHELL_DENY_TIERS, is_sensitive_bash_command, audit_bash_exfiltration, is_denied), so I expect the candidates to confirm no regression. The tightenings it does make are in places the classifier cannot reach: the skill-script validator, the KAS allowedTools translation, the cron route guard and the login-link print gate. They are named below as unadjudicated gaps, and none is a demonstrated regression.

TIGHTENING: skill-script validator sensitive-path regex now accepts \ and \\ as well as / -- it refuses generated skill scripts that reach credential stores through Windows spellings (+ re.escape(d).replace("/", r"[\\/]+") in src/kiro_crew/skills_script_validator.py). Smaller tightenings ride along: KAS translation stops sending ? and any \ (+ if "\\" in ref or _GLOB_METACHARACTERS.intersection(server):), the cron session-control guard now covers /api/chat/slots/<id>/reset-conversation, and startup and restart print no ?token= link unless stdout is a tty (+ return bool(isatty and isatty())).

ADJUDICATED: 25 candidates, 0 confirmed newly-refused

PLATFORM COVERAGE: I wrote posix and windows rows; no any rows, because every candidate names an executable or a path. The validator change only matters for backslash separators, so the windows rows put \ paths next to sensitive entries without being one of them: $env:USERPROFILE\.kiro\agents beside .kiro\crew-auth-staging, %USERPROFILE%\.config\kirocrew beside .config\gcloud, and .venv\Scripts\python.exe test runs. The posix rows cover the same neighbours with / (~/.kiro/agents, git config --global credential.helper beside .git-credentials, docker context ls beside .docker/config.json). The login-link gate is spelled differently per platform, so both are covered: kirocrew token / kirocrew.exe token, do-restart.sh / do-restart.ps1, and the gateway log read with tail and with Get-Content. The permission probe is spawned under -P with a platform-specific interpreter, so I wrote it as both python3 -I -P -m … and .venv\Scripts\python.exe -I -P -m …. These rows only check the shell gate, not the guards changed in this diff.

UNADJUDICATED:

  • Skill-script validator (skills_script_validator._SENSITIVE_PATH_RE). Call path: a generated skill candidate goes through the script validation entry point (staging and auto-approve), then the _SENSITIVE regex scan over the script source. No verdict is available for these inputs, which I would have submitted:

    • Python source holding a Windows path built with \\ that ends in a sensitive leaf name but means something else, e.g. a project folder C:\\work\\.azure-pipelines (blocked by (?!\w)? - is not \w, so .azure matches).
    • C:\\repo\\.npmrc.example (. is not \w, so it matches).
    • A regex literal or docstring containing \\.ssh.

    The new [\\/]+ only changes multi-segment entries (.config/gcloud, .docker/config.json, .kube/config, .kiro/crew-auth-staging, the adapter stores). The bare-leaf over-matches above already existed before this diff. What is new is the Windows spelling of the multi-segment entries, e.g. a script that names .kube\\config-samples. That is narrowing to argue, not a confirmed regression.

  • KAS allowedTools translation (acp/kas_permissions._mcp_pattern). Call path: an agent's allowedTools @server/tool entry goes through _mcp_pattern, then the KAS resource rule. An entry such as @github/get_?ssue or @srv/tool\_name now returns None, so the KAS backend prompts where it used to auto-grant. Inputs I would have submitted: @db/query_?, @fs/read\*. By the diff's own reasoning, the stricter result (a prompt) is the intended one.

  • Cron session-control guard (dashboard/handlers/_shared_route_guards._cron_session_control_refusal). Call path: POST /api/chat/slots/<id>/reset-conversation with an X-Session-Key: cron:<job> header now gets refused. Input I would have submitted: a script cron that resets its own slot's conversation before each run. That is a dashboard HTTP route, not a shell line.

  • Login-link print gate (dashboard/urls.login_link_may_print). Call path: gateway startup lines and kirocrew restart when stdout is not a tty, e.g. systemd/launchd, the docker exec logs, or the do-restart.* pipe. An automation that scraped ?token= from gateway.log or from kirocrew restart | … loses the link and has to run kirocrew token instead. I submitted the remedy commands as rows, but whether a non-tty consumer still gets its link depends on runtime state, which no shell classifier can judge.

[SCOPE-REVIEWED] 4bcbd58

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ human override accepted

Human judgment by @bolichen97 overrides the GPT 6.1 finding for 4bcbd5832e0db1e4b279cbec0f2b4e45437f2b74; the recorded reason is authoritative for this commit.

[GPT-OVERRIDE] 4bcbd58

This comment is updated in place on each push.

The model was not re-run because an authorized human decision supersedes it.

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 4bcbd5832e0db1e4b279cbec0f2b4e45437f2b74 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
@bolichen97

Copy link
Copy Markdown
Contributor Author

/ai-review override gpt 4bcbd58 pre-existing: agent: verbatim cherry-pick of main a1f286a (#32457), same patch-id; origin/main still runs this one-time shared-registry adoption on the loop (run_registry.py:115). The adjudicator rated it LOW harm: a self-clearing first-boot stall, not a security, data-loss or crash defect. Moving it off the loop is a main fix first, then a backport, not a change to this pick.

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Human judgment recorded

@bolichen97 recorded a pre-existing release (class pre-existing) for the gpt AI finding on 4bcbd5832e0db1e4b279cbec0f2b4e45437f2b74.

agent: verbatim cherry-pick of main a1f286a (#32457), same patch-id; origin/main still runs this one-time shared-registry adoption on the loop (run_registry.py:115). The adjudicator rated it LOW harm: a self-clearing first-boot stall, not a security, data-loss or crash defect. Moving it off the loop is a main fix first, then a backport, not a change to this pick.

This decision applies only to this commit. A new push requires a new judgment.

@bolichen97

Copy link
Copy Markdown
Contributor Author

/ai-review override fable 4bcbd58 not-applicable: agent: Opus discovery cannot finish one pass over this 879,120-byte, 233-file diff: both runs ended with no [OPUS-DISCOVERY] marker and no finding (https://github.com/kirodotdev/KiroCrew/actions/runs/42656690652). 48 of the 50 commits are verbatim cherry-pick -x of merged main commits (e.g. a1f286a #32457, 5635855 #31997); GPT, Design, UX, First Principles and Security Scope reviewed this whole head, the 2 release-only fix-ups included.

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Human judgment recorded

@bolichen97 recorded a not-applicable release (class not-applicable) for the fable AI finding on 4bcbd5832e0db1e4b279cbec0f2b4e45437f2b74.

agent: Opus discovery cannot finish one pass over this 879,120-byte, 233-file diff: both runs ended with no [OPUS-DISCOVERY] marker and no finding (https://github.com/kirodotdev/KiroCrew/actions/runs/42656690652). 48 of the 50 commits are verbatim cherry-pick -x of merged main commits (e.g. a1f286a #32457, 5635855 #31997); GPT, Design, UX, First Principles and Security Scope reviewed this whole head, the 2 release-only fix-ups included.

This decision applies only to this commit. A new push requires a new judgment.

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ human override accepted

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

Human judgment by @bolichen97 overrides the Opus 5.5 finding for 4bcbd5832e0db1e4b279cbec0f2b4e45437f2b74; the recorded reason is authoritative for this commit.

[OPUS-OVERRIDE] 4bcbd58

Verdict recorded from an authorized human decision for commit 4bcbd5832e0db1e4b279cbec0f2b4e45437f2b74.

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

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.

9 participants