syntaqxA host a cloud job's guardrails refuse is named in the refusal's status line, not only its body: `403 Forbidden by g1t guardrails: api.expo.dev is not an allowed domain`. Many tools show only the status line of a failed request. eas-cli's GraphQL client prints the reason phrase and drops a body that is not JSON, and apk prints `HTTP 403: Forbidden`, so a refused Expo call surfaced as a bare "Forbidden" followed by "GraphQL request failed", with nothing pointing at the guardrails. The refusal also carries an x-g1t-blocked-host header beside x-g1t-guardrails: blocked. Its plain-text body says where to allow the host: Allowed domains for every sandbox, or Workflow-only domains for the jobs of one workflow and environment. The guardrails and Actions guides say what a refused request shows.3039e06History
- ..
- 0001_init.sql
- 0002_text_ids.sql
- 0003_unique_email.sql
- 0004_email_verification.sql
- 0005_token_expiry.sql
- 0006_device_codes.sql
- 0007_rfc3339_timestamps.sql
- 0008_workspaces.sql
- 0009_oauth.sql
- 0010_workspace_tokens.sql
- 0011_agent_tokens.sql
- 0012_avatars.sql
- 0013_profiles.sql
- 0014_workspace_redirects.sql
- 0015_run_credentials.sql
- 0016_deleted_workspaces.sql
- 0017_github.sql
- 0018_invites.sql
- 0019_user_emails.sql
- 0020_access.sql
- 0021_waitlist_notices.sql
- 0022_token_scopes.sql
- 0023_retire_token_reach.sql
- 0024_g1t_name.sql
- 0025_workspace_soft_delete.sql
- 0026_workspace_residency.sql
- 0027_teams.sql
- 0028_team_creation.sql
- 0029_workspace_aliases.sql
- 0030_job_tokens.sql
- 0031_membership.sql
- 0032_two_factor.sql
- 0033_identity_jobs.sql
- 0034_fine_grained_tokens.sql
- 0035_deploy_keys.sql
- 0036_email_confirmation_codes.sql
- 0037_account_deletion.sql
- 0038_shared_invites.sql
- 0039_profile_timezone.sql
- 0040_workspace_invitations.sql
- 0041_one_kind_of_token.sql
- 0042_username_case.sql
- 0043_website_tokens.sql
- 0044_dock_pins.sql
- 0045_people_and_teams.sql
- 0046_sound_settings.sql