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
- ..
- notify
- repo
- settings
- workspace
- auth-github-callback.tsx
- auth-github-username.tsx
- auth-github.ts
- confirm-email.tsx
- desktop-runner.ts
- device.tsx
- download.tsx
- downloads-runner.ts
- explore.tsx
- forgot.tsx
- github-install.ts
- github-setup.tsx
- home.tsx
- hovercard-user.ts
- inbox-json.ts
- inbox-moved.ts
- invitations.tsx
- invite.tsx
- login-two-factor.tsx
- login.tsx
- logout.tsx
- new-github.tsx
- new.tsx
- not-found.tsx
- notifications.tsx
- oauth-authorize.tsx
- people-json.ts
- policies.tsx
- policy.tsx
- pricing.tsx
- register.tsx
- reset.tsx
- robots-txt.ts
- search-json.ts
- search.tsx
- security-txt.ts
- security.tsx
- settings-menu-json.ts
- sitemap-xml.ts
- status-json.ts
- status.tsx
- support.tsx
- user.tsx
- verify.tsx
- well-known-g1t.ts