Background review read-mark persistence across tool contexts
Cluster 73965 · skills. Data as of
Nothing open on GitHub. Fix merged in #94511 on 25 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #94511. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where background review read marks were stored in a turn-scoped ContextVar, causing them to be lost between tool calls and blocking view-then-patch workflows. The fixes preserve read marks so curator patches are not refused after a prior skill_view.
Open issues0
Open PRs0
Fixes on record
-
#94511 fix(skills): background-review curator patches no longer refused after skill_view (#75618, salvage #73975)
files:
tests/tools/test_skill_manager_tool.py,tools/skill_manager_tool.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#73975 fix(skills): preserve review read marks across tool contexts · merged via another change →
335c60e,#94511,#75618
Closed issues · 1
- Closed#73965bg-review: _background_review_read_before_write_guard uses turn-scoped ContextVar, preventing multi-turn view→patch workflow
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- skills
- Merged PRs
- #94511
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 25 Aug 2026