{"content":"[dev-journal] assist-base-service WS-D bundle (commit e6e130d, branch feat/bundle): implemented the REQ-D-6 partner egress policy (mechanism choice for CR-1: configured IP allowlist, no partner-key header in v1). New partner.* config (partner.egress_ips, partner.daily_new_identity_limit default 50, partner.alert_per_day default 200) with an exact-match conf.IsPartnerEgressIP helper. Effect on the four per-IP surfaces, keeping per-identity limits everywhere: LLM bootstrap new-account limit rises from 20/day to the partner floor on partner IPs (the binding constraint for 50 signups/day from the shared tenant egress); free-grant per-IP claim limiter is bypassed on partner IPs (the one-claim-per-identity rule stays); sponsor per-IP rate window and per-IP open-order ceiling are skipped on partner IPs (per-address limits stay) — note the existing 20-requests/min/IP sponsor window already allowed far more than 50/day, so the binding limit was bootstrap. Traffic account creation has no per-IP limit (documented for the delivery note). New admin endpoint GET /v1/admin/partner/egress-ips shows each configured IP's new-identity count today (UTC) with the effective limit and the >200/day alert flag. Unit tests cover the egress matcher; go build + go test ./... green.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}