@stigmer/server 3.27.2 → 3.28.0

package/src/authorization/__tests__/fixtures/fga/platform-visibility.fga.yaml

@@ -1,199 +0,0 @@
-# Pinned copy of stigmer-cloud backend/services/stigmer-server/fga/tests/platform-visibility.fga.yaml
-# as changed by stigmer-cloud#765 (the OpenFGA store test the cloud runs against its live model).
-# The body below is byte-identical to the source; the cloud re-runs the LIVE
-# file against this evaluator at the re-pin, so a stale copy is caught there.
-# Store tests for platform visibility (visibility_platform).
-#
-# Verifies the userset chain end-to-end against the authorization model:
-#
-#   blueprint#platform_viewer -> identity_provider#platform_user
-#     -> member from managed_org -> organization#member
-#
-# Run with:
-#   fga model test --tests platform-visibility.fga.yaml
-#
-# Scenario: "planton" is a platform org owning identity_provider:idp1, which
-# manages two customer orgs (acme, beta). Blueprints owned by planton and
-# shared with visibility_platform must be viewable/executable by acme and
-# beta members, invisible to members of an unrelated org, and never editable
-# by managed-org members.
-name: platform-visibility
-model_file: ../model/fga.mod
-
-tuples:
-  # --- Platform tenancy: idp1 is owned by planton and manages acme + beta ---
-  - user: organization:planton
-    relation: organization
-    object: identity_provider:idp1
-  - user: organization:acme
-    relation: managed_org
-    object: identity_provider:idp1
-  - user: organization:beta
-    relation: managed_org
-    object: identity_provider:idp1
-
-  # --- Org memberships ---
-  - user: identity_account:swarup
-    relation: owner
-    object: organization:planton
-  - user: identity_account:priya
-    relation: member
-    object: organization:planton
-  - user: identity_account:veda
-    relation: viewer
-    object: organization:planton
-  - user: identity_account:alice
-    relation: member
-    object: organization:acme
-  - user: identity_account:bob
-    relation: member
-    object: organization:beta
-  - user: identity_account:mallory
-    relation: member
-    object: organization:outsider
-
-  # --- Platform-shared agent (visibility_platform) owned by planton ---
-  # PLATFORM carries the org floor tuple too (viewer@org#viewer — the org's
-  # full read audience, cloud#257), exactly as VisibilityTupleReconciler
-  # writes it, so everyone in the platform org keeps access.
-  - user: organization:planton
-    relation: organization
-    object: agent:sara
-  - user: identity_account:swarup
-    relation: owner
-    object: agent:sara
-  - user: identity_provider:idp1#platform_user
-    relation: platform_viewer
-    object: agent:sara
-  - user: organization:planton#viewer
-    relation: viewer
-    object: agent:sara
-
-  # --- Private agent owned by planton (no platform_viewer tuple) ---
-  - user: organization:planton
-    relation: organization
-    object: agent:internal-bot
-  - user: identity_account:swarup
-    relation: owner
-    object: agent:internal-bot
-
-  # --- Platform-shared blueprints of the other three kinds ---
-  - user: organization:planton
-    relation: organization
-    object: skill:research
-  - user: identity_provider:idp1#platform_user
-    relation: platform_viewer
-    object: skill:research
-  - user: organization:planton
-    relation: organization
-    object: workflow:onboarding
-  - user: identity_provider:idp1#platform_user
-    relation: platform_viewer
-    object: workflow:onboarding
-  - user: organization:planton
-    relation: organization
-    object: mcp_server:github
-  - user: identity_provider:idp1#platform_user
-    relation: platform_viewer
-    object: mcp_server:github
-
-tests:
-  - name: managed-org members can view and execute a platform-shared agent
-    check:
-      - user: identity_account:alice
-        object: agent:sara
-        assertions:
-          can_view: true
-          can_execute: true
-          can_create_instance: true
-          can_edit: false
-          can_delete: false
-      - user: identity_account:bob
-        object: agent:sara
-        assertions:
-          can_view: true
-          can_execute: true
-
-  - name: outsiders and unrelated orgs get nothing from platform visibility
-    check:
-      - user: identity_account:mallory
-        object: agent:sara
-        assertions:
-          can_view: false
-          can_execute: false
-          can_create_instance: false
-
-  - name: platform org's own members keep access via the org floor tuple
-    check:
-      - user: identity_account:priya
-        object: agent:sara
-        assertions:
-          can_view: true
-          can_execute: true
-          can_edit: false
-      # cloud#257: the viewer-shaped org floor reaches the platform org's own
-      # read-only viewers too. (Managed-org audiences are deliberately
-      # narrower: platform_user resolves member-from-managed_org.)
-      - user: identity_account:veda
-        object: agent:sara
-        assertions:
-          can_view: true
-          can_edit: false
-
-  - name: platform visibility does not leak the platform org's private agents
-    check:
-      - user: identity_account:alice
-        object: agent:internal-bot
-        assertions:
-          can_view: false
-          can_execute: false
-      # Private is real: even the platform org's own members see nothing
-      # without an explicit visibility tuple.
-      - user: identity_account:priya
-        object: agent:internal-bot
-        assertions:
-          can_view: false
-          can_execute: false
-
-  - name: platform-shared skill is usable by managed-org members
-    check:
-      - user: identity_account:alice
-        object: skill:research
-        assertions:
-          can_view: true
-          can_use: true
-          can_edit: false
-
-  - name: platform-shared workflow is viewable and executable by managed-org members
-    check:
-      - user: identity_account:alice
-        object: workflow:onboarding
-        assertions:
-          can_view: true
-          can_execute: true
-
-  - name: platform-shared mcp_server is usable by managed-org members
-    check:
-      - user: identity_account:alice
-        object: mcp_server:github
-        assertions:
-          can_view: true
-          can_use: true
-          can_connect: true
-
-  - name: platform owner retains full control of shared blueprints
-    check:
-      - user: identity_account:swarup
-        object: agent:sara
-        assertions:
-          can_view: true
-          can_edit: true
-          can_delete: true
-
-  - name: list managed-org member's viewable agents includes only the shared one
-    list_objects:
-      - user: identity_account:alice
-        type: agent
-        assertions:
-          can_view:
-            - agent:sara

package/src/authorization/__tests__/fixtures/fga/provider-standing-viewer.fga.yaml

@@ -1,40 +0,0 @@
-# Pinned copy of stigmer-cloud backend/services/stigmer-server/fga/tests/provider-standing-viewer.fga.yaml
-# at commit b87dd1170 (the OpenFGA store test the cloud runs against its live model).
-# The body below is byte-identical to the source; the cloud re-runs the LIVE
-# file against this evaluator at the re-pin, so a stale copy is caught there.
-# Store tests for the provider-standing view permission (cloud#447).
-#
-# can_view_provider_standing gates the read-only operator console view of
-# platform provider standing (the canary-probe verdicts the cloud#370
-# probe records). It derives from the platform operator role — provider
-# account health is platform-internal, so ordinary tenants (even org
-# owners) never see it, regardless of what they own.
-#
-# Run with:
-#   fga model test --tests provider-standing-viewer.fga.yaml
-name: provider-standing-viewer
-model_file: ../model/fga.mod
-
-tuples:
-  # A platform operator.
-  - user: identity_account:opal
-    relation: operator
-    object: platform:stigmer
-
-  # A tenant org owner — owns everything in their org, nothing on the
-  # platform.
-  - user: identity_account:mallory
-    relation: owner
-    object: organization:acme
-
-tests:
-  - name: operator may view provider standing, tenants may not
-    check:
-      - user: identity_account:opal
-        object: platform:stigmer
-        assertions:
-          can_view_provider_standing: true
-      - user: identity_account:mallory
-        object: platform:stigmer
-        assertions:
-          can_view_provider_standing: false

package/src/authorization/__tests__/fixtures/fga/reserved-label-writer.fga.yaml

@@ -1,41 +0,0 @@
-# Pinned copy of stigmer-cloud backend/services/stigmer-server/fga/tests/reserved-label-writer.fga.yaml
-# at commit b87dd1170 (the OpenFGA store test the cloud runs against its live model).
-# The body below is byte-identical to the source; the cloud re-runs the LIVE
-# file against this evaluator at the re-pin, so a stale copy is caught there.
-# Store tests for the reserved-label write permission (cloud#320).
-#
-# can_write_reserved_labels gates who may introduce or change labels in
-# the reserved stigmer.ai/* namespace at client-facing write boundaries
-# (GuardReservedLabelsStep). It derives from the platform operator role
-# — the seeding machine account holds it, ordinary tenants (even org
-# owners) never do, regardless of what they own.
-#
-# Run with:
-#   fga model test --tests reserved-label-writer.fga.yaml
-name: reserved-label-writer
-model_file: ../model/fga.mod
-
-tuples:
-  # The bootstrap machine account is the platform operator
-  # (BootstrapIdentitySeeder re-asserts this tuple on every boot).
-  - user: identity_account:machine
-    relation: operator
-    object: platform:stigmer
-
-  # A tenant org owner — owns everything in their org, nothing on the
-  # platform.
-  - user: identity_account:mallory
-    relation: owner
-    object: organization:acme
-
-tests:
-  - name: operator may write reserved labels, tenants may not
-    check:
-      - user: identity_account:machine
-        object: platform:stigmer
-        assertions:
-          can_write_reserved_labels: true
-      - user: identity_account:mallory
-        object: platform:stigmer
-        assertions:
-          can_write_reserved_labels: false

package/src/authorization/__tests__/fixtures/fga/schedule-owner.fga.yaml

@@ -1,113 +0,0 @@
-# Pinned copy of stigmer-cloud backend/services/stigmer-server/fga/tests/schedule-owner.fga.yaml
-# at commit b87dd1170 (the OpenFGA store test the cloud runs against its live model).
-# The body below is byte-identical to the source; the cloud re-runs the LIVE
-# file against this evaluator at the re-pin, so a stale copy is caught there.
-# Schedules are owner-scoped operational config (whatsapp-proactive-
-# messaging DD-008/DD-009, cloned from the agent_channel model): the
-# creator owns the schedule; view/edit/delete require ownership or an
-# explicit grant. Plain org members get NO implicit access — a schedule's
-# levers are billing-affecting (every fire spends the owning org's
-# credits, unattended). Creation is target-gated (can_edit on the
-# referenced agent, checked in-handler), so no organization-level
-# can_create_schedule relation exists to test.
-#
-# Org ADMINS inherit owner (T08, consistent with agents and channels — an
-# admin who can edit the agent can manage its schedules). The narrowness
-# these tests pin: owner + admins have control, granted viewers read,
-# plain members have nothing.
-#
-# Run: fga model test --tests schedule-owner.fga.yaml
-
-name: schedule-owner
-model_file: ../model/fga.mod
-
-tuples:
-  # Org membership for both accounts — proving membership grants nothing.
-  - user: identity_account:alice
-    relation: member
-    object: organization:acme
-  - user: identity_account:mallory
-    relation: member
-    object: organization:acme
-
-  # Org admin — proving T08 inheritance reaches schedules.
-  - user: identity_account:ana
-    relation: admin
-    object: organization:acme
-
-  # The schedule, created by alice (the config-driven create tuples).
-  - user: organization:acme
-    relation: organization
-    object: schedule:daily-fee-reminders
-  - user: identity_account:alice
-    relation: owner
-    object: schedule:daily-fee-reminders
-
-  # An explicit viewer grant to carol (not even an org member).
-  - user: identity_account:carol
-    relation: viewer
-    object: schedule:daily-fee-reminders
-
-tests:
-  - name: owner has full control including grant management
-    check:
-      - user: identity_account:alice
-        object: schedule:daily-fee-reminders
-        assertions:
-          can_view: true
-          can_edit: true
-          can_delete: true
-          can_grant_access: true
-          can_view_access: true
-
-  - name: explicitly granted viewer can read but not mutate
-    check:
-      - user: identity_account:carol
-        object: schedule:daily-fee-reminders
-        assertions:
-          can_view: true
-          can_edit: false
-          can_delete: false
-          can_grant_access: false
-          can_view_access: true
-
-  - name: fellow org member has no implicit access
-    check:
-      - user: identity_account:mallory
-        object: schedule:daily-fee-reminders
-        assertions:
-          can_view: false
-          can_edit: false
-          can_delete: false
-          can_grant_access: false
-          can_view_access: false
-
-  - name: org admin inherits schedule management (T08)
-    check:
-      - user: identity_account:ana
-        object: schedule:daily-fee-reminders
-        assertions:
-          can_view: true
-          can_edit: true
-          can_delete: true
-          can_grant_access: true
-
-  - name: listing schedules reflects ownership and grants, not membership
-    list_objects:
-      - user: identity_account:alice
-        type: schedule
-        assertions:
-          can_view:
-            - schedule:daily-fee-reminders
-          can_edit:
-            - schedule:daily-fee-reminders
-      - user: identity_account:carol
-        type: schedule
-        assertions:
-          can_view:
-            - schedule:daily-fee-reminders
-          can_edit: []
-      - user: identity_account:mallory
-        type: schedule
-        assertions:
-          can_view: []

package/src/authorization/__tests__/fixtures/fga/schedule-session-visibility.fga.yaml

@@ -1,214 +0,0 @@
-# Pinned copy of stigmer-cloud backend/services/stigmer-server/fga/tests/schedule-session-visibility.fga.yaml
-# at commit b87dd1170 (the OpenFGA store test the cloud runs against its live model).
-# The body below is byte-identical to the source; the cloud re-runs the LIVE
-# file against this evaluator at the re-pin, so a stale copy is caught there.
-# Store tests for schedule-session read-only observability (the session
-# `schedule` structural link — project DD-012 D-E, the channel-session
-# idiom's second application).
-#
-# A session created by the schedule runtime carries a single
-#   session#schedule@schedule:<id>
-# tuple and inherits the schedule's viewer set (creator owner + org admins
-# via `admin from organization` on schedule + explicit grantees) into
-# can_view ONLY — `viewer from schedule` is composed into session.can_view,
-# deliberately NOT into session.viewer, so schedule observers never gain
-# can_create_execution_in / can_edit / can_delete / can_grant_access
-# (injecting a console message into an unattended run is not
-# observability). Executions follow through agent_execution's
-# `can_view: viewer or can_view from session`.
-#
-# The personal-session invariant is untouched: console sessions never carry
-# a schedule tuple, so `viewer from schedule` resolves to nothing for them
-# (pinned below and by session-personal-resource.fga.yaml).
-#
-# Run with:
-#   fga model test --tests schedule-session-visibility.fga.yaml
-#
-# Scenario: org "acme" has admin alice, member bob (who created the
-# fee-reminder schedule and owns it), member carol (no relation to the
-# schedule), and member dave (an explicit schedule viewer grant — the
-# console "share this schedule" affordance). "rival" is another org whose
-# admin eve must see nothing. The schedule session is owned by acme's
-# system-schedule account; bob also has a normal personal console session
-# to prove the invariant.
-name: schedule-session-visibility
-model_file: ../model/fga.mod
-
-tuples:
-  # --- Org roles ---
-  - user: identity_account:alice
-    relation: admin
-    object: organization:acme
-  - user: identity_account:bob
-    relation: member
-    object: organization:acme
-  - user: identity_account:carol
-    relation: member
-    object: organization:acme
-  - user: identity_account:dave
-    relation: member
-    object: organization:acme
-  - user: identity_account:eve
-    relation: admin
-    object: organization:rival
-
-  # --- The Schedule (tuples written on create: org link + creator owner) ---
-  - user: organization:acme
-    relation: organization
-    object: schedule:fee-reminder
-  - user: identity_account:bob
-    relation: owner
-    object: schedule:fee-reminder
-  # dave's explicit viewer grant on the schedule (never on the session):
-  - user: identity_account:dave
-    relation: viewer
-    object: schedule:fee-reminder
-
-  # --- The schedule session (owned by the org's system-schedule account) ---
-  - user: organization:acme
-    relation: organization
-    object: session:scheduled-run
-  - user: identity_account:sys-schedule-acme
-    relation: owner
-    object: session:scheduled-run
-  # The structural link written by ScheduleSessionLinkStep:
-  - user: schedule:fee-reminder
-    relation: schedule
-    object: session:scheduled-run
-
-  # --- An execution inside the schedule session ---
-  - user: session:scheduled-run
-    relation: session
-    object: agent_execution:scheduled-run-1
-
-  # --- bob's ordinary personal console session (NO schedule tuple) ---
-  - user: organization:acme
-    relation: organization
-    object: session:bobs-chat
-  - user: identity_account:bob
-    relation: owner
-    object: session:bobs-chat
-  - user: session:bobs-chat
-    relation: session
-    object: agent_execution:bobs-run-1
-
-tests:
-  - name: schedule creator can view the run but only view it
-    check:
-      - user: identity_account:bob
-        object: session:scheduled-run
-        assertions:
-          can_view: true
-          can_create_execution_in: false
-          can_edit: false
-          can_delete: false
-          can_grant_access: false
-          can_view_access: false
-
-  - name: org admin inherits view through the schedule, read-only
-    check:
-      - user: identity_account:alice
-        object: session:scheduled-run
-        assertions:
-          can_view: true
-          can_create_execution_in: false
-          can_edit: false
-          can_delete: false
-          can_grant_access: false
-
-  - name: plain org member without schedule access sees nothing
-    check:
-      - user: identity_account:carol
-        object: session:scheduled-run
-        assertions:
-          can_view: false
-          can_create_execution_in: false
-
-  - name: another org's admin sees nothing
-    check:
-      - user: identity_account:eve
-        object: session:scheduled-run
-        assertions:
-          can_view: false
-
-  - name: the system-schedule account keeps full session ownership
-    check:
-      - user: identity_account:sys-schedule-acme
-        object: session:scheduled-run
-        assertions:
-          can_view: true
-          can_create_execution_in: true
-          can_edit: true
-          can_delete: true
-
-  - name: executions inherit read-only schedule observability
-    check:
-      - user: identity_account:bob
-        object: agent_execution:scheduled-run-1
-        assertions:
-          can_view: true
-          can_edit: false
-      - user: identity_account:alice
-        object: agent_execution:scheduled-run-1
-        assertions:
-          can_view: true
-          can_edit: false
-      - user: identity_account:carol
-        object: agent_execution:scheduled-run-1
-        assertions:
-          can_view: false
-
-  - name: an explicit schedule viewer grant reaches the run read-only
-    check:
-      # dave holds schedule viewer only — he can open the runs, still
-      # read-only, and gains nothing on the schedule's management levers.
-      - user: identity_account:dave
-        object: session:scheduled-run
-        assertions:
-          can_view: true
-          can_create_execution_in: false
-          can_edit: false
-      - user: identity_account:dave
-        object: agent_execution:scheduled-run-1
-        assertions:
-          can_view: true
-          can_edit: false
-
-  - name: personal-session invariant is untouched by the schedule model
-    check:
-      # Admin still has no path into a console session (no schedule tuple).
-      - user: identity_account:alice
-        object: session:bobs-chat
-        assertions:
-          can_view: false
-          can_edit: false
-          can_delete: false
-      - user: identity_account:alice
-        object: agent_execution:bobs-run-1
-        assertions:
-          can_view: false
-      # And the owner's own access is unchanged.
-      - user: identity_account:bob
-        object: session:bobs-chat
-        assertions:
-          can_view: true
-          can_edit: true
-          can_create_execution_in: true
-
-  - name: list viewable sessions resolves the schedule chain
-    list_objects:
-      - user: identity_account:alice
-        type: session
-        assertions:
-          can_view:
-            - session:scheduled-run
-      - user: identity_account:bob
-        type: session
-        assertions:
-          can_view:
-            - session:scheduled-run
-            - session:bobs-chat
-      - user: identity_account:carol
-        type: session
-        assertions:
-          can_view: []