Skip to content

Preserve branch boundaries in aggregation prompts - #7

Open
ray-suton wants to merge 1 commit into
InternScience:mainfrom
ray-suton:agent/fix-aggregation-branch-separator
Open

Preserve branch boundaries in aggregation prompts#7
ray-suton wants to merge 1 commit into
InternScience:mainfrom
ray-suton:agent/fix-aggregation-branch-separator

Conversation

@ray-suton

Copy link
Copy Markdown

Summary

  • Join branch summaries with the intended 80-dash divider between each branch.
  • Add focused regression coverage for multi-branch and single-branch formatting.

Root cause

The previous inline expression mixed string concatenation and join(). Due to operator precedence, the divider was added only once while summaries were joined by bare newlines, weakening the boundaries in the aggregation prompt.

The new helper makes the formatting rule explicit without changing aggregation search behavior or prompt content.

Verification

  • python3 -m unittest discover -s tests -v — 2 tests passed
  • python3 -m compileall -q agents tests
  • git diff --check

Scope

No dependencies or public APIs changed. A full live MLEvolve search run was not performed.

Branch summaries were joined by bare newlines because operator precedence applied the divider only once. A small helper makes the intended boundary explicit and gives the behavior a focused regression test.

Constraint: Keep aggregation search semantics and prompt content unchanged
Rejected: Parenthesize the inline expression only | leaves the boundary rule implicit and untested
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep separator formatting covered when aggregation prompt structure changes
Tested: python3 -m unittest discover -s tests -v; python3 -m compileall -q agents tests; git diff --check
Not-tested: Full live MLEvolve search run
@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@ray-suton
ray-suton marked this pull request as ready for review July 26, 2026 10:15
@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant