@super-hands/connect 0.1.16 → 0.1.17

package/client.mjs

@@ -41,7 +41,7 @@ function codexConfigBlock(args) {
 }
 
 // lib/connect-skill.ts
-var CONNECT_SKILL_VERSION = 11;
+var CONNECT_SKILL_VERSION = 12;
 var CONNECT_SKILL_DIR = MCP_SERVER_KEY;
 var CONNECT_SKILL_FILENAME = "SKILL.md";
 var VERSION_MARKER = `[//]: # (superhands-skill-version: ${CONNECT_SKILL_VERSION})`;
@@ -75,9 +75,6 @@ Before you build, change, or restyle any UI:
      example \`["app/marketing/pricing.tsx"]\`. The team writes down where
      Instructions apply, and a path answers that far better than a description
      does. Leave it out if you do not know yet; it narrows nothing away.
-   - If that tool is not available on this server, it is an older deployment:
-     call \`superhands_get_guidance\` and \`superhands_get_skill\` instead,
-     with the same \`intent\` \u2014 those two are older and take no \`paths\`.
 2. Plan against what comes back, and note which parts of your plan each set of
    keys covers. The first answer renders what to read first, then names
    under **Reachable** the modules judged to matter to parts you have not
@@ -87,7 +84,7 @@ Before you build, change, or restyle any UI:
    the team has written down; say so rather than quietly using your own
    defaults.
 3. As you start each part \u2014 the sidebar, then the table, then the form \u2014 call
-   \`superhands_get_playbook_modules\` with the reachable keys covering the
+   \`superhands_get_instruction_modules\` with the reachable keys covering the
    part you are starting now and \`part\` set to that part in a few words,
    for example \`"the form's validation errors"\`. A key ending in \`*\` takes
    everything under it, so \`better-ui/*\` is a whole skill and
@@ -101,27 +98,32 @@ Before you build, change, or restyle any UI:
      the start. These are instructions to follow, not facts to know, so modules
      for a part you are not building are a page of directions about the wrong
      thing sitting in your context while you work.
-   - Team-authored decision entries from step 1 need no such loop. They are
+   - Review-enforced decision entries from step 1 need no such loop. They are
      concise enough to stay in the opening brief, so one read at the start is
      the right read.
-   - If that tool is not available on this server, it is an older deployment:
+   - If that tool is not available on this server,
      build from what step 1 already returned and skip this step. Do not ask
      for the whole library instead \u2014 that is the wall of text step 1 avoided.
 4. Build to what comes back. Use the selected Instructions together. When two
    entries pull in different directions, prefer the more specific instruction,
    preserve explicit exceptions, and call out any conflict you cannot honestly
    resolve.
-5. When you have finished \u2014 not part-way through \u2014 send the files you wrote or
+5. As your work reaches files your opening intent never mentioned, call
+   \`superhands_possible_misses\` with the \`paths\` you are actually in. It is
+   a free, instant, advisory list of checks those files usually need \u2014 not a
+   review, not a gate \u2014 so call it as the work moves and once before your
+   summary, passing \`handled\` for anything you already covered.
+6. When you have finished \u2014 not part-way through \u2014 send the files you wrote or
    changed with \`superhands_report_completed_build\`, naming the \`route\` if
    you know it. The team looks at what their agents build there; it records
    and does not review, so a failed report costs the work nothing.
-6. When you finish, say you followed the team's Instructions \u2014 never that your
+7. When you finish, say you followed the team's Instructions \u2014 never that your
    work was checked. Reading Instructions is not a check, reporting a build is
    not a review, and nothing has looked at what you built.
 
-If the tool answers \`no-instructions\` (or \`no-guidance\` from an older
-server), carry on with what you were asked for and mention that the team
-adds its Instructions on the Superhands Instructions page.
+If the tool answers \`no-instructions\`, carry on with what you were asked for
+and mention that the team adds its Instructions on the Superhands Instructions
+page.
 
 If the \`${MCP_SERVER_KEY}\` MCP server is not reachable in this session, say
 so rather than guessing at the team's decisions \u2014 it is configured on this

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@super-hands/connect",
-  "version": "0.1.16",
+  "version": "0.1.17",
   "description": "Connect the coding agents on this machine to your team's Superhands MCP server, refresh it later with `update` (no token needed), and take it back off again with `uninstall`. Writes each client's own config; reads no repository, uploads nothing.",
   "bin": {
     "superhands-connect": "client.mjs"