prose: update CLI and Rust library reference for ant-client timeout split — 2026-05-13#41
Draft
JimCollinson wants to merge 3 commits into
Draft
prose: update CLI and Rust library reference for ant-client timeout split — 2026-05-13#41JimCollinson wants to merge 3 commits into
JimCollinson wants to merge 3 commits into
Conversation
…ent 91d5f18 ant-client PR #78 split the single --store-timeout-secs flag into two separate hidden flags: --store-timeout-secs (chunk store only) and --chunk-get-timeout-secs (chunk retrieve). Update command-reference to reflect the split and add the missing flag. ClientConfig gained two new timeout fields: merkle_store_timeout_secs (270 s default, required for storer-side Kademlia lookup before accepting Merkle proof) and chunk_get_timeout_secs (10 s). Update library-reference Key types table to reflect the expanded timeout surface. https://claude.ai/code/session_01LJogEk6BZv2YdWXpWDdrpw
This reverts commit 73114b6.
JimCollinson
pushed a commit
that referenced
this pull request
May 13, 2026
PR #41 hit prose-guard because the routine bundled a useful .gitignore addition (ignore transient sweep_report*.json files) into a prose PR. PR #37 hit the same shape of issue with a misnamed sweep summary file. Both cases were the routine doing legitimate infrastructure tidying during the audit and silently bundling it into the prose envelope, where prose-guard correctly rejects it. Add an explicit "stay strictly within the prose envelope" bullet to step 5.2's Prose PR section that names the categories of root-level housekeeping the routine has slipped on (.gitignore, scripts/, .github/, repo-registry.yml, component-registry.yml) and points to "Suggested follow-ups" in the PR body as the place to surface infrastructure cleanups the audit noticed. A human can then open a separate PR for those. No rule duplication; this just makes the existing prose-guard envelope explicit at the moment the routine is assembling the PR. https://claude.ai/code/session_019cz1M7pXuXFQykMZxfdXHm
JimCollinson
pushed a commit
that referenced
this pull request
May 13, 2026
scripts/sweep_poll.py writes sweep_report.json on every routine run and on local validation invocations. The file is never part of the docs assembly, and committing it would just create noise in PR diffs. This addition was first attempted as part of prose PR #41 (commit 73114b6), which the prose-guard correctly rejected because the prose envelope does not cover root-level housekeeping. Landing it as a standalone change here. https://claude.ai/code/session_019cz1M7pXuXFQykMZxfdXHm
5 tasks
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
2 participants
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.
Upstream
ant-client:
6cada1d6b318a93e52ea6c34aa4b68fc2782c946→91d5f18e3fbf5125fc6b5bbc46bb0a1fe6356ae8Source artifacts inspected
ant-cli/src/cli.rs— hidden flag definitions andhide = trueannotationsant-core/src/data/client/mod.rs—ClientConfigstruct fields and default constantsDeveloper-facing change
ant-client PR #78 split the single
--store-timeout-secsflag into two:--store-timeout-secs(chunk store only) and a new--chunk-get-timeout-secs(chunk retrieve).ClientConfiggainedmerkle_store_timeout_secs(270 s default, required to outlast the storer-side 240 s Kademlia lookup before the node accepts a Merkle proof) andchunk_get_timeout_secs(10 s default).Files changed in this PR
docs/cli/command-reference.mddocs/rust/library-reference.mdWhy prose changed
docs/cli/command-reference.md: The--store-timeout-secsrow previously described the flag as controlling "chunk store and retrieve timeouts". After the split it controls only chunk store operations; a new separate--chunk-get-timeout-secsflag controls chunk retrieve. Both flags are hidden (hide = trueinant-cli/src/cli.rs). The row description is updated to reflect the narrower scope and the new flag is added.docs/rust/library-reference.md: TheClientConfigdescription in the Key types table previously said "Separate quote and store timeouts". The struct now exposes four distinct timeouts: quote, chunk store, Merkle batch store (270 s default), and chunk retrieve. The description is updated to reflect the expanded surface.Verification run
python3 scripts/sweep_poll.pyon the prose branch: statusok, these two pages no longer appear as drifted.skills/start/SKILL.mdbody (no linked release triggered).version,published_date, orCHANGELOG.md.--chunk-get-timeout-secsexists inant-cli/src/cli.rsat91d5f18ewithhide = true.merkle_store_timeout_secsdefault of 270 s inant-core/src/data/client/mod.rsat91d5f18e.Uncertainties
None. Both flags are
hide = truein the source; flagging them in the docs is consistent with the existing policy of noting hidden flags "where they matter for troubleshooting".Generated by Claude Code