Repository navigation
feat: optional local session dashboard - #13
Merged
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.
Add an optional local dashboard for launch-selected profiles and projects. Browse sessions and literal previews, review native transfers, edit a complete handoff, return the current worked session under a new identity, inspect durable operations and view recorded usage observations.
The dashboard binds only to loopback and starts explicitly through
smigrate web. Its default run is readonly. Native publication, handoff, return and each recovery service have separate explicit launch flags; HTTP accepts opaque launch-owned selections rather than paths, environment or executable values. Private capabilities stay with the worker through preparation, confirmation and cleanup. Revocation before publication cancels preparation; after publication starts, the owning operation retains its guards and reports the original durable outcome.Usage counters retain provenance and unknown dimensions; native totals, cost and context percentages remain unknown when not proved. Handoff is derived user context. OpenCode user handoffs retain PARTIAL coverage, full return to OpenCode remains blocked, and in-place update remains unavailable because native exclusion/CAS has not been demonstrated.
Validation completed:
Earlier installed Pilot opening failures and an intermittent post-publication finalization failure remain in the validation receipts, with their individual causes unconfirmed. The scoped readiness proof, independent review and final clean installed gate passed without weakening publication guards. Exact-head CI is required before merge.