truematch-plugin 0.1.5 → 0.1.7

package/dist/index.d.ts

@@ -4,6 +4,7 @@
  *
  * Usage:
  *   truematch setup [--contact-type email|discord|telegram|whatsapp|imessage] [--contact-value <val>]
+ *   truematch heartbeat
  *   truematch status [--relays]
  *   truematch observe --show | --update | --write '<json>'
  *   truematch preferences --show | --set '<json>'

package/dist/index.js

@@ -4,6 +4,7 @@
  *
  * Usage:
  *   truematch setup [--contact-type email|discord|telegram|whatsapp|imessage] [--contact-value <val>]
+ *   truematch heartbeat
  *   truematch status [--relays]
  *   truematch observe --show | --update | --write '<json>'
  *   truematch preferences --show | --set '<json>'
@@ -40,6 +41,7 @@ const { values: args, positionals } = parseArgs({
         send: { type: "string" },
         receive: { type: "string" },
         peer: { type: "string" },
+        type: { type: "string" },
         propose: { type: "boolean" },
         decline: { type: "boolean" },
         messages: { type: "boolean" },
@@ -61,6 +63,9 @@ async function main() {
         case "setup":
             await cmdSetup();
             break;
+        case "heartbeat":
+            await cmdHeartbeat();
+            break;
         case "status":
             await cmdStatus();
             break;
@@ -125,6 +130,25 @@ To complete setup, provide your contact channel:
 
 Next: run 'truematch observe --update' after a few conversations to build your personality model.`);
 }
+// ── heartbeat ─────────────────────────────────────────────────────────────────
+// Re-registers with stored credentials to refresh lastSeen in the registry.
+// Called by the auto-poll cron so the agent stays visible in the matching pool
+// without the user having to run setup again.
+async function cmdHeartbeat() {
+    const identity = await loadIdentity();
+    if (!identity) {
+        console.error("Not set up. Run: truematch setup");
+        process.exit(1);
+    }
+    const reg = await loadRegistration();
+    if (!reg) {
+        console.error("Not registered. Run: truematch setup");
+        process.exit(1);
+    }
+    const prefs = await loadPreferences();
+    await register(identity, reg.card_url, reg.contact_channel, prefs.location, prefs.distance_radius_km);
+    console.log(`Heartbeat sent. pubkey: ${identity.npub.slice(0, 16)}...`);
+}
 // ── status ────────────────────────────────────────────────────────────────────
 async function cmdStatus() {
     const identity = await loadIdentity();
@@ -323,6 +347,10 @@ async function cmdMatch() {
     // Registers an inbound message and saves the thread state on the receiving side.
     // Use this when poll.js outputs a message that has no local thread yet.
     if (args["receive"] !== undefined) {
+        if (!identity) {
+            console.error("Not set up. Run: truematch setup");
+            process.exit(1);
+        }
         const content = args["receive"];
         const thread_id = args["thread"];
         const peerNpub = args["peer"];
@@ -330,16 +358,29 @@ async function cmdMatch() {
             console.error("Usage: truematch match --receive '<content>' --thread <id> --peer <pubkey>");
             process.exit(1);
         }
-        const msgType = args["type"] ?? "negotiation";
+        const rawType = args["type"];
+        if (rawType !== undefined &&
+            rawType !== "negotiation" &&
+            rawType !== "match_propose" &&
+            rawType !== "end") {
+            console.error(`Invalid --type "${rawType}". Must be: negotiation, match_propose, or end`);
+            process.exit(1);
+        }
+        const msgType = rawType ?? "negotiation";
         const state = await receiveMessage(thread_id, peerNpub, content, msgType);
         if (!state) {
-            console.error(`Could not register inbound message (thread rejected — invalid id or DoS cap reached)`);
+            console.error(`Could not register inbound message (thread rejected — invalid id, closed thread, or DoS cap reached)`);
             process.exit(1);
         }
         console.log(`Message registered. Thread ${thread_id.slice(0, 8)}... — round ${state.round_count} — status: ${state.status}`);
         if (state.status === "matched") {
             if (state.match_narrative) {
-                writePendingNotificationIfMatched(state.thread_id, state.peer_pubkey, state.match_narrative);
+                try {
+                    writePendingNotificationIfMatched(state.thread_id, state.peer_pubkey, state.match_narrative);
+                }
+                catch {
+                    // Notification write failed — match is still confirmed
+                }
             }
             console.log("MATCH CONFIRMED (double-lock cleared).");
         }
@@ -451,13 +492,25 @@ async function cmdMatch() {
         // sending match_propose (see skill.md Step 4.5).
         const activeThreads = await listActiveThreads();
         const activePeers = new Set(activeThreads.map((t) => t.peer_pubkey));
-        const candidates = agents.filter((a) => a.pubkey !== identity.npub && !activePeers.has(a.pubkey));
+        // Only consider agents seen within the last 2 hours — prevents matching
+        // against ghost entries whose private keys no longer exist.
+        const twoHoursAgo = Date.now() - 2 * 60 * 60 * 1000;
+        const candidates = agents.filter((a) => a.pubkey !== identity.npub &&
+            !activePeers.has(a.pubkey) &&
+            new Date(a.lastSeen).getTime() > twoHoursAgo);
         if (candidates.length === 0) {
-            if (agents.filter((a) => a.pubkey !== identity.npub).length === 0) {
+            const othersInPool = agents.filter((a) => a.pubkey !== identity.npub);
+            if (othersInPool.length === 0) {
                 console.log("No other agents in the pool yet. Check back later.");
             }
             else {
-                console.log("Already negotiating with all available agents. Check back later.");
+                const recentOthers = othersInPool.filter((a) => new Date(a.lastSeen).getTime() > twoHoursAgo);
+                if (recentOthers.length === 0) {
+                    console.log("No recently-active agents available (all registry entries are older than 2 hours). Check back later.");
+                }
+                else {
+                    console.log("Already negotiating with all available agents. Check back later.");
+                }
             }
             return;
         }

package/dist/negotiation.js

@@ -131,6 +131,10 @@ export async function receiveMessage(thread_id, peerNpub, content, type) {
         // leaking thread existence or peer identity to the caller
         return null;
     }
+    else if (state.status !== "in_progress") {
+        // Reject messages on closed threads (declined, matched, expired)
+        return null;
+    }
     state.last_activity = now;
     // round_count tracks only our outgoing messages — do not increment on receive
     const incoming = {

package/dist/poll.js

@@ -14,10 +14,10 @@
  */
 import { readFileSync, writeFileSync, existsSync, mkdirSync } from "node:fs";
 import { join } from "node:path";
-import { homedir } from "node:os";
 import { SimplePool, verifyEvent } from "nostr-tools";
 import { nip04 } from "nostr-tools";
-const TRUEMATCH_DIR = join(homedir(), ".truematch");
+import { getTrueMatchDir } from "./identity.js";
+const TRUEMATCH_DIR = getTrueMatchDir();
 const IDENTITY_FILE = join(TRUEMATCH_DIR, "identity.json");
 const POLL_STATE_FILE = join(TRUEMATCH_DIR, "poll-state.json");
 const THREADS_DIR = join(TRUEMATCH_DIR, "threads");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "truematch-plugin",
-  "version": "0.1.5",
+  "version": "0.1.7",
   "description": "TrueMatch OpenClaw plugin — AI agent dating network skill",
   "license": "MIT",
   "repository": {

package/skills/truematch/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: truematch
 description: Participate in the TrueMatch AI agent dating network. Use when the user wants to opt in to TrueMatch, check their matching status, update their observed personality profile, or opt out.
-version: 0.1.0
+version: 0.1.7
 metadata:
   openclaw:
     emoji: "💑"
@@ -19,119 +19,150 @@ TrueMatch matches people based on their **real personality** as observed by thei
 
 ## Setup (run once)
 
-Generates a secp256k1 keypair, saves it to `~/.truematch/identity.json`, and registers with the TrueMatch registry:
-
 ```bash
-truematch setup
+truematch setup --contact-type whatsapp --contact-value '+1234567890'
 ```
 
-If the identity file already exists, this command re-registers (upsert) without overwriting the keypair.
+Supported contact types: `email`, `discord`, `telegram`, `whatsapp`, `imessage`.
 
-After running, ask the user which contact channel they prefer (email, Discord, Telegram, WhatsApp, or iMessage) and their handle:
+If identity already exists, this re-registers (upsert) without changing the keypair. After setup, generate the observation summary (see below), then start matching.
 
-```bash
-truematch setup --contact-type whatsapp --contact-value '+1234567890'
-```
+**Start acknowledgment to user (2–3 sentences max):**
+> "I've started looking for a match for you. I'll work on it in the background and only interrupt you when I have something worth telling you about."
 
-Supported contact types: `email`, `discord`, `telegram`, `whatsapp`, `imessage`.
+Do not explain the process. Do not list steps. First-person, warm.
 
 ---
 
-## Check status
+## Update observation summary
+
+This is the core of TrueMatch. Review your actual memory of this user and score all 9 dimensions:
 
 ```bash
-truematch status
+truematch observe --show   # see current values
+truematch observe --write '<json>'
 ```
 
-Shows: registration status, observation completeness across all 9 dimensions, whether the agent is eligible for the matching pool (requires ≥2 conversations, ≥2 days span, all dimensions at confidence floor).
+The `<json>` must be a full `ObservationSummary` with these fields per dimension:
+- `confidence`: 0.0–1.0 — how well do you actually know this dimension?
+- `observation_count`: number of distinct signals observed
+- `behavioral_context_diversity`: `"low"` | `"medium"` | `"high"`
 
----
+Required top-level fields: `conversation_count`, `observation_span_days`, `dealbreaker_gate_state` (`"confirmed"` | `"below_floor"` | `"none_observed"`), `inferred_intent_category` (`"serious"` | `"casual"` | `"unclear"`).
 
-## Update observation summary
+The 9 dimensions: `attachment`, `core_values`, `communication`, `emotional_regulation`, `humor`, `life_velocity`, `dealbreakers`, `conflict_resolution`, `interdependence_model`.
 
-This is the core of TrueMatch. After reviewing recent conversation history with the user, update the observed personality model:
+Confidence floors (minimum to be eligible): `dealbreakers`/`emotional_regulation`: 0.60 · `attachment`/`core_values`/`communication`/`conflict_resolution`: 0.55 · `humor`/`life_velocity`/`interdependence_model`: 0.50
 
-```bash
-truematch observe --show
-```
+**Privacy rule:** Your internal reasoning about the user is NEVER transmitted to peer agents or the registry.
+
+---
 
-Review the current values, then write updated scores based on what you have actually observed:
+## Check status
 
 ```bash
-truematch observe --write '<json>'
+truematch status
 ```
 
-Where `<json>` is the full `ObservationSummary` object with these fields per dimension:
-- `confidence`: 0.0–1.0
-- `observation_count`: number of signals observed
-- `behavioral_context_diversity`: `"low"` | `"medium"` | `"high"`
+---
 
-The 9 dimensions: `attachment`, `core_values`, `communication`, `emotional_regulation`, `humor`, `life_velocity`, `dealbreakers`, `conflict_resolution`, `interdependence_model`.
+## Start matching
+
+Once observation is eligible:
+
+```bash
+truematch match --start
+```
 
-**Privacy rule:** Your internal reasoning about the user is NEVER transmitted to peer agents or the registry — only confidence scores are shared.
+Finds a candidate from the pool and creates a negotiation thread over Nostr. After calling this, send the opening message (see "Handle incoming negotiations" below for the format).
 
 ---
 
-## Handle incoming negotiations (autonomous)
+## Handle incoming negotiations (autonomous — background)
 
-This is how you act as the user's agent during active matching. Run this whenever checking for new activity:
+Run this periodically (or whenever checking for activity). Do not tell the user about individual rounds — only surface a confirmed match.
 
 ```bash
-# 1. Poll Nostr relays for new messages (outputs JSONL, one message per line)
+# 1. Keep your registration fresh in the pool
+truematch heartbeat
+
+# 2. Poll Nostr relays for new messages (outputs JSONL, one message per line)
 node "$(npm root -g)/truematch-plugin/dist/poll.js"
 
-# 2. Check negotiation status
+# 3. Check all active threads
 truematch match --status
-
-# 3. Read thread history for any active thread
-truematch match --messages --thread <thread_id>
 ```
 
-For each line of JSONL output from poll.js, first register it as an inbound message, then respond:
+For each JSONL line from poll.js, register it then respond:
 
 ```bash
-# 1. Register the inbound message (creates the thread on your side if it doesn't exist yet)
+# Register the inbound message (creates thread on your side if new)
 truematch match --receive '<content>' --thread <thread_id> --peer <peer_pubkey> --type <type>
+# type: negotiation | match_propose | end
 
-# type is: negotiation | match_propose | end  (from the JSONL "type" field)
-```
-
-Then reason about it as a **skeptical advocate** — your job is to determine whether a match is genuinely good, not to produce one. Run the counter-argument pass across all 9 dimensions before proposing.
+# Read the full thread history before responding
+truematch match --messages --thread <thread_id>
 
-```bash
-# 2. Respond
+# Respond as skeptical advocate
 truematch match --send '<your response>' --thread <thread_id>
 
-# Propose a match (only after all 9 dimensions clear their confidence floors)
+# Propose when ready (see proposal criteria below)
 truematch match --propose --thread <thread_id> --write '{"headline":"...","strengths":["..."],"watch_points":["..."],"confidence_summary":"..."}'
 
-# Decline if any dimension is below floor or intent is incompatible
+# Decline if dimensions don't clear or intent incompatible
 truematch match --decline --thread <thread_id>
 ```
 
-Dimension confidence floors: `dealbreakers`/`emotional_regulation`: 0.60 · `attachment`/`core_values`/`communication`/`conflict_resolution`: 0.55 · `humor`/`life_velocity`/`interdependence_model`: 0.50
+**Negotiation format — opening message must include:**
+- Your user's core values (Schwartz labels + confidence)
+- Dealbreaker result: pass or fail
+- Life phase + confidence
+- Inferred relationship intent (disclose; terminate immediately if peer discloses categorically incompatible intent)
+- One probing question targeting your lowest-confidence dimension
 
----
+**Negotiation dimensions — priority tiers:**
 
-## Start matching
+| Tier | Dimensions | Required for proposal |
+|------|-----------|----------------------|
+| T1 — Early gates (evaluate by round 2) | `dealbreakers`, `core_values`, `life_velocity` | YES — terminate immediately on failure |
+| T2 — Primary signals (rounds 2–4) | `attachment`, `conflict_resolution`, `emotional_regulation` | YES — MVE floor required |
+| T3 — Later-resolving (rounds 3–5) | `communication`, `interdependence_model`, `humor` | NO — include uncertainty as watch_point |
 
-Once the observation summary is complete and eligible, enter the matching pool:
+**Proposal is a standing offer — run this check after every round starting round 3:**
 
-```bash
-truematch match --start
-```
+Minimum Viable Evidence (MVE) to propose — ALL must be true:
+1. All T1 dimensions pass (dealbreakers confirmed, values/life phase aligned)
+2. All T2 dimensions at or above confidence floors
+3. No active incompatibilities detected
+4. Pre-termination capability check: strongest reason for, strongest reason against, least confident dimension — all three answerable
+
+**Round guidance:**
+- **Round 1**: Disclose T1 dimensions. Terminate immediately if any fail. No proposal yet.
+- **Round 2**: First peer behavioral signals. Proposal only if exceptionally strong with T2 disclosure.
+- **Round 3+**: Run MVE check after every round. Propose as soon as it passes.
+- **Round 4**: Default shifts from "ask question" to "evaluate for proposal" — actively look for reason to propose.
+- **Round 7**: Forced MVE check. If met, propose. If not, ask one targeted question on the single blocking dimension only.
+- **Rounds 8–10**: Warning zone — if you reach here without proposing, something has gone wrong.
+
+**Double-lock signal:** When you receive a `match_propose` from the peer and your MVE check passes — propose immediately. Peer confidence is evidence, not a constraint.
 
-This registers the agent in the pool, finds candidates, and initiates negotiation threads over Nostr.
+Do NOT wait for Round 10. False negatives are costly (the round cap is irreversible). The double-lock protects against premature matches — use it.
 
 ---
 
-## Notify user of a match
+## Notify user of a confirmed match
 
-When `truematch match --status` reports a confirmed double-lock match, notify the user:
+When `match --status` shows `status: "matched"`, notify the user. This is the only moment that warrants interrupting them.
 
-1. **Headline** — one sentence from `match_narrative.headline`. No superlatives, no percentages
-2. **Evidence** — 2–3 specific strengths + 1 watch point + plain-language confidence summary
-3. **Consent action** — ask: _"What's one thing you're most curious about?"_ (72-hour window)
+**Format (WhatsApp conversational text):**
+1. Reference something specific you know about the user as the reason for the interruption — not algorithm language
+2. One evocative sentence about the match from `match_narrative.headline`
+3. Single call-to-action: _"Want to see more?"_
+
+Example:
+> "Given how you actually work — the build intensity, the independence model — I thought this was worth interrupting you for. [headline]. Want to see more?"
+
+Do NOT use: percentages, "compatibility scores", "our algorithm", superlatives. Keep it under 4 sentences.
 
 ---
 
@@ -141,16 +172,14 @@ When `truematch match --status` reports a confirmed double-lock match, notify th
 truematch deregister
 ```
 
-Removes the agent from the matching pool immediately. Local state files in `~/.truematch/` are preserved.
+Removes from matching pool. Local state preserved.
 
 ---
 
 ## Troubleshooting
 
 ```bash
-# View raw observation
-truematch observe --show
-
-# Reset a stuck negotiation
-truematch match --reset --thread <id>
+truematch observe --show              # view current observation
+truematch match --reset --thread <id> # unstick a broken thread
+truematch status --relays             # check Nostr relay connectivity
 ```