Repository navigation
feat(provider-tangle): resolve hosted subscription credentials - #404
Merged
Merged
Conversation
tangletools
approved these changes
Oct 2, 2026
tangletools
left a comment
There was a problem hiding this comment.
✅ Auto-approved PR — f4caca94
Blanket team auto-approval is intentional. The merge gates are CI and codex-p1.
No automated review runs on this PR. This approval rests on the rule above alone.
tangletools · auto-approval · reason: blanket_auto_approve · 2026-10-02T07:06:22Z
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.
A remote research controller can now resolve a subscription profile through an authenticated account owner without carrying native account homes or setup tokens.
The Provider forwards the exact profile, immutable dispatch key, and original validity deadline; the response contains only narrowly granted Sandbox secret references.
Capacity errors preserve explicit quota versus unavailable state and reset metadata without exposing private diagnostics or inventing HTTP status.
The account owner implementation is delivered separately in drewstone/tangle-tools.
Validation: 545 Provider source tests, types and workspace build passed.
Independent review passed 32 HTTP/command transport cases with no blocking finding.
Normal merge-tree and push hooks passed against current main.
The only follow-up change formats the release note.
Hosted deployment and actual quota pause remain live proof, not claims established by these tests.