@nanopm/cli 0.1.6 → 0.1.7

package/dist/index.js

@@ -105,7 +105,7 @@ var CAPABILITIES = [
    * `projects.website_url`, never a model's choice, and only that host and three fixed
    * paths are fetched. That is what lets a skill holding the founder's repository read
    * their landing page without an outbound socket sitting next to private code, which is
-   * the combination the taint rule exists to prevent (docs/nanopm-60-onboarding-end-to-end.md §6).
+   * the combination the taint rule exists to prevent (docs/✅nanopm-60-onboarding-end-to-end.md §6).
    *
    * Capped nowhere, and it does not taint: there is no tool here to misuse.
    */
@@ -139,7 +139,7 @@ var CAPABILITIES = [
   /** Maintain the market view: write_market, and list_market under `memory`. */
   "market",
   /**
-   * A conversation with Nano (docs/nanopm-68-talk-to-nano.md): read the opportunity map and the
+   * A conversation with Nano (docs/✅nanopm-68-talk-to-nano.md): read the opportunity map and the
    * board and change them as the founder asked — the tools in `TALK_TOOLS`. Nothing else: no
    * repository, no web, no data. Capped nowhere: every change is one the founder can make from a
    * sheet, and only what they asked for is done.
@@ -374,7 +374,7 @@ var SkillManifestSchema = z2.object({
   ),
   /**
    * The cap for a run with `params.depth: 'deep'`, when the skill has one: the deep needs map
-   * runs ten sessions and never fit the quick map's forty minutes (docs/nanopm-63-quick-first.md §4).
+   * runs ten sessions and never fit the quick map's forty minutes (docs/✅nanopm-63-quick-first.md §4).
    */
   timeout_deep: z2.string().refine(
     (t) => {
@@ -872,7 +872,7 @@ var CHAINED = {
   // and the crew runs when the founder asks for it from the business card.
   onboard: ["market"],
   // A problem list is what solutions hang under, so a fresh list is followed by fresh
-  // solutions. **The problem crew itself is retired** (docs/nanopm-59-opportunity-map.md,
+  // solutions. **The problem crew itself is retired** (docs/✅nanopm-59-opportunity-map.md,
   // Guillaume, 2026-09-25): the opportunity map replaced it, and nothing queues it any more —
   // not the market read, not a review, not a watch, not the founder leaving Voices. A map
   // someone still runs by hand keeps this edge, because every bet still hangs off a problem
@@ -880,7 +880,7 @@ var CHAINED = {
   problems: ["solutions"],
   // The pitch crew runs after the market read, which is the one automatic run that changes
   // what the pitch can say without anyone asking: an "unlike" clause needs competitors. It
-  // proposes beside a confirmed pitch and never over it (docs/nanopm-52-pitch-crew.md).
+  // proposes beside a confirmed pitch and never over it (docs/✅nanopm-52-pitch-crew.md).
   //
   // The direction crew **was** chained here too, for the same reason — a vision rests on who
   // else exists — then after `onboard`, and since 2026-10-01 after nothing: see the note on
@@ -891,7 +891,7 @@ var CHAINED = {
   // for both, and gets to say something different to each.
   //
   // **The persona crew follows a from-scratch start's market run, and no other**
-  // (docs/nanopm-54-personas-by-the-crew.md; docs/nanopm-63-quick-first.md §2). A start writes a
+  // (docs/✅nanopm-54-personas-by-the-crew.md; docs/✅nanopm-63-quick-first.md §2). A start writes a
   // sentence per person, and the crew draws the profile. It followed a scan's market run too
   // until 2026-09-28, to put a critic over the scan's one pass — and the redo, with the pitch
   // behind it, stood between the founder and the first opportunities while redrawing what the
@@ -900,7 +900,7 @@ var CHAINED = {
   // start: the daemon claims in queue order, and the pitch and the map read what it wrote.
   //
   // **The first opportunity map follows the onboarding's own market run, and no other**
-  // (docs/nanopm-59-opportunity-map.md §8). `ONLY_AFTER` below holds it there: a market run from
+  // (docs/✅nanopm-59-opportunity-map.md §8). `ONLY_AFTER` below holds it there: a market run from
   // the card or the terminal queues no map, so a founder's refresh of the landscape never
   // redraws it. It reads the card, the personas and their needs the onboarding wrote, and the
   // market just read; a needs map is one source among the others, never a constraint
@@ -914,7 +914,7 @@ var CHAINED = {
   // draw, on the founder's word; drawn there, it queues nothing and the page offers *Rank
   // again*. The deep map still follows a deep needs map queued after a start (`AFTER_DEEP`).
   market: ["personas", "pitch", "opportunities"],
-  // **Solutions follow the map, but not through this table** (docs/nanopm-64-solutions-from-
+  // **Solutions follow the map, but not through this table** (docs/✅nanopm-64-solutions-from-
   // opportunities.md §3): the store queues a Flash the moment a branch ranked high enough has
   // leaves with no solution — when the map is recorded, and when the founder moves, confirms or
   // sets one aside (`queue_solutions_due`). Only some maps call for one, and a map is not the only
@@ -964,7 +964,7 @@ var SKILL_SENTENCE = {
   problems: "working out the problems",
   market: "reading the market",
   // Kept: `research` is no longer chained or run from anywhere a founder can see, but the
-  // problem crew still calls it inline for its look outside (docs/nanopm-55-market-crew.md
+  // problem crew still calls it inline for its look outside (docs/✅nanopm-55-market-crew.md
   // §9), and a job of it in the journal should still read as a sentence.
   research: "reading the market",
   personas: "working out who it is for",
@@ -6892,7 +6892,7 @@ async function attempt4({ adapter, spec, onEvent, role: which, prompt, say }) {
     harnessWeb: which === "scout" ? spec.harnessWeb : false,
     // A role runs on its own model when its manifest names one: the scout on Sonnet, as spec 55
     // wanted and as it never did, because every role inherited the coordinator's — the user's
-    // default (docs/nanopm-57-needs-map.md §10).
+    // default (docs/✅nanopm-57-needs-map.md §10).
     model: skill.manifest.model ?? spec.model,
     outputSchema: schema,
     maxTurns: skill.manifest.maxTurns,
@@ -7601,7 +7601,7 @@ var OpportunitiesParams = z13.object({
   chain: z13.boolean().optional(),
   repo_path: z13.string().optional(),
   // The daemon's: a run chained as background work is claimed once no quick job is queued
-  // (docs/nanopm-63-quick-first.md). The deep map after the deep needs map carries it.
+  // (docs/✅nanopm-63-quick-first.md). The deep map after the deep needs map carries it.
   background: z13.boolean().optional()
 }).strict();
 function opportunitiesAsk(params) {
@@ -7793,7 +7793,7 @@ async function attempt6({ adapter, spec, onEvent, skill: skillName, name, schema
   await onEvent({ type: "text", text: say });
   for await (const event of adapter.run({
     ...spec,
-    // A role that may not read the code does not stand in it (docs/nanopm-71-deep-dive-lenses.md).
+    // A role that may not read the code does not stand in it (docs/✅nanopm-71-deep-dive-lenses.md).
     cwd: grant.includes("read_repo") ? spec.cwd : runDir,
     runDir,
     sessionId: randomUUID8(),
@@ -13234,7 +13234,7 @@ var MEMORY_TOOL_NAMES = [
   "list_market",
   "write_market",
   "remove_files",
-  // Talk to Nano (docs/nanopm-68-talk-to-nano.md): the map read, and changed as the founder asked.
+  // Talk to Nano (docs/✅nanopm-68-talk-to-nano.md): the map read, and changed as the founder asked.
   ...TALK_TOOLS
 ];
 async function startMemoryServer(env = process.env) {
@@ -13969,7 +13969,7 @@ import { promisify as promisify8 } from "util";
 // package.json
 var package_default = {
   name: "@nanopm/cli",
-  version: "0.1.6",
+  version: "0.1.7",
   description: "An autonomous product manager for builders who run several small products. Runs on your machine, drives your own coding harness.",
   type: "module",
   license: "MIT",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nanopm/cli",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "description": "An autonomous product manager for builders who run several small products. Runs on your machine, drives your own coding harness.",
   "type": "module",
   "license": "MIT",

package/skills/direction/SKILL.md

@@ -16,5 +16,5 @@ A mission or a vision the founder has said yes to is theirs. When one exists, th
 winner is written beside it as a proposal (`mission-next`, `vision-next`) and the founder
 decides on the business card; the run never replaces a stated row.
 
-See docs/nanopm-53-direction.md, and docs/reference/mission-vision.md for the rules the three
+See docs/✅nanopm-53-direction.md, and docs/reference/mission-vision.md for the rules the three
 roles judge by.

package/skills/market/SKILL.md

@@ -16,4 +16,4 @@ what was learned *about* a company attached to that company rather than beside i
 
 It replaces `research` everywhere a founder can see. `research` stays in the bundle for one
 caller — the problem crew's inline look outside — and is chained from nowhere
-(docs/nanopm-55-market-crew.md §9).
+(docs/✅nanopm-55-market-crew.md §9).

package/skills/needs/SKILL.md

@@ -1,7 +1,7 @@
 The needs crew's coordinator is **code**, not a model: `packages/daemon/src/needs-job.ts`.
 This file exists because a job names a skill and a skill has a manifest.
 
-Nothing reads this as a prompt. The run is five roles and a gate (docs/nanopm-57-needs-map.md §4):
+Nothing reads this as a prompt. The run is five roles and a gate (docs/✅nanopm-57-needs-map.md §4):
 
 1. **`needs-listener`** — the product's own users: the signals, the repository's notes about
    people, and on a deep run the connected services (`read_data`). No web, no write.

package/skills/onboard/SKILL.md

@@ -81,8 +81,9 @@ product is.
      it does from the line alone? These three are the pitch the founder reads first on the
      web and says yes to; the pitch crew may propose better ones later, beside theirs.
    - Batch 1, who it is for: `segments` up to 3 — **personas**, see step 4 — and `needs` up
-     to 5, each keyed to the persona it belongs to; **`mission` and `vision` only where the
-     product's own words already say one** — see step 4.
+     to 5, each keyed to the persona it belongs to; then **`mission` and `vision`, always** —
+     see step 4. They are climbed from the personas and needs, so they come right after them,
+     and Direction is the first section the founder reads after the pitch.
    - Batch 2, the rest of what it is and the money: `identity` `what-it-is-for` and at
      most one more, and `revenue` up to 4 (who pays, for what, how much).
    - Batch 3, the product: `products` — the `areas` item, the `not-doing` item, plus up
@@ -163,18 +164,29 @@ product is.
      roadmap, a milestone, a phase or a commit: those are things to build, not outcomes.
    - a principle the code states in words ("no human in the loop", "never email
      without consent") as `preferences`, one line each.
-   Two things you **do not** propose, and this is the one place the rule is different: a
-   **mission** (topic `mission`, key `mission`) and a **vision** (topic `vision`, key
-   `vision`). Write one only where the product's own words already say it — the first lines
-   of a README, a MANIFESTO, the hero of a landing page, an About page — and then it is
-   `observed`, with those files as its sources, in their words and not yours. The vision has
-   its own cap of 280 characters; the mission is a fact's 200.
-   **Never infer either from the routes and the feature set.** A mission read off what the
-   code does is the pitch with a wider adjective, and it is exactly the row this rule exists
-   to stop (docs/nanopm-53-direction.md §3). If the product's own words do not say where the
-   company is going, write nothing under these two topics and say so in your final log: the
-   card asks the founder for the mission in their own words, and the business card drafts a
-   mission and a vision with them when they ask. Do not write a gap for it: the card asks.
+   A **mission** (topic `mission`, key `mission`) and a **vision** (topic `vision`, key
+   `vision`), **always**: Direction on the card is these two, Yes or Edit (Nicolas,
+   2026-10-02). Where the product's own words already say one — the first lines of a README,
+   a MANIFESTO, a landing page's hero, an About page, the founder's wiki — write those words,
+   `observed`, with the files as sources. Otherwise draft them, `inferred`:
+   - **Mission**: the long-term change the founder is making in a business situation, the
+     lasting problem they solve, for whom. For whom → what fundamental value → why it
+     matters, one sentence under 200 characters a person could repeat from memory.
+   - **Vision**: what becomes true for the world, or the industry, once the mission
+     succeeds — and a person still living in it, doing something. One or two sentences,
+     under 280.
+   **Climb to them from the personas and needs, never from the routes and the feature
+   set**: a mission read off what the code does is the pitch with a wider adjective
+   (docs/✅nanopm-53-direction.md §3). In your head, in order: what the primary persona does
+   today *instead* (usually not a product: the time goes and leaves nothing); why they
+   struggle, the cause and not the pain; the progress they need, true even if the product
+   were rebuilt in another form; their world once it worked. Then compress: the mission from
+   the progress, the vision from that world. Before writing, check both against the direction
+   crew's must-pass tests (docs/reference/mission-vision.md): neither is the product back —
+   no feature, area name, platform, metric or date; no competitor could sign either
+   unchanged; the vision is more than today slightly improved, an outcome rather than one
+   solution, and adds a picture the mission does not already hold. A stated mission or
+   vision is the founder's: propose nothing under its key.
    Only when the repo states a stance in words (a README that says "maintenance mode",
    a roadmap that says "growth"), call set_preferences with `stance_provenance:
    "inferred"`; otherwise do not call it at all. The stance is `grow` until someone says

package/skills/opportunities/SKILL.md

@@ -1,7 +1,7 @@
 The opportunity crew's coordinator is **code**, not a model: `packages/daemon/src/opportunity-job.ts`.
 This file exists because a job names a skill and a skill has a manifest.
 
-Nothing reads this as a prompt. The run (docs/nanopm-61-opportunity-tree-whole.md §29):
+Nothing reads this as a prompt. The run (docs/✅nanopm-61-opportunity-tree-whole.md §29):
 
 **Quick** — the onboarding's run, and a quick *Update the map*:
 

package/skills/personas/SKILL.md

@@ -13,4 +13,4 @@ not write where decisions are made. The crew reads the market view instead — w
 already brought back — which is how a competitor's own words about their buyer reach the
 personas without that boundary moving.
 
-See docs/nanopm-50-personas.md.
+See docs/✅nanopm-50-personas.md.

package/skills/pitch/SKILL.md

@@ -13,4 +13,4 @@ A pitch the founder has said yes to is theirs. When one exists, the crew's winne
 beside it as a proposal (`pitch-<line>-next`) and the founder decides on the business card;
 the run never replaces a stated line.
 
-See docs/nanopm-52-pitch-crew.md.
+See docs/✅nanopm-52-pitch-crew.md.

package/skills/problem-mapper/SKILL.md

@@ -48,7 +48,7 @@ source merely to fill the sources array. Expert hypotheses may have an empty arr
 A source whose `provenance` is `inferred` may be marked context or contradicts, never
 supports: the store refuses it, and the refusal aborts the whole publication, so one
 wrong mark costs the entire run. Since the market crew began keeping what it found but
-could not read (docs/nanopm-55-market-crew.md §5), the competitors it saw named in a
+could not read (docs/✅nanopm-55-market-crew.md §5), the competitors it saw named in a
 search and never opened arrive here as `inferred` — they are real names worth reasoning
 from and they are not proof of anything.
 

package/skills/talk/skill.json

@@ -1,6 +1,6 @@
 {
   "name": "talk",
-  "description": "A conversation with Nano about one opportunity (docs/nanopm-68-talk-to-nano.md): one round per message, on the daemon's quick lane. Nano answers like a CPO on the founder's side — the objective first, one push back, then their call — and changes the map with his tools: what the founder asked for at once, his own ideas only as suggestions.",
+  "description": "A conversation with Nano about one opportunity (docs/✅nanopm-68-talk-to-nano.md): one round per message, on the daemon's quick lane. Nano answers like a CPO on the founder's side — the objective first, one push back, then their call — and changes the map with his tools: what the founder asked for at once, his own ideas only as suggestions.",
   "capabilities": ["talk"],
   "model": "claude-sonnet-5-5",
   "maxTurns": 12,