Skip to content

Maintainer: 2026-10-26 — 4 entries - #135

Merged
markramm merged 6 commits into
mainfrom
maintainer/2026-10-26
Oct 26, 2026
Merged

markramm merged 6 commits into
mainfrom
maintainer/2026-10-26

Conversation

@markramm

Copy link
Copy Markdown
Owner

Daily maintainer run, 2026-10-26. 1 fix to an existing entry and 3 new entries from the California registry. Every entry keeps last_verified: null. Nothing was submitted on any form.

Fixes

leadershipconnect-io: Fixes #39

  • /dsar/ redirects to the homepage (seen by the monitor) and returned HTTP 429 to a direct fetch today.
  • The footer's "Do Not Sell My Personal Information" link now goes to https://leadershipconnect.io/opt-out/. That page embeds https://optout.leadershipconnect.io/, a "Request Optout" form with required Name and Email fields and a reCAPTCHA-gated Submit button.
  • Changes: opt_out_url → /opt-out/, method: portal → form, captcha: false → true (tier stays guided). The steps were rewritten. The mailing step now gives both addresses, because the policy still says 325 7th St NW and the footer now says 525 9th Street NW.

New entries (CA registry ours == new)

lusha-com: B2B contact database (work emails and phones).

  • https://www.lusha.com/privacy-center/request-removal/ embeds a OneTrust webform. Rendered headless, it asks for a reason, country (required), state and email (required), and shows a visible "I'm not a robot" reCAPTCHA, so the entry is guided.
  • Fallbacks from the privacy notice: privacy@lusha.com, or 1-866-467-8688 with service code 2001#.
  • Priority standard (B2B-only, same as uplead-com).

swordfish-ai: contact and cell-phone lookup for sales, recruiting and investigations.

wiza-com: prospecting and contact-enrichment tool (wiza.com redirects to wiza.co; the entry uses the registry's domain so the CA row matches).

  • https://wiza.co/optout-contact-info requires name and one email; a second email and two phone numbers are optional. A visible reCAPTCHA is shown, so the entry is guided.
  • Fallback: optout@wiza.com.
  • Priority high: the page asks for personal emails and past phone numbers too.

validate_broker.py and build_brokers.py pass. brokers.json and manifest.json are rebuilt in the last commit.


Generated by Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
)

CI's rebuild-and-diff step re-ran the build on an already-built tree and
bumped 0.1.17 to 0.1.18, so the validate check could never pass.

Co-Authored-By: Claude <noreply@anthropic.com>

Copy link
Copy Markdown
Owner Author

CI validate failed on 62e4096 with "data/brokers.json or data/manifest.json is stale". The PR's data wasn't stale. scripts/build_brokers.py bumps dataset_version every time it runs, so CI's rebuild of an already-built tree turned 0.1.17 into 0.1.18 and the diff could never be empty. That's a base-branch bug, and open PR #116 already fixes it. I ported #116's build_brokers.py change into this PR (one commit, a no-op once #116 merges). Locally, the full CI sequence now passes: validate, rebuild with no diff, --check, and the semver bump (0.1.16 → 0.1.17). The same bug will likely fail any other maintainer PR that CI rebuilds before #116 merges.


Generated by Claude Code

@markramm
markramm marked this pull request as ready for review October 26, 2026 14:57
@markramm
markramm merged commit d47af20 into main Oct 26, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Page monitor: leadershipconnect-io

2 participants