ilml-plugin-linkedin 1.2.1 → 1.2.2

package/CHANGELOG.md

@@ -0,0 +1,28 @@
+# Changelog
+
+## 1.2.2
+- README polish based on real-user feedback:
+  - Cleaner top — removed the metadata bullet list (npm/tracker/license) that was the very first thing visitors saw on the npm page; now opens straight into "What it does"
+  - Removed the entire `Developer Notes` section — it was internal-only and not useful for end users (release process and architecture notes live in `CLAUDE.md` and the SDK's plugin spec)
+  - Clarified the `LINKEDIN_SEARCH_URL` instruction (no more raw URL parameters like `f_AL=true` — just "open LinkedIn → Jobs, set filters, copy URL")
+  - New **Author & contact** section with personal page, LinkedIn, and a **DigitalTwins.team** call-to-action for custom plugin development
+- `CHANGELOG.md` is now shipped in the npm tarball (added to `package.json#files`), so the npm package page renders release notes next to the README
+- New **Feedback & support** section in the README pointing at a dedicated **Support** node in iLiveMyLife (`0000019dde81b04f-2e534bb8ebad0000`) — users can write directly to the maintainer via the in-graph messenger or `ilml send` from the terminal
+
+## 1.2.1
+- Documentation overhaul — `README.md` rewritten in English, split into **User Guide** (install, configure, run, update) and **Developer Notes** (release process, architecture, security checklist)
+- Removed outdated `.env`-based user instructions — the plugin is now fully self-configuring via `ilml plugin install linkedin` + first-run prompts (or `ilml plugin config linkedin set KEY VALUE`)
+- Added `CHANGELOG.md` (this file)
+- Added `CLAUDE.md` — project-level guide for the AI assistant covering release process and key architecture pointers
+- Added a `Releases` node in the iLiveMyLife graph for in-app release notifications
+
+## 1.2.0
+- First public publish on npm as `ilml-plugin-linkedin`
+- `src/config.mjs` refactored to use `getPluginConfig()` from `@ilivemylife/graph-sdk` v1.0.17
+  - Resolved configuration is merged into `process.env` so the rest of the codebase (16+ files reading `process.env.X`) keeps working unchanged
+  - The manual `LINKEDIN_NAME` bootstrap check is removed — schema validation in the SDK handles it
+  - Works in both **production** (`ilml linkedin <command>`) and **development** (`node run.mjs` with `.env` next to manifest), without any code changes between modes
+- Bumped `@ilivemylife/graph-sdk` peer to `^1.0.17`
+- `package.json` polish for npm publish — `author`, `license: UNLICENSED`, `keywords`, strict `files: ["dist", "ilml-plugin.json"]` whitelist
+- `ilml-plugin.json` declares config via `config.sections[].fields[]` (richer manifest format supported by SDK 1.0.17): grouped fields with `label`, `hint`, types (`text`, `secret`, `path`, `nodeId`, `url`, `number`, `boolean`)
+- All sensitive files (`.env`, `cookies.json`, raw sources, internal handoff docs, runtime data) excluded from the npm tarball via `.npmignore`

package/README.md

@@ -2,12 +2,6 @@
 
 LinkedIn job-search and networking automation as a plugin for the [`ilml`](https://www.npmjs.com/package/@ilivemylife/graph-sdk) CLI.
 
-- **npm:** https://www.npmjs.com/package/ilml-plugin-linkedin
-- **Tracker / Releases (in iLiveMyLife):** open the **Releases** node inside the **LinkedIn Automation** project in your iLiveMyLife app
-- **License:** UNLICENSED — all rights reserved
-
----
-
 ## What it does
 
 A toolkit that drives LinkedIn from your machine via a real browser (Puppeteer + stealth), with results synced into your [iLiveMyLife](https://ilivemylife.io) knowledge graph:
@@ -94,7 +88,7 @@ ilml plugin config linkedin reset                      # wipe all; will re-promp
 | Data storage | `DATA_DIR` | no | Absolute path to a directory for the local DB / cookies. **Recommended** — keeps data outside the plugin install folder so it survives plugin updates. |
 | Apply bot | `City` | no | Default city for filters. Default: `Toronto`. |
 | | `MAX_APPLY_FOR_RUN` | no | Stop after this many applications per run. Default: `50`. |
-| | `LINKEDIN_SEARCH_URL` | no | Default LinkedIn jobs search URL with your filters (use `f_AL=true` for Easy Apply). |
+| | `LINKEDIN_SEARCH_URL` | no | Default LinkedIn jobs search URL — open LinkedIn → Jobs, set your filters, then make sure **Easy Apply** is on. Copy the resulting URL from the address bar and paste it here. |
 | Scouting | `LINKEDIN_SCOUT_URLS` | no | Comma-separated job search URLs to scan without applying. |
 | Resume / CV | `CV_TEXT`, `RESUME_PDF_URL`, `RESUME_FILENAME` | no | CV snippet, public PDF URL, suggested filename. Used in messages to recruiters. |
 | Funnel | `FUNNEL_USE_CUSTOM_MESSAGE` | no | Send a custom note with connection requests. Default: `false`. |
@@ -198,105 +192,28 @@ ilml plugin config linkedin reset
 
 To clean up the data directory (cookies, DBs), delete the folder you set as `DATA_DIR` manually.
 
----
-
-# Developer Notes
-
-> Single-developer project. The reference for plugin architecture and SDK contracts is the iLiveMyLife graph-sdk repo's [`PLUGINS.md`](https://github.com/iLiveMyLife/graph-sdk.iLiveMyLife.io/blob/main/PLUGINS.md). Most of what follows is just reminders for me when I come back to this in a few months.
-
-## Layout
-
-```
-ilml-plugin.json     # manifest: name, version, commands, config.sections[].fields[]
-package.json         # npm metadata; "files": ["dist", "ilml-plugin.json"] is the publish whitelist
-.npmignore           # belt-and-suspenders excludes (.env, cookies.json, sources, etc.)
-.env / .env.example  # dev only; gitignored
-
-run.mjs / syncAll.mjs / messageBot.mjs / scout.mjs / ...  # entry points (one per ilml subcommand)
-src/
-  config.mjs         # reads via SDK getPluginConfig(); merges into process.env so the rest of the codebase keeps using process.env.X
-  graphClient.mjs    # SDK client wrapper
-  database.mjs       # local JSON DB at DATA_DIR
-  saveLoginState.mjs # entry: ilml linkedin login
-  ... domain modules ...
-scripts/
-  build-plugin.mjs   # esbuild bundler — outputs dist/*.mjs (minified, no sourcemaps)
-                     # externalizes: puppeteer, dotenv, @ilivemylife/graph-sdk
-```
-
-## Configuration model
-
-- The plugin reads its config **only** through `getPluginConfig()` from `@ilivemylife/graph-sdk` (called once in `src/config.mjs`).
-- Resolved values are merged into `process.env` so existing files reading `process.env.LINKEDIN_NAME` etc. keep working unchanged. New code should read directly from the SDK return value when feasible.
-- Auth token: `process.env.ILML_TOKEN` — injected by ilml CLI in production; resolved by the SDK in dev (local config / `.env` / global config / env var).
-- Active scope dir: `process.env.ILML_SCOPE_DIR` — set in production only. Plugin code never reads it directly; the SDK does.
+## Feedback & support
 
-## Two run modes
+Bug reports, feature requests, and general questions land in the plugin's **Support** node inside iLiveMyLife. Send a message there and we'll get back to you:
 
-| Mode | How invoked | Where config comes from |
-|---|---|---|
-| **Production** | `ilml linkedin <command>` | The active ilml scope's `<scope>/.ilivemylife/plugins-state/linkedin.json` |
-| **Dev** | `node run.mjs` (etc.) | `.env` next to `ilml-plugin.json` (auto-detected by SDK) |
+- In any iLiveMyLife app (web / mobile / desktop): open https://app.ilivemylife.io/item/0000019dde81b04f-2e534bb8ebad0000 and use the messenger panel
+- From the terminal: `ilml send 0000019dde81b04f-2e534bb8ebad0000 "your message"`
 
-The plugin code is identical between the two. `ILML_SCOPE_DIR`'s presence is the only signal.
-
-## Local dev iteration
-
-When the plugin code itself is what's changing:
-
-```bash
-# 1. (optional) edit ilml-plugin.json or src/*
-# 2. Build
-npm run build:plugin
+## Links
 
-# 3a. Quick check via direct run (uses .env)
-node run.mjs
-
-# 3b. Full check via ilml CLI — needs the plugin re-packed and re-installed
-npm pack
-ilml plugin install linkedin file:///$(pwd)/ilml-plugin-linkedin-X.Y.Z.tgz
-ilml linkedin <command>
-```
-
-When the **SDK** is what's changing alongside, also rebuild and re-install the SDK from the sibling `graph-sdk.iLiveMyLife.io` repo:
-
-```bash
-# In ../graph-sdk.iLiveMyLife.io
-npm run build && npm pack
-
-# In this repo
-npm install ../graph-sdk.iLiveMyLife.io/ilivemylife-graph-sdk-X.Y.Z.tgz --no-save
-npm run build:plugin
-```
-
-## Release process
-
-1. **Update `CHANGELOG.md`** — add an entry at the top describing what changed for users.
-2. **Bump version in BOTH** `package.json#version` AND `ilml-plugin.json#version`. They must match — `ilml plugin update` compares the manifest version against npm's `dist-tags.latest`. Drift here causes false update loops or silent skips.
-3. **Commit with explicit paths only:**
-   ```bash
-   git commit -- package.json ilml-plugin.json CHANGELOG.md <other-changed-files> -m "v1.X.Y: short description"
-   ```
-4. **Push:** `git push`.
-5. **Publish:** `npm publish --access public`. The `prepublishOnly` script runs `build:plugin` automatically — `dist/` is rebuilt from current sources before packing.
-6. **Update the Releases node in the graph** — sync description with the new CHANGELOG entry.
-
-## Security checklist before each `npm publish`
+- This plugin on npm: https://www.npmjs.com/package/ilml-plugin-linkedin
+- `ilml` CLI on npm: https://www.npmjs.com/package/@ilivemylife/graph-sdk
+- iLiveMyLife: https://ilivemylife.io
 
-- `npm pack --dry-run` — verify only `dist/`, `ilml-plugin.json`, `package.json`, `README.md` end up in the tarball (~13 files). No `.env`, `cookies.json`, `*.json` data files, source `.mjs` at the repo root, `node_modules/`, internal handoff `.md`, `tmpclaude-*`, `.git/`.
-- `grep -E "ilya|sorokin|password|token|@gmail" dist/*.mjs dist/src/*.mjs` — no real personal data should appear in bundled output. (Examples in `README.md` like `ivan@example.com` are fine — they're documentation placeholders.)
-- `ls dist/*.map dist/**/*.map 2>/dev/null` — must return nothing (no sourcemaps).
-- `npm whoami` — confirm correct npm account before publish.
+---
 
-## Useful pointers
+## Author & contact
 
-- iLiveMyLife graph-sdk Plugin spec & 12 architecture rules: [`PLUGINS.md`](https://github.com/iLiveMyLife/graph-sdk.iLiveMyLife.io/blob/main/PLUGINS.md)
-- SDK source: https://github.com/iLiveMyLife/graph-sdk.iLiveMyLife.io
-- This plugin on npm: https://www.npmjs.com/package/ilml-plugin-linkedin
-- ilml CLI on npm: https://www.npmjs.com/package/@ilivemylife/graph-sdk
+**[Ilya Sorokin](https://www.digitaltwins.team/team/ilya-sorokin)** — creator of [iLiveMyLife.io](https://ilivemylife.io) and this plugin.
 
----
+- LinkedIn: [linkedin.com/in/ilyasorokin](https://www.linkedin.com/in/ilyasorokin/)
+- Email: info@ilivemylife.io
 
-## Author
+### Need a custom plugin or extension?
 
-Ilya Sorokin · [iLiveMyLife.io](https://ilivemylife.io) · info@ilivemylife.io
+[**DigitalTwins.team**](https://www.digitaltwins.team/) — my consulting company — designs and builds custom automation, SDK extensions, and bespoke plugins for the iLiveMyLife ecosystem (and beyond). If you want to integrate your own workflow with iLiveMyLife, extend this plugin's behavior, or commission something new, get in touch.

package/ilml-plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "linkedin",
-  "version": "1.2.1",
+  "version": "1.2.2",
   "description": "LinkedIn job automation: apply, scout, sync, funnel, messages",
   "commands": {
     "apply":       { "run": "node dist/run.mjs" },

package/package.json

@@ -1,11 +1,12 @@
 {
   "name": "ilml-plugin-linkedin",
-  "version": "1.2.1",
+  "version": "1.2.2",
   "description": "ilml plugin: LinkedIn job automation — apply, scout, sync, funnel, messages",
   "type": "module",
   "files": [
     "dist",
-    "ilml-plugin.json"
+    "ilml-plugin.json",
+    "CHANGELOG.md"
   ],
   "scripts": {
     "build:plugin": "node scripts/build-plugin.mjs",