v0.1.0

First tagged version. Seekter has been in daily use for a month; this is the
point where that stops being an untagged moving target.

What it does

Five slash commands inside Claude Code. /seekter-init interviews you and
writes your profile. /seekter-run searches five sources, filters every
posting against your rules, fills the forms in your own Chrome and records
what it did. /seekter-log records what came back. /seekter-report gives
you the funnel. /seekter-git ships what the kit learned without shipping
you.

What is in this version

• 12 documented job sources, plus a file on the ones that were measured
  and found not worth the calls.
• 24 documented application form systems, each written from real filled
  forms, plus a file of one-offs.
• A markdown tracker written only through scripts/seekter.py, with a
  normalised job_key so the same posting reached through LinkedIn, an
  aggregator and the company's own site is still caught as one.
• 39 tests over the tracker CLI: python3 -m unittest discover tests.
• Guardrails that do not bend: no CAPTCHAs, no account creation, no
  passwords, no accepting terms of use, no messages sent as you, and no
  answer it cannot verify from your profile.

Requirements

Claude Code, the Claude in Chrome extension, Python 3.9+ and curl. No
packages to install.

Your data stays yours

profile/, applications/ and runs/ are git-ignored, and /seekter-git
scans every diff against your own identity values before it pushes.

Why 0.1.0 and not 1.0.0

Because the structure is about to move. A Claude Code plugin is next, which
means the skills relocate and the tracker root stops being "wherever you
cloned this". If you clone today, expect the step up to 1.0.0 to need manual
work. 1.0.0 will be the version where that has settled.

Contributing

The most useful thing you can send is a measurement: a form system or a job
source behaving in a way nobody has written down yet. An issue is enough, no
pull request needed. See CONTRIBUTING.md.