ilml-plugin-linkedin 1.20.1 → 1.20.2

package/CHANGELOG.md

@@ -1,5 +1,8 @@
 # Changelog
 
+## 1.20.2
+- **Discovery is now a normal setting you can turn on — no environment variable needed.** The experimental "build a pool of people to reach next" feature (from 1.20.0) is controlled by a config toggle: `ilml plugin config linkedin set DISCOVERY_ENABLED true`. It's still **off by default**. When on, `connect run` quietly notes LinkedIn's "People also viewed / More profiles for you" suggestions as it works (no extra page loads), and `ilml linkedin connect fill --from-discovered` tops up your connection queue from them, ranked by relevance to you. See `ilml linkedin help connect` for the full command reference and `ilml plugin config linkedin` for the setting. No schema change.
+
 ## 1.20.1
 - **Fixed the discovery feature (from 1.20.0) so the "who to reach next" list is actually ranked by relevance.** It was saving each discovered person without their job title — it accidentally grabbed the "2nd/3rd-degree" label instead — which left the relevance ranking blank. It now reads each person's real headline, so the best-fit people rise to the top. It's also more robust: names with special characters stay intact, people are grouped under the right section, and duplicate links no longer skew the order. Discovery is still off by default. No schema change.
 

package/README.md

@@ -98,6 +98,7 @@ ilml plugin config linkedin reset                  # re-prompt on next run
 | | `FUNNEL_EXCLUDE_LOCATIONS` | no | Comma-separated locations to skip. |
 | Connection limits | `CONNECT_MAX_DAILY` | no | Max connection requests per day across every path (`connect`, `funnel`, `apply`). Default: `20`. LinkedIn's real limit is dynamic and unknown — keep this under it, or raise it deliberately to surface LinkedIn's own limit (`connect` stops itself after 3 failures in a row and saves what LinkedIn showed to `connect-diagnostics/`). |
 | | `CONNECT_MAX_WEEKLY` | no | Rolling 7-day cap. Default: `100`. Free accounts are often limited around 100–200/week. Set e.g. `ilml plugin config linkedin set CONNECT_MAX_WEEKLY 250`. |
+| Discovery (experimental) | `DISCOVERY_ENABLED` | no | **Off by default.** When `true`, `connect run` also reads LinkedIn's "People also viewed / More profiles for you" side-panel on each profile it already opens and saves those people to a local discovery pool — no extra page loads, no effect on the connect itself. `connect fill --from-discovered` then tops up your queue from that pool, ranked by relevance to you. Adds ~2–3s per profile (a scroll to load the panel); English-locale LinkedIn only. Enable with `ilml plugin config linkedin set DISCOVERY_ENABLED true`. |
 
 ## Setting up your graph
 
@@ -187,7 +188,7 @@ You normally never touch it. Two things worth knowing:
 | `ilml linkedin apply-queue` | Apply to the top-scored jobs from the latest `scout` run. |
 | `ilml linkedin messages` | Batch messaging — draft, review, then push. Nothing sends without your approval. Common forms: `messages --review-drafts` (review pending drafts) and `messages --push-drafts` (push approved). |
 | `ilml linkedin funnel` | Run the recruiter / founder / investor connection-request queue. |
-| `ilml linkedin connect` | Build a reviewable, prioritised queue of people to connect with, then send under your daily/weekly quota. `connect add <file.json>` drops a curated list; `connect fill --category=founder,investor,hiring_manager` (or `--valuable`) pulls from people already categorised in your contacts; `connect list` / `approve` / `note` / `priority` / `skip` manage the queue; `connect run` sends only the approved ones. Sends go **without a note** by default (LinkedIn caps custom notes to a few per month) — save notes on the deliberate few with `connect note` and send them with `connect run --with-notes`. Every send goes through the same quota gate; `run` stops itself after 3 failures in a row (often LinkedIn's own limit). |
+| `ilml linkedin connect` | Build a reviewable, prioritised queue of people to connect with, then send under your daily/weekly quota. `connect add <file.json>` drops a curated list; `connect fill --category=founder,investor,hiring_manager` (or `--valuable`) pulls from people already categorised in your contacts; `connect fill --from-discovered` tops up from the discovery pool (see `DISCOVERY_ENABLED`), ranked by relevance to you; `connect list` / `approve` / `note` / `priority` / `skip` manage the queue; `connect run` sends only the approved ones. Sends go **without a note** by default (LinkedIn caps custom notes to a few per month) — save notes on the deliberate few with `connect note` and send them with `connect run --with-notes`. Every send goes through the same quota gate; `run` stops itself after 3 failures in a row (often LinkedIn's own limit). |
 | `ilml linkedin quota` | No-browser report: how much of today's / this week's connection quota is left and how it was spent (by source), the acceptance rate per source (which outreach actually converts), and high-value contacts you haven't connected to yet. `--json` for machine output. |
 | `ilml linkedin visit` | Visit recruiter / target profiles so they see you in "who viewed your profile". |
 | `ilml linkedin viewers` | Pull the "who viewed your profile" list. |