@popoverinstall/cli 0.8.1 → 0.9.1

package/plugin/scripts/roster.mjs

@@ -1,52 +1,52 @@
-#!/usr/bin/env node
-// Renders the /team menu.
-//
-// Invoked from the command's `!` injection, so its stdout becomes part of the prompt
-// Claude sees. Two consequences shape everything here:
-//   - always exit 0. A non-zero exit aborts the whole slash command.
-//   - always print something useful. If the daemon is down, say so in words the model
-//     can relay, rather than printing an empty section and letting it invent a reason.
-
-import { callerSessionId, request } from "./_ipc.mjs";
-
-// `fromSessionId` is what lets the daemon mark this agent's own line. It comes from the
-// session's environment, so a bare shell run of this script sends nothing and the roster
-// comes back unmarked.
-const reply = await request(
-  {
-    t: "roster",
-    id: "cli",
-    refresh: true,
-    ...(callerSessionId() ? { fromSessionId: callerSessionId() } : {}),
-    // Fallback for the window where the daemon has not yet resolved this session's repo —
-    // the same hint the MCP server sends. Without it an unplaceable caller falls through to
-    // pure recency across every session on the machine, so `/popover:team` run in one repo
-    // could print the roster for another, under a heading claiming it was this one.
-    cwd: process.cwd(),
-  },
-  { timeoutMs: 8000 },
-);
-
-if (!reply) {
-  console.log(
-    "The popover daemon is not running on this machine, so teammate agents are not visible.\n" +
-      "Start it with `popover daemon start`, or check `popover doctor`.",
-  );
-} else if (reply.t === "error") {
-  // The daemon distinguishes "no credentials" from "signed in but cannot connect", so
-  // relay its message rather than assuming the user has not logged in.
-  console.log(
-    reply.code === "not_authenticated"
-      ? reply.message
-      : `Could not load the team roster: ${reply.message}`,
-  );
-} else if (reply.t === "roster.ok") {
-  console.log(reply.rendered);
-  if (reply.stale) {
-    console.log("\n(Showing cached data — the backend was unreachable.)");
-  }
-} else {
-  console.log("The popover daemon returned an unexpected response.");
-}
-
-process.exit(0);
+#!/usr/bin/env node
+// Renders the /team menu.
+//
+// Invoked from the command's `!` injection, so its stdout becomes part of the prompt
+// Claude sees. Two consequences shape everything here:
+//   - always exit 0. A non-zero exit aborts the whole slash command.
+//   - always print something useful. If the daemon is down, say so in words the model
+//     can relay, rather than printing an empty section and letting it invent a reason.
+
+import { callerSessionId, request } from "./_ipc.mjs";
+
+// `fromSessionId` is what lets the daemon mark this agent's own line. It comes from the
+// session's environment, so a bare shell run of this script sends nothing and the roster
+// comes back unmarked.
+const reply = await request(
+  {
+    t: "roster",
+    id: "cli",
+    refresh: true,
+    ...(callerSessionId() ? { fromSessionId: callerSessionId() } : {}),
+    // Fallback for the window where the daemon has not yet resolved this session's repo —
+    // the same hint the MCP server sends. Without it an unplaceable caller falls through to
+    // pure recency across every session on the machine, so `/popover:team` run in one repo
+    // could print the roster for another, under a heading claiming it was this one.
+    cwd: process.cwd(),
+  },
+  { timeoutMs: 8000 },
+);
+
+if (!reply) {
+  console.log(
+    "The popover daemon is not running on this machine, so teammate agents are not visible.\n" +
+      "Start it with `popover daemon start`, or check `popover doctor`.",
+  );
+} else if (reply.t === "error") {
+  // The daemon distinguishes "no credentials" from "signed in but cannot connect", so
+  // relay its message rather than assuming the user has not logged in.
+  console.log(
+    reply.code === "not_authenticated"
+      ? reply.message
+      : `Could not load the team roster: ${reply.message}`,
+  );
+} else if (reply.t === "roster.ok") {
+  console.log(reply.rendered);
+  if (reply.stale) {
+    console.log("\n(Showing cached data — the backend was unreachable.)");
+  }
+} else {
+  console.log("The popover daemon returned an unexpected response.");
+}
+
+process.exit(0);

package/plugin/skills/popover/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: popover
-description: "Judgment for reaching a teammate's Claude Code agent *without being asked to* — when it is worth spending their tokens, and which of /popover:team, /popover:ask, /popover:tell and /popover:fork fits. Nothing to invoke by hand: use it when a question turns on what a colleague decided, ruled out, or is changing right now — why the code is the way it is when the repo does not say, whether work about to start is already in flight, or why something nobody touched is broken."
+description: "Judgment for reaching a teammate's Claude Code agent *without being asked to*, and for keeping this conversation where the team can ask it later — when it is worth spending their tokens, and which of /popover:team, /popover:ask, /popover:tell, /popover:fork and /popover:vault fits. Nothing to invoke by hand: use it when a question turns on what a colleague decided, ruled out, or is changing right now — why the code is the way it is when the repo does not say, whether work about to start is already in flight, or why something nobody touched is broken; or when this session has worked something out that the team will want and the repo will not record, which is the moment to vault it rather than let it be deleted."
 ---
 
 # popover
@@ -10,7 +10,7 @@ accumulated context you do not have: the alternatives they rejected, the constra
 forced an awkward shape, what they changed twenty minutes ago and have not pushed. popover
 lets you reach those agents.
 
-**This skill is not a command, and there is nothing here for a user to invoke.** The four
+**This skill is not a command, and there is nothing here for a user to invoke.** The five
 commands are the things a user types:
 
 | | |
@@ -19,6 +19,7 @@ commands are the things a user types:
 | `/popover:ask` | one question to one agent, and you wait for the answer |
 | `/popover:tell` | a heads-up into a teammate's live session; nothing comes back |
 | `/popover:fork` | hand this whole conversation to a teammate |
+| `/popover:vault` | publish this conversation to the team's archive, or ask one already there |
 
 This file is the judgment around them: when reaching for one is worth it, which one fits, and
 what each one spends. It exists because the moment to use popover rarely announces itself. The
@@ -26,13 +27,13 @@ user asks why something is the way it is, and the honest answer is that the repo
 record it — but a colleague's agent worked it out this morning. Nobody will type `/popover:ask`
 for you. Noticing is your job.
 
-## The three tools
+## The six tools
 
 They arrive as deferred MCP tools, so you have their names but not their schemas. Load them
 before use:
 
 ```
-ToolSearch("select:mcp__plugin_popover_popover__team_list,mcp__plugin_popover_popover__team_ask,mcp__plugin_popover_popover__team_tell")
+ToolSearch("select:mcp__plugin_popover_popover__team_list,mcp__plugin_popover_popover__team_ask,mcp__plugin_popover_popover__team_tell,mcp__plugin_popover_popover__vault_search,mcp__plugin_popover_popover__vault_ask,mcp__plugin_popover_popover__vault_create")
 ```
 
 Their own descriptions are detailed and authoritative on arguments and limits — read them
@@ -45,6 +46,17 @@ once loaded rather than guessing. In short:
   cannot be changed by it. Takes up to ~90s by default.
 - **`team_tell`** — a one- or two-sentence heads-up delivered into a teammate's live session
   before its next prompt. Nothing comes back, and their user is notified that you sent it.
+- **`vault_search`** — search the conversations your team has frozen and published. Free, no
+  model, nothing resumed. Not limited to this repo, and not limited to people who are working
+  right now. Always the first of the two.
+- **`vault_ask`** — one question to one vault, answered from its frozen context on *this*
+  machine at your user's expense. Roughly $0.50 and up to 90 seconds. Never call it on a
+  vault you have not seen in a search result.
+- **`vault_create`** — publish *this* conversation into the archive the other two read.
+  The only one of the six that writes something permanent: the whole conversation goes to
+  everyone on the team, it does not expire, and it cannot be edited afterwards. You may call
+  it on your own judgement — see *Vaults are a different thing again* below — but say plainly
+  that a vault is **readable by the popover service**, which a fork is not.
 
 ## When to reach for it on your own
 
@@ -144,6 +156,31 @@ include, and leave it there. If they pass, do not raise it again.
 When the user wants an *answer* rather than to hand over the whole conversation, an ask is the
 cheaper and more private thing. Offer that instead.
 
+## Vaults are a different thing again
+
+A vault is this conversation published to the **team**, permanently, and asked later by
+whoever needs it. Nobody has to be online for it, nobody has to still be at the company, and
+the person asking pays rather than the person who wrote it.
+
+**Unlike a fork, creating one is yours to decide.** Not to offer and wait on — to decide. The
+rule differs from the fork rule deliberately: a fork discloses one conversation to one named
+individual, while a vault goes to a team that already shares the repository and the work, so
+the disclosure is smaller and the cost of missing the moment is higher. The moment for a vault
+is one the user is usually too deep in the work to notice, and a conversation nobody vaults is
+deleted when the session ends.
+
+It is still a real disclosure, and two things must be said plainly when you make one:
+
+- **A vault is readable by the popover service.** A fork is end-to-end and this is not.
+  Anyone who has internalized the first will assume the second unless you say otherwise.
+- **It cannot be edited or withdrawn.** A correction is a *note* appended beside the original;
+  `popover vault archive` retires a vault without erasing the record that it was made.
+
+Vault a conversation that worked something out the team will want and the repo will not
+record — a decision and its reasons, an approach tried and rejected, an investigation into why
+something is the way it is. Do not vault routine work: an index full of everything is one
+nobody trusts, which fails in the same way as vaulting nothing.
+
 ## When it does not work
 
 The tools return errors as text; relay them rather than retrying with different arguments.
@@ -158,7 +195,7 @@ The tools return errors as text; relay them rather than retrying with different
 
 ## The user-facing commands
 
-The four commands carry the full flows for when the user drives this explicitly — how to
+The five commands carry the full flows for when the user drives this explicitly — how to
 present a roster, how to word an ask, how to take delivery of a fork. Do not restate their
 steps here or work around them: **when the user invokes a command, follow that command.** This
 skill is for the other case, where nobody invoked anything and you noticed the moment yourself.