slopwaresystems 0.1.1 → 0.1.2

package/README.md

@@ -4,7 +4,7 @@ The [Slopware Tasks](https://tasks.slopware.systems) board from the terminal. Bu
 
 ```bash
 npm i -g slopwaresystems
-slop login                # approve the machine in your browser
+slop login                # approve the machine in your browser (on a VM or over SSH: open the printed link on any device)
 cd your-repo && slop link WEB
 slop task create "Retry storms on 429" -s high -d -
 slop skills install       # puts the agent skills into .claude/skills/

package/dist/index.js

@@ -3379,7 +3379,7 @@ import { homedir } from "os";
 import { join } from "path";
 
 // skills/slop-cli.md
-var slop_cli_default = '---\nname: slop-cli\ndescription: How to use the slop CLI to read and update the task board this repository is linked to. Load when asked to create, update, plan, comment on or finish tasks.\n---\n\n# slop: the board from the terminal\n\nThe repository you are in is linked to a project on Slopware Tasks. Everything a person can do on the board, you can do with `slop`. Add `--json` to any command for machine-readable output.\n\n## Orientation\n\n```bash\nslop status                 # which project this checkout is linked to\nslop statuses               # the board\'s columns (key, label, category)\nslop members                # who tasks can be assigned to\nslop task list [--all] [--status <column>] [--assignee me]\nslop task show <KEY>        # title, status, severity, assignee, links, plan, description\nslop task history <KEY>     # everything that happened to it, in order\n```\n\nTask keys look like `WEB-12`; the bare number works inside the linked project.\n\n## Creating and changing tasks\n\n```bash\nslop task create "Short imperative title" -d "What, where, why" -s <low|medium|high|critical> [--status <column>] [-a <email|me|none>]\nslop task update <KEY> [--title \u2026] [-d \u2026] [-s \u2026] [--status \u2026] [-a \u2026]\nslop task move <KEY> "<column label or key>"\nslop task start <KEY>       # first "in progress" column\nslop task done <KEY>        # first "done" column\nslop task assign <KEY> <email|me|none>\nslop task link <KEY> <url>  # a PR, a design, a log; GitHub PRs are recognised\nslop task notes <KEY> [text|-]  # the scratchpad under the links: read it, or replace it whole\n\n## Sessions (see the `slop-sessions` skill)\n\n```bash\nslop session start <KEY>      # claim: assign me, move to in progress\nslop session wait <KEY>       # be live until someone says something; run in the background\nslop session end <KEY>\nslop sessions                 # who is live on what\nslop task ask <KEY> "\u2026"       # say something to whoever is live on it (also on the timeline)\n```\nslop task archive <KEY>     # off the board, history kept\n```\n\nDescriptions are Markdown and are shown in full. Long text: `-d -` reads stdin.\n\n## Plans (see the `slop-planning` skill)\n\n```bash\nslop task items <KEY>                       # the plan, numbered, with notes\nslop task plan <KEY> - <<\'EOF\'              # one item per line, appended in order\nInventory the Intercom data model\nWrite the export script\nEOF\nslop task item add <KEY> "title" [-n "note"]\nslop task item done <KEY> <n>               # by number from `items`\nslop task item reopen <KEY> <n>\nslop task item note <KEY> <n> "what is true now"\nslop task item rename <KEY> <n> "new title"\nslop task item remove <KEY> <n>\n```\n\n## Projects\n\n```bash\nslop projects\nslop project create "Name" [--key KEY]\nslop project update [--name \u2026] [--description \u2026] [--theme <theme>]\nslop project status add "In review" -c in_progress      # columns: add | rename | remove | order\n```\n\n## Rules of the road\n\n- Do not delete tasks you did not create. Archive finished work instead.\n- Keep titles short and imperative; put the reasoning in the description or the plan\'s notes. There is no chat: the plan\'s notes are the running state, the description holds decisions.\n- When you open a pull request for a task, link it.\n';
+var slop_cli_default = '---\nname: slop-cli\ndescription: How to use the slop CLI to read and update the task board this repository is linked to. Load when asked to create, update, plan, comment on or finish tasks.\n---\n\n# slop: the board from the terminal\n\nThe repository you are in is linked to a project on Slopware Tasks. Everything a person can do on the board, you can do with `slop`. Add `--json` to any command for machine-readable output.\n\n## Orientation\n\n```bash\nslop status                 # which project this checkout is linked to\nslop statuses               # the board\'s columns (key, label, category)\nslop members                # who tasks can be assigned to\nslop task list [--all] [--status <column>] [--assignee me]\nslop task show <KEY>        # title, status, severity, assignee, links, plan, description\nslop task history <KEY>     # everything that happened to it, in order\n```\n\nTask keys look like `WEB-12`; the bare number works inside the linked project.\n\nA link belongs to the clone: every git worktree of it (including agent sandboxes made with `git worktree add`) is linked without doing anything. On a machine with no browser, `slop login` prints a link and a code; open it on any device.\n\n## Creating and changing tasks\n\n```bash\nslop task create "Short imperative title" -d "What, where, why" -s <low|medium|high|critical> [--status <column>] [-a <email|me|none>]\nslop task update <KEY> [--title \u2026] [-d \u2026] [-s \u2026] [--status \u2026] [-a \u2026]\nslop task move <KEY> "<column label or key>"\nslop task start <KEY>       # first "in progress" column\nslop task done <KEY>        # first "done" column\nslop task assign <KEY> <email|me|none>\nslop task link <KEY> <url>  # a PR, a design, a log; GitHub PRs are recognised\nslop task notes <KEY> [text|-]  # the scratchpad under the links: read it, or replace it whole\n\n## Sessions (see the `slop-sessions` skill)\n\n```bash\nslop session start <KEY>      # claim: assign me, move to in progress\nslop session wait <KEY>       # be live until someone says something; run in the background\nslop session end <KEY>\nslop sessions                 # who is live on what\nslop task ask <KEY> "\u2026"       # say something to whoever is live on it (also on the timeline)\n```\nslop task archive <KEY>     # off the board, history kept\n```\n\nDescriptions are Markdown and are shown in full. Long text: `-d -` reads stdin.\n\n## Plans (see the `slop-planning` skill)\n\n```bash\nslop task items <KEY>                       # the plan, numbered, with notes\nslop task plan <KEY> - <<\'EOF\'              # one item per line, appended in order\nInventory the Intercom data model\nWrite the export script\nEOF\nslop task item add <KEY> "title" [-n "note"]\nslop task item done <KEY> <n>               # by number from `items`\nslop task item reopen <KEY> <n>\nslop task item note <KEY> <n> "what is true now"\nslop task item rename <KEY> <n> "new title"\nslop task item remove <KEY> <n>\n```\n\n## Projects\n\n```bash\nslop projects\nslop project create "Name" [--key KEY]\nslop project update [--name \u2026] [--description \u2026]\nslop project status add "In review" -c in_progress      # columns: add | rename | remove | order\n```\n\n## Rules of the road\n\n- Do not delete tasks you did not create. Archive finished work instead.\n- Keep titles short and imperative; put the reasoning in the description or the plan\'s notes. There is no chat: the plan\'s notes are the running state, the description holds decisions.\n- When you open a pull request for a task, link it.\n';
 
 // skills/slop-planning.md
 var slop_planning_default = '---\nname: slop-planning\ndescription: How to break long or multi-session work into a plan on its task, keep each item\'s note current, and pick up where you left off. Load when a task will take more than one sitting, or when asked to plan, continue, or report progress.\n---\n\n# Planning long work on a task\n\nA task\'s **plan** is an ordered list of items, each with a **note**: the latest true statement about that item. The plan plus the task\'s timeline is your memory between sessions. Write to it as you work, not at the end.\n\n## Starting\n\n1. Read the task: `slop task show <KEY>`. If it has a plan, read the notes; they are what the last session knew.\n2. If there is no plan, write one. Items are concrete, checkable, and ordered by what unlocks what. Eight to fifteen is typical; more means the task should be split.\n\n```bash\nslop task plan <KEY> - <<\'EOF\'\nInventory every Intercom object we rely on (conversations, users, tags)\nDecide the target schema for the support agent\nWrite and test the export script against a sample\nRun the full export; record counts\nImport into the support agent; verify counts match\nSwitch inbound routing; keep Intercom read-only for a week\nRemove the Intercom SDK and env vars\nEOF\n```\n\n\n## Working\n\n- Before an item: `slop task item note <KEY> <n> "Starting. Approach: \u2026"`\n- As facts arrive, replace the note. Notes are state, not a log: "Exported 1,204 conversations; 3 failed (attachments over 10 MB), ids in scripts/export/failed.json".\n- When an item is done: `slop task item done <KEY> <n>`. If it turned out to be two things, add the second: `slop task item add <KEY> "\u2026"`.\n- Blocked? Put the blocker in the note, then move on to an item that is not blocked. Do not mark blocked items done.\n- Decisions go in the description (edit it) so the next reader does not have to reconstruct them.\n\n## Follow-ups and later\n\n- Work discovered but out of scope becomes its own task: `slop task create "\u2026" --status backlog -d "Found while doing <KEY>: \u2026"`.\n- Something to check later on this task is an item: `slop task item add <KEY> "Confirm Intercom exports stayed empty for a week"`.\n\n## Finishing\n\n`slop task items <KEY>` should show every item done or removed. Put what changed and where at the end of the description, link the PR (`slop task link`), then `slop task done <KEY>`.\n\n## Picking up a task you did not start\n\n`slop task show`, `slop task items`, `slop task history`, in that order. The notes tell you the present; the history tells you how it got there. Then continue from the first item that is not done.\n';
@@ -23207,9 +23207,21 @@ var Invitation = external_exports.object({
   role: OrgRole,
   createdAt: Timestamp
 });
+var InviteLink = external_exports.object({
+  id: Id,
+  role: OrgRole,
+  createdAt: Timestamp,
+  expiresAt: Timestamp.nullable(),
+  uses: external_exports.number()
+});
+var CreateInviteLinkInput = external_exports.object({ role: OrgRole.default("member"), expiresInHours: external_exports.number().int().min(1).max(24 * 30).nullable().default(24) });
+var CreatedInviteLink = InviteLink.extend({ url: external_exports.string() });
+var JoinPreview = external_exports.object({ org: external_exports.object({ id: Id, name: external_exports.string() }), role: OrgRole, alreadyMember: external_exports.boolean() });
 var MembersResult = external_exports.object({
   members: external_exports.array(Member),
-  invitations: external_exports.array(Invitation)
+  invitations: external_exports.array(Invitation),
+  /** Active links only. Admins see them; members get an empty list. */
+  links: external_exports.array(InviteLink)
 });
 var InviteMemberInput = external_exports.object({ email: Email, role: OrgRole.default("member") });
 var UpdateMemberInput = external_exports.object({ role: OrgRole });
@@ -23241,8 +23253,6 @@ function findStatus(statuses, ref) {
 
 // ../contract/src/work/projects.ts
 var ProjectKey = external_exports.string().trim().toUpperCase().pipe(external_exports.string().regex(/^[A-Z][A-Z0-9]{1,7}$/, "2\u20138 letters or digits, starting with a letter"));
-var PROJECT_THEMES = ["slate", "stone", "zinc", "mist", "sand", "rose", "violet", "emerald"];
-var ProjectTheme = external_exports.enum(PROJECT_THEMES);
 var TaskCounts = external_exports.record(external_exports.string(), external_exports.number());
 var Project = external_exports.object({
   id: Id,
@@ -23250,8 +23260,6 @@ var Project = external_exports.object({
   key: external_exports.string(),
   name: external_exports.string(),
   description: external_exports.string(),
-  /** Null: no theme of its own; the viewer's personal theme applies. */
-  theme: ProjectTheme.nullable(),
   /** The board's columns, in order. */
   statuses: external_exports.array(ProjectStatus),
   createdAt: Timestamp,
@@ -23266,8 +23274,7 @@ var CreateProjectInput = external_exports.object({
 });
 var UpdateProjectInput = external_exports.object({
   name: external_exports.string().trim().min(1).max(80),
-  description: external_exports.string().trim().max(2e3),
-  theme: ProjectTheme.nullable()
+  description: external_exports.string().trim().max(2e3)
 }).partial();
 function suggestProjectKey(name) {
   const words = name.toUpperCase().replace(/[^A-Z0-9 ]+/g, " ").split(/\s+/).filter(Boolean);
@@ -23640,19 +23647,21 @@ function openBrowser(url2) {
   }
 }
 var sleep = (ms) => new Promise((done) => setTimeout(done, ms));
+var headless = () => Boolean(process.env.SSH_CONNECTION || process.env.SSH_TTY) || platform2() === "linux" && !process.env.DISPLAY && !process.env.WAYLAND_DISPLAY;
 function registerAuthCommands(program3) {
-  program3.command("login").description("Sign this machine in. Opens the web app, where you approve the login.").option("--url <url>", "the Slopware Tasks instance to sign in to").option("--no-browser", "print the link instead of opening it").action(async (options) => {
+  program3.command("login").description("Sign this machine in. Opens the web app, where you approve the login. On a VM or over SSH, open the printed link on any device.").option("--url <url>", "the Slopware Tasks instance to sign in to").option("--no-browser", "print the link instead of opening it").action(async (options) => {
     const baseUrl = (options.url || process.env.SLOP_URL || readConfig()?.baseUrl || DEFAULT_URL).replace(/\/+$/, "");
     const api = createApi({ baseUrl, token: null });
     const started = await api.post("/cli/auth/start", { machine: machineInfo() });
+    const remote = headless();
     process.stderr.write(`
-Approve this login in your browser:
+Approve this login in a browser${remote ? " on any device (this machine has no browser; your laptop or phone is fine)" : ""}:
   ${started.verifyUrl}
 
 Confirm the code matches:  ${started.userCode}
 
 `);
-    if (options.browser) openBrowser(started.verifyUrl);
+    if (options.browser && !remote) openBrowser(started.verifyUrl);
     const deadline = Date.now() + started.expiresIn * 1e3;
     while (Date.now() < deadline) {
       await sleep(started.interval * 1e3);
@@ -23721,8 +23730,9 @@ function git(args, cwd = process.cwd()) {
 function findRepo() {
   const commonDir = git(["rev-parse", "--path-format=absolute", "--git-common-dir"]);
   if (!commonDir) return null;
-  const root = basename(commonDir) === ".git" ? resolve(commonDir, "..") : git(["rev-parse", "--show-toplevel"]) ?? commonDir;
-  return { root, linkPath: join4(commonDir, "slop.json") };
+  const worktree = git(["rev-parse", "--show-toplevel"]);
+  const root = basename(commonDir) === ".git" ? resolve(commonDir, "..") : worktree ?? commonDir;
+  return { root, worktree: worktree ?? root, linkPath: join4(commonDir, "slop.json") };
 }
 function requireRepo() {
   const repo = findRepo();
@@ -23845,17 +23855,13 @@ function registerProjectCommands(program3) {
     const statuses = await api.put(`/projects/${target.id}/statuses/order`, { ids: refs.map((ref) => columnOf(target, ref).id) });
     emit(statuses, () => list(statuses));
   });
-  project.command("update").description("Change the linked project's name, description or theme.").option("-p, --project <key>", "project key (default: the linked project)").option("-n, --name <name>").option("-d, --description <text>").option("--theme <theme>", `${PROJECT_THEMES.join(" | ")} | none`).action(async (options) => {
+  project.command("update").description("Change the linked project's name or description.").option("-p, --project <key>", "project key (default: the linked project)").option("-n, --name <name>").option("-d, --description <text>").action(async (options) => {
     const api = authedApi();
     const target = await resolveProject(api, options.project);
-    const theme = options.theme === void 0 ? void 0 : options.theme === "none" ? null : options.theme;
-    if (theme && !PROJECT_THEMES.includes(theme)) {
-      throw new CliError(`Unknown theme "${theme}"`, `use one of: ${PROJECT_THEMES.join(", ")}, none`);
-    }
-    if (options.name === void 0 && options.description === void 0 && theme === void 0) {
-      throw new CliError("Nothing to change", "pass --name, --description or --theme");
+    if (options.name === void 0 && options.description === void 0) {
+      throw new CliError("Nothing to change", "pass --name or --description");
     }
-    const updated = await api.patch(`/projects/${target.id}`, { name: options.name, description: options.description, theme });
+    const updated = await api.patch(`/projects/${target.id}`, { name: options.name, description: options.description });
     emit(updated, () => `Updated ${updated.key}  ${updated.name}`);
   });
   project.command("create <name>").description("Create a project.").option("-k, --key <key>", "task key prefix, e.g. WEB (default: derived from the name)").option("-d, --description <text>", "what the project is").option("--org <slug-or-id>", "which org, if you belong to several").action(async (name, options) => {
@@ -23891,10 +23897,11 @@ Try: slop task create "My first task"`);
   program3.command("status").description("Show what this repository is linked to.").action(async () => {
     const repo = findRepo();
     const link = repo ? readLink(repo) : null;
+    const where = !repo ? "" : repo.worktree === repo.root ? repo.root : `${repo.worktree}  (worktree of ${repo.root})`;
     emit(
-      { repo: repo?.root ?? null, link },
-      () => !repo ? "Not inside a git repository." : !link ? `${repo.root}
-not linked. Run: slop link <PROJECT_KEY>` : `${repo.root}
+      { repo: repo?.root ?? null, worktree: repo?.worktree ?? null, link },
+      () => !repo ? "Not inside a git repository." : !link ? `${where}
+not linked. Run: slop link <PROJECT_KEY>` : `${where}
 linked to ${link.projectKey}  ${link.projectName}  (${link.baseUrl})`
     );
   });
@@ -24253,7 +24260,7 @@ ${written.map((path3) => `  ${path3}`).join("\n")}`);
 }
 
 // src/index.ts
-var program2 = new Command().name("slop").description("Slopware Tasks from the terminal. Everything a person can do on the board, an agent can do here.").version("0.1.1").option("--json", "machine-readable output: JSON on stdout, errors as JSON on stderr").hook("preAction", (_, action) => setJsonMode(Boolean(action.optsWithGlobals().json))).showHelpAfterError("(run with --help for usage)");
+var program2 = new Command().name("slop").description("Slopware Tasks from the terminal. Everything a person can do on the board, an agent can do here.").version("0.1.2").option("--json", "machine-readable output: JSON on stdout, errors as JSON on stderr").hook("preAction", (_, action) => setJsonMode(Boolean(action.optsWithGlobals().json))).showHelpAfterError("(run with --help for usage)");
 registerAuthCommands(program2);
 registerProjectCommands(program2);
 registerSessionCommands(program2, registerTaskCommands(program2));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "slopwaresystems",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "private": false,
   "description": "slop: the Slopware Tasks board from the terminal, for people and coding agents.",
   "type": "module",