Skip to content

refactor(sandbox): name the Python-env-only strip policy - #21663

Merged
KiroCrewCaptain merged 1 commit into
mainfrom
refactor/8054-name-python-env-strip-policy
Oct 19, 2026
Merged

KiroCrewCaptain merged 1 commit into
mainfrom
refactor/8054-name-python-env-strip-policy

Conversation

@iamwhatever

@iamwhatever iamwhatever commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: The "drop only Kiro Crew's Python settings, keep the user's credentials" rule for a child process has one name in sandbox, and every place that applies it calls that name.

Three spawn sites hand-write the same prefix loop over sandbox._PYTHON_ENV_PREFIXES: the dashboard terminal's shell (terminal_shell._pty_child_env), the voice list's aws polly describe-voices call (chat_voice.api_voice_voices), and the third-party branch of the pooled MCP backend spawn (mcp_gateway/daemon/launch.env_target_resolver). None of them can use scrub_agent_subprocess_env, because that one also strips SSH_AUTH_SOCK, AWS_*, GNUPGHOME and GIT_ASKPASS, which these children need. So the rule is real, has three callers, and no name.

Why it matters

The next caller copies the loop a fourth time, and copies drift: two of the three already compare case-sensitively while the third does not. With a name, a reader sees which policy a spawn uses, and a change to it happens in one place.

Not a goal

  • No change to scrub_agent_subprocess_env, scrub_env, or any agent spawn site.
  • No change to the control-plane branch in launch.py, which strips the wider _SPEC_ENV_DENIED_PREFIXES set.
  • No change to the membership of _PYTHON_ENV_PREFIXES.
  • Not touching the open-coded copies that open PR fix(voice): keep the gateway's Python env out of Polly's other aws calls #14207 adds; that PR can adopt the helper after this lands.

What changed (motivation → approach → change)

Three copies of one rule → give the rule a name beside scrub_env → sandbox_spawn.without_python_env(env=None) returns a copy of the environment without any _PYTHON_ENV_PREFIXES key and with every other key kept. The terminal shell, the voice list and the third-party MCP backend spawn now call it. The sandbox facade forwards the new name like its siblings.

  • src/kiro_crew/sandbox_spawn.py: the new helper, beside scrub_env.
  • src/kiro_crew/sandbox.py: the facade's type-checking import lists it.
  • src/kiro_crew/dashboard/handlers/terminal_shell.py, src/kiro_crew/dashboard/chat_voice.py, src/kiro_crew/mcp_gateway/daemon/launch.py: call it instead of the loop.
  • src/kiro_crew/dashboard/handlers/terminal.py: the facade's type-checking import follows its owner.

The helper compares names case-insensitively, as launch.py already did. For the terminal and the voice list this can only remove more: a lower-case pythonpath the gateway inherited. Python itself ignores lower-case names on POSIX, and Windows upper-cases environment names.

It is called without_python_env, not strip_python_env, because strip_python_env is already a keyword argument on the agent spawn path, and that path means the other policy.

Backwards compatibility

Compatible: each child gets the same environment as before, except the terminal and the voice list also drop lower-case spellings of the four Python keys.

Removes nothing: _PYTHON_ENV_PREFIXES stays exported from sandbox, and no public function or key is removed. The terminal facade's type-checking import changes from _PYTHON_ENV_PREFIXES to without_python_env because test_terminal_facade requires it to match what its owner modules import.

Tests

  • test/test_sandbox_no_isolation.py::test_without_python_env_drops_only_python_settings: all four Python keys (and a lower-case one) are dropped; PYTHONUNBUFFERED, SSH_AUTH_SOCK, AWS_*, GNUPGHOME, GIT_ASKPASS survive; the input is not mutated.
  • test/test_sandbox_no_isolation.py::test_without_python_env_defaults_to_os_environ: with no argument it reads os.environ.
  • test/test_sandbox_refactor_facade.py: the sandbox_spawn owner list names the new function.
  • Existing test_terminal_handler.py tests still assert PYTHONPATH/PYTHONHOME are absent while SSH_AUTH_SOCK, AWS_*, TERM and KIROCREW_TERMINAL survive in the terminal child.

Run locally before the first push: 9 related files, 1978 passed, 1 skipped (test_sandbox_no_isolation, test_terminal_handler, test_terminal_facade, test_chat_voice, test_mcp_gatewayd_coverage, test_mcp_cron_security, test_sandbox_refactor_facade, test_sandbox_refactor_generated_programs, test_s29_spawn_env_regression).

Run locally after the rebase onto main 2e50054d2e (same patch, no conflicts): 1263 passed, 1 skipped across 7 of those files plus test_session_allocation_bindings.py::test_every_name_patched_through_the_facade_reaches_every_owner_reading_it. That node timed out on the first head's CI shard; it is flake #21671, fixed on main by #21640, and it now passes here.

Run locally after each rebase onto main (2d378bf4b6, then 9d088c85ad; same patch, no conflicts): the same 7 files, 1262 passed, 1 skipped.

Rebased onto main 943a4e5c0e, which carries the test_history_bindings.py fix from #21792 (that file failed the Windows shard on the previous head): the same 7 files plus test_history_bindings.py, 1474 passed, 1 skipped.

Determinism: the two new tests passed 30/30 repeated runs, and the whole test_sandbox_no_isolation.py file passed in a shuffled order (13/13). Flake-pattern ratchet: 58 passed.

Manual verification

N/A — unit coverage sufficient: the change only moves an existing loop behind a name, and each call site is covered by its existing environment tests.

Related Issues

Closes #8054

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

@github-actions

github-actions Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

Sensitive Change Review

Sensitive files changed:

  • src/kiro_crew/sandbox.py

  • src/kiro_crew/sandbox_spawn.py

  • @iamwhatever posted a complete reasoning template for f33dc55.

@github-actions

github-actions Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

Revision f33dc550e29a733a91a683c5641600ba8afa27b1 touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Advisory — does not block merge.

@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 17, 2026
@github-actions

github-actions Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of f33dc550e29a733a91a683c5641600ba8afa27b1 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Check that no test or the terminal facade mirror still patches _PYTHON_ENV_PREFIXES through terminal_shell or chat_voice. Those modules no longer bind it.

[DESIGN-REVIEWED] f33dc55

Description read

[DESCRIPTION-READ] 44e8a2c1accfe3baa6b91fa178d4fd330df20204d19ab1f384528ad61a39062f

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 Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of f33dc550e29a733a91a683c5641600ba8afa27b1 — 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/CONCERNS are advisory.

First-Principles-Verdict: PASS

Nothing to check.

Not justified as shipped

  • Item 5 — rides along: the refactor changes behaviour slightly: "the terminal and the voice list also drop lower-case spellings of the four Python keys". The change is declared and causes no harm.

What this change ships

Inventory (6 items) — 5 justified

Intent: give one name to the rule that a non-agent child gets every environment variable except Kiro Crew's Python settings, so spawn sites stop copying the loop. This is a FIX (Closes #8054).

  1. A new helper, sandbox_spawn.without_python_env, that drops only the Python settings (3 src consumers) — justified
  2. The dashboard terminal's child environment is built through the helper — justified
  3. The voice list's aws polly describe-voices environment is built through the helper — justified
  4. The third-party branch of the pooled MCP backend spawn uses the helper; the control-plane branch is unchanged — justified
  5. The terminal and voice children now also drop lower-case python* keys — rides along
  6. The sandbox and terminal facades forward the new name — justified

The grep for _PYTHON_ENV_PREFIXES in src/ finds no fourth hand-written loop. The other uses are in sandbox_argv.py, which feeds the launcher's prefix lists, and in scrub_env/scrub_agent_subprocess_env, which apply the wider agent policy.

[FIRST-PRINCIPLES-REVIEWED] f33dc55

Description read

[DESCRIPTION-READ] 6dcc4e38515827fa888f00fa5b247033ed486bc4fb8825399a5d05cfb9173733

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 Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

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

Review details

No findings.

[OPUS-REVIEWED] f33dc55

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

False positive or not applicable? A repository writer can comment:
/ai-review override fable f33dc550e29a733a91a683c5641600ba8afa27b1: <one-sentence reason>

@github-actions

github-actions Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

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

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] f33dc55

False positive or not applicable? A repository writer can comment:
/ai-review override gpt f33dc550e29a733a91a683c5641600ba8afa27b1: <one-sentence reason>

@iamwhatever

Copy link
Copy Markdown
Contributor Author

Sensitive change review

  • Head commit: 9010673
  • What rule changed: Python-runtime environment stripping now has one shared helper. Sandbox admission, command denial, and agent subprocess scrubbing do not change.
  • Before -> after (what was allowed/blocked, now): Terminal, voice, and daemon launch removed Python-only environment keys with three local loops. They now call one helper. Existing uppercase Python keys are still removed. Lower-case Python-prefixed keys are also removed consistently. Non-Python keys remain.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): A caller relying on a lower-case Python-prefixed environment key would lose it. The change does not broaden commands, expose secrets, or lock users out.
  • Evidence checked (which sandbox result proves it): Focused helper tests prove Python keys are removed while SSH_AUTH_SOCK, AWS keys, GNUPGHOME, and GIT_ASKPASS remain.
  • No regression:
    • Tools still work (which tools/commands were run, result): Terminal handler, terminal facade, chat voice, MCP gateway daemon, sandbox facade, and spawn environment tests passed.
    • Backward compatible (old config / old data / old callers still work, how checked): No config, stored data, or public call shape changes. All three callers keep their prior environment mapping contract.
    • Existing tests (which suites passed on this head): 1262 related tests passed and 1 skipped. New tests passed 30 repeated runs and a shuffled 13-test run. Lint, type, semgrep, GPT review, and Opus review passed.
  • How to undo: Revert commit 9010673.

@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 Oct 17, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Punchline: the terminal shell and the voice-list aws call now also drop lower-case python* keys — rebutted (no user-visible change)

Scope: only keys whose upper-cased name starts with one of the four _PYTHON_ENV_PREFIXES (PYTHONPATH, PYTHONHOME, PYTHONPYCACHEPREFIX, PYTHONDONTWRITEBYTECODE), not every python* key: src/kiro_crew/sandbox_spawn.py:381 key.upper().startswith(prefix).
POSIX: CPython reads only the upper-case names, so a lower-case pythonpath changed nothing for a Python child before and changes nothing now.
Windows: os.environ upper-cases every key (os.encodekey returns encode(key).upper()), so the old case-sensitive loop already saw these keys upper-case and dropped them. No change there.
Non-Python readers: grep -rnE "['\"](pythonpath|pythonhome|pythonpycacheprefix|pythondontwritebytecode)" src/ scripts/ website/src finds no reader in the repo.
Precedent: the pooled third-party MCP spawn already matched case-insensitively on main (4b066e090c:src/kiro_crew/mcp_gateway/daemon/launch.py:527); this makes the three callers agree.
Pinned: test/test_sandbox_no_isolation.py::test_without_python_env_drops_only_python_settings drops "pythonpath": "/lower" and keeps PYTHONUNBUFFERED, SSH_AUTH_SOCK, AWS_*, GNUPGHOME, GIT_ASKPASS. The PR body's Backwards compatibility line states the same.

@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 Oct 17, 2026
@iamwhatever
iamwhatever force-pushed the refactor/8054-name-python-env-strip-policy branch from 9010673 to 7db77df Compare October 18, 2026 05:28
@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 Oct 18, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor Author

Sensitive change review

  • Head commit: 7db77df
  • What rule changed: Python-runtime environment stripping now has one shared helper, sandbox_spawn.without_python_env. Sandbox admission, command denial, and agent subprocess scrubbing do not change.
  • Before -> after (what was allowed/blocked, now): Terminal, voice, and daemon launch removed Python-only environment keys with three local loops. They now call one helper. Existing uppercase Python keys are still removed. Lower-case Python-prefixed keys are also removed consistently. Non-Python keys remain.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): A caller relying on a lower-case Python-prefixed environment key would lose it. The change does not broaden commands, expose secrets, or lock users out.
  • Evidence checked (which sandbox result proves it): Focused helper tests prove Python keys are removed while SSH_AUTH_SOCK, AWS keys, GNUPGHOME, and GIT_ASKPASS remain.
  • No regression:
  • How to undo: Revert commit 7db77df.

@iamwhatever
iamwhatever force-pushed the refactor/8054-name-python-env-strip-policy branch from 7db77df to 9a790c2 Compare October 18, 2026 06:17
@iamwhatever

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in same-dir and import neighbours of this PR's files since this head went green (2e50054 -> 2d378bf); same patch (range-diff unchanged), related tests 1262 passed; CI re-running.

@iamwhatever

Copy link
Copy Markdown
Contributor Author

Sensitive change review

  • Head commit: 9a790c2
  • What rule changed: Python-runtime environment stripping now has one shared helper, sandbox_spawn.without_python_env. Sandbox admission, command denial, and agent subprocess scrubbing do not change.
  • Before -> after (what was allowed/blocked, now): Terminal, voice, and daemon launch removed Python-only environment keys with three local loops. They now call one helper. Existing uppercase Python keys are still removed. Lower-case Python-prefixed keys are also removed consistently. Non-Python keys remain.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): A caller relying on a lower-case Python-prefixed environment key would lose it. The change does not broaden commands, expose secrets, or lock users out.
  • Evidence checked (which sandbox result proves it): Focused helper tests prove Python keys are removed while SSH_AUTH_SOCK, AWS keys, GNUPGHOME, and GIT_ASKPASS remain.
  • No regression:
    • Tools still work (which tools/commands were run, result): Terminal handler, terminal facade, chat voice, MCP gateway daemon, sandbox facade, and spawn environment tests passed on this head.
    • Backward compatible (old config / old data / old callers still work, how checked): No config, stored data, or public call shape changes. All three callers keep their prior environment mapping contract. This head is the same patch as 9010673, rebased onto main 2d378bf with no conflicts (git range-diff shows it unchanged).
    • Existing tests (which suites passed on this head): 1262 related tests passed and 1 skipped (sandbox, terminal, chat voice, MCP gateway daemon, sandbox facade, spawn env suites).
  • How to undo: Revert commit 9a790c2.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Punchline: the terminal shell and the voice-list aws call now also drop lower-case python* keys — rebutted (no user-visible change)

Scope: only keys whose upper-cased name starts with one of the four _PYTHON_ENV_PREFIXES (PYTHONPATH, PYTHONHOME, PYTHONPYCACHEPREFIX, PYTHONDONTWRITEBYTECODE), not every python* key: src/kiro_crew/sandbox_spawn.py:381 key.upper().startswith(prefix).
POSIX: CPython reads only the upper-case names, so a lower-case pythonpath changed nothing for a Python child before and changes nothing now.
Windows: os.environ upper-cases every key (os.encodekey returns encode(key).upper()), so the old case-sensitive loop already saw these keys upper-case and dropped them. No change there.
Non-Python readers: grep -rnE "['\"](pythonpath|pythonhome|pythonpycacheprefix|pythondontwritebytecode)" src/ scripts/ website/src finds no reader in the repo.
Precedent: the pooled third-party MCP spawn already matched case-insensitively on main (4b066e090c:src/kiro_crew/mcp_gateway/daemon/launch.py:527); this makes the three callers agree.
Pinned: test/test_sandbox_no_isolation.py::test_without_python_env_drops_only_python_settings drops "pythonpath": "/lower" and keeps PYTHONUNBUFFERED, SSH_AUTH_SOCK, AWS_*, GNUPGHOME, GIT_ASKPASS. The PR body's Backwards compatibility line states the same.

@iamwhatever
iamwhatever force-pushed the refactor/8054-name-python-env-strip-policy branch from 9a790c2 to cf3dc39 Compare October 18, 2026 07:12
@iamwhatever

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in same-dir and import neighbours of this PR's files since this head went green (2d378bf -> 9d088c8); same patch (range-diff unchanged), related tests 1262 passed; CI re-running.

@iamwhatever

Copy link
Copy Markdown
Contributor Author

Sensitive change review

  • Head commit: cf3dc39
  • What rule changed: Python-runtime environment stripping now has one shared helper, sandbox_spawn.without_python_env. Sandbox admission, command denial, and agent subprocess scrubbing do not change.
  • Before -> after (what was allowed/blocked, now): Terminal, voice, and daemon launch removed Python-only environment keys with three local loops. They now call one helper. Existing uppercase Python keys are still removed. Lower-case Python-prefixed keys are also removed consistently. Non-Python keys remain.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): A caller relying on a lower-case Python-prefixed environment key would lose it. The change does not broaden commands, expose secrets, or lock users out.
  • Evidence checked (which sandbox result proves it): Focused helper tests prove Python keys are removed while SSH_AUTH_SOCK, AWS keys, GNUPGHOME, and GIT_ASKPASS remain.
  • No regression:
    • Tools still work (which tools/commands were run, result): Terminal handler, terminal facade, chat voice, MCP gateway daemon, sandbox facade, and spawn environment tests passed on this head.
    • Backward compatible (old config / old data / old callers still work, how checked): No config, stored data, or public call shape changes. All three callers keep their prior environment mapping contract. This head is the same patch as 9010673, rebased onto main 9d088c8 with no conflicts (git range-diff shows it unchanged).
    • Existing tests (which suites passed on this head): 1262 related tests passed and 1 skipped (sandbox, terminal, chat voice, MCP gateway daemon, sandbox facade, spawn env suites).
  • How to undo: Revert commit cf3dc39.

@iamwhatever
iamwhatever force-pushed the refactor/8054-name-python-env-strip-policy branch from cf3dc39 to f33dc55 Compare October 18, 2026 07:35
@iamwhatever

Copy link
Copy Markdown
Contributor Author

Rebased onto main 943a4e5, which carries the red-main fix #21792 for test/test_history_bindings.py::test_the_member_set_is_the_frozen_inventory (the Windows (1) shard failure on cf3dc39). Same patch (range-diff unchanged); related tests plus test_history_bindings.py: 1474 passed. CI re-running.

@iamwhatever

Copy link
Copy Markdown
Contributor Author

Sensitive change review

  • Head commit: f33dc55
  • What rule changed: Python-runtime environment stripping now has one shared helper, sandbox_spawn.without_python_env. Sandbox admission, command denial, and agent subprocess scrubbing do not change.
  • Before -> after (what was allowed/blocked, now): Terminal, voice, and daemon launch removed Python-only environment keys with three local loops. They now call one helper. Existing uppercase Python keys are still removed. Lower-case Python-prefixed keys are also removed consistently. Non-Python keys remain.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): A caller relying on a lower-case Python-prefixed environment key would lose it. The change does not broaden commands, expose secrets, or lock users out.
  • Evidence checked (which sandbox result proves it): Focused helper tests prove Python keys are removed while SSH_AUTH_SOCK, AWS keys, GNUPGHOME, and GIT_ASKPASS remain.
  • No regression:
    • Tools still work (which tools/commands were run, result): Terminal handler, terminal facade, chat voice, MCP gateway daemon, sandbox facade, and spawn environment tests passed on this head.
    • Backward compatible (old config / old data / old callers still work, how checked): No config, stored data, or public call shape changes. All three callers keep their prior environment mapping contract. This head is the same patch as 9010673, rebased onto main 943a4e5 with no conflicts (git range-diff shows it unchanged).
    • Existing tests (which suites passed on this head): 1474 related tests passed and 1 skipped (sandbox, terminal, chat voice, MCP gateway daemon, sandbox facade, spawn env suites, plus test_history_bindings).
  • How to undo: Revert commit f33dc55.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • Punchline: check that no test or the terminal facade mirror still patches _PYTHON_ENV_PREFIXES through terminal_shell or chat_voice — checked, nothing does (no change needed)

Tests: grep -rn "_PYTHON_ENV_PREFIXES" test | grep -E "setattr|patch" on this head finds no match. No test patches the name through any module.
Source: grep -rn "_PYTHON_ENV_PREFIXES" src/kiro_crew/dashboard src/kiro_crew/mcp_gateway finds no match. So terminal.py, terminal_shell.py, chat_voice.py and daemon/launch.py neither bind nor read it now.
Facade mirror: the terminal facade's TYPE_CHECKING import now names without_python_env instead of _PYTHON_ENV_PREFIXES. test/test_terminal_facade.py checks that list against what its owners import, and it passes on this head.
The name still lives in sandbox_tiers and is served by the sandbox facade, so other readers (sandbox_argv, sandbox_spawn, tests that read sb._PYTHON_ENV_PREFIXES) keep working.
Evidence: related tests on this head, including test_terminal_facade.py, test_terminal_handler.py, test_chat_voice.py and test_sandbox_refactor_facade.py: 1474 passed, 1 skipped.

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 18, 2026

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Every review lane on the head is clean (only runner notices and PR Scope size warnings); held by the triage cron on a path, category, checklist or P0-area rule, not a finding. Approved on the watch holder's request.

@KiroCrewCaptain
KiroCrewCaptain enabled auto-merge (squash) October 19, 2026 01:17
@KiroCrewCaptain
KiroCrewCaptain merged commit 1b96d89 into main Oct 19, 2026
108 checks passed
@KiroCrewCaptain
KiroCrewCaptain deleted the refactor/8054-name-python-env-strip-policy branch October 19, 2026 01:17
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 19, 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.

name the Python-env-only strip policy instead of a third open-coded copy

2 participants