Repository navigation
Batch nightly corrections through discovery and shared validation - #2233
Merged
Merged
Conversation
|
Reviewed commit 3371b99 — no issues found. |
PR Surface ReportCompared Summary: 6 changed file(s) | EF migrations: 0 added file(s), max 0/1 per context Reforge Surface Score
Section DeltasNo section score changes. Section Size & Complexity DeltasNo section size/complexity changes. Rule DeltasNo rule score changes. Published Write Surface17 of 51 sections publish write capability, 51 interfaces (0). Interface SurfaceNo new interfaces or interface members. Diff Size
|
3 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
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.
What
Nightly sweeps must discover related simple corrections within the section and shared consumers before editing, state the candidate list and shared validation plan, then validate and commit the batch. Splitting known compatible candidates requires a concrete reason in the report; singleton batches state the searched scope. Deferred candidates carry forward across rounds.
The initial goal and continuation prompts reinforce this workflow. Display-ordering guidance requires inspecting each consumer before batching straightforward moves; risk-sensitive changes retain individual scrutiny.
Why
The sweep in #2228 repeatedly ran validation for closely related corrections despite existing general batching instructions. Discovery and explicit batch boundaries make that instruction actionable.
Existing surface checked
Updated the existing daily prompt, ladder, goal/continuation messages, README, and nightly memory atom/index. No new runtime components or public surface.
Validation
Checklist
Deployment
The scheduled service uses an immutable runner release. This change must be included in its next provisioned release to affect scheduled runs; merging alone does not replace the pinned runner.