@kilogent/runner 0.1.5 → 0.1.7

package/dist/cli.js

@@ -200,6 +200,22 @@ function effectiveAgentTools(agent) {
   };
 }
 
+// ../shared/dist/agentProposal.js
+var DRAFT_FIELDS = {
+  name: true,
+  emoji: true,
+  persona: true,
+  engine: true,
+  model: true,
+  credentialId: true,
+  contract: true,
+  tools: true,
+  autonomy: true,
+  riskyActions: true,
+  playbooks: true
+};
+var PROPOSAL_DRAFT_FIELDS = Object.keys(DRAFT_FIELDS);
+
 // ../shared/dist/assistant.js
 var ASSISTANT_ACTOR_ID = "assistant";
 var ASSISTANT_NAME = "Workspace assistant";
@@ -272,7 +288,18 @@ var CONFIG_DOCS = {
    * installs, and keeping them out of a package the app also reads keeps a surface a captain can
    * edit from ever naming a version.
    */
-  engines: "engines"
+  engines: "engines",
+  /**
+   * `crewConfig/launch` — whether the product is open, and what the front gate says while it is
+   * not. Defaults live in `@lumi/crew-shared/launch.ts`.
+   *
+   * THE ONLY `crewConfig` DOCUMENT A SIGNED-OUT BROWSER MAY READ, and the rule is written for
+   * this id alone (packages/crew/firestore.rules). The login page has to say the right thing
+   * BEFORE the Google button is pressed and there is no session at that point — so `assistant`,
+   * which holds the shipped prompt, and `engines`, which holds the fleet's versions, stay closed
+   * beside it rather than a collection-wide read being opened for one boolean.
+   */
+  launch: "launch"
 };
 var DEFAULT_ASSISTANT_MODEL = "gemini-3.1-flash-lite";
 var DEFAULT_DAILY_CAP_USD = 0.1;
@@ -341,24 +368,46 @@ var DEFAULT_FREE_CONTRACT = `# Finish in one reply
 You get a small budget per message and only a person's message starts you. Your own reply does not
 wake you again, so finish your thought rather than promising to continue.
 
-# When somebody describes their business
-This is the most useful conversation you will have with a new workspace. Give them a real answer,
-not a questionnaire.
+# When somebody describes their business, or asks who to hire
+"Who should I hire", "what crew should I start with", "who would help here" and anyone describing
+what their company does are all the SAME REQUEST, and it is the most useful conversation you will
+have with a new workspace.
 
-Propose a crew: three to five agents, each with a name, one line on what it would own, and how work
+THEY ARE ASKING ABOUT AI AGENTS ON THIS WORKSPACE, NOT ABOUT PEOPLE. Never answer with advice on
+writing a job advert, hiring a contractor or finding a person, and never suggest putting a role on
+the board as a task. An agent here is a thing they can switch on this afternoon.
+
+Sketch the crew: three to five agents, each with a name, one line on what it would own, and how work
 passes between them. Use their words for their work, not ours. Be concrete enough that they can
 disagree with it.
 
-DO NOT CREATE THE AGENTS. Designing one properly is careful work and you are the light-weight half
-of this product; say what you would build and let the workspace's own crew-builder do it once it is
-set up. Never claim you have created something you have not.
+YOU CANNOT CREATE AN AGENT HERE, AND YOU CANNOT OFFER TO. There is no tool on this path that makes
+one, so both of these are false and the second is worse:
+
+  reporting  \u2014 "I have created", "I have added", "I have set up", "these are now on your workspace"
+  offering   \u2014 "I can set them up now", "shall I create them", "say the word and I will", "which one
+               would you like me to start with"
+
+The first sends somebody to the Agents page to look for crew that is not there. The second gets a
+"yes please" you cannot act on, which is the same lie with a delay on it.
+
+NEVER SAY A SEAT, A PLAN OR A BILL HAS CHANGED OR WILL CHANGE. "This adds three paid seats" is a
+statement about something happening; nothing in this conversation touches billing at all. If seats
+are worth mentioning, they are what a crew WOULD cost once somebody adds it.
 
-Write the proposal into the library with knowledge_write so it survives \u2014 this conversation scrolls
-out of view, and whoever builds the crew later needs to read it back. Say that you saved it, and
-name the slug.
+Speak conditionally throughout \u2014 "I would start with", "this one would own", "you could add".
 
-Then say plainly what is still missing before any of it can run, and stop. One clear sentence beats
-a sales pitch, and the person is already looking at the buttons.
+THEN END BY SAYING WHO DOES BUILD IT, and end there. Once this workspace has a machine online the
+assistant runs on it instead \u2014 on their own AI credential, with time to read the repositories and
+the board first \u2014 and puts each agent in front of them as a card they add with one press or open and
+change. That is where a crew actually gets built, and it is why the sketch above is a sketch:
+designing a persona, a contract with real boundaries, a tool whitelist and an autonomy level is
+careful work, and you are the light-weight half of this product.
+
+THE CARDS APPEAR IN THIS CONVERSATION, NOT ON ANOTHER PAGE. Never send somebody to the Agents page
+to find them \u2014 there is nothing waiting there, and a person who goes looking finds an empty roster
+and no way to tell what went wrong. The setup facts you were given above say which step is actually
+outstanding; name that one, and stop there. Do not ask which agent to start with.
 
 # What you can promise
 Nothing runs on this workspace until it has a subscription and a machine. Never imply otherwise,
@@ -372,11 +421,29 @@ Nothing you do in this session is visible to anybody until you call chat_send. T
 person hears from you. End the session with run_report so the next run knows what happened.
 
 # Building the crew
-You can create agents, and on this path you should. If the library holds a crew proposal, read it
-back and build what it describes rather than asking for the description again.
+THIS IS THE PATH WHERE CREW GETS DESIGNED, and you are the half of the product that can do it. Read
+what the workspace actually holds first \u2014 its repositories, its board, its knowledge library, what
+it has been asking for \u2014 and let that decide the crew rather than the paragraph you were given.
+
+When somebody asks who to hire, or describes what their company does: call chat_send with your
+answer, then call propose_agents with the messageId it returns. The cards land under that reply and
+a captain adds each one with a press, or opens it and changes anything first.
+
+A PERSONA AND A CONTRACT ARE NOT OPTIONAL, and the tool refuses a proposal without them. They are
+what make the thing an agent rather than a job title: the persona is the line the roster shows,
+written in its own first-person voice, and the contract is the markdown it reads before every run \u2014
+Mission, Responsibilities, Boundaries. There is no workspace default for either, so leaving one out
+is a hole rather than an inherited setting.
+
+EVERYTHING ELSE: SET ONLY WHAT YOU HAVE A REASON FOR. Tools, autonomy, model, credential and
+playbooks all have a workspace default, so a field you leave out is shown as "not proposed" and
+takes it \u2014 which is honest, while a whitelist or a model id you guessed at is a wrong answer wearing
+a confident face. What you DID go and read is worth setting, and that reading is the whole reason a
+proposal from here beats one from the included model.
+
+If the conversation already holds cards nobody answered, do not propose the same crew again.
 
-Say what each agent is for in one line, and say that every agent adds a paid seat to this
-workspace. Never create one nobody asked for.`;
+Say that each agent adds a paid seat, and never create one nobody asked for.`;
 function text(value, cap = MAX_ASSISTANT_CONTRACT_CHARS) {
   if (typeof value !== "string")
     return void 0;
@@ -558,6 +625,22 @@ var COLLECTIONS = {
    * `messages`, and the path is only ever composed from `chats` above it.
    */
   chatMessages: "messages",
+  /**
+   * `ships/{shipId}/chats/{chatId}/proposals/{proposalId}` — crew the assistant has proposed in
+   * this conversation, and what the captain decided about each (PRD §15.86).
+   *
+   * UNDER THE CHAT, not under the Ship, and that placement carries three things for free. Its
+   * visibility is the chat's: `chatVisible()` already answers "may this person read this thread",
+   * and a proposal is a paragraph of that thread. Its lifetime is the chat's: `deleteChatDeep`
+   * drains it with the messages, so a deleted conversation leaves no crew nobody remembers being
+   * offered. And the app's listener is chat-scoped, which is the only scope any reader wants.
+   *
+   * THE DECISION LIVES HERE RATHER THAN ON THE MESSAGE because `messages` is `allow update: if
+   * false` and must stay so — the whole thread's integrity rests on it. A proposal is the opposite
+   * kind of thing: it is written once by the assistant and then answered, days later, by a person.
+   * Those are two documents, not one.
+   */
+  chatProposals: "proposals",
   /** `ships/{shipId}/agents/{agentId}` — the crew: one doc = one configured agent. */
   agents: "agents",
   /** `ships/{shipId}/agents/{agentId}/workflows/{workflowId}` — that agent's playbooks. */
@@ -1277,14 +1360,14 @@ import os from "node:os";
 import path from "node:path";
 
 // src/version.ts
-var RUNNER_VERSION = true ? "0.1.5" : "0.0.0-dev";
+var RUNNER_VERSION = true ? "0.1.7" : "0.0.0-dev";
 var RUNNER_PACKAGE = true ? "@kilogent/runner" : "@kilogent/runner-dev";
 var RUNNER_BIN = true ? "kilogent-runner" : "kilogent-runner-dev";
 
 // src/config.ts
 var IS_DEV_BUILD = RUNNER_PACKAGE.endsWith("-dev");
 var DEFAULT_PROJECT_ID = IS_DEV_BUILD ? "lumi-afb7d" : "kilogent-crew-prod";
-var DEFAULT_MCP_URL = IS_DEV_BUILD ? "https://dev.app.kilogent.com/mcp" : "https://app.kilogent.com/mcp";
+var DEFAULT_MCP_URL = IS_DEV_BUILD ? "https://dev-app-kilogent.web.app/mcp" : "https://app.kilogent.com/mcp";
 var LEGACY_DIR_NAME = ".crew-runner";
 var DIR_NAME = `.${RUNNER_BIN}`;
 var LUMI_DIR_NAME = ".lumi-runner";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kilogent/runner",
-  "version": "0.1.5",
+  "version": "0.1.7",
   "type": "module",
   "description": "Lumi Crew runner daemon — claims jobs from your Ships and executes them as headless agent sessions (Claude Code today) on your own machine.",
   "//name": "The ONLY package in this monorepo published to the public registry, so it is the one that does not follow the internal @lumi/crew-* convention: `@lumi` is not a scope we own, `@lumi.ai` is (the npm org). The workspace DIRECTORY stays packages/crew/runner — renaming the package is not renaming the folder.",