Skip to content

Batch nightly corrections through discovery and shared validation - #2233

Merged
peterdrier merged 1 commit into
mainfrom
fix/nightly-batch-discovery
Nov 1, 2026
Merged

peterdrier merged 1 commit into
mainfrom
fix/nightly-batch-discovery

Conversation

@peterdrier

Copy link
Copy Markdown
Owner

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

  • All 44 existing runner tests passed.
  • Python compilation and git diff --check passed.
  • No .NET code changed; scoped runner verification applies.
  • Actual batching compliance must be assessed from the next sweep's candidate plans and split reasons; these are agent instructions, not deterministic enforcement.

Checklist

  • Review tier: tier:standard; section: infra.
  • Feature branch from origin/main, targeting peterdrier/Humans:main.
  • Reuse-first checked; durable rule and INDEX updated together.
  • Runner docs and tests apply. No app localization, authorization, GDPR, schema, navigation, or section invariant changes.

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.

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown

Reviewed commit 3371b99 — no issues found.

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown

PR Surface Report

Compared 130aa17d...3371b992. Scored with reforge 0.31.1.

Summary: 6 changed file(s) | EF migrations: 0 added file(s), max 0/1 per context

Reforge Surface Score

metric base head delta
total 61657 61657 0
surface 14439 14439 0

Section Deltas

No section score changes.

Section Size & Complexity Deltas

No section size/complexity changes.

Rule Deltas

No rule score changes.

Published Write Surface

17 of 51 sections publish write capability, 51 interfaces (0).

Interface Surface

No new interfaces or interface members.

Diff Size

bucket added deleted
docs 50 12
other 6 1

@peterdrier
peterdrier merged commit 5db8ae2 into main Nov 1, 2026
10 checks passed
@peterdrier
peterdrier deleted the fix/nightly-batch-discovery branch November 1, 2026 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant