RAGE #54: trusted delegated Auto-Dig session registration #55
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
priority:P1
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/quasar!55
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rage/54-trusted-delegated-session-registration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Tests-first owner-boundary slice for #54.
The RED contract requires a disabled-by-default trusted registration seam that can accept an already-authenticated StarIntel human principal/scopes/workspaces from an internal service adapter, register only canonical fixed Auto-Dig capabilities, and produce a short-lived WebSocket session without ever receiving a user OAuth bearer token.
Initial tests require:
No production registration endpoint or gateway enablement is included on this initial head. Expected state is RED.
WIP: RAGE #54: trusted delegated Auto-Dig session registrationto RAGE #54: trusted delegated Auto-Dig session registration663226ad82toc38ebe003aIteration 2 implemented and rebased onto current main (
1fa125c).Implementation (feat: trusted delegated Auto-Dig registration seam):
TDD evidence: RED proven first (suite exit 1: registration handler/lookup absent), then GREEN. Full quasar-tests suite exit 0 in the canonical nix develop environment, no undefined-function warnings; check-control-plane-deps and LOAD_ONLY control-plane load gates exit 0.
Deferred to the enablement slice on this same issue (per design record): private HTTP route wiring, deployment secret provisioning for the trusted StarIntel caller (infra #72), and handshake-time one-time consumption policy.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.