Repository navigation
fix: say in one way where idd-close's doc-sync sweep sits (#512) - #523
Merged
kiki830621 merged 3 commits intoNov 12, 2026
Merged
Conversation
Step 6.3's position sentence said the sweep runs before gh issue close; the step order, the Step 0.5 task list and Step 4 all run it after the close. The sentence now states the same position. The doc-sync-sweep suite reads SKILL.md and compares the three places, and runs the comparison on seven copies broken on purpose. Spec change idd-512-doc-sync-after-close adds the capability idd-close-doc-sync.
Four more copies broken on purpose (a sentence that says both closed and before the close, the close command moved after the sweep, the Step 6.3 heading gone, the task missing), so that every condition of the checker has a check that fails without it. One order test that could never fire is removed.
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.
Refs #512
Summary
idd-closeStep 6.3 has a sentence that states where the doc-sync sweep sits. It said the sweep runs beforegh issue close; the step order, the Step 0.5 task list and Step 4 (which posts the summary and then runs the command in one block) all run it afterwards. The sentence now says the same as the rest: the issue is already closed and the closing summary posted, then the body sync, then the sweep, then the distribution sync. The order of the steps is unchanged.idd-close-doc-syncwith one requirement and an Example of eight rows (spec changeidd-512-doc-sync-after-close, archived).doc-sync-sweepsuite reads SKILL.md and compares the three places, and runs the comparison on copies broken on purpose, so each condition of the check is seen to fail (19 checks, was 7).--retroactiveruns Step 6.3 is [bug] idd-close --retroactive: the table does not say what happens to Step 1.55, 3.5, 3.6, 6.3 and 6.8 (found during #512) #521; four LOW and INFO rows of the verify report are [enhancement] doc-sync position check: LOW and INFO findings left by the verify of #512 (follow-up from #512) #522.Verification
Verify gate clean — see the verify report on issue #512. /idd-all merges this PR next if CI and the close-stage guardrails pass.
Checklist
Related
#521, #522
🤖 Generated by /idd-all. Do NOT add a GitHub close trailer (Closes/Fixes/Resolves) — IDD discipline requires /idd-close (run by /idd-all's close stage, or by hand) to enforce the checklist gate + closing summary.