Context
The branch janus-auth-token-packages on saga-ed/soa was meant to publish two new soa packages: @saga-ed/soa-auth-token and @saga-ed/soa-auth-token-client. Per the design doc at docs/request-context-design.md (added later), those packages get deleted in favor of:
@saga-ed/soa-request-context (new, generic primitive — separate issue)@saga-ed/janus-client in ~/dev/janus (already built, hosts the Janus-specific code)@saga-ed/iam-client in ~/dev/rostering (separate issue)
The branch was never published to CodeArtifact. No consumers depend on it.
Scope
- Close the branch unmerged.
- After confirming
@saga-ed/janus-client covers the use cases (it does — the gate Lambda already consumes it; saga-dash and iam-api will once it's published), delete the remote branch.
- No commits or PRs needed against soa main.
- Optional: a closing comment / paper trail on the branch noting where the work moved.
Acceptance criteria
Originated in
2026-05-05 deploy session — strategic decision to host Janus primitives in janus repo, not soa.
Context
The branch
janus-auth-token-packagesonsaga-ed/soawas meant to publish two new soa packages:@saga-ed/soa-auth-tokenand@saga-ed/soa-auth-token-client. Per the design doc atdocs/request-context-design.md(added later), those packages get deleted in favor of:@saga-ed/soa-request-context(new, generic primitive — separate issue)@saga-ed/janus-clientin~/dev/janus(already built, hosts the Janus-specific code)@saga-ed/iam-clientin~/dev/rostering(separate issue)The branch was never published to CodeArtifact. No consumers depend on it.
Scope
@saga-ed/janus-clientcovers the use cases (it does — the gate Lambda already consumes it; saga-dash and iam-api will once it's published), delete the remote branch.Acceptance criteria
@saga-ed/soa-auth-tokenor@saga-ed/soa-auth-token-clientin any repo.Originated in
2026-05-05 deploy session — strategic decision to host Janus primitives in janus repo, not soa.