8000 feat(agentcore): add runtime execution orchestration by Fodesu · Pull Request #94 · felinics/twilight · GitHub
[go: up one dir, main page]

Skip to content
1 8000

feat(agentcore): add runtime execution orchestration - #94

Merged
Fodesu merged 1 commit into
feat/agent-runtime-core-20-executor-workerfrom
feat/agent-runtime-core-21-runtime
Oct 3, 2026
Merged

Fodesu merged 1 commit into
feat/agent-runtime-core-20-executor-workerfrom
feat/agent-runtime-core-21-runtime

Conversation

@Fodesu
@Fodesu Fodesu commented Oct 3, 2026 •
Copy link
Copy Markdown
Member

Summary

Adds the runtime that composes the Run Loop, execution port, session ownership, and recovery paths into one process-independent execution service. The runtime package is the coordination layer above individual Run transitions and below application ownership.

Design

Runtime accepts a session-scoped execution request, loads or creates the relevant Run store, and drives the Loop until it reaches a terminal result, quiescent wait, or an ownership/recovery boundary. It does not duplicate Run state: each advance and settlement reloads the authoritative snapshot, derives actions, and commits through the store. The execution service routes outcomes by stable AssignmentKey and uses the effect Watcher rather than one polling goroutine per effect.

The runtime’s recovery path identifies Executing model steps and tool calls that were not settled by the current process. It asks the executor for attachment state, defers orphaned records that may still be recovered, and applies the explicit missing-effect policy for records the executor no longer holds. Recovery commands are derived from the EffectID, making takeover idempotent across owner processes. A runtime-level lifetime bounds delivery registrations while detached settlement contexts protect accepted effects from caller cancellation.

The conformance harness builds fake stores, builders, executors, and clocks around the public runtime ports. It is structured to test the composition boundary—startup, dispatch, outcome delivery, cancellation, terminal results, and recovery—without requiring a provider or a network executor. The harness also provides the setup used by later application and integration tests.

Testing

This branch adds runtime conformance infrastructure and a store-oriented test. The detailed behavior matrix is exercised by the follow-on runtime and integration suites.

@Fodesu
Fodesu added this pull request to stack #105 October 3, 2026 12:27
@Fodesu Fodesu changed the title feat/agent runtime core 21 runtime feat(agentcore): add runtime execution orchestration Oct 3, 2026
@Fodesu
Fodesu force-pushed the feat/agent-runtime-core-21-runtime branch from 2229360 to a060905 Compare October 3, 2026 14:43
@Fodesu
Fodesu force-pushed the feat/agent-runtime-core-21-runtime branch from a060905 to a89fc6a Compare October 3, 2026 14:55
@Fodesu
Fodesu force-pushed the feat/agent-runtime-core-21-runtime branch from a89fc6a to 6a6e81d Compare October 3, 2026 15:35
@Fodesu
Fodesu removed this pull request from stack #105 October 3, 2026 16:13
@Fodesu
Fodesu added this pull request to stack #107 October 3, 2026 16:16
@Fodesu
Fodesu marked this pull request as ready for review October 3, 2026 16:23
@Fodesu
Fodesu removed this pull request from stack #107 October 3, 2026 16:34
@Fodesu
Fodesu added this pull request to stack #108 October 3, 2026 16:37
@Fodesu
Fodesu removed this pull request from stack #108 October 3, 2026 16:51
@Fodesu
Fodesu added this pull request to stack #110 October 3, 2026 16:55
@Fodesu
Fodesu force-pushed the feat/agent-runtime-core-21-runtime branch from 6a6e81d to 731d4ca Compare October 3, 2026 17:04
@Fodesu
Fodesu force-pushed the feat/agent-runtime-core-21-runtime branch from 731d4ca to c2d0933 Compare October 3, 2026 17:11
@Fodesu
Fodesu merged commit d89acfd into main Oct 3, 2026
4 checks passed
@Fodesu
Fodesu deleted the feat/agent-runtime-core-21-runtime branch October 5, 2026 07:35
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

0