Skip to content

Reuse exact-owned Hermes forwards during onboarding and resume (PR #11427) #11557

Description

@prekshivyas

Parent epic: #11573

Delivered outcome

Repeated Hermes onboarding and resume retain verified dashboard and API forwards on their registered ports. Missing forwards are restored; sibling reservations, foreign listeners, changed identity, and unsafe ownership fail closed.

Pull request

Relationship to the Portable candidate

Candidate commit 30ef9ec7a independently addressed the occupied-forward failure found in the seat cycle. It is not an ancestor of current main; #11427 delivered the reviewed, broader implementation and is the source of truth.

Status: delivered to main by #11427.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area: onboardingOnboarding FSM, provider setup, sandbox launch, or first-run flowarea: sandboxOpenShell sandbox lifecycle, runtime, config, or recoverybugintegration: hermesHermes integration behavior

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions