Skip to content

fix: guard parent folders of caller-provided hidden paths in the Linux sandbox - #39551

Merged
KiroCrewCaptain merged 2 commits into
mainfrom
fix/sandbox-caller-hidden-parent-guards
Nov 20, 2026
Merged

KiroCrewCaptain merged 2 commits into
mainfrom
fix/sandbox-caller-hidden-parent-guards

Conversation

@chenmingwei23

@chenmingwei23 chenmingwei23 commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Hidden paths a caller passes to the sandbox get the same parent-folder rename guards as the built-in hidden paths, on Linux and macOS.

The Linux sandbox now follows the same rule as the built-in hidden paths.

Why it matters

Callers that pass extra_hidden_dirs expect the same protection as the built-in hidden set. The guard set should not depend on who named the path or on the backend.

Not a goal

  • No change to which paths are hidden.
  • No change to the built-in guard set.
  • Parent folders stay writable inside; only renaming the folder entries is guarded.

What changed (motivation -> approach -> change)

Reuse the existing guard helpers so caller-provided hidden paths are guarded like the built-in ones in the Linux sandbox. The macOS guards are unchanged.

Backwards compatibility

Behaviour change on the Linux namespace backend only (macOS already guarded these paths): inside the sandbox, the parent folders of a caller-provided hidden path (for example ~/.config, ~/.docker or ~/.kube when a file below them is hidden) are now pinned. Renaming or removing such a parent fails with EBUSY, and renaming something across one of them fails with EXDEV. Files inside those folders stay readable and writable as before. If a pin cannot be placed, the spawn stops instead of running without the guard.

Removes nothing: no path, key, validator or function is removed; the change only adds pins, and no mask, seal or read-only mount is undone.

Reader: src/kiro_crew/sandbox_argv.py:_live_plan_host -- chat -- a session spawn with extra_hidden_dirs now lists the renameable parents of each caller entry; test_namespace_guards_every_ancestor_of_a_caller_mask_against_rename
Reader: src/kiro_crew/sandbox_plan.py:_namespace_plan -- app -- an app backend spawn pins a caller parent that is the app's own folder after the masks, like the read-only and operator pins; test_live_host_pins_a_caller_parent_that_is_an_app_folder_after_the_masks
Reader: src/kiro_crew/sandbox_argv.py:_live_plan_host -- subagent -- only parents this uid could rename are pinned, so a spawn with a hidden path under a foreign or missing folder starts as before; test_live_host_filters_caller_parents_by_what_this_uid_can_rename

Tests

  • test_namespace_guards_every_ancestor_of_a_caller_mask_against_rename: Linux plan lists the parent and ancestors of a caller entry, drops unrelated host guards, and keeps the built-in guards in front.
  • test_a_caller_mask_file_is_sealed_and_its_parent_guarded_on_both_backends: a caller hidden file keeps its write seal on macOS, its parent is guarded on both backends, and the built-in guards are the same with and without the entry.
  • test_live_host_guards_only_the_caller_ancestors_that_exist: both backends list existing parents only.
  • test_seatbelt_guards_every_ancestor_of_a_caller_mask_against_rename: the Linux expectation is updated.

Proof: not provable -- other: prove.py was not run on the crew; red then green was run by hand (6 failed on the test commit, 89 passed with the fix).

Manual verification

N/A -- unit coverage of the plan builders is sufficient; no real sandbox run.

Real-machine verification

Run on the KiroCrew CI runner of the Backend Tests (namespace sandbox) job (GitHub-hosted ubuntu-latest, unprivileged user namespaces enabled, the real namespace sandbox), through two throwaway draft PRs that add one test, test/test_sandbox_hidden_leaf_parent_pins.py::TestACallerHiddenFilesParentStaysInPlace::test_renaming_the_parent_folder_is_refused. In a temporary HOME it hides a file under ~/.config, then inside the sandbox renames ~/.config and moves a file across it.

Machine: GitHub Actions ubuntu-latest, x86_64, namespace sandbox job
Before (main + test, #39806 dcb2e1c): the test is marked xfail(strict) there; https://github.com/kirodotdev/KiroCrew/actions/runs/44696690856/job/136157513808 -> REALMACHINE-39551 rename rc=renamed err=; cross rc=ENOENT err=No such file or directory (the parent rename succeeds; 1 xfailed)
After (head da205dd + test, #39807 2aca059): https://github.com/kirodotdev/KiroCrew/actions/runs/44695215425/job/136152949502 -> REALMACHINE-39551 rename rc=EBUSY err=Device or resource busy; cross rc=EXDEV err=Invalid cross-device link (passed)
Cleanup: hosted runner, temporary HOME removed; both draft PRs closed

Screenshots / video

N/A -- no user-visible UI change.

Related Issues

None linked.

Sibling sweep

Swept: git grep -n "caller_ancestor_guards" -- src test
Sibling: src/kiro_crew/sandbox_plan.py -- changed here
Sibling: src/kiro_crew/sandbox_argv.py -- changed here
Sibling: src/kiro_crew/sandbox_plan.py (macOS plan) -- not affected -- already guarded

Pattern harvest

Not generalizable: one-off difference between the two sandbox backends.

Checklist

  • A Conventional Commits title (fix: guard parent folders of caller-provided hidden paths on Linux)
  • 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.

@github-actions

github-actions Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Sensitive Change Review

Sensitive files changed:

  • src/kiro_crew/sandbox_argv.py

  • src/kiro_crew/sandbox_plan.py

  • @chenmingwei23 posted a complete reasoning template for da205dd.

@github-actions

github-actions Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

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

@github-actions

github-actions Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

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

The caller-mask guards on Linux land at mechanism level. The reversed "Seatbelt only" pin has support in the base's own reasoning that a later session re-resolves a masked path by name.

Notes

  • Item 3 — oversized: the hunk caller_after_masks = {g for g in caller_ancestor_guards if app_dir_ids and _is_app_dir_pin(g)} copies the after_masks split already applied to readonly_ancestor_guards a few lines above in _live_plan_host (src/kiro_crew/sandbox_argv.py). The function now has two copies of one rule. Subtraction: delete the second copy and run the existing after_masks split once over both tuples.
  • Item 1 — inherited framing: the description's only stated harm is symmetry: "The guard set should not depend on who named the path or on the backend". It never says why the deleted pin == () / "Seatbelt only" was wrong. The base's operator_parent_pins comment does say why: "the next session resolves the entry by name again, so a parent renamed in between would leave the real tree unsealed".

What this change ships

Inventory (3 items) — 2 justified

Intent: stop a sandboxed agent from renaming the folders above a caller-hidden path on Linux, so a later session's mask does not miss the moved content. FIX.

  1. Linux sandbox now pins the existing parent folders of caller-hidden paths against rename, but only folders this user could rename — justified
  2. On Linux, host-listed caller guards that are not above a live caller mask are dropped from the plan — justified
  3. An app folder above a caller-hidden path is pinned after the masks, not before — oversized (copies the existing split)

[FIRST-PRINCIPLES-REVIEWED] da205dd

Description read

[DESCRIPTION-READ] db32fdd47f4006c125f15d3bc5867d9fa5cc0b3f34c6ccf05c6337227cd22c7b

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

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

Design-Verdict: PASS

Nothing blocks. This applies the documented rule that every hidden spelling's parent is guarded on both backends (sandbox_argv.py: "on Linux the mask is a mount that moves with the parent, so the NEXT spawn reads the leaf") to caller masks, using the existing pin mechanism.

Notes

  • These new Linux pins fail closed. A pin that can't be mounted, or whose target changes while it is placed, stops the spawn (_pin_over_themselves → _mount_or_die / sys.exit). That now applies to every spawn that passes extra_hidden_dirs: cron scripts, prerequisite probes, MCP discovery probes, codex STT and office slides. None of the tests run a real namespace sandbox. Adding one caller-mask case to test/test_seal_parent_pin_real_sandbox.py, which already runs in the namespace-sandbox CI job, would show the pins land and refuse a rename.

[DESIGN-REVIEWED] da205dd

Description read

[DESCRIPTION-READ] 56b605d028139168ed0d80b122ee19e4b8e23eeb73cd899f7a804342a445313e

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

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

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

Review details

No findings.

[OPUS-REVIEWED] da205dd

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

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

@github-actions

github-actions Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ human override accepted

Human judgment by @chenmingwei23 overrides the GPT 6.1 finding for da205dd65e90be6326e83cfe41d9188e23de13ad; the recorded reason is authoritative for this commit.

[GPT-OVERRIDE] da205dd

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 da205dd65e90be6326e83cfe41d9188e23de13ad false-positive: <reason, 20 to 500 characters>

Plan-level tests for both backends: a caller-provided hidden file under a
writable parent gets a guard on the parent and its ancestors, the file stays
write-sealed, and the built-in guard set is unchanged. The namespace
expectations fail on main.
Hidden paths a caller passes to the sandbox now get the same parent-folder
rename guards as the built-in hidden paths on the Linux backend, limited to
the folders this user could rename. The macOS guards are unchanged. Parents
stay writable and the hidden set is unchanged.
@chenmingwei23
chenmingwei23 force-pushed the fix/sandbox-caller-hidden-parent-guards branch from bb513e6 to da205dd Compare November 19, 2026 18:55
@github-actions github-actions Bot added the readiness: action required A blocking check or review needs attention label Nov 19, 2026
@chenmingwei23
chenmingwei23 marked this pull request as ready for review November 19, 2026 19:56
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

Sensitive change review

  • Head commit: da205dd
  • What rule changed: On Linux, the parent folders of caller-provided hidden paths (extra_hidden_dirs) are now guarded against rename, as the built-in hidden paths are. A guard that is an app's own folder is placed after the masks, like the read-only and operator guards.
  • Before -> after (what was allowed/blocked, now): Before, on Linux, a sandboxed process could rename a parent folder of a caller-provided hidden path. After, that rename is refused; reads and writes inside those folders are unchanged. macOS already guarded them and is unchanged.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): A command that renames a parent folder of a caller hidden path fails inside the sandbox. No path becomes newly readable and nobody is locked out.
  • Evidence checked (which sandbox result proves it): test/test_sandbox_plan.py fails on the test commit 46513a4 (6 failed) and passes with the fix (89 passed); the plan tests pin the guard list and ordering on both backends.
  • No regression:
    • Tools still work (which tools/commands were run, result): Only rename of guarded parent folders is refused; parents stay writable inside. CI sandbox jobs are the check on this head.
    • Backward compatible (old config / old data / old callers still work, how checked): No config, key or caller signature changes; the built-in guard set is unchanged, pinned by the tests.
    • Existing tests (which suites passed on this head): test/test_sandbox_plan.py on the crew; the full suite runs in CI on this head.
  • How to undo: Revert the PR; the caller guards go back to macOS only. No data migration.

@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 20, 2026
@KiroCrewCaptain

Copy link
Copy Markdown
Collaborator

Code change approver recommendation: A person should decide

Why: the decider thinks the change is probably fine but estimates a 20% chance that this change introduces a defect, above the 12% limit for approving on its own.

Extends the existing parent-rename pins (renameable-by-uid filter, pin_seal_parents, app folder pinned after masks) to caller extra_hidden_dirs on the Linux namespace backend, matching the documented rationale for crew-home hidden leaves (a Linux mask moves with its parent so the next spawn reads the leaf). The Seatbelt output is unchanged; the namespace plan keeps only guards above live, non-cancelled caller masks, folded consistently with mask paths. Tests would fail without the change. No concrete regression path found; spec drift, missing real-sandbox coverage and the added EXDEV cost are noted as non-blocking.

Tier: 2, held for a person: security-sensitive path.

An automated recommendation, not a review: a maintainer still decides. It approves on its own only when the estimated chance of a defect is at most 12% and the change has at most 400 changed lines. Decider v3c (217fe607) · commit da205dd65e · 136 changed lines. If this recommendation is wrong, reply here: replies are how the approver is evaluated.

@chenmingwei23

Copy link
Copy Markdown
Contributor Author

Sensitive change review

  • Head commit: da205dd
  • What rule changed: On Linux, the parent folders of caller-provided hidden paths (extra_hidden_dirs) are now guarded against rename, as the built-in hidden paths are. A guard that is an app's own folder is placed after the masks, like the read-only and operator guards.
  • Before -> after (what was allowed/blocked, now): Before, on Linux, a sandboxed process could rename a parent folder of a caller-provided hidden path. After, that rename is refused; reads and writes inside those folders are unchanged. macOS already guarded them and is unchanged.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): A command that renames a parent folder of a caller hidden path fails inside the sandbox. No path becomes newly readable and nobody is locked out.
  • Evidence checked (which sandbox result proves it): test/test_sandbox_plan.py fails on the test commit 46513a4 (6 failed) and passes with the fix (89 passed); the plan tests pin the guard list and ordering on both backends.
  • No regression:
    • Tools still work (which tools/commands were run, result): Only rename of guarded parent folders is refused; parents stay writable inside. CI sandbox jobs are the check on this head.
    • Backward compatible (old config / old data / old callers still work, how checked): No config, key or caller signature changes; the built-in guard set is unchanged, pinned by the tests.
    • Existing tests (which suites passed on this head): test/test_sandbox_plan.py on the crew; the full suite runs in CI on this head.
  • How to undo: Revert the PR; the caller guards go back to macOS only. No data migration.

@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.

Thanks for the Linux follow-up to #39273. On this head the review read the full diff and confirmed the namespace branch now builds caller guards with _renameable_ancestor_guards, the same helper the built-in and operator pins use. The plan keeps only guards above a live, uncancelled caller mask, the pins run before the masks with a recursive bind, and no mask, seal or read-only mount is undone. All 6 new or changed tests fail at the test-only commit 46513a4 and pass at the head. Done well: no new pin mechanism, so Linux and macOS now pick the same guard set.

Two things need to change before merge. Both are about what the PR says, not the code.

  1. ## Real-machine verification says N/A, but this diff changes what every Linux spawn with extra_hidden_dirs mounts, and a pin that cannot be placed stops the spawn. The repository allows N/A only when the diff runs nothing. Please reproduce on the base (a parent such as ~/.config above a caller mask can be renamed inside the sandbox), run the same command on this head (the rename returns EBUSY, sibling writes still work, the spawn exits 0), and record machine, before, after and cleanup. A caller-mask case in test/test_seal_parent_pin_real_sandbox.py would also keep this pinned in CI.
  2. ## Backwards compatibility says "Removes nothing" and "nothing that works today is rejected". Inside the sandbox, renaming or removing a guarded parent such as ~/.config, ~/.docker or ~/.kube now fails with EBUSY, a rename across one of those folders fails with EXDEV, and a pin that cannot be placed stops the spawn. Please say so, with the Reader: lines the take-away rule asks for. This needs only a body edit.

Security: this touches the sandbox files and only adds pins. No mask, seal or refusal is removed, the pins keep every seal and mask below them, and a parent the check cannot inspect counts as renameable, so the check fails toward pinning.

Optional:

  • The not m.cancelled and origin == "caller" predicates in the new plan filter can be deleted without any test going red.
  • The body's test counts (4 then 87) should be 6 then 89.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: passed Eligible automated validation passed for the current revision labels Nov 20, 2026
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

Thanks for the review. The body is updated on the same head (da205dd), no code change:

  • Backwards compatibility now says that inside the Linux sandbox renaming or removing a guarded parent (such as ~/.config, ~/.docker, ~/.kube) fails with EBUSY, a rename across one fails with EXDEV, and a pin that cannot be placed stops the spawn. It adds three Reader: lines.
  • Test counts are corrected to 6 failed on the test commit and 89 passed with the fix.
  • Real-machine verification is not N/A any more: it lists the exact before/after commands. The run itself is pending, because the hosts available to us have no unprivileged user namespaces (unshare -Urm true -> Operation not permitted). The output will be added here once it has run on a host that has them.

The two optional predicate cleanups are noted as a follow-up.

@chenmingwei23

Copy link
Copy Markdown
Contributor Author

Real-machine verification is now filled in, on the same head (da205dd), no code change. It ran in the Backend Tests (namespace sandbox) CI job, which runs the real namespace sandbox, through two throwaway draft PRs that add one test:

Both draft PRs are closed now. The backwards-compatibility text and the 6/89 test counts are as updated earlier.

@KiroCrewCaptain

Copy link
Copy Markdown
Collaborator

Thanks for the body update. On this head (da205dd) the review read the full diff again. The Linux branch reuses _renameable_ancestor_guards and the existing pin_seal_parents path. The plan keeps a caller guard only above a live, uncancelled caller mask. No mask, seal or read-only mount is undone. The red-then-green claim holds: the new tests fail at the test-only commit and pass at the head. Done well: no new pin mechanism, and Linux and macOS now pick the same caller guard set.

Follow-up on the earlier change request:

  1. Real-machine verification: still stands. The section says Pending and lists expected results, not real output. You say the run is queued with a maintainer, so it needs a person with a host that has user namespaces.
  2. Backwards compatibility: fixed. The body now names the EBUSY/EXDEV cost and the fail-closed spawn, and it adds Reader: lines. The test counts are corrected too.

This PR needs a maintainer for two things. Someone must run the real namespace sandbox, or decide the evidence is enough. Someone must also clear the PR Readiness failure: one AI lane finding points at test/integration/test_app_release_upgrade_auth.py:523, which this diff does not touch and which is the same on main. A maintainer will post the decision here.

Security: this PR changes sandbox files but only adds pins. It removes no mask, seal or refusal, so it does not widen what the sandbox allows.

Optional:

  • Add a caller-mask case to test/test_seal_parent_pin_real_sandbox.py, which already runs in the namespace-sandbox CI job. It would hide a file under $HOME/.config/x, check that renaming $HOME/.config fails with EBUSY, that a sibling write still works, and that the spawn exits 0. That would prove the pins in CI without waiting for a host.
  • docs/system-specs/modules/security.md (around line 2276) covers parent rename guards for crew-home leaves only. One sentence about caller extra_hidden_dirs parents would keep the spec current.
  • The Reader: list could also name the cron script, MCP discovery probe and office-slides spawns, which pass extra_hidden_dirs and now get pins too.

@KiroCrewCaptain
KiroCrewCaptain enabled auto-merge (squash) November 20, 2026 08:31

@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.

Thanks for the Linux follow-up to #39273. On this head the review read the full diff. It also confirmed that reverting the two production hunks makes exactly the six named tests fail, while the head passes 89. The new tests use only tmp_path and monkeypatch. Done well: Linux and macOS now build caller guards from the same caller_parents list with the existing helpers, and a caller parent that is an app folder is still pinned after the masks.

Follow-up on the earlier change request:

  1. Real-machine verification: fixed. The two namespace-sandbox jobs named in the body ran, both concluded success, and their logs show rename rc=renamed on main plus the test, and rc=EBUSY / rc=EXDEV on this head plus the test. The earlier follow-up comment that called this pending read an older body.
  2. Backwards compatibility: fixed. The body names the EBUSY/EXDEV cost and the fail-closed spawn, and adds Reader: lines. The test counts are corrected.

Security: this touches the sandbox files, but it only adds rename pins. It removes no mask, seal or refusal. Pins are placed before the masks and keep every seal below them. A parent the check cannot inspect counts as renameable, so the check fails toward pinning. Nothing that main refuses is now allowed.

Optional:

  • Commit the real-sandbox case from the draft PR (TestACallerHiddenFilesParentStaysInPlace) to this repository, so CI keeps checking that a caller parent pin refuses a rename.
  • Add one sentence to docs/system-specs/modules/security.md near line 2276: the existing, renameable parents of caller extra_hidden_dirs entries are pinned the same way, with the same EBUSY/EXDEV cost.
  • No test fails if you delete the caller-side app_dir_pins.setdefault loop in sandbox_argv.py (around line 600). A case where the spawn lifts the app's declared leaf with extra_visible_dirs and asserts the app folder is in mask_parent_pins would catch that.

@chenmingwei23

Copy link
Copy Markdown
Contributor Author

/ai-review override gpt da205dd false-positive: the superseded GPT block (run 44692496479 attempt 1) pointed at test/integration/test_app_release_upgrade_auth.py:523, which this PR does not touch; its diff is only sandbox_argv.py, sandbox_plan.py and test_sandbox_plan.py. GPT runs 44697952448 and 44692496479 attempt 2 on this head found no blocking issue.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@chenmingwei23 recorded a false-positive release (class false-positive) for the gpt AI finding on da205dd65e90be6326e83cfe41d9188e23de13ad.

the superseded GPT block (run 44692496479 attempt 1) pointed at test/integration/test_app_release_upgrade_auth.py:523, which this PR does not touch; its diff is only sandbox_argv.py, sandbox_plan.py and test_sandbox_plan.py. GPT runs 44697952448 and 44692496479 attempt 2 on this head found no blocking issue.

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

@github-actions github-actions Bot removed the readiness: action required A blocking check or review needs attention label Nov 20, 2026
@KiroCrewCaptain
KiroCrewCaptain merged commit 26b943c into main Nov 20, 2026
123 of 128 checks passed
@github-actions github-actions Bot added the readiness: passed Eligible automated validation passed for the current revision label Nov 20, 2026
@KiroCrewCaptain
KiroCrewCaptain deleted the fix/sandbox-caller-hidden-parent-guards branch November 20, 2026 09:47
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 20, 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.

2 participants