@tobos/cli 0.4.49 → 0.4.50

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -5,7 +5,7 @@ import {
5
5
  init_define_TOBOS_PRESENT_TYPES,
6
6
  init_define_TOBOS_SKILL,
7
7
  init_define_TOBOS_TOOLCHAIN
8
- } from "./chunk-FAVJGDWJ.js";
8
+ } from "./chunk-LMBMEGJH.js";
9
9
 
10
10
  // ../deck/src/deck-json.ts
11
11
  init_define_TOBOS_PRESENT_TYPES();
@@ -55,7 +55,7 @@ var init_define_TOBOS_PRESENT_TYPES = __esm({
55
55
  var define_TOBOS_SKILL_default;
56
56
  var init_define_TOBOS_SKILL = __esm({
57
57
  "<define:TOBOS_SKILL>"() {
58
- define_TOBOS_SKILL_default = { "SKILL.md": "---\nname: tobos-present\ndescription: Build presentations as code with Tobos Present. Use when the user wants a talk, lecture, pitch or slide deck made, changed, rendered, presented or exported as a PDF, or mentions Tobos or `tobos`.\n---\n\n<!-- Installed by the `tobos` CLI and overwritten when it updates, so changes made here don't last. -->\n\n# Tobos Present\n\nTobos hosts presentations written as code: a deck is a folder of files, one Svelte 5 file per scene, advancing one beat per click. You build it with the `tobos` command, which needs no git; Tobos checks every push, keeps every version, hosts the deck and puts it on stage. `tobos --help` lists every command, and each takes `--json`.\n\n## Get to the deck\n\n- `tobos ls` lists the decks the person can work on, by id. `tobos pull <id>` gets one; `tobos new \"Title\"` starts one and pulls it.\n- A new deck starts from Tobos standard's design. The person's own house styles are decks in `tobos ls`: start from one with `--from <id>`, which copies its master, and ask which when there are several.\n- Then read the deck's `AGENTS.md`: it points to the loop, the format and the deck's slide master.\n- The deck's outline, its chapters and scenes in order, their titles and which are hidden, isn't a file: Tobos holds it, and `tobos outline` shows and changes it, live at once. A new scene's file shows nowhere until `tobos outline place <scene>` puts it in. deck.json lists only the npm packages.\n- A deck has no chapters, or every scene is in one. Its first chapter, `tobos outline chapter add <id> \"Title\"`, takes every scene; add the others after it, and move scenes in. Make a chapter's id six random lowercase letters and digits, starting with a letter (`k7gh02`): its title is what the slides show. `tobos outline chapter remove --all` takes every chapter out, the scenes staying in order.\n- The person's decks are in folders, which `tobos --help` lists the commands for.\n\nExit code 3 means this machine isn't connected to the person's account. Run `tobos login`: it prints an address, which the person opens on any device, logs in at (a first login signs them up, and accepts https://tobos.ai/terms) and approves this machine. Give it to them in one line, then, once they did, run `tobos login` again. In CI or a sandbox with no one to ask, `TOBOS_TOKEN` and `TOBOS_SERVER` stand in for the login.\n\n## Follow the person\n\nThey decide what to make and how much of it you build: one scene at a time, or the whole deck at once. Build what they ask, at the size they ask, from what they have told you about the talk. When they ask how Tobos works or where to start, give them the tour, https://tobos.ai/tour, and nothing of your own: no explanation, no deck to try.\n\n## Folders\n\n- Look at the person's folders before you make or move a deck, and file it under a folder name they have already, as they wrote it, rather than a new one that means the same.\n- File every deck you make: once it is made, move it into the folder it belongs in.\n- Before you move more than a handful of decks, show the person the tree you propose, and make it once they say yes.\n- A reorganisation is taken back by moving the decks back where they were: note where they were before you move them.\n- Make a folder with `tobos mkdir /path` (or a move into a path that isn't there), and rename one in place with `tobos mv /path --name New`. A folder stays when it empties.\n- Deleting a folder or a deck is the person's, on the web: you never delete one. An empty folder they no longer want, tell them about, and leave it.\n- A deck shared with the person can have one shortcut in their folders: `tobos mv` of it places that shortcut, or moves it, and `tobos ls /path` marks it as one, with its owner. The deck stays its owner's. Leaving a deck shared with them, and deleting a shortcut, are the person's, on the web.\n- A deck or folder the person deleted waits in their trash for 30 days, and is gone to you meanwhile: `tobos ls` doesn't list it, and naming it answers that it isn't there. Only the person restores it, from the trash on the web.\n\n## What stays the person's\n\n- **Exit code 5** is a limit or an archived deck. Show the person the message as it is, which says what they can do, and wait for their answer. The deck stays in Tobos: a deck built elsewhere to upload later, media shrunk or hosted elsewhere to fit, or someone else's account would decide for them what is theirs to decide.\n- **Archiving, opening again and deleting** a deck, and deleting a session's answers, are done by the person on the deck's page, in their own browser.\n- **Who is on a deck, and its link,** are the person's, on the deck's page: they put people on it, change what each may do, take them off, and turn the link on or off there. You neither see nor change any of it: `tobos ls` tells you only what you may do on each deck and whose it is. Can edit builds it with their own agent, can present presents it with its notes and polls and starts decks from its design, and can view sees the slides.\n- **Each scene's notes,** what the speaker says, are the person's: they write them under the stage on the deck's page, and the presenter sees them. You neither read nor write them, and a scene needs none from you.\n- **The URL `tobos open` prints** is the deck's page, where the person watches it, presents it and shares it. Presenting starts there alone: no link you can get presents the deck.\n" };
58
+ define_TOBOS_SKILL_default = { "SKILL.md": "---\nname: tobos-present\ndescription: Build presentations as code with Tobos Present. Use when the user wants a talk, lecture, pitch or slide deck made, changed, rendered, presented or exported as a PDF, or mentions Tobos or `tobos`.\n---\n\n<!-- Installed by the `tobos` CLI and overwritten when it updates, so changes made here don't last. -->\n\n# Tobos Present\n\nTobos hosts presentations written as code: a deck is a folder of files, one Svelte 5 file per scene, advancing one beat per click. You build it with the `tobos` command, which needs no git; Tobos checks every push, keeps every version, hosts the deck and puts it on stage. `tobos --help` lists every command, and each takes `--json`.\n\n## Get to the deck\n\n- `tobos ls` lists the decks the person can work on, by id. `tobos pull <id>` gets one; `tobos new \"Title\"` starts one and pulls it.\n- A new deck starts from Tobos standard's design. The person's own house styles are decks in `tobos ls`: start from one with `--from <id>`, which copies its master, and ask which when there are several.\n- Then read the deck's `AGENTS.md`: it points to the loop, the format and the deck's slide master.\n- The deck's outline, its chapters and scenes in order, their titles and which are hidden, isn't a file: Tobos holds it, and `tobos outline` shows and changes it, live at once. A new scene's file shows nowhere until `tobos outline place <scene>` puts it in. deck.json lists only the npm packages.\n- A deck has no chapters, or every scene is in one. Its first chapter, `tobos outline chapter add <id> \"Title\"`, takes every scene; add the others after it, and move scenes in. Make a chapter's id six random lowercase letters and digits, starting with a letter (`k7gh02`): its title is what the slides show. `tobos outline chapter remove --all` takes every chapter out, the scenes staying in order.\n- The person's decks are in folders, which `tobos --help` lists the commands for.\n\nExit code 3 means this machine isn't connected to the person's account. Run `tobos login`: it prints an address, which the person opens on any device, logs in at (a first login signs them up, and accepts https://tobos.ai/terms) and approves this machine. Give it to them in one line, then, once they did, run `tobos login` again. In CI or a sandbox with no one to ask, `TOBOS_TOKEN` and `TOBOS_SERVER` stand in for the login.\n\n## Follow the person\n\nThey decide what to make and how much of it you build: one scene at a time, or the whole deck at once. Build what they ask, at the size they ask, from what they have told you about the talk. When they ask how Tobos works or where to start, give them the tour, https://tobos.ai/tour, and nothing of your own: no explanation, no deck to try.\n\n## Folders\n\n- Look at the person's folders before you make or move a deck, and file it under a folder name they have already, as they wrote it, rather than a new one that means the same.\n- File every deck you make: once it is made, move it into the folder it belongs in.\n- Before you move more than a handful of decks, show the person the tree you propose, and make it once they say yes.\n- A reorganisation is taken back by moving the decks back where they were: note where they were before you move them.\n- Make a folder with `tobos mkdir /path` (or a move into a path that isn't there), and rename one in place with `tobos mv /path --name New`. A folder stays when it empties.\n- Deleting a folder or a deck is the person's, on the web: you never delete one. An empty folder they no longer want, tell them about, and leave it.\n- A deck shared with the person can have one shortcut in their folders: `tobos mv` of it places that shortcut, or moves it, and `tobos ls /path` marks it as one, with its owner. The deck stays its owner's. Leaving a deck shared with them, and deleting a shortcut, are the person's, on the web.\n- A deck or folder the person deleted waits in their trash for 30 days, and is gone to you meanwhile: `tobos ls` doesn't list it, and naming it answers that it isn't there. Only the person restores it, from the trash on the web.\n\n## What stays the person's\n\n- **Exit code 5** is a limit or a View only deck. Show the person the message as it is, which says what they can do, and wait for their answer. The deck stays in Tobos: a deck built elsewhere to upload later, media shrunk or hosted elsewhere to fit, or someone else's account would decide for them what is theirs to decide.\n- **Choosing which decks are editable** (Free keeps 3; the rest are View only, presented and shared as before), **deleting** a deck and **deleting a session's answers** are done by the person on the web, in their own browser. When `tobos new` says a deck is View only now to make room, tell the person, with the link it gives.\n- **Who is on a deck, and its link,** are the person's, on the deck's page: they put people on it, change what each may do, take them off, and turn the link on or off there. You neither see nor change any of it: `tobos ls` tells you only what you may do on each deck and whose it is. Can edit builds it with their own agent, can present presents it with its notes and polls and starts decks from its design, and can view sees the slides.\n- **Each scene's notes,** what the speaker says, are the person's: they write them under the stage on the deck's page, and the presenter sees them. You neither read nor write them, and a scene needs none from you.\n- **The URL `tobos open` prints** is the deck's page, where the person watches it, presents it and shares it. Presenting starts there alone: no link you can get presents the deck.\n" };
59
59
  }
60
60
  });
61
61
 
package/dist/cli.js CHANGED
@@ -7,7 +7,7 @@ import {
7
7
  mergeText,
8
8
  parseMediaJson,
9
9
  unpackTar
10
- } from "./chunk-CEQVVOY7.js";
10
+ } from "./chunk-BQ6AZLKZ.js";
11
11
  import {
12
12
  ASK_THE_PERSON,
13
13
  CliError,
@@ -19,7 +19,7 @@ import {
19
19
  init_define_TOBOS_TOOLCHAIN,
20
20
  offerUpdate,
21
21
  update
22
- } from "./chunk-FAVJGDWJ.js";
22
+ } from "./chunk-LMBMEGJH.js";
23
23
 
24
24
  // src/main.ts
25
25
  init_define_TOBOS_PRESENT_TYPES();
@@ -90,7 +90,7 @@ var CHANGESET_SCHEMA = {
90
90
  };
91
91
  var VERBS = {
92
92
  list: {
93
- does: "The decks the person works on, by id: their own, and those shared with them that they may present or change. Each with its title, your level on it and whose it is, whether it is archived (read-only), when it last changed, its address in Tobos, and, for the person\u2019s own, its folder. With a path, what that folder holds: its folders, then its decks, a shortcut to a deck shared with the person marked as one, with its owner.",
93
+ does: "The decks the person works on, by id: their own, and those shared with them that they may present or change. Each with its title, your level on it and whose it is, whether it is View only (beyond the decks its owner\u2019s plan keeps editable: it takes no change), when it last changed, its address in Tobos, and, for the person\u2019s own, its folder. With a path, what that folder holds: its folders, then its decks, a shortcut to a deck shared with the person marked as one, with its owner.",
94
94
  input: { properties: { path: { type: "string", description: FOLDER_PATH } }, required: [] },
95
95
  cli: [
96
96
  {
@@ -278,7 +278,7 @@ function settings() {
278
278
  }
279
279
 
280
280
  // src/api.ts
281
- var VERSION = true ? "0.4.49" : "dev";
281
+ var VERSION = true ? "0.4.50" : "dev";
282
282
  function newer(a, b) {
283
283
  const parse = (v) => /^\d+\.\d+\.\d+/.test(v) ? v.split(".").map((n) => parseInt(n)) : null;
284
284
  const x = parse(a);
@@ -965,7 +965,7 @@ function aboutDeck(d) {
965
965
  const can = { editor: "you edit", presenter: "you present", viewer: "you view" };
966
966
  const notes = [
967
967
  d.role && d.role !== "owner" && `${d.owner ?? "someone else"}\u2019s, ${can[d.role]}`,
968
- d.archived && "archived: read-only"
968
+ (d.viewOnly ?? d.archived) && "view only: no pushes"
969
969
  ].filter(Boolean);
970
970
  return notes.length ? ` (${notes.join("; ")})` : "";
971
971
  }
@@ -1124,6 +1124,8 @@ async function create(out, args) {
1124
1124
  { ...info, dir: dir2 ?? null },
1125
1125
  () => [
1126
1126
  `Created ${info.title}: ${info.url}`,
1127
+ // Made where the plan kept no more editable: which deck is View only now, for the person.
1128
+ info.madeViewOnly ? info.madeViewOnly.note : "",
1127
1129
  dir2 ? `Pulled into ${relative2(process.cwd(), dir2) || "."}. Read AGENTS.md there first.` : ""
1128
1130
  ].filter(Boolean).join("\n")
1129
1131
  );
@@ -1153,7 +1155,7 @@ async function check(out, args) {
1153
1155
  );
1154
1156
  const problems = [...written.problems];
1155
1157
  if (args.values.types) {
1156
- const { checkTypes } = await import("./types-7TCIR6PZ.js");
1158
+ const { checkTypes } = await import("./types-QU4FJJX4.js");
1157
1159
  problems.push(...await checkTypes(copy.root, (m) => out.note(m)));
1158
1160
  }
1159
1161
  const { errors, warnings } = problemSummary(problems);
@@ -1361,7 +1363,7 @@ async function openApp(out) {
1361
1363
  out.result({ url, opened }, () => url);
1362
1364
  }
1363
1365
  async function render(out, args) {
1364
- const { renderBeats } = await import("./render-UNQZU7KB.js");
1366
+ const { renderBeats } = await import("./render-C2EYQWDS.js");
1365
1367
  const copy = findCopy();
1366
1368
  const deck = copy?.base ? { id: copy.base.deck, root: copy.root } : void 0;
1367
1369
  const id = typeof args.values.deck === "string" ? parseId(args.values.deck) : deck?.id;
@@ -1485,8 +1487,8 @@ The skill (what your harness reads to know Tobos without this help)
1485
1487
 
1486
1488
  Every command takes --json and then prints one JSON object.
1487
1489
  Exit codes: 0 ok, 1 error, 2 the deck has problems, 3 not logged in (or not yet approved),
1488
- 4 a conflict: someone changed the same lines (pull, resolve, push again), 5 a plan's limit or an
1489
- archived deck: the person decides what to do, so show them the message and wait.
1490
+ 4 a conflict: someone changed the same lines (pull, resolve, push again), 5 a plan's limit or a
1491
+ View only deck: the person decides what to do, so show them the message and wait.
1490
1492
  `;
1491
1493
  var COMMON = {
1492
1494
  json: { type: "boolean" },
@@ -6,7 +6,7 @@ import {
6
6
  init_define_TOBOS_PRESENT_TYPES,
7
7
  init_define_TOBOS_SKILL,
8
8
  init_define_TOBOS_TOOLCHAIN
9
- } from "./chunk-FAVJGDWJ.js";
9
+ } from "./chunk-LMBMEGJH.js";
10
10
 
11
11
  // src/render.ts
12
12
  init_define_TOBOS_PRESENT_TYPES();
@@ -3,7 +3,7 @@ import { createRequire as __tobosRequire } from 'node:module';
3
3
  const require = __tobosRequire(import.meta.url);
4
4
  import {
5
5
  parseDeckJson
6
- } from "./chunk-CEQVVOY7.js";
6
+ } from "./chunk-BQ6AZLKZ.js";
7
7
  import {
8
8
  CliError,
9
9
  __commonJS,
@@ -14,7 +14,7 @@ import {
14
14
  init_define_TOBOS_PRESENT_TYPES,
15
15
  init_define_TOBOS_SKILL,
16
16
  init_define_TOBOS_TOOLCHAIN
17
- } from "./chunk-FAVJGDWJ.js";
17
+ } from "./chunk-LMBMEGJH.js";
18
18
 
19
19
  // ../node_modules/.pnpm/aria-query@5.3.1/node_modules/aria-query/lib/util/iteratorProxy.js
20
20
  var require_iteratorProxy = __commonJS({
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tobos/cli",
3
- "version": "0.4.49",
3
+ "version": "0.4.50",
4
4
  "description": "The command line of Tobos: https://tobos.ai",
5
5
  "type": "module",
6
6
  "license": "FSL-1.1-ALv2",