Repository navigation
docs: wrap up the download strategy hardening - #211
Draft
greenhat616 wants to merge 1 commit into
Draft
greenhat616 wants to merge 1 commit into
greenhat616 wants to merge 1 commit into
Conversation
greenhat616
force-pushed
the
feat/hardening-46-wrapup
branch
from
November 13, 2026 07:44
aee88fa to
e486b90
Compare
greenhat616
marked this pull request as draft
November 13, 2026 08:56
Close out the plan. The maintainer decided on 2026-11-11 to defer P2 (admission, per-host connection caps, a shared speed limit and the host capability cache): these are policies across tasks and belong in a client or job layer above Task. T16 to T18 stay unticked as a reference for that layer. The IDM improvement plan's PR table marks every other row as implemented and awaiting merge, with its PRs and migrations, and the design notes gain an inventory of what bolt-load still lacks compared with IDM, for the maintainer to decide on. The READMEs describe the connection limit, the per-range budget and the other task options, resuming and its conditions, the current growth strategy, and that limits across tasks belong above Task.
greenhat616
force-pushed
the
feat/hardening-46-wrapup
branch
from
November 13, 2026 22:25
e486b90 to
ee37336
Compare
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.
T22, the last commit of the download strategy hardening plan (
docs/spec/2026-11-01-download-strategy-hardening/). It is stacked on #210 (C20c), its base branch. Docs only.What
P2 deferred (maintainer decision, 2026-11-11)
T16–T18 are not implemented in this plan:
Limits);They are policies across tasks, so they belong in a client or job layer above
Task, by the same principle as §11.5.1 and #195.None, so they never apply now.IDM plan §5 table
Gaps compared with IDM (design §14.32)
Each row gives:
Where an IDM claim is an inference, it keeps the source's confidence. Shared host caps and an aggregate bandwidth bucket are bolt-load's own P2 extension, not IDM behaviour. The section decides nothing. It ends by asking the maintainer which gaps to fill, and in which layer.
READMEs
max_connections(8),max_attempts_per_range(5), and the other options with their builder methods and defaults, checked against the code;max_connections(8 whatever the CPU count), no longer "one runner per CPU core".Onbehaves asOff;ResourceChangedor a fallback cannot clear the state:kept_for_resumevsleftover_temp_file;ResumeRejectedanddiscard_partial.Task.Limits: not mentioned, since P2 is deferred.tasks.md
The three T22 boxes are ticked. The note on the IDM table says to update it again when the PRs merge.
Review
Reviewed with
/ccg:review, using the codex backend only (a single-model review).Checks
include_str!is bolt-load-sync's, which is untouched.cargo fmt --all -- --checkpasses, andgit diff --checkis clean.