Repository navigation
Guardian package: SSO and SCIM moved from Roster - #1
Merged
jayjfletcher merged 38 commits intoOct 30, 2026
Merged
Conversation
…uite Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…uite Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…gration, models and create migrations (salvaged) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…gration, models and create migrations Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…d MCP (salvaged) Move Roster's SSO domain source (actions, data, events, exceptions, HTTP, MCP, resources, services, routes) into Guardian and register the seven SSO tools on GuardianServer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…d MCP Scope SSO audit entries to their organization as Roster did (SsoAudit on Keystone's AuditHooks), test the guardian.mcp web and local servers, move Roster's connection-secret redaction case, apply Pint, tick group 3 and record it in build.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…d MCP Retry: every group 3 task was already committed; record the re-check in build.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nd MCP Fix the salvaged SCIM move: ScimException no longer redeclares Keystone's protected $status as readonly, the SCIM domain names guardian.scim. as the scim audit surface as Roster did, the ten-tool listing browses the catalog through search_tools, and the scim.enabled route test refreshes name lookups. Drop a test for an audit entry Roster never wrote. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nd MCP Retry: no code change. Record that the one failing test came from vendor Keen being linked to an unmerged Keen job branch; the link is restored to ../Keen as composer.local.lock records. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…llers, views) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…er application Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… script and browser workflow Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…uild Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…on Roster's tables and permissions at the pinned SHA Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s with Roster's at the pinned SHA Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ecture/dependencies departure Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nt fails open until Guardian is installed Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…uild Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…'s public API, publish views, record the provider deviation - SsoLoginAction and ScimUsers join through Guardian's JoinsOrganizations, not Roster's internal ManagesMemberships trait - ScimQuery keeps its own case-insensitive eq instead of Roster's Support\CaseInsensitive - SsoIdentityResource nests Guardian's UserSummaryResource, held equal to Roster's by a test - RosterBoundaryTest denies Roster domain Concerns and Resources and every Support class but Users, Statuses, UserKey and Tables - views publish under guardian and guardian-views - standards-feedback rows for the booting() domain provider registration and the two departures the boundary fix brings Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…'s rollback check to its own tables D-040: the sso migration checks only guardian_sso_*, the scim migration only guardian_scim_*, so SCIM rows no longer block a targeted SSO rollback. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…r OIDC link and just-in-time sign-in D-039: Sso::claims() sets IdentityClaims::emailVerified from the id_token's email_verified claim (only a literal true) for OIDC connections; SAML and Entra ID leave it true. SsoLoginAction refuses link-by-email and JIT creation with reason unverified_email and its own lang string; identities already linked still sign in. The moved OidcFlowTest now sends email_verified true. README, the Boost skill and CHANGELOG record the change from Roster. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…lback test to D-040 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…uild Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…oster The workbench User used Roster's HasRoster unconditionally, so package:discover fatalled once the job uninstalled Roster. UsesRoster wraps it when Roster exists. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- PermissionsTest compares forward-slash paths, so Windows skips src/Upgrade. - The test job restores the committed composer.json after the matrix pins, which PackageWiringTest reads. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The MCP tool snapshots carry the title annotation laravel/mcp 1.1 added, so the prefer-lowest jobs failed on 1.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- CHANGELOG: the Unreleased notes become v0.1.0 (2026-10-30). - Suite packages are required as ^0.1 instead of dev-main; PackageWiringTest expects them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jayjfletcher
deleted the
ring-master/2026-10-29-2038-guardian-package
branch
November 11, 2026 04:13
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.
Risk: high
What changed
refactor-circus/guardian: auth and security for the suite. Its first features are SSO (OIDC, SAML, Entra ID) and SCIM 2.0 provisioning, moved out of Roster with their actions, data, events, models, policies, HTTP API, MCP tools (seven SSO, three SCIM) and routes.conflictonrefactor-circus/atrium <0.1.0. Without Roster, Guardian boots inert and itsaboutline says "Inactive: install refactor-circus/roster" (D-023).Roster::requireSignIn(),externalSignInFor(),provisionedStatus(),Resources,PermissionCatalogue,MembershipSources) plus Roster's public domain API (D-024).RosterBoundaryTestdenies Roster's internals.guardian.ssoandguardian.scimtabs and theguardian.sso-identitiesaside are placed on Roster's screens fromconfig/guardian.phpatrium.screens. There is also aguardian.sso-connectionscreen. A WithoutAtrium suite and CI lane prove Guardian runs without Atrium.Handovergate means no SSO/SCIM routes, morph aliases or table rename until Roster's SSO code is gone (D-022).guardian:upgrade-from-rosterand the2026_11_01_000000migration rename the tables and merge theroster.sso.*/roster.scim.*grants. Stranded tables are reported, never enforced (D-029).email_verifiedclaim istrue.Why
SSO and SCIM are security features with their own lifecycle. Moving them into Guardian keeps Roster focused on users and organizations, and gives MFA, session policies and IP rules a home.
Look at
src/Upgrade/RosterUpgrade.php: the table rename and grant merge, plan-then-act.src/Domains/Sso/Actions/SsoLoginAction.php:linkOrCreate()with the D-039 email check.src/Domains/Sso/Concerns/JoinsOrganizations.php: writes Roster's membership models directly, because Roster has no public action that takes a membership source (recorded in standards-feedback.md).src/Support/Integration.php: the Roster and Atrium detection that gates everything.database/migrations/2026_11_01_000001_create_guardian_sso_tables.php:down()refuses to drop tables with rows unless forced (D-031, D-040).Tested
composer test: PHPStan, Pint, 100% type coverage and 546 Pest tests pass.tests/moved-tests.json). Comparisons with Roster's config and MCP tools use fixtures captured at that SHA.--group=upgrade-mysql) run only in CI and have not run yet.Risks
Permissions::forgetCache();Prerequisites and merge order
Guardian requires Refactor-Circus/Roster#11 (auth extension seams) and #13 (SSO and SCIM removed from Roster, which also contains #12), plus Refactor-Circus/Atrium#16 and Refactor-Circus/Keen#8, all merged before Guardian is tagged.
Decisions taken during the build
Support\Integration::rosterPresent()is public and marked@internal.guardian.ui.enabledconfig key; the plugin registers through Keystone'sregisterAtriumPlugin().email_verified(a change from Roster).down()checks only the tables it drops.Remaining nits
SsoLoginRefuseduses a public constructor rather than aforX()named constructor.Bulk.phpreads one config value without casting it.SsoLoginFailedActionEventis dispatched from the web controller.Services\Ssois notfinal.Spec:
docs/agent/specs/2026-10-29-2038-guardian-package/🤖 Generated with Claude Code