Update to Date App Plugin

{
  "name": "task-and-ruleset-router",
  "description": "Route Date Chatbot requests into opener, reply, review, explanation, re-entry, CTA, or pause workflows; select effort, language, discovery goals, and conversational rules from Match, Wiki, timeline, event, and personal-profile context. Use before dating-message strategy or generation.",
  "included_files": [
    {
      "relative_path": "references/rulesets.md",
      "size_in_bytes": 5604
    }
  ],
  "skill_md_contents": "---\nname: task-and-ruleset-router\ndescription: Route Date Chatbot requests into opener, reply, review, explanation, re-entry, CTA, or pause workflows; select effort, language, discovery goals, and conversational rules from Match, Wiki, timeline, event, and personal-profile context. Use before dating-message strategy or generation.\n---\n\n# Task and Ruleset Router\n\nDecide what work should happen before any response is drafted. The router must\nconsume the grounded outputs of `interpret-match-context`,\n`interpret-property-map`, `read-conversation-timeline`, `event-state-engine`,\nand `personal-profile` when their data is relevant.\n\nRead [references/rulesets.md](references/rulesets.md) before routing an opener,\nlowering effort, selecting a checklist discovery goal, or pausing for context.\n\n## Preflight\n\nBefore choosing a task:\n\n1. Confirm one Match record and its relevant Wiki payload were interpreted.\n2. Read the complete latest conversational turn and all active topics.\n3. Resolve the current event state and retry budget.\n4. Inspect relevant details, checklist answers, Wiki meanings, positive or\n   negative assessments, blockers, and attractiveness.\n5. Load only relevant verified personal-profile facts and disclosure rules.\n6. Determine response language from root `match.language`: `en` means English;\n   `lt` means Lithuanian.\n7. Run the missing-context gate. If required context is absent, stop before\n   strategy or generation and ask the smallest question that unlocks the task.\n\nDo not skip preflight because the latest message appears easy.\n\n## Select the task\n\nChoose one primary task:\n\n- `generate_opener`: no real conversation exists and the user wants a first\n  message;\n- `generate_reply`: the latest complete turn belongs to the match;\n- `review_draft`: the user supplied a candidate message for evaluation;\n- `reentry`: the current event permits one bounded low-pressure restart;\n- `advance`: CTA is current and a next-step proposal is appropriate;\n- `explain`: the user asks for interpretation or strategy rather than copy;\n- `wait`: the user's message is latest and no follow-up is currently justified;\n- `pause_for_context`: generation requires missing or ambiguous information;\n- `close`: a blocker, boundary, explicit rejection, or user instruction ends\n  the interaction.\n\nThe user's explicit current request controls when compatible with facts,\nconsent, event limits, and disclosure rules.\n\n## Opener rules\n\nFor `generate_opener`, prefer something unexpected and compact that tests for a\ncompatible sense of humor. The opener may:\n\n- ask an intriguing, slightly unconventional question;\n- make a playful observation from a distinctive Match detail or profile prompt;\n- use a line such as “I know your name. What's your social ID?” as an absurdist\n  joke about a social handle—not a demand for legal identity or private data;\n- use one restrained ASCII-art or Unicode-styled greeting when visual novelty is\n  the whole hook.\n\nDo not default to cheesy fantasy hypotheticals, impossible “what if” scenarios,\ngeneric interview questions, generic compliments, or copied pickup lines.\nExamples to avoid include “What superpower would you choose?”, “How was your\nday?”, and “What do you do for fun?” unless the existing context makes that exact\nquestion specific and meaningful.\n\nUnicode styling or ASCII art is optional, not a requirement. Keep it readable,\nshort, and copyable. Do not fake platform-native bold or italic formatting when\nthe platform may not support it.\n\nNever generate an invitation for coffee, a date, or going out. The user does not\nwant the agent to initiate an in-person meeting. CTA may route toward a\nlow-pressure Instagram or Facebook exchange under the event-state rules.\n\n## Effort selection\n\nChoose:\n\n- `minimal`: low user priority, low attractiveness, several explicit negative\n  non-blocking assessments, a weak/closed thread, or a simple factual response;\n- `normal`: ordinary viable interaction with adequate context;\n- `high`: high user priority, strong relevant positives, several active topics,\n  hidden callbacks, CTA, sensitive ambiguity, or a strategically important\n  turn;\n- `pause`: a blocker, prohibited action, or missing context makes generation\n  inappropriate.\n\nAttractiveness and Wiki assessments represent the user's private prioritization,\nnot the match's human worth. Lower effort means less analysis, fewer callbacks,\nand less personalization—not a rude, careless, deceptive, or incoherent reply.\nA blocker may route to `close` or `pause`; it must not be silently averaged away\nby attractiveness.\n\n## Checklist and personality discovery\n\nMaintain awareness of unresolved `check_list` items. When an unanswered item is\nrelevant and the conversation offers a natural opening, choose at most one as a\nsecondary discovery goal. It may be asked directly or approached indirectly,\nbut never through deception, pressure, or a hidden psychological test.\n\nDo not force checklist questions into every message. Answering the current turn\nand keeping the conversation organic take precedence. Never expose that an\nanswer was privately scored as good, bad, or blocking.\n\nIf the match asks why a topic matters, do not lie. Give a neutral truthful answer,\ndefer the private evaluation, or say the user is curious how she sees it. Never\ninvent agreement or claim a neutral opinion the user does not hold.\n\nBuild an early social/personality portrait only from direct messages, explicit\ndetails, checklist answers, and clearly labeled Wiki interpretation. Keep traits\ntentative and evidence-linked. Do not diagnose, stereotype, or infer character\nfrom MBTI, autism, profile aesthetics, response latency, or a single answer.\n\n## Factual-grounding invariant\n\nNever generate wording that asserts or implies an unsupported fact about the\nuser. Audit implications, not only literal statements.\n\nFor example, a photo with a Glock imitation/air pistol does not support “I go to\nthe shooting range,” “I own a gun,” or a shared shooting hobby. The only usable\nfacts are those explicitly present in the personal profile, Match conversation,\nor current user instruction and permitted by disclosure rules.\n\nIf an appealing response depends on an unknown personal fact, route to\n`pause_for_context` or choose a response that does not depend on it.\n\n## Missing-context gate\n\nPause and ask when generation materially depends on:\n\n- a referenced image, voice note, profile item, or earlier conversation that was\n  not supplied;\n- ambiguous sender, event owner, reply target, or conversation link;\n- a factual claim about the user absent from the personal profile;\n- unclear language or intended task;\n- missing consent/boundary context for re-entry or CTA;\n- a contradiction that changes what may safely or honestly be said.\n\nAsk one precise question or a small tightly related set. Do not pause for merely\noptional color when a grounded organic response is already possible.\n\n## Router output\n\nReturn a routing brief before generation:\n\n- `task`;\n- `language`;\n- `effort` and evidence-based rationale;\n- active event state and retry eligibility;\n- primary conversational obligation;\n- active secondary topics that cannot be ignored;\n- optional checklist discovery goal;\n- tentative personality/social hypotheses relevant now;\n- relevant profile facts permitted for use;\n- blockers, boundaries, and forbidden moves;\n- missing context and the exact question to ask, if paused;\n- ruleset name from the reference.\n\nDo not draft response candidates in this skill.\n"
}