Hard cut agent lifecycle to topology#31
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughImplements end-to-end graveyard resurrection: frontend button + API client, MetadataServer HTTP handlers, multiplexer lifecycle implementations, persistence resurrection into offline topology, session-exit preservation, session reconciliation before resume/restore, and CLI remote-first wiring. ChangesGraveyard Resurrection Feature
Sequence DiagramsequenceDiagram
participant UI as GraveyardScreen
participant Client as resurrectGraveyardAgent
participant Server as MetadataServer
participant Multiplexer as dashboardTailMethods
participant Persistence as resurrectTopologySession
UI->>Client: POST /graveyard/resurrect {sessionId}
Client->>Server: forward request
Server->>Multiplexer: host.resurrectGraveyardSession(sessionId)
Multiplexer->>Persistence: resurrectTopologySession(sessionId)
Persistence-->>Multiplexer: {sessionId,status:"offline"}
Multiplexer->>Server: notify change
Server->>Client: 200 {ok:true, sessionId, status:"offline"}
Client->>UI: success -> update UI, kickDesktopStateRefresh
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsGit: Failed to clone repository. Please run the Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/main.ts`:
- Around line 2461-2464: The command is calling
Multiplexer.resurrectGraveyardSession(...) directly (via prepareProjectContext
and new Multiplexer()) instead of using the daemon/ project service call path
used by sibling lifecycle commands; update the graveyard resurrect flow to call
the project service API (the same daemon-ready project service helper used
elsewhere) and only fall back to local Multiplexer.resurrectGraveyardSession
when the service is unavailable, preserving existing behavior for opts.json
output and the identical case at the other occurrence around
resurrectGraveyardSession at the later location; locate usages of
prepareProjectContext, Multiplexer, and resurrectGraveyardSession to implement
the service-first, local-fallback routing.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: e726d820-18ff-4b2a-b65b-4a9a5cc298d3
📒 Files selected for processing (21)
app/app/(main)/(tabs)/(dashboard)/graveyard.tsxapp/lib/api.tsdocs/runtime-core-hard-cut-roadmap.mdsrc/dashboard/session-actions.tssrc/main.tssrc/metadata-server.test.tssrc/metadata-server.tssrc/multiplexer/agent-io-methods.tssrc/multiplexer/archives.tssrc/multiplexer/dashboard-model.tssrc/multiplexer/dashboard-ops.tssrc/multiplexer/dashboard-tail-methods.test.tssrc/multiplexer/dashboard-tail-methods.tssrc/multiplexer/persistence-methods.test.tssrc/multiplexer/persistence-methods.tssrc/multiplexer/session-launch.test.tssrc/multiplexer/session-launch.tssrc/multiplexer/session-runtime-core.test.tssrc/multiplexer/session-runtime-core.tssrc/runtime-core/index.test.tssrc/runtime-core/index.ts
💤 Files with no reviewable changes (2)
- src/runtime-core/index.ts
- src/runtime-core/index.test.ts
Summary
Verification
Note: full app lint still has unrelated existing prettier/hook warnings in other app files.
Summary by CodeRabbit