Skip to content

refactor: isolate execution kernel and tool runner contracts - #164

Closed
LIghtJUNction wants to merge 1 commit into
mainfrom
fix/execution-boundaries-20260929
Closed

LIghtJUNction wants to merge 1 commit into
mainfrom
fix/execution-boundaries-20260929

Conversation

@LIghtJUNction

@LIghtJUNction LIghtJUNction commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Superseded to avoid concurrent duplicate implementation

This regression-first draft is intentionally closed, not merged and not treated as an implemented fix. Source code is unchanged at head 63b4a3f83f2a128aaab555a2b14f4cc0df7fe12c.

A concurrent session submitted #165 for #160 and is taking #156. Coordination was updated in #83 comment 5878201914. Its independent implementation must remain the integration path; do not merge this draft's deliberately failing tests or create a second ToolRunner contract.

The new tests remain useful as reference for import isolation, single schema/decoder ownership, explicit executor assembly, event/job/result rollback, receipt/replay stability and runner-result publication separation. Focused cloud run: 36481054810 (head above). No successful implementation or issue closure is claimed here.

This session continues on #157 in fix/metadata-session-boundary-20260929, with notes in docs/METADATA_SESSION_PROGRESS.md. No production deployment, Root/PIN, funds, external mail or recovery promotion was performed.

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