chore(upstream-watch): record the 2026-09-28 closures and replies in the registry - #258
Merged
Merged
Conversation
agentic-qe closed ten of our threads on 2026-09-28: no. 734 is retired (fixed; nothing in ak waits on it), no. 736 is adopted with first fixed version 3.14.4 (confirmed by the maintainer's re-test), and no. 735 and nos. 753-759 are fixed upstream but unreleased. Ruflo nos. 3444, 3445 and 3473 are fixed upstream but not in 3.47.1. The agentic-qe no. 574 adjustment now follows the Windows confirmation: 3.14.4 reports LockHeld, not FsyncFailed, after a live lock.
Adds a dated "commented" history line, with the comment link, for each reply posted on 2026-09-28: agentic-qe no. 528, 532, 535, 574, 734, 736 and 756, and ruflo no. 420, 952, 2356 and 2885. The threads that were only cited before (agentic-qe no. 528, 532 and 535, ruflo no. 420 and 2356) now carry relation "commented". agentic-qe no. 736 is retired: adopted in ak and closed upstream, as the watch proposed.
… comments Adds today's reply on openai/codex no. 16045 (issuecomment-5878392424). A sweep of every active watch entry against its GitHub comments found seven comments of ours that no history line recorded; each is added with its date and link: - openai/codex no. 16045 and ruvnet/ruflo no. 952: 2026-09-27 - ruvnet/ruflo no. 3196: 2026-09-09, 2026-09-20 and 2026-09-27 (its 2026-09-26 line gains its link) - ruvnet/ruflo no. 2885: 2026-09-26 - pacphi/agentic-kit no. 240: 2026-09-27
This was referenced Sep 28, 2026
Merged
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
1 participant
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.
Summary
Registry-only update (
src/lib/hook-audit/agentic-dependency-constraints.json) for the 2026-09-28 upstream round. Upstream threads are written asowner/repo no. nso this pull request adds no cross-reference to them.fixed-unreleased.fixed-unreleased; 3.47.1 contains none of them.LockHeldinstead ofFsyncFailedafter a live lock (confirmed on Windows). The adjustment now says to re-run the live-owner fixture on macOS and Linux before removing the busy rule (tracking: remove temporary AQE live-lock busy rule once fixed upstream (agentic-qe#574 / #719) #240).commentedhistory line with its link. These are agentic-qe no. 528, 532, 535, 574, 734, 736 and 756; ruflo no. 420, 952, 2356 and 2885; and codex no. 16045. The five threads that were only cited before now have relationcommented.No code or docs change. The agentic-kit follow-ups these closures unlock (removing the #574 busy rule, and the
HOST-SUPPORT.mdrisk links for agentic-qe no. 528 and 532) come in separate pull requests.Test plan
node scripts/run-tests.mjs uniton Node 26.4.0: 5638 pass, 0 fail, 6 skipped (Windows-only)node scripts/upstream-watch.mjs report --json: registryvalid, nothing left in "Ready to retire"🤖 Generated with Claude Code