Skip to content

fix: 0.13 backport, Kiro telemetry from dev homes and the one-time off-form offer (#37460, #37463, #37545) - #37598

Closed
chenmingwei23 wants to merge 102 commits into
release/0.13.0from
crew/backport-0.13.0-telemetry-b
Closed

chenmingwei23 wants to merge 102 commits into
release/0.13.0from
crew/backport-0.13.0-telemetry-b

Conversation

@chenmingwei23

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Ship the two follow-ups to the Kiro telemetry destination in 0.13.0. #37471 put #22397, #33422 and #37183 on release/0.13.0; these two merged on main after it and are not on 0.13 yet.

Backport onto release/0.13.0 (head de4155bd701b, #37471). Each source commit was picked with git cherry-pick -x in main's merge order, then the picks were squashed into one commit, which lists the source PRs and their main commits. All three picks applied with no conflict, and git range-diff shows each backported patch is identical to its main commit.

Pick Main commit What 0.13 users get
#37460 2a679d6f4279 The built-in Kiro telemetry destination is also listed under a non-default KIROCREW_HOME (dev homes, pods, worktree previews). kiro_export.destinations() drops only the is_default_home() check; the LTS, CI and test-suite gates and every consent gate stay. The daily heartbeat keeps its own default-home rule.
#37463 8de422de3c39 Installs that are off only because an older build wrote telemetry.enabled: false into every new config see the Privacy chapter once, in an off form that names Kiro telemetry, with Turn on performance metrics / Keep off. kiro_export.off_offer_due decides that case. Keep off records only the notice version, so it is not asked again.
#37545 09b0ddc69e18 Test only: the TestOffOffer tests fake the default data home, since the offer is asked only there. Without it three tests from #37463 fail on 0.13 as they did on main.

Why it matters

Without #37463, most existing public-build installs on 0.13 stay off without having chosen it and never see the notice v3 text that #37471 shipped. Without #37460, the 0.13 docs and destination listing disagree with main for non-default homes.

Not a goal

  • Any other main commit. Nothing outside the three picks is carried.

What changed (motivation -> approach -> change)

No hunk was hand-resolved. Files with an auto-merge: docs/system-specs/modules/metrics.md, src/kiro_crew/dashboard/handlers/core.py, the i18n locale files, website/src/shell/boot/firstRun.tsx, website/src/test/App.test.tsx. Original authorship is named in the commit message.

Backwards compatibility

Behaviour change by design, the same as on main. Dev homes that have recording on and notice v3 acknowledged now also send the reviewed product metrics to Kiro telemetry. Installs off only by an old written false are asked once; nothing turns on unless the person picks Turn on. Nothing is removed: no key, path or record.

Tests

Test changes come from the picks.

Release PRs get no backend test lanes in CI, so the backend tests ran locally with pytest -n 2 on the squashed tree: metrics/test_kiro_export_destination.py, test_telemetry_consent_notice.py, test_usage_notice.py, test_telemetry_handlers_cov80.py, test_api_theme_config.py, metrics/test_telemetry_handler.py, test_telemetry_ui_control_route.py, metrics/test_provider_otlp_destinations.py, metrics/test_otlp_endpoint_list.py: 448 passed. Without #37545 the same set had 3 failures in TestOffOffer.

Frontend: vitest PrivacyChapter.test.tsx and App.test.tsx, 128 passed; tsc -p tsconfig.app.json clean; eslint on the changed .ts/.tsx files clean; scripts/check-i18n-keys.mjs OK. flake8 and black on every changed Python file: clean.

Manual verification

N/A. Unit coverage above; the same changes are on main.

Screenshots / video

These are the screenshots from #37463 on main. The backported PrivacyChapter.tsx diff is identical to main's.

Off form shown to a user who is off only because of an older build's written false:

Privacy chapter off form at 1280x640: intro naming Kiro telemetry, heartbeat fields, bottom fade, Turn on performance metrics and Keep off

The same form at 1280x900:

Privacy chapter off form at 1280x900

Turn on whose save fails: the read-back shows recording still off, so the form says nothing changed:

Privacy chapter off form showing the save error after Turn on failed

Turn on whose switch lands but whose acknowledgement fails: the chapter shows the on form with Keep on / Turn off:

Privacy chapter after a half-landed Turn on: on form saying metrics are now on, Keep on and Turn off

Turn on whose result cannot be read back:

Turn on whose result cannot be read back: may now be on

Keep off whose result cannot be read back:

Keep off whose result cannot be read back: could not be saved or confirmed

Related Issues

Backport of #37460, #37463 and #37545.

Sibling sweep

Siblings: none -- the backport touches the same sites the picked PRs changed on main

Pattern harvest

Not generalizable: backport of already-reviewed changes

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.

bolichen97 and others added 30 commits November 13, 2026 09:28
Start the 0.13.0 insider line on release/0.13.0. The three version
files declare 0.13.0-rc.1, as release.md asks of a release branch that
is cutting RCs, and the tag v0.13.0-rc.1 goes on this commit once it
merges.

CHANGELOG.md gains the 0.13.0 section, written once under its final
heading from the commits main took after the 0.12 branch point, less
the fixes 0.12.1 and 0.12.2 already shipped. The shipped 0.12.2 section
is already on main, so nothing else in the file changes.
…36536)

The local-destructive-rm-rf-root row matches its pattern anywhere in the
text, so `rm -rf /tmp/build && mkdir -p /tmp/build` was refused as a
deletion rooted at the filesystem root. Only the literal -rf spelling is
refused: -fr, -r -f and --recursive --force already pass on main, so the
row protected nothing for these paths and only pushed agents to respell.

The row now reads a view of the command in which the words of each plain
`rm` whose every operand is a direct /tmp/<name> entry are blanked. The
rm must be the unquoted program word (after kiro-cli's "Running:" title
prefix at most), every word literal (no $, glob, brace, paren, quote or
escape), no `--`, nothing glued on either edge (a backtick or paren
there lets bash add operands), and each operand exactly one component
under /tmp, so no folder on the way can be a symlink an earlier command
planted. Redirections stay in the text. Every other row, and the rm
floor for / and ~, still read the full text.

Four existing tests used /tmp/<name> as an always-refused example; they
now use /srv/<name> (or /etc), keeping what each test checks.

Replay of 25 recorded rm-row false positives: 17 now allowed; every
recorded true positive is still refused. No catalog regex changed.

Co-authored-by: Joe Guo <zejiangg@amazon.com>
(cherry picked from commit 3b22e33)
…is (#36538)

Co-authored-by: Joe Guo <zejiangg@amazon.com>
(cherry picked from commit e80a131)
…36603)

The KAS engine sends one extra model request at a session's first
prompt to title the session for kiro-cli's own session list. Crew
titles its chats itself and never reads that title, so apply_spawn_env
sets KIRO_DISABLE_SESSION_TITLE_LLM=true on both routes; an inherited
value wins.

Closes #35799

(cherry picked from commit 5275a5d)
…at (#36530)

Every chat starts Kiro Crew's own MCP servers, and each loads its tool
handlers right after its tool list. kirocrew-guide, kirocrew-mate and
kirocrew-cron imported all of kiro_crew.mcp_core for its HTTP verbs and
identity resolvers, which loads the whole core server: about 970
package modules and 90 MB per process, three times per chat.

The verbs (_send, _get, _post, _patch, _put, _delete) move to the
gateway owner, mcp_core_parts/gateway.py, beside the target resolution
they already used. mcp_core stays their import path and patch surface
through its mirror facade. The three servers import the verbs and the
identity resolvers from mcp_core_parts, so their handler modules load
about 310 to 430 package modules and never the core server. The listing
import-budget test now also bounds each small server's handler import.

The default agent's never-defer row also gains its six most used small
own tools (autonudge_stop, memory_recall, nothing_to_do,
search_chat_history, skill_search, wait), picked by how many default-
agent sessions called each at least once. A first use of one no longer
costs a tool-load model call. The row grows by 1,491 schema tokens; its
budget moves from 3,300 to 4,950.

(cherry picked from commit 5ea941c)
…36362)

While the official catalog is unreachable, or the listing is backing
off after a failed fetch, every store listing raised CatalogUnavailable
into a broad except that logged a full stack trace at WARNING. That is
an expected answer and it recurs on every listing, so the log filled
with identical tracebacks. Both listing paths had it: list_registry's
inventory, and the catalog-first listing's _catalog_installable_rows.

Catch CatalogUnavailable first at both sites and log through one
helper, official_catalog.log_unavailable: one WARNING line naming the
cause, the stack at DEBUG. Any other exception keeps its traceback at
WARNING, since that one is a bug, not an outage. The app-kit-platform
spec records the split.

(cherry picked from commit 62f35ec)
#36558)

The sweep that stops the app backends a gateway spawned is a dashboard
cleanup hook, and aiohttp runs cleanup hooks only after in-flight
requests drain (up to 60s). An open /api/logs stream holds that drain
past the 10s graceful budget, so the budget cuts the shutdown before
the sweep runs and os._exit leaves every backend and its sandbox
wrapper running under PID 1, still holding its port.

The exit path now runs the same sweep after the graceful shutdown,
before its hard exit. When the cleanup hook already ran, the tracking
table is empty and the sweep returns at once. Adopted backends stay
excluded, as before.

(cherry picked from commit ee81308)
* perf(crew): one scheduler for crew-workers reads: no overlap, capped, backoff, If-None-Match (Refs #36154)

A page that is hidden no longer re-reads the list, a re-read never cancels
or doubles one in flight, at most two list requests are out per origin so a
send always finds a free connection, slow answers widen the wait, and the
client sends the last ETag and keeps its cached list on a 304.

* fix(crew): crew-workers reads wait for a free slot; ETag read by lowercase name (Refs #36154)

A read over the cap now waits in a FIFO queue and reads fresh data instead
of resolving with the cached list, cold loads obey the cap too, and a
rejected read frees its slot. Header names are case-insensitive, so the ETag
is read in lowercase, which the untranslated-literal gate does not flag.

---------

Co-authored-by: kirocrew-agent <agent@kirocrew.local>
(cherry picked from commit db39373)
… write (#36534)

Co-authored-by: Joe Guo <zejiangg@amazon.com>
(cherry picked from commit ac45981)
…e prompt (#36593)

* perf(acp): record the process tree beside the start and the turn end

The runtime walked its process tree in front of the person three
times: after the initialize handshake, after session/new or
session/load, and at the end of every turn. On macOS that walk starts
a pgrep per process and a ps per pid, 352 ms with no servers and
954 ms with 64 on the first prompt alone, and 68 to 105 ms at the end
of each warm turn.

Only a kill or a teardown reads that record. So the spawn, every
session start and the shared runtime's turn end now start the same
guarded pass as a task, and every reader that signals or takes a kill
handle waits for it first: _kill_inner before it signals the root,
and refresh_process_tree before its own walk. The identity data and
its checks are unchanged; the record is written before anything acts
on it.

Part of #36582

* perf(kas): read the MCP config scopes once per agent projection

The KAS custom-agent projection asked mcp_server_muted_in_any_store
about each declared server, and each call re-read every MCP config
scope through the sensitive-path fence. Two loops did that per start,
so the projection grew with the user's servers: 214 ms with 30 servers
on Linux against 45 ms with none, and 359 ms with 64 on macOS.

Both loops now read mcp_scope_muted_aliases once and hand the set to
the predicate, through the same reader and patch seam. The answer per
server and the payload are the same.

Part of #36582

(cherry picked from commit aeb98eb)
…35590)

An app agent such as Mochi took a granted server's launch spec only
from its template, the Kiro global mcp.json and the managed servers,
so a server added on the MCP Management page, installed from a
registry or contributed by the edition was skipped with "no launch
spec found" while the app reported the policy applied. A built-in
app's grant now reads the default agent's own spec ahead of the
global file, the rebuild's merge of those sources with the store
winning a tie, and leaves out other apps' own servers. A
user-installed app writes its own grant file and no owner consent
covers what it names, so its grant keeps main's sources. A copied
entry that is muted is withheld: turned off, not yet consented, or a
secret:// reference the rebuild withholds.

Enabling an app, or re-installing an installed one from the registry
(how a registry-sourced app updates), wrote its <app>:<server> entries
into the agent spec and stopped, so on a harness that does not watch
the spec file a chat already open never got the change. These routes
now end with the step an MCP page write ends with, as update, disable
and uninstall already do; the enable decides it from the app's record
as it stands inside the lifecycle lock. A fresh install registers
nothing for the disabled record it writes, so it needs no step.

Closes #33020

(cherry picked from commit 712d24f)
…36194) (#36262)

A slot-detail page stops at 1.5 MB of serialized rows, cut from the old end;
the newest row is always sent, so a row over the budget goes alone and is never
dropped. next_before and has_more point at the first row actually sent. The
finished body goes through conditional_json_response: ETag/304 and gzip, no
change to the response shape.

Co-authored-by: kirocrew-agent <agent@kirocrew.local>
(cherry picked from commit b77f3df)
)

opencode 1.x keeps a saved session on the directory it was created in.
A session/load naming another cwd split the session across two of its
instances: approval replies went to the wrong one and were dropped, and
the MCP servers sent with the load (Kiro Crew's own tools) were mounted
where the model was not.

Add ACP_BACKENDS_CWD_BOUND_SESSIONS (opencode). When the stored cwd of
a member's saved session differs from the folder the chat now starts
in, the allocator does not hand the client the resume sid, so the start
opens session/new in the new folder and the conversation is replayed
as text. kiro-cli takes the cwd from each load and keeps native resume.

Fixes #35459

(cherry picked from commit a67f6ed)
On a KAS main harness with no stored Kiro Crew sign-in, agents run on
kiro-cli's login. When the usage API refused that credential, the Kiro
account popup showed the passive "No active Kiro sign-in" notice, as if
nobody had signed in, with no error and no agent hand-off.

The usage reply now marks a refused credential with
credential_rejected, and the popup shows that state as the error
notice with the agent hand-off. A missing credential keeps the passive
notice, and a stored Kiro Crew sign-in keeps its own lapsed notice.

Closes #35483

(cherry picked from commit 94155a1)
…36818)

The shared reader behind the [AGENT SYSTEM PROMPT] block now takes
kiro-cli's systemPrompt spelling, expands $VAR and ~ in a file:// path,
checks the resolved path with the same rule the KAS reader uses, and
names a prompt file it cannot use in one WARNING. It reuses
acp/kas_prompt.py (spec_prompt, the new expand_prompt_ref) and
acp/kas_prompt_paths.py rather than copying them.

Co-authored-by: Joe Guo <zejiangg@amazon.com>
(cherry picked from commit 4c7a874)
Inside a memory-limited container /proc/meminfo reports the VM or node
the container runs on, so /api/system showed that machine's total and
free memory while spawn admission sized against the container's cgroup
limit. On an 8 GiB Fargate task with a 7.75 GiB container limit the
gauge read 15.4 GB total.

The cgroup walk admission uses now also returns the tightest limit
(_container_cgroup_reading). Session import's (limit, headroom) reader,
_cgroup_memory_bounds, drops its own limit loop and reads that walk, and
/api/system calls it, so the Linux memory figures are bounded by the
limit and the headroom under it. The agents slice stays out of the
gauge: it caps agent processes, not the machine.

(cherry picked from commit 848e002)
…nded (Refs #36194) (#36845)

Turn-end and reconnect refreshes (refreshSlot, warmSlotCache, switchSlot and
the pane hydrate all read the newest bounded page through api.chatSlotDetail)
now ask for a cursor (cursor=1) and echo it on the next read, with
If-None-Match set to the last ETag. A refresh that missed nothing gets a 304;
one that missed rows gets only the rows from since on. A cursor the server
rejects (400) or a delta that does not fit the held page is read whole.

A cursor-mode page is now cut by the same byte budget as a plain page, so the
dashboard's reads keep the bound from #36262.

warmSlotCache no longer reads the whole transcript when the count-matched
bound declines (legacy rows with no timestamp): it reads one clamp-sized page
and walks older pages, as refreshSlot and switchSlot do.

Co-authored-by: kirocrew-agent <agent@kirocrew.local>
(cherry picked from commit 714b0d5)
On KAS, a chat whose project has files in .kiro/hooks got the "hook
files in .kiro/hooks do not run" notice again on every new backend
session, so each reconnect, reload or restart added one more copy.

The chat now keeps a mark of the project folder and the sorted file
names, the way the KAS telemetry notice does, and saves it on the
chat's metadata line. The notice shows again only for another folder
or another set of files.

Closes #36821

(cherry picked from commit 911bde8)
With Kiro CLI saved as the harness on a computer where Kiro CLI runs
on Kiro Agent, the Kiro CLI row in Settings > Agent Harness said "New
sessions switch from Kiro Agent to Kiro CLI." and showed a "Use Kiro
CLI" button. The button saved the value that was already saved, so
nothing changed and the panel showed the same two lines again.

The row now shows no button in that state and says that Kiro CLI runs
on Kiro Agent. Every other row keeps its button, and so does the Kiro
CLI row when Kiro CLI does not run on Kiro Agent.

Closes #36170

(cherry picked from commit ecf7d56)
…#36069)

A shared MCP server that waits for an approval showed nowhere outside
the MCP Servers page, so a pause could go unseen for days. The Customize rail
row and its MCP Servers tab carry the count of such servers, read by
the shell from the same status query the servers list's notice uses;
the tab's label is a plural catalog key. The gateway
records a refusal when it starts, so the socket's connect handler marks
that read stale and the shell's own poll runs only every five minutes.

The paused row's hint compared the approved and the new command lines
as lists. One line is drawn per launch, so one program listed twice
before and three times after read as a changed command although only
its env differed. The lines are compared as a set, and the env hint
says the program is the same and only its environment variables
changed. A line that carries a redaction tag never reads as the same
program.

(cherry picked from commit 21b6680)
)

The harnesses AcpClient starts directly (claude, OpenCode, goose, pi,
Copilot, DeepSeek) do not go through the runtime's retrying spawn factory,
so a CreateProcess refusal with winerror 5 or 1260 reached the chat as a
generic error. The shared launch tail now marks such an error at process
creation, naming the binary; ensure_ready keeps its one retry and then
raises the existing AcpSpawnBlocked for a marked error only, so the chat
shows the policy card. An access denied after the process started (a file
cleanup) is not marked and is unchanged. Detection only: nothing changes
how or whether the binary is started.

Co-authored-by: Joe Guo <zejiangg@amazon.com>
(cherry picked from commit 0b32483)
…ng (#36819)

On a host whose ceiling came from central distribution, KAS-managed MCP
children exited before MCP initialize ("Connection closed"): the sandbox
masked policy_cache, so a cache-only child found no ceiling.

The sandbox's existing read-only cache lift (enterprise_policy_cache_view)
now applies when central_ceiling_installed(), not only in an LTS build, and
keeps its refusals. The gateway derives the cache-only markers
(policy_cache_only_env) for the harness env, managed MCP declarations, the
KAS projection and the discovery probe. A cache-only child accepts a
source-less distribution block.

Closes #36775
Supersedes #36710

Co-authored-by: Joe Guo <zejiangg@amazon.com>
Co-authored-by: Pedro Evangelista <pedro.evangelista@mindera.com>
(cherry picked from commit 918a1c8)
The MCP page's sharing card hid its whole memory row whenever either
figure was missing. With sharing off no stub runs, so "with sharing"
has no stub price and is null, and the row vanished exactly when the
reading of what MCP servers use now matters most.

"Using now" now shows whenever it was read, on its own. "With sharing"
and its arrow show only when that figure was read too. No placeholder
stands in for a missing figure.

Part of #36884

(cherry picked from commit ed9d0b0)
…#36586)

While config.json has a change made outside Kiro Crew pending review,
every trust write the built-in adoption APPLY pass makes is refused
with PendingEditBlocksSave. The pass caught it as an unexpected error
and logged a full traceback at ERROR for each pinned app on every
boot, although nothing is wrong: the built-in keeps running and the
staged ledger is retried at the next start.

Treat that refusal as the expected state it is. The pin's outcome is
waiting_for_review, its ledger is left untouched, and the pass logs one
warning naming the pending file and every waiting app, with each trace
at DEBUG. Recording the legacy nav of an already adopted app waits the
same way, at DEBUG only.

Part of #26967

(cherry picked from commit 4579388)
A Bot's chat is a ChatPane, whose replies go through the shared bubble
(renderAssistantBubble). That bubble passed meta.redactions but never
meta.blocked_links, so a removed link stayed as its raw
"[REDACTED: suspicious URL to <host>]" text: no chip, no card, no
"Allow for this host". The bubble now passes the records on the same
local-slot rule as the lock tags, so a window drawing another gateway's
rows keeps the plain text and what can be allowed does not change.

After Allow or Undo, the chat page reloads only the slot it shows. A
pane now re-reads its own slot on the same event, so the restored link
replaces the chip in a Bot's chat too.

Closes #36862

(cherry picked from commit 8c58e18)
…ts (#31546)

A provider marks its one-run work directory (cron_<job>_<run>, subagent_<id>,
...) once, in start(), and its shutdown reclaim removes it. A runtime started
or resumed again for the same session after that reclaim -- a failed resume
that starts fresh, a killed runtime that respawns -- handed KAS a deleted cwd.
Node's spawn reports a missing cwd as "spawn <command> ENOENT", so every
managed MCP server failed naming a binary that exists, e.g.:

  KAS managed MCP initialization failed: kirocrew-cron: failed
  (spawn .../python3.12/bin/python3.12 ENOENT)

Defense in depth:
- Prevent: on the unbound (non-macOS) path, _session_work_dir re-creates a
  missing directory whose name has a one-run shape and whose parent is the
  workspace root, through mark_run_dir, so the reclaim and the sweep see the
  same provenance. A one-run name anywhere else is never created, only
  logged. Any other cwd skips the check and its thread hop, so a chat or
  title start reaches the admission gate in the same order as before.
  Errors are swallowed; the guard never adds a start failure.
- Diagnose: a managed MCP readiness failure with ENOENT names the
  session cwd when it no longer exists.

Docs: acp-client.md run work directory section.

Co-authored-by: Ray Xu <buluoray@gmail.com>
Co-authored-by: RAVI KUMAR <14358622+kingravi17@users.noreply.github.com>
(cherry picked from commit d1f38d7)
The Agent Harness detail for an absent harness showed its install
command bare. For OpenCode that is `npm i -g opencode-ai@1`, and on a
host without Node.js it fails with "npm: command not found" while the
card never says that npm comes with Node.js. Several other harnesses
send an `npm i -g` command too.

AgentInstallDetail now adds one muted line under an install command
that starts with `npm `: the command needs Node.js and npm on the
gateway host, with a link to the Node.js download page. A curl
installer or an empty command gets no line. The component backs both
Settings > Agent Harness and the first-run agent picker, so both get
the line. The new key is translated in every shipped catalog.

Closes #36377

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 5317def)
…#37539

Two backend tests on release/0.13.0 were red for reasons main has
already fixed in test-only commits:

- test/tracing/test_tracing_otlp.py expected four spans, but #37005
  (already on the branch) adds kirocrew.step. Cherry-picked #37171
  unchanged.
- TestSelfModuleIndexIsLinear failed three runs in a row on the 0.5 s
  budget (0.522 s, 0.511 s, 0.509 s). Took main's end state of
  test/test_denied_commands_security_cost.py and
  test/denied_commands_security_helpers.py, which carries #37451 (min of
  five readings), #37530 (tracer paused) and #37539 (count work, not CPU
  time), plus the #37539 hunk of
  docs/system-specs/common/testing-conventions.md. The picks conflict
  one by one because the file also carries #28293, a test-only change.

No src/ changes.

(cherry picked from commit 6de8528)
@chenmingwei23
chenmingwei23 force-pushed the crew/backport-0.13.0-telemetry-b branch from 495ec97 to 48292e2 Compare November 16, 2026 03:40
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Nov 16, 2026
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

/ai-review override first-principles 48292e2 owner-decision: Owner decision recorded at #37598 (comment) - dev homes send and the old-false one-time offer match main (#37460, #37463); head rebased onto the fixed release branch.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@chenmingwei23 recorded a owner-decision release (class owner-decision) for the first-principles AI finding on 48292e233e425482914de40cd59957b6a473e60c.

Owner decision recorded at #37598 (comment) - dev homes send and the old-false one-time offer match main (#37460, #37463); head rebased onto the fixed release branch.

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

@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 16, 2026
@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention labels Nov 16, 2026
chenmingwei23 and others added 2 commits November 15, 2026 21:37
…k runner (#37653) (#37818)

Playwright 1.58.2 has no ubuntu26.04 host entry, and kirocrew-linux-4-core
now boots ubuntu-26.04, so every fork PR's E2E, render benchmark and i18n
render gate fail at 'npx playwright install chromium'. On that image only,
set PLAYWRIGHT_HOST_PLATFORM_OVERRIDE to the ubuntu24.04 build and carry it
through GITHUB_ENV to the steps that launch the browser.

Part of #37647.

(cherry picked from commit b5ac843)

Co-authored-by: Bolin Chen <bolichen@amazon.com>
…f-form offer (#37460, #37463, #37545)

Backport to release/0.13.0 of three main commits, picked with
git cherry-pick -x in main's merge order and squashed into one commit.
They follow up #37183, which #37471 already put on 0.13:

- #37460 (2a679d6): the built-in
  kiro-telemetry destination is also returned under a non-default
  KIROCREW_HOME. kiro_export.destinations() drops only the
  is_default_home() check; the LTS, CI and test-suite gates and every
  consent gate stay. The heartbeat keeps its own default-home rule.
- #37463 (8de422d): installs that are off
  only because an older build wrote telemetry.enabled: false into their
  config are shown the Privacy chapter once, in an off form that names
  Kiro telemetry, with Turn on performance metrics / Keep off.
  kiro_export.off_offer_due decides that case; Keep off records only the
  notice version so it is not asked again.
- #37545 (09b0ddc): test only. The
  TestOffOffer tests fake the default data home, since the offer is asked
  only there and the test home is a private KIROCREW_HOME.

All three picks applied without conflicts; each backported patch is
identical to its main commit (git range-diff shows no change).

(cherry picked from commit 2a679d6)
(cherry picked from commit 8de422d)
(cherry picked from commit 09b0ddc)

Co-authored-by: Raymond Chen <chenmingwei23@users.noreply.github.com>
@chenmingwei23
chenmingwei23 force-pushed the crew/backport-0.13.0-telemetry-b branch from 48292e2 to 302590d Compare November 16, 2026 05:41
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: passed Eligible automated validation passed for the current revision labels Nov 16, 2026
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

/ai-review override first-principles 302590d owner-decision: Owner decision recorded at #37598 (comment) - dev homes send and the old-false one-time offer match main (#37460, #37463); head rebased onto release/0.13.0 with the #37818 Playwright fix.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@chenmingwei23 recorded a owner-decision release (class owner-decision) for the first-principles AI finding on 302590dbfeb367b61272d38949cd1630bd46c409.

Owner decision recorded at #37598 (comment) - dev homes send and the old-false one-time offer match main (#37460, #37463); head rebased onto release/0.13.0 with the #37818 Playwright fix.

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

@buluoray

Copy link
Copy Markdown
Contributor

@chenmingwei23 release/0.13.0 was rebuilt from main for 0.13.0-rc.2 (head 2fae50aae751029a1c9b2e5879ee762862df1dca). It already contains #37460, #37463 and #37545 (each merge commit is an ancestor of that head). Replaying this PR's commit 302590dbfeb3 onto the new head leaves no change. So I did not rebase or push this branch; it looks safe to close. Your call.

@chenmingwei23

Copy link
Copy Markdown
Contributor Author

Closing: release/0.13.0 now already contains #37460 (2a679d6) and #37463 (8de422d), and both ship in v0.13.0-rc.2, so this backport is no longer needed.

@github-actions github-actions Bot removed the readiness: action required A blocking check or review needs attention label Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge conflict Branch has merge conflicts with its base — author must resolve before merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.