@creator-notes/cnotes 0.59.0 → 0.59.1

package/dist/lib/brand.d.ts

@@ -20,6 +20,9 @@ export declare const BRAND: {
     readonly url: "https://creatornotes.app";
     /** Bare domain. */
     readonly domain: "creatornotes.app";
+    /** Developer portal (docs only). The API stays on `url`; never a server target. */
+    readonly devUrl: "https://cnotes.dev";
+    readonly devDomain: "cnotes.dev";
     /** The installed command. */
     readonly command: "cnotes";
     /** Published package name. */

package/dist/lib/brand.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"brand.d.ts","sourceRoot":"","sources":["../../src/lib/brand.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AACH,eAAO,MAAM,KAAK;IAChB,kDAAkD;;IAElD,kEAAkE;;IAElE,mBAAmB;;IAEnB,6BAA6B;;IAE7B,8BAA8B;;IAE9B,uFAAuF;;IAEvF,oCAAoC;;CAE5B,CAAC"}
+{"version":3,"file":"brand.d.ts","sourceRoot":"","sources":["../../src/lib/brand.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AACH,eAAO,MAAM,KAAK;IAChB,kDAAkD;;IAElD,kEAAkE;;IAElE,mBAAmB;;IAEnB,mFAAmF;;;IAGnF,6BAA6B;;IAE7B,8BAA8B;;IAE9B,uFAAuF;;IAEvF,oCAAoC;;CAE5B,CAAC"}

package/dist/lib/brand.js

@@ -20,6 +20,9 @@ export const BRAND = {
     url: "https://creatornotes.app",
     /** Bare domain. */
     domain: "creatornotes.app",
+    /** Developer portal (docs only). The API stays on `url`; never a server target. */
+    devUrl: "https://cnotes.dev",
+    devDomain: "cnotes.dev",
     /** The installed command. */
     command: "cnotes",
     /** Published package name. */

package/dist/lib/brand.js.map

@@ -1 +1 @@
-{"version":3,"file":"brand.js","sourceRoot":"","sources":["../../src/lib/brand.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AACH,MAAM,CAAC,MAAM,KAAK,GAAG;IACnB,kDAAkD;IAClD,IAAI,EAAE,eAAe;IACrB,kEAAkE;IAClE,GAAG,EAAE,0BAA0B;IAC/B,mBAAmB;IACnB,MAAM,EAAE,kBAAkB;IAC1B,6BAA6B;IAC7B,OAAO,EAAE,QAAQ;IACjB,8BAA8B;IAC9B,WAAW,EAAE,uBAAuB;IACpC,uFAAuF;IACvF,SAAS,EAAE,SAAS;IACpB,oCAAoC;IACpC,IAAI,EAAE,uBAAuB;CACrB,CAAC"}
+{"version":3,"file":"brand.js","sourceRoot":"","sources":["../../src/lib/brand.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AACH,MAAM,CAAC,MAAM,KAAK,GAAG;IACnB,kDAAkD;IAClD,IAAI,EAAE,eAAe;IACrB,kEAAkE;IAClE,GAAG,EAAE,0BAA0B;IAC/B,mBAAmB;IACnB,MAAM,EAAE,kBAAkB;IAC1B,mFAAmF;IACnF,MAAM,EAAE,oBAAoB;IAC5B,SAAS,EAAE,YAAY;IACvB,6BAA6B;IAC7B,OAAO,EAAE,QAAQ;IACjB,8BAA8B;IAC9B,WAAW,EAAE,uBAAuB;IACpC,uFAAuF;IACvF,SAAS,EAAE,SAAS;IACpB,oCAAoC;IACpC,IAAI,EAAE,uBAAuB;CACrB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@creator-notes/cnotes",
-  "version": "0.59.0",
+  "version": "0.59.1",
   "description": "CLI for CreatorNotes — create notes, build canvases, search knowledge from the terminal",
   "type": "module",
   "bin": {

package/skills/attention-planner/references/orientation-canvas.md

@@ -25,8 +25,12 @@ sections size themselves around their content, so no coordinates.
 | `3 · Advances` | The Project, Decision, or Customer the card names in `advances`, with a text card saying what becomes true if the block succeeds and which external send still needs a yes | from the card: `advances` |
 | `Where things live` (bottom) | Portals: the work board the card came from and the home board | none |
 
-Banner at the top, `richtext` medium, untinted, at most five sentences: the block
-day and time, the reading order, "answer on the card", where the portals go.
+Banner at the top, `richtext` medium, untinted, at most five sentences, in the
+cnotes skill's banner order (hard rule 7 under "Canvas Elements"): what happened,
+what this board is for, who answers and where, how to read it. Then the lines
+only this canvas needs: the block day and time, "answer on the card", where the
+portals go. A banner that opens with the block time and the reading order and
+never says what the card is about fails the cnotes cold-reader test.
 Reminder material (rules, operating plan) does not go on an orientation canvas;
 the home board carries it.
 

package/skills/cnotes/SKILL.md

@@ -253,7 +253,11 @@ cnotes canvas digest <canvasId>
 # NAMING: never put an em-dash (—) or en-dash (–) in a canvas name. Use the interpunct
 # · (U+00B7, MIDDLE DOT — a small mid-height dot, NOT a bullet •) as the separator,
 # e.g. "Path to Revenue · Funding strategy", not "Path to Revenue — Funding strategy".
-cnotes canvas create "<name>" [--goal "<text>"] [--audience "<text>"]   # prints Ref (CANVAS-N) + Link — surface them to the user (see "Surfacing the canvas link")
+cnotes canvas create "<name>" --goal "<text>" [--audience "<text>"]   # prints Ref (CANVAS-N) + Link — surface them to the user (see "Surfacing the canvas link")
+# --goal is not optional in practice: write it FIRST, for a reader, as the decision or artifact
+# the board exists to produce ("Decide whether X; pick the first slice"), never as a brief to
+# yourself ("Research Tufte, diverge on..."). The goal renders only inside the (i) popover, so
+# nobody sees it before the banner; the banner restates it (hard rule 7).
 cnotes canvas update <canvasId> [--title "<text>"] [--goal "<text>"] [--audience "<text>"]
 cnotes canvas delete <canvasId>
 cnotes canvas set-as-home <canvasId>
@@ -266,7 +270,7 @@ cnotes canvas add-node <canvasId> --note <noteId> [--x <n>] [--y <n>]   # (despi
 # text = free-form rich text placed on the canvas (wire type: richtext). Markdown —
 # headings, emphasis, images. Optional background tint (--color); DEFAULT IS NO BACKGROUND.
 # A HEADING IS JUST `--content '# Q1 Goals'` with no tint — there is no separate heading
-# element. CARD-sized framing (at most ~3 sentences): orientation banners, emphasis
+# element. CARD-sized framing (at most ~3 sentences; the orientation banner may run to ~5 and follows hard rule 7), emphasis
 # quoting a note, image tiles. Unversioned, unsearchable, no display ID (nothing can cite
 # it) — never the sole home of a claim. When the card names a note or canvas, write a
 # relationship mention with the REAL title, `[NOTE-12: Title](relationship:verb)`: it renders
@@ -878,7 +882,7 @@ A canvas holds two tiers of material, and the difference is load-bearing:
 | N distinct things (questions, risks, options, findings) | **N notes** grouped in a **list**; `--description` = one-line frame | bullets in one text element or in a list `--description` |
 | A named REGION of the canvas ("Shaping", "Open Questions") | a **section** frame (`add-section`) — draggable region, mention-addressable as `[[SECTION-<n>]]` from note bodies | a floating text heading over an implied area |
 | A heading / one-line label where a frame is too heavy (a column header inside a frame, a lane key) | a **text** element holding a markdown heading — `add-text --content '# Q1 Goals'`, no `--color` (leave it untinted), title case | a tinted card, or a section frame for something that isn't a region |
-| Prose telling the reader how to traverse THIS canvas | a **text** orientation banner (one per canvas or band; up to ~5 sentences) | a Guide note nobody needs off-canvas |
+| Orientation: what happened, what this board is for, and how to read it | a **text** orientation banner in the fixed shape of rule 7 (one per canvas; a band may add a short one; up to ~5 sentences) | a reading-order-only banner, or a Guide note nobody needs off-canvas |
 | Emphasis — restating a key claim for screen presence | a **text** element that QUOTES a note (the note stays the home) | the text element as the only copy |
 | An image tile (logo, mockup, screenshot) | a **text** element holding the image, beside the owning note; embed the same image in the note body via `cnotes files upload <path> --markdown` so the note stays self-contained | the image as the knowledge itself |
 | A grid of images for review (mood board) | N text-element image tiles in a `grid` place spec + ONE note holding the decision criteria / rationale for the set | a caption note per tile, or rationale in the tiles |
@@ -906,14 +910,23 @@ A canvas holds two tiers of material, and the difference is load-bearing:
 
    Do not hand-pick a hex outside this table: the renderer snaps every tint to the nearest role by hue, so an off-palette color does not get you a new shade — it just picks a role imprecisely (`#c2410c` lands on Danger, not Warning). A tint colors the CARD only; text inside it keeps the normal prose colors, so the tint can never make a card harder to read. If you cannot name the role, omit the color.
 
-#### Two completion tests
+7. **The orientation banner opens for a stranger, in a fixed order.** The banner is the first and often the only card a cold reader sees (the goal sits behind the (i) button; nobody reads it first), so a banner that gives only the reading order fails: one shipped as "A story in six frames, read top to bottom. Frames 1 to 3 are the events: a release note is written, an agent writes an ad from it, the scope changes" and the reader could not say which release note, whose agent, or why any of it mattered. Write it in this order, at most ~5 sentences, heading = the board's subject (the canvas title or the goal), never a clever name for the banner:
+   1. **What happened** — one dated sentence naming the people, products and events a stranger can look up ("On 19 September 2026 Deniss asked why CreatorNotes records every note a person opens but nothing an agent reads").
+   2. **What this board is for** — the goal restated in reader's words: the decision or artifact it produces.
+   3. **Who acts on it and how** — who decides, answers, or builds, and where the answer goes (as a mention chip with its real title, rule 2).
+   4. **How to read it** — reading order and what each frame holds.
+   Nothing before the banner has defined anything, so no unnamed referents in it: not "the ad", "the app", "the scope", "the card" until the thing has been named or chipped. Wayfind maps and Attention orientation canvases add their own lines (destination, block time) after these four, never instead of them.
 
-Run both before ending your operation:
+#### Three completion tests
+
+Run all three before ending your operation:
 
 **The read-back test (for the next agent):** run `cnotes canvas read` and check that every claim is present as a NOTE section with a display ID, and the reasoning can be followed through note bodies and their mentions. Content that appears only as anonymous text-element prose fails the test even when visible — nothing can cite, search, or version it. List members read back as ID+title links without bodies; that is fine — the IDs are citable and batch-fetchable via `cnotes notes get`. As a heuristic for working canvases, at least ~4 notes per text element (zero text elements is fine); fewer means text elements are carrying content. Explainer canvases using the projection pattern (rule 4) are exempt from the ratio, not from the test.
 
 **The glance test (for the human):** zoomed to fit, a person should grasp what this canvas argues and where to start reading in about 10 seconds. A canvas that passes read-back but renders as an undifferentiated card grid is also not done — that is what section labels, orientation banners, projections, and layout are for.
 
+**The cold-reader test (for the person who was not in the session):** cover everything but the banner. Can someone who never saw the conversation say what happened, what this board decides or produces, and who acts on it? If the banner only gives the reading order, or leans on "the ad" / "the app" / "the card" before naming them, it fails (rule 7). Run this on the banner text itself, not on your memory of the run.
+
 #### Worked example
 
 Right shape (a real competitor scan): 31 typed notes (COMPETITOR profile, FACT evidence row, INSIGHT verdicts per dimension, RISK/IDEA/STRATEGY response bands, QUESTION follow-ups in a list), three short text banners framing the bands ("Threats, Steals, Response — what hurts us, what's worth taking, the plan"), and labeled edges mirrored as mentions (`FACT-44 --grounds--> INSIGHT-361`).

package/skills/wayfind/SKILL.md

@@ -137,8 +137,10 @@ The user arrives with a loose idea.
    `wayfind` plus the mode.
 5. **Place the map** in one `cnotes canvas place` spec: orientation banner,
    the four sections with their contents, blocking edges (blocker → dependent,
-   label "blocks"). Banner is at most five sentences, plain display IDs only —
-   mention syntax corrupts richtext.
+   label "blocks"). Banner is at most five sentences in the cnotes skill's banner
+   order (hard rule 7 under "Canvas Elements"): what happened and who asked,
+   the destination in reader's words, who resolves tickets and how, then how the
+   four frames read. Plain display IDs only — mention syntax corrupts richtext.
 6. **Fire the research subagents** for frontier research tickets; fold whatever
    returns into resolutions (steps 4–6 of the work loop) before closing.
 7. **Close the run, surface the canvas link, stop.** Charting resolves nothing