Repository navigation
host: make the sandbox items that only their own module uses private - #1686
Merged
Pedro Henrique Penna (ppenna) merged 1 commit intoNov 17, 2026
Merged
Conversation
Twenty-seven pub(crate) items and fields of host::sandbox's distro, scratch, options, and mount modules were named only inside their own module and its child modules: its tests, scratch's imp, and mount's request. Among them were the test seams of the distro and scratch bindings, Access with verify_with, check_with, and bind_with, through which any module of the crate could replace the opens and seals that DistroBinding::verify and check and ScratchBinding::bind and check fix, such as the guarded open of a distro layer's staged check. Each is now private to its module: the binding versions, both Access seams with their fields and constants, PolicyResult, PolicyVerdict with its fields and ACCEPTED, verify_with, both check_with, bind_with, the systemd entrypoints and the managed exec environment's limits, with sandbox_mounts_with and exec_environment_from_file, and mount's limits on policy paths and guest targets. CheckedDistro stays pub(crate), since the crate-visible DistroBinding::check returns it. Only visibility changes: no item, code path, serde form, error message, or public API changes, and the tests, which are child modules, still reach every item. At 621f8b2, whose host::sandbox matches the issue's base, e5330ad, cargo test --locked --all-features --lib host::sandbox passed 94 tests on Windows and 89 on Linux (nvx-kvm-test, Azure Linux 3.0 with KVM, Rust 1.97.1). With the change, it passes the same 94 on Windows, where cargo fmt --check and cargo clippy --all-targets --all-features -D warnings are clean. Refs #1683 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues remain for the sandbox visibility cleanup.
No open issues 🎉
What changed in this PR
Addresses #1683 by making 27 module-local items and fields private in nvx::host::sandbox. This narrows internal access without changing runtime behavior, serialized formats, or the public API.
Changes:
- Makes distro and scratch binding test seams private, preserving access through existing production entry points.
- Makes module-local policy types, binding versions, option helpers, and limits private.
- Preserves access for child modules and existing tests; no tests change.
| File | Description |
|---|---|
nvx/src/host/sandbox/scratch.rs |
Makes the binding version, access seam, and binding helpers private. |
nvx/src/host/sandbox/options.rs |
Makes option limits, entrypoint constants, and internal helpers private. |
nvx/src/host/sandbox/mount/mod.rs |
Makes mount limits private while retaining child-module access. |
nvx/src/host/sandbox/distro.rs |
Makes the binding version, policy types, access seam, and verification helpers private. |
Review effort: Balanced
Pedro Henrique Penna (ppenna)
enabled auto-merge
November 17, 2026 04:46
Pedro Henrique Penna (ppenna)
added a commit
that referenced
this pull request
Nov 17, 2026
doc/contribute.md asks every pull request to reference an issue on the first line of its description, but nothing checks it: pull requests such as #1675, whose only references sit in the template's HTML comment, and #1516, whose Refs #1509 names a pull request, reference no issue, and a reviewer has to notice. Add the Issue link workflow, which pull_request_target runs, from the default branch, when a pull request is opened, reopened, pushed to, edited, labelled, or unlabelled. Its script, check_issue_link.py, reads the pull request through gh api, in UTF-8 whatever the locale, and passes it when GitHub links it to an issue of the repository (closingIssuesReferences) or when its description holds close, fix, resolve (in any form), Part of, or Refs, with an optional colon, then #N, microsoft/nvx#N, or the issue's URL, where N is an issue. A pull request's number, a missing number, a bare #N, and another repository's issue do not count. The script reads the description as GitHub renders it, through the Markdown API in the repository's context, and only the text that GitHub shows counts: not an HTML comment, an attribute such as a link's title, or code, inline, fenced, indented, or in <pre>, nor a keyword that code or the end of a block, such as a list item or a table cell, separates from its number. GitHub's own renderer keeps the check in step with what the pull request's page shows, which a parser of CommonMark, GFM tables, and raw HTML written here kept missing. It looks up at most the first 10 numbers, so a description cannot make it call the API without bound. Pull requests by dependabot[bot] or github-actions[bot], or labelled no-issue, are exempt, and closed ones are left alone. An unlinked pull request gets the needs-issue label and one marker comment that says how to reference an issue, and the check fails; editing the description reruns it, which then removes the label and rewrites the comment. Only a comment of github-actions[bot] that starts with the marker is the script's. The script does every read before its first write, so an API error fails the check and changes nothing, and its summary names the verdict and the numbers, never the description. The job has no condition, since a skipped run would replace the previous verdict, runs one check a pull request at a time, keeps no checkout credentials, and gets only the pull request's number. Its token reads contents and writes pull requests; reading an issue of a public repository needs no issues permission, so the nightly report and issue labelling stay the only workflows that write issues. Evidence: dry runs against the live repository pass #1687, #1686, and #1682, which GitHub links to issues, and #1679, whose description references #1676, and flag #1675, #1516, #1510, and #1509, as reading their descriptions confirms. A 64 KiB description renders in about a second, and its text reads in at most 60 ms. test_issue_link.py covers the reading of GitHub's HTML, as gh api markdown renders it: keywords and targets, other repositories, code and <pre>, attributes, the ends of blocks and table cells, and inline elements; the verdicts and the writes through a fake gh api, the render request, gh's input and output in UTF-8, the bound on lookups, an API error at each read, a comment that quotes the marker or has no author, and the workflow's triggers, permissions, checkout, concurrency, and inputs. validate-nvx runs it on Linux and Windows. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Nov 17, 2026
Pedro Henrique Penna (ppenna)
added a commit
that referenced
this pull request
Nov 17, 2026
doc/contribute.md asks every pull request to reference an issue on the first line of its description, but nothing checks it: pull requests such as #1675, whose only references sit in the template's HTML comment, and #1516, whose Refs #1509 names a pull request, reference no issue, and a reviewer has to notice. Add the Issue link workflow, which pull_request_target runs, from the default branch, when a pull request is opened, reopened, pushed to, edited, labelled, or unlabelled. Its script, check_issue_link.py, reads the pull request through gh api, in UTF-8 whatever the locale, and passes it when GitHub links it to an issue of the repository (closingIssuesReferences) or when its description holds close, fix, resolve (in any form), Part of, or Refs, with an optional colon, then #N, microsoft/nvx#N, or the issue's URL, where N is an issue. A pull request's number, a missing number, a bare #N, and another repository's issue do not count. The script reads the description as GitHub renders it, through the Markdown API in the repository's context, and only the text that GitHub shows counts: not an HTML comment, an attribute such as a link's title, or code, inline, fenced, indented, or in <pre>, nor a keyword that code or the end of a block, such as a list item or a table cell, separates from its number. A link counts by where it goes, whatever its text: a link to an issue or a pull request as OWNER/REPO#N, and any other link as code does. GitHub's own renderer keeps the check in step with what the pull request's page shows, which a parser of CommonMark, GFM tables, and raw HTML written here kept missing. It looks up at most the first 10 numbers, so a description cannot make it call the API without bound. Pull requests by dependabot[bot] or github-actions[bot], or labelled no-issue, are exempt, and closed ones are left alone. An unlinked pull request gets the needs-issue label and one marker comment that says how to reference an issue, and the check fails; editing the description reruns it, which then removes the label and rewrites the comment. Only a comment of github-actions[bot] that starts with the marker is the script's. The script does every read before its first write, so an API error fails the check and changes nothing, and its summary names the verdict and the numbers, never the description. The job has no condition, since a skipped run would replace the previous verdict, runs one check a pull request at a time, keeps no checkout credentials, and gets only the pull request's number. Its token reads contents and writes pull requests; reading an issue of a public repository needs no issues permission, so the nightly report and issue labelling stay the only workflows that write issues. Evidence: dry runs against the live repository pass #1687, #1686, and #1682, which GitHub links to issues, and #1679, whose description references #1676, and flag #1675, #1516, #1510, and #1509, as reading their descriptions confirms. A 64 KiB description renders in about a second, and its text reads in at most 60 ms. test_issue_link.py covers the reading of GitHub's HTML, as gh api markdown renders it: keywords and targets, other repositories, code and <pre>, attributes, links, the ends of blocks and table cells, and inline elements; the verdicts and the writes through a fake gh api, the render request, gh's input and output in UTF-8, the bound on lookups, an API error at each read, a comment that quotes the marker or has no author, and the workflow's triggers, permissions, checkout, concurrency, and inputs. validate-nvx runs it on Linux and Windows. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Pedro Henrique Penna (ppenna)
added a commit
that referenced
this pull request
Nov 17, 2026
doc/contribute.md asks every pull request to reference an issue on the first line of its description, but nothing checks it: pull requests such as #1675, whose only references sit in the template's HTML comment, and #1516, whose Refs #1509 names a pull request, reference no issue, and a reviewer has to notice. Add the Issue link workflow, which pull_request_target runs, from the default branch, when a pull request is opened, reopened, pushed to, edited, labelled, or unlabelled. Its script, check_issue_link.py, reads the pull request through gh api, in UTF-8 whatever the locale, and passes it when GitHub links it to an issue of the repository (closingIssuesReferences) or when its description holds close, fix, resolve (in any form), Part of, or Refs, with an optional colon, then #N, microsoft/nvx#N, or the issue's URL, where N is an issue. A pull request's number, a missing number, a bare #N, and another repository's issue do not count. The script reads the description as GitHub renders it, through the Markdown API in the repository's context, and only the text that GitHub shows counts: not an HTML comment, an attribute such as a link's title, or code, inline, fenced, indented, or in <pre>, nor a keyword that code or the end of a block, such as a list item or a table cell, separates from its number. A link counts by where it goes, and of its text only a keyword that starts it: a link to an issue or a pull request, absolute or root-relative, with nothing after the number other than a slash, a query, or a fragment, as that keyword and OWNER/REPO#N, and any other link as code does. GitHub's own renderer keeps the check in step with what the pull request's page shows, which a parser of CommonMark, GFM tables, and raw HTML written here kept missing. It looks up at most the first 10 numbers, so a description cannot make it call the API without bound. Pull requests by dependabot[bot] or github-actions[bot], or labelled no-issue, are exempt, and closed ones are left alone. An unlinked pull request gets the needs-issue label and one marker comment that says how to reference an issue, and the check fails; editing the description reruns it, which then removes the label and rewrites the comment. Only a comment of github-actions[bot] that starts with the marker is the script's. The script does every read before its first write, so an API error fails the check and changes nothing, and its summary names the verdict and the numbers, never the description. The job has no condition, since a skipped run would replace the previous verdict, runs one check a pull request at a time, keeps no checkout credentials, and gets only the pull request's number. Its token reads contents and writes pull requests; reading an issue of a public repository needs no issues permission, so the nightly report and issue labelling stay the only workflows that write issues. Evidence: dry runs against the live repository pass #1687, #1686, and #1682, which GitHub links to issues, and #1679, whose description references #1676, and flag #1675, #1516, #1510, and #1509, as reading their descriptions confirms. A 64 KiB description renders in about a second, and its text reads in at most 60 ms. test_issue_link.py covers the reading of GitHub's HTML, as gh api markdown renders it: keywords and targets, other repositories, code and <pre>, attributes, links, the ends of blocks and table cells, and inline elements; the verdicts and the writes through a fake gh api, the render request, gh's input and output in UTF-8, the bound on lookups, an API error at each read, a comment that quotes the marker or has no author, and the workflow's triggers, permissions, checkout, concurrency, and inputs. validate-nvx runs it on Linux and Windows. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Pedro Henrique Penna (ppenna)
deleted the
agents/issue-1683-sandbox-private-items
branch
November 17, 2026 05:55
8 tasks
Pedro Henrique Penna (ppenna)
added a commit
that referenced
this pull request
Nov 17, 2026
doc/contribute.md asks every pull request to reference an issue on the first line of its description, but nothing checks it: pull requests such as #1675, whose only references sit in the template's HTML comment, and #1516, whose Refs #1509 names a pull request, reference no issue, and a reviewer has to notice. Add the Issue link workflow, which pull_request_target runs, from the default branch, when a pull request is opened, reopened, pushed to, edited, labelled, or unlabelled. Its script, check_issue_link.py, reads the pull request through gh api, in UTF-8 whatever the locale, and passes it when GitHub links it to an issue of the repository (closingIssuesReferences) or when its description holds close, fix, resolve (in any form), Part of, or Refs, with an optional colon, then #N, microsoft/nvx#N, or the issue's URL, where N is an issue. A pull request's number, a missing number, a bare #N, and another repository's issue do not count. The script reads the description as GitHub renders it, through the Markdown API in the repository's context, and only the text that GitHub shows counts: not an HTML comment, an attribute such as a link's title, or code, inline, fenced, indented, or in <pre>, nor a keyword that code or the end of a block, such as a list item or a table cell, separates from its number. A link counts by where it goes, and of its text only a keyword that starts it: a link to an issue or a pull request, absolute or root-relative, with nothing after the number other than a slash, a query, or a fragment, as that keyword and OWNER/REPO#N, which no text after the link extends, and any other link as code does. An issue's URL that GitHub shows as text follows the same rule, but for the punctuation that ends a sentence. GitHub's own renderer keeps the check in step with what the pull request's page shows, which a parser of CommonMark, GFM tables, and raw HTML written here kept missing. It looks up at most the first 10 numbers, so a description cannot make it call the API without bound. Pull requests by dependabot[bot] or github-actions[bot], or labelled no-issue, are exempt, and closed ones are left alone. An unlinked pull request gets the needs-issue label and one marker comment that says how to reference an issue, and the check fails; editing the description reruns it, which then removes the label and rewrites the comment. Only a comment of github-actions[bot] that starts with the marker is the script's. The script does every read before its first write, so an API error fails the check and changes nothing, and its summary names the verdict and the numbers, never the description. The job has no condition, since a skipped run would replace the previous verdict, runs one check a pull request at a time, keeps no checkout credentials, and gets only the pull request's number. Its token reads contents and writes pull requests; reading an issue of a public repository needs no issues permission, so the nightly report and issue labelling stay the only workflows that write issues. Evidence: dry runs against the live repository pass #1687, #1686, and #1682, which GitHub links to issues, and #1679, whose description references #1676, and flag #1675, #1516, #1510, and #1509, as reading their descriptions confirms. A 64 KiB description renders in about a second, and its text reads in at most 60 ms. test_issue_link.py covers the reading of GitHub's HTML, as gh api markdown renders it: keywords and targets, other repositories, code and <pre>, attributes, links, the ends of blocks and table cells, and inline elements; the verdicts and the writes through a fake gh api, the render request, gh's input and output in UTF-8, the bound on lookups, an API error at each read, a comment that quotes the marker or has no author, and the workflow's triggers, permissions, checkout, concurrency, and inputs. validate-nvx runs it on Linux and Windows. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Pedro Henrique Penna (ppenna)
added a commit
that referenced
this pull request
Nov 17, 2026
doc/contribute.md asks every pull request to reference an issue on the first line of its description, but nothing checks it: pull requests such as #1675, whose only references sit in the template's HTML comment, and #1516, whose Refs #1509 names a pull request, reference no issue, and a reviewer has to notice. Add the Issue link workflow, which pull_request_target runs, from the default branch, when a pull request is opened, reopened, pushed to, edited, labelled, or unlabelled. Its script, check_issue_link.py, reads the pull request through gh api, in UTF-8 whatever the locale, and passes it when GitHub links it to an issue of the repository (closingIssuesReferences) or when its description holds close, fix, resolve (in any form), Part of, or Refs, with an optional colon, then #N, microsoft/nvx#N, or the issue's URL, where N is an issue. A pull request's number, a missing number, a bare #N, and another repository's issue do not count. The script reads the description as GitHub renders it, through the Markdown API in the repository's context, and only the text that GitHub shows counts: not an HTML comment, an attribute such as a link's title, or code, inline, fenced, indented, or in <pre>, nor a keyword that code or the end of a block, such as a list item or a table cell, separates from its number. A link counts by where it goes, and of its text only a keyword that starts it: a link to an issue or a pull request, absolute or root-relative, with nothing after the number other than a slash, a query, or a fragment, as that keyword and OWNER/REPO#N, which no text after the link extends, and any other link as code does. An issue's URL that GitHub shows as text follows the same rule, but for the punctuation that ends a sentence. GitHub's own renderer keeps the check in step with what the pull request's page shows, which a parser of CommonMark, GFM tables, and raw HTML written here kept missing. It looks up at most the first 10 numbers, so a description cannot make it call the API without bound. Pull requests by dependabot[bot] or github-actions[bot], or labelled no-issue, are exempt, and closed ones are left alone. An unlinked pull request gets the needs-issue label and one marker comment that says how to reference an issue, and the check fails; editing the description reruns it, which then removes the label and rewrites the comment. Only a comment of github-actions[bot] that starts with the marker is the script's. The script does every read before its first write, so an API error fails the check and changes nothing, and its summary names the verdict and the numbers, never the description. The job has no condition, since a skipped run would replace the previous verdict, runs one check a pull request at a time, keeps no checkout credentials, and gets only the pull request's number. Its token reads contents and writes pull requests; reading an issue of a public repository needs no issues permission, so the nightly report and issue labelling stay the only workflows that write issues. Evidence: dry runs against the live repository pass #1687, #1686, and #1682, which GitHub links to issues, and #1679, whose description references #1676, and flag #1675, #1516, #1510, and #1509, as reading their descriptions confirms. A 64 KiB description renders in about a second, and its text reads in at most 60 ms. test_issue_link.py covers the reading of GitHub's HTML, as gh api markdown renders it: keywords and targets, other repositories, code and <pre>, attributes, links, the ends of blocks and table cells, and inline elements; the verdicts and the writes through a fake gh api, the render request, gh's input and output in UTF-8, the bound on lookups, an API error at each read, a comment that quotes the marker or has no author, and the workflow's triggers, permissions, checkout, concurrency, and inputs. validate-nvx runs it on Linux and Windows. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1683
What does this pull request change?
It makes private the 27
pub(crate)items and fields ofnvx::host::sandboxthat #1683 lists: those that only their own module and its child modules name. It changes nothing else: each edit removes onepub(crate). Start withnvx/src/host/sandbox/distro.rs.distro:BINDING_VERSION; the test seamAccess, with its fieldsopenandsealand its constantsREADandGUARDED;PolicyResult;PolicyVerdict, with its fieldsrevisionandresultand its constantACCEPTED;DistroBinding::check_with; andverify_with.scratch:SCRATCH_BINDING_VERSION; the test seamAccess, with its fieldopenand its constantWRITABLE;ScratchBinding::check_with; andbind_with.options:SYSTEMD_ENTRYPOINTS,MAX_ENVIRONMENT_FILE_BYTES,MAX_EXEC_ENVIRONMENT,MAX_EXEC_ENVIRONMENT_BYTES,sandbox_mounts_with, andexec_environment_from_file.mount:MAX_MOUNT_POLICY_PATHSandMAX_MOUNT_TARGET_BYTES, which only its child modulerequestreads.Once
SYSTEMD_ENTRYPOINTSfits on one line, rustfmt joins it, so the diff is 27 insertions and 28 deletions in 4 files. Nothing else changes: no item is renamed, moved, or edited, and no code path, serde form, error message,ErrorKind, public API, or test changes.Left out:
CheckedDistrostayspub(crate), since the crate-visibleDistroBinding::checkreturns it.host::sandbox's submodules, such as the seamsplan_mounts_withandrequire_mount_owner_supported_on, and needpub(super)orpub(in crate::host::sandbox). Otherhostmodules have the same kind of candidates. And the host's hexadecimal helpers are duplicated.Why is this change needed?
These items were visible to the whole crate, though nothing outside their own module used them.
The
Accessseams, withverify_with,check_with, andbind_with, let any module of the crate replace the opens and seals that the bindings' entry points fix:DistroBinding::verifyopens withseal::open_read.DistroBinding::checkopens withseal::open_guarded, which on Windows denies writing and deleting the layer while a launch holds it.ScratchBinding::bindandcheckopen withimp::open_writable.With the change, these entry points are the only way in from the rest of the crate, and the compiler refuses any new use from outside these modules. The binding versions, the policy verdict, and the limits of options and mounts read as what they are: details of their module, which its tests can still name.
Nothing is broken, so there is no root cause: this is a code-quality change, behavior-preserving by construction.
Alternatives rejected:
pub(crate)item ofhost::sandboxat once. Items that sibling modules or the parent's tests read needpub(super)orpub(in crate::host::sandbox), and thepub(crate) usere-exports ofmount/mod.rswould have to split. This change keeps to one rule, private where every use is in the item's own module, and leaves the rest to host: make the sandbox items that only their own module uses private #1683's follow-ups.CheckedDistrotoo. A privateCheckedDistroin the signature of the crate-visibleDistroBinding::checkwould tripprivate_interfacesunder-D warnings.How was this change validated?
The change preserves behavior. So in place of a reproduction and a regression test, #1683's acceptance criteria hold: the affected tests pass at the base revision and with the change, and stay unchanged. The base,
621f8b2c200(origin/dev), holds the samehost::sandboxandnvx/public-api/as the issue's base,e5330ad60af.Checks and results, with Rust 1.97.1:
621f8b2c200)2986195b61c)cargo test --locked --all-features --lib host::sandbox(innvx/)cargo test --locked --all-features --lib host::sandbox(innvx/)python scripts\local_gates.py --base origin/dev --runtest-changes(no change to an existing test),markdown-links,test-layout,nvx-format,nvx-lint,nvx-test(1098 library tests with all features, 543 with the default ones, and 191 without; no failure in any binary),nvx-doc,nvx-msrv, andnvx-cli(2261 Python tests OK with 88 skipped, and 84 adversarial tests OK with 11 skipped)python3 scripts/local_gates.py --base origin/dev --run --keep-going --only test-layout markdown-links nvx-format nvx-lint nvx-test nvx-doc nvx-public-api nvx-msrv nvx-macos nvx-guest-binaries-lint nvx-guest-binaries-build, aftertest-changespassed therenvx-public-apifound the snapshots innvx/public-api/unchanged, andnvx-testran 1815 library tests with all features, 543 with the default ones, and 191 withoutpython3 scripts/nvx.py test-microvm --backend kvm --scenario sandbox-lifecycle --scenario sandbox-gpt-layer --scenario managed-exec-configNotes:
shcame from Git'susr\binonPATH, andNVXnamed a releasenvxbuilt from the change withcargo build --release --locked --features cli. Thepip installstep ofnvx-clifound every requirement already satisfied.python3but nopython. A temporarypythonlink topython3, removed afterwards, let the gates'pythoncommands run. The first attempt, without it, stopped atmarkdown-linkswith exit code 127.Backend, host OS, host type, and guest: the Linux host is an Azure Linux 3.0 (x86-64) virtual machine with KVM, which ran the Linux checks in a temporary worktree of this branch. The KVM scenarios used the packaged artifacts of
v0.1.0-dev.621f8b2c2002, the base's release, and annvxbuilt from the change. They booted the default Alpine guest, with the Ubuntu distro layer and the sandbox scratch template of that release.Left to CI:
nvx-clivalidation. Its first step runspip install, which this session does not run on a remote host.Checklist
python3 scripts/check_test_layout.pychecks.python3 scripts/check_test_changes.py --base origin/devlists no changeto an existing test, or a Changes to existing tests section below
explains each one.
.github/copilot-instructions.mdand the skills when a convention orworkflow changes.
nvxupdatesnvx-rs/public-api/withpython3 scripts/public_api.py --update.description says how the change versions or migrates them.
No behavior changes, so the first item does not apply, and the existing tests, which are child modules of the changed ones, still reach every item. No documentation describes these items' visibility. The public API is unchanged:
host::sandboxis private to the crate. The serde forms ofDistroBinding,PolicyVerdict, andScratchBindingkeep their fields and names.