docs: correct devbox-agent README warm-path status from pending to implemented#99
Merged
jplock merged 1 commit intoJul 15, 2026
Conversation
jplock
deleted the
detail/fix-docs/docs-correct-devbox-agent-readme-warm-path-status-c26b12
branch
July 15, 2026 18:17
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.
The devbox-agent README described the snapshot-builder schedule, the Launch Template block-device-mapping that seeds /workspace, and the system-wide RUSTUP_HOME/CARGO_HOME settings as "still in devbox-infra" (pending), but these pieces are implemented end-to-end in the devbox-infra snapshot-builder and pool modules.
A reader would wrongly conclude the warm-cache pipeline is half-built and that /workspace seeding / toolchain-cache persistence is still unbuilt, sending them to look for pending work that already exists.
Introduced by commit ce2cd59 (@jplock, #94)
Doc Drift PRs can be configured here.