[codex] Replace AgentOS with repository runtime#203
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements the repository runtime replacement plan end to end. The PR replaces the
jido_agent_osintegration with product-ownedJidoCode.Runtimecontainers, nativeJido.Podmanager topology, runtime snapshots/restoration, product entrypoint cutover, health/telemetry, contributor documentation, and acceptance coverage.What changed
Jido.Podusage through static instance managers.AgentWorkspace, specialist lookup, source graph, memory graph, source watching, refresh scheduling, and context-management flows through the repository runtime.jido_agent_osdependency.mix runtime.verifyand repository runtime migration/contributor docs.Validation
Passed:
mix test test/jido_code/runtime/repository_runtime_test.exsmix runtime.verifymix source_graph.verifymix memory.verifymix test test/jido_code/memory_graph_test.exs test/jido_code/memory_graph_workspace_test.exs test/jido_code/memory_graph_actions_test.exs test/jido_code/memory_graph_product_service_test.exs test/jido_code/memory_graph_workflow_service_test.exsmix test test/jido_code/conversations_child_work_test.exs test/jido_code/context_management_test.exs test/jido_code/conversations_test.exs test/jido_code/conversations_coordinator_test.exs test/jido_code/conversations_context_compaction_test.exs test/jido_code/conversations/context_memory_test.exsmix test test/jido_code/runtime/repository_runtime_acceptance_test.exs test/jido_code/conversations_child_work_test.exsFull-suite caveat:
mix testwas run and failed with995 tests, 96 failures, 4 excluded, 16 skipped. The failures are existing broad-suite drift outside this runtime replacement scope, including removed direct resource helper calls, stale LiveView selector expectations, old memory timeout expectations, large control-plane record validation cases, legacy setup/auth helper references, and unrelated conversation/control-plane timeouts.