TL;DR: The skills/ directory is 3.6MB / 282 files — smaller than a single retina screenshot. Splitting it into a separate repo adds real operational complexity to solve a non-problem, and partially reintroduces the version-coupling failures that caused the outages we're trying to fix.
Total: 3.6 MB, 282 files
Period: 2 weeks (2026-02-16 to 2026-03-02)
Organization: Faction-V
Data source: Local git repos cloned via ghorg (all branches, git log --all)
Period: 60 days (2026-01-01 to 2026-03-02)
Organization: Faction-V
Total repos in org: 134
Repos with activity: 30+
Total commits (excluding bots): 2,725
Active developers: 19
Data source: Local git repos cloned via ghorg (all branches, git log --all)
PR #363 (sso_user_id_updates by CapitolCoder) — 527 additions, 8 deletions, 3 files
PR #362 (feature/COM-18-ad-phase-1 by jordotech) — 8 additions, 1 deletion, 1 file
Both PRs add Authorization: Bearer header support to get_current_user() so SSO users can authenticate with agentic-backend.
| Aspect | PR #363 | PR #362 (ours) |
PR #365 (sso_user_id_updates by CapitolCoder) — 3,143 additions, 80 deletions, 16 files
PR #363 (feature/COM-18-ad-phase-1 by jordotech) — 3,124 additions, 264 deletions, 22 files
Both PRs target the same goal: make platform-api Auth0-aware so SSO users get proper UUIDs instead of Auth0 sub strings.
| Aspect | PR #365 | PR #363 |
As part of the Auth0 tenant migration (COM-18), we identified that SSO users cannot authenticate with agentic-backend. This is a pre-existing gap — not a regression from the migration — but it blocks SSO rollout for EY and future enterprise clients.
The frontend sends tokens differently depending on auth method:
This document describes an enterprise SSO implementation for EY using Auth0 and Azure Entra ID. Phase 1 is complete and validated end-to-end on staging as of February 23, 2026.