Repository navigation
Recover Runtime sessions through enrolled service authority - #401
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Maneek21
force-pushed
the
push-p3-runtime
branch
from
October 21, 2026 01:01
6c2965e to
a75045f
Compare
This was referenced Oct 21, 2026
Maneek21
added a commit
that referenced
this pull request
Oct 21, 2026
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.
Change
Expired technical channel sessions currently require a human to issue replacements. Add a bounded, service-authenticated reconciliation route that resolves the Runtime's current reviewed owner bindings and delivers replacement sessions through the existing authenticated installer. The service credential is restricted to its configured registration/installation and its operator's own active, until-revoked account grant. It cannot create a grant, select a different owner, or bypass current membership, consent, deployment, grant and revocation checks.
Existing background-access exports and the owner-triggered installer stay compatible. Persistent service issuance uses a branded, live authority guard and records service-registration provenance in the existing renewal provenance field; it does not require a browser session or an old technical session row. No schema migration.
Validation
Release this Host change before the paired deft-email Runtime change (Maneek21/deft-email#14). No merge, release or deployment is part of this PR. The service path deliberately retains explicit until-revoked consent; it does not convert finite grants or carry authority across an unreviewed update.
CI at 6c2965e is green: https://github.com/Maneek21/Deft/actions/runs/39497023450 (API, production build/smoke and versioned upgrade), plus CodeQL and dependency checks. The Hermes gate is intentionally skipped for the core release scope.