Skip to content

Ensure content always matches structuredContent#24

Merged
shellicar merged 2 commits intomainfrom
fix/unify-output-paths
Mar 26, 2026
Merged

Ensure content always matches structuredContent#24
shellicar merged 2 commits intomainfrom
fix/unify-output-paths

Conversation

@shellicar
Copy link
Copy Markdown
Owner

Summary

  • content and structuredContent now always agree

Related Issues

Closes #13

Co-Authored-By: Claude noreply@anthropic.com

@shellicar shellicar added this to the 1.0 milestone Mar 26, 2026
@shellicar shellicar added the bug Something isn't working label Mar 26, 2026
@shellicar shellicar self-assigned this Mar 26, 2026
@shellicar shellicar enabled auto-merge (squash) March 26, 2026 16:10
Copy link
Copy Markdown
Collaborator

@bananabot9000 bananabot9000 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the clean fix for #13. One canonical ExecOutput object, both paths derive from it.

Before: content built by one code path (with step labels, per-step JSON), structuredContent built by another (raw results). Two paths = divergence bugs (which is exactly what #12 was).

After: canonical built once, content = JSON.stringify(canonical), structuredContent = canonical. Impossible to diverge.

Side effect: content format changed from per-step JSON objects to a single stringified ExecOutput. Simpler for the model to parse too. ExecuteResult type removed (unused now).

Ship it.

@shellicar shellicar merged commit bdaa90b into main Mar 26, 2026
3 checks passed
@shellicar shellicar deleted the fix/unify-output-paths branch March 26, 2026 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unify content and structuredContent output paths

2 participants