Update docs: domain-based auth lookup, no connection IDs needed

Connection IDs are no longer stored in settings.json. The applier
finds auth connections by domain (linkedin.com, wellfound.com) at
runtime via the Kernel SDK. Updated SKILL.md, README.md, and bumped
to 0.1.4.

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

README.md

@@ -53,12 +53,12 @@ kernel proxies create --type residential --country US --name "claw-apply-proxy"
 kernel auth connections create --profile-name "LinkedIn-YourName" --domain linkedin.com
 kernel auth connections create --profile-name "WellFound-YourName" --domain wellfound.com
 
-# Complete initial login flows
+# Complete initial login flows (use: kernel auth connections list  to find IDs)
 kernel auth connections login <linkedin-connection-id>
 kernel auth connections login <wellfound-connection-id>
 ```
 
-Add the profile names, connection IDs, and proxy ID to `config/settings.json`.
+Add the profile names and proxy ID to `config/settings.json`. Connection IDs are not needed — the applier finds them automatically by domain.
 
 ### 3. Set up Telegram notifications
 

SKILL.md

@@ -37,16 +37,16 @@ kernel proxies create --type residential --country US --name "claw-apply-proxy"
 
 # Create managed auth connections (one per platform)
 kernel auth connections create --profile-name "LinkedIn-YourName" --domain linkedin.com
-# Note the connection ID from output
-
 kernel auth connections create --profile-name "WellFound-YourName" --domain wellfound.com
-# Note the connection ID from output
 
-# Trigger initial login flows (opens a browser URL to complete auth)
+# Complete initial login flows (opens a hosted URL to log in)
+# Use: kernel auth connections list   to find the connection IDs
 kernel auth connections login <linkedin-connection-id>
 kernel auth connections login <wellfound-connection-id>
 ```
 
+> **Note:** You only need connection IDs for the initial login. After that, the applier finds connections automatically by domain (`linkedin.com`, `wellfound.com`) — no IDs to store or keep in sync. Kernel's managed auth handles session refresh and re-authentication with stored credentials.
+
 ### 3. Configure
 
 ```bash
@@ -61,8 +61,6 @@ cp config/search_config.example.json config/search_config.json
 - `kernel.proxy_id` — proxy ID from step 2
 - `kernel.profiles.linkedin` — profile name e.g. `LinkedIn-YourName`
 - `kernel.profiles.wellfound` — profile name e.g. `WellFound-YourName`
-- `kernel.connection_ids.linkedin` — connection ID from step 2
-- `kernel.connection_ids.wellfound` — connection ID from step 2
 
 **`profile.json`** — your name, email, phone, resume path, work authorization, salary targets
 

claw.json

@@ -1,6 +1,6 @@
 {
   "name": "claw-apply",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "Automated job search and application for LinkedIn and Wellfound. Searches for matching roles, applies automatically using stealth browsers, and learns from every unknown question.",
   "author": "MattJackson",
   "license": "AGPL-3.0-or-later",

package.json

@@ -1,6 +1,6 @@
 {
   "name": "claw-apply",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "Automated job search and application for LinkedIn and Wellfound",
   "type": "module",
   "scripts": {