extend network egress allowlist for a scheduled Claude Code cloud environment

**Account:** yajie.zhu@icloud.com (individual account)
**Environment:** `schedule_job_search` (id `env_01767zSP9SMpwGGTEoVtLnFS`)
**Routine:** "Daily job scrape - ai-job-search" (id `trig_01MbVDsvLjSNnEpzhq1QvHSc`), repo `YajieZhu018/ai-job-search`, fires daily at 10:00 UTC

## Problem

The scheduled routine scrapes job postings and then fetches each posting's full text to score it against my profile. Starting around 2026-08-22, this fetch step has been failing with `EGRESS_BLOCKED` / `CONNECT tunnel failed, response 403` for a growing list of job-board and ATS domains, confirmed on every run from 2026-08-22 through 2026-08-25. This means most newly-found postings can never be scored — they sit at `status: "new"` indefinitely — so the daily shortlist has shrunk sharply even though the raw number of postings found per day hasn't.

I could not find a self-service way to edit this environment's network policy under my individual account's settings. Requesting the domains below be added to the egress allowlist for environment `env_01767zSP9SMpwGGTEoVtLnFS`.

## Domains to allowlist

ATS platforms (used by many different employers — wildcard where possible):
```
*.myworkdayjobs.com
*.jobs.personio.com
*.jobs.personio.de
jobs.ashbyhq.com
job-boards.greenhouse.io
jobs.smartrecruiters.com
jobs.gem.com
*.teamtailor.com
```

Job aggregators / boards:
```
www.arbeitnow.com
www.arbeitsagentur.de
www.adzuna.de
www.adzuna.co.uk
careers-page.com
himalayas.app
```

Direct company career sites seen in recent runs:
```
www.google.com
cast.ai
jobsearch.harman.com
sumup.com
```

## Evidence

Example error from a run log (session `cse_013ezDnoTbMLv3pMAnQAtWnv`, 2026-08-25):
```
tool_result ERROR: {"error_type":"EGRESS_BLOCKED","domain":"jobs.ashbyhq.com","message":"Access to jobs.ashbyhq.com is blocked by the network egress proxy."}
```
Confirmed via the proxy's own status endpoint (`$HTTPS_PROXY/__agentproxy/status`) as a gateway policy rejection, not a transient or certificate issue — same pattern for every domain listed above, across 4 consecutive daily runs.

## Ask

Please add the above domains to the egress allowlist for environment `env_01767zSP9SMpwGGTEoVtLnFS`, or let me know how to self-manage this allowlist for an individual account if that's possible.

No repository file, test, or entry point is identified in the report. Start by determining whether individual-account egress policy is managed in this repository or by the service; done would mean the listed domains are allowlisted for the named environment or documented self-service configuration is provided.

Vom Indexierungsmodell aus dem Issue-Text verfasst.