@empirical-gauzza/cli 1.0.40 → 1.0.41

package/bin/empirical.js

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 
 'use strict';
 

package/lib/constants.js

@@ -352,13 +352,15 @@ A new interview is charged. \`setup abandon\` stops one but does not return what
     empirical workspace shape show --workspace-id <id>
     empirical workspace shape add-type "Reviewer" --workspace-id <id> --statuses "Not Yet Invited, Invited, Call Completed (done)" --fields "Email:text:required; Open to a call:select:Yes|No|Not asked; Wave:number" [--apply]
     empirical workspace shape add-status <type-key> "Declined" --done --workspace-id <id> [--apply]
+    empirical workspace shape add-status <type-key> "Call Scheduled" --after form_submitted --workspace-id <id> [--apply]
+    empirical workspace shape reorder-statuses <type-key> new,form_submitted,call_scheduled,call_held,won --workspace-id <id> [--apply]
     empirical workspace shape add-field <type-key> "Wave" --kind number --workspace-id <id> [--apply]
     empirical workspace shape edit --file <edit.json> [--mapping-file <m.json>] --workspace-id <id> [--apply]
     empirical workspace shape set --file <shape.json> --workspace-id <id> [--apply]
 
 The interview is the guided way and is charged. These are the direct way: you name the change and nothing is charged. Every change is a dry run until you add \`--apply\`: it is checked against the workspace's current shape, the result is printed, and with \`--apply\` it is saved only if the shape is still the one that was shown. You must manage the workspace; \`--apply\` needs \`--workspace-id\` written out, so a stale directory binding cannot aim a change at the wrong workspace.
 
-\`add-type\` on a workspace with no shape yet also needs \`--purpose "what this workspace is for"\` and creates its first shape. A kind of item with statuses must mark one as finished with \`(done)\`, and takes at most six fields. Field kinds: text, longText, number, date, select, multiSelect, person, link, url. \`--category\` and \`--node-type\` say how an item is stored as a memory (default project and entity). Keys are made from labels once and never change; refer to a type or status later by its key, which \`show\` prints in brackets.
+\`add-type\` on a workspace with no shape yet also needs \`--purpose "what this workspace is for"\` and creates its first shape. A kind of item with statuses must mark one as finished with \`(done)\`, and takes at most six fields. Field kinds: text, longText, number, date, select, multiSelect, person, link, url. \`--category\` and \`--node-type\` say how an item is stored as a memory (default project and entity). Keys are made from labels once and never change; refer to a type or status later by its key, which \`show\` prints in brackets. A new status goes just before the first finished status unless \`--after <key>\` or \`--before <key>\` places it; \`reorder-statuses\` takes every status key of the type once, in the new order (the first status is where new items start). Neither moves any item.
 
 \`edit\` takes the server's merge format: \`{"itemTypes":{"add":[...],"update":[{"key":"reviewer","statuses":{"add":[{"label":"Declined","isDone":true}]}}],"remove":["old-type"]}}\`. Removing or renaming something that has stored values needs \`--mapping-file\` saying where those values go. To save an item into the shape: \`empirical memory record --category lead --summary "..." --item-type reviewer --item-status invited --field email=a@b.com\` (run with \`EMPIRICAL_WORKSPACE_ID=<id>\` or after \`workspace use\`).
 

package/lib/help.js

@@ -53,7 +53,7 @@ function showHelp() {
   log('                                                Re-shape a team workspace you manage by interview. Without --workspace-id it');
   log('                                                confirms the workspace bound to this directory with you, at a terminal only;');
   log('                                                in a script or with --accept-cost it needs --workspace-id. A new interview is charged');
-  log('  empirical workspace shape show|set|edit|add-type|add-status|add-field --workspace-id <id> ...');
+  log('  empirical workspace shape show|set|edit|add-type|add-status|add-field|reorder-statuses --workspace-id <id> ...');
   log('                                                Edit the item types, statuses and fields of a workspace by hand, with no interview and no');
   log('                                                charge. A dry run until --apply. Details: empirical doc workspace');
   log('  empirical workspace invite create [--role reader|writer|manager] [--expires-in-days <n>] [--max-uses <n>]');

package/lib/shapeCommands.js

@@ -6,7 +6,8 @@
 //   empirical workspace shape set       --workspace-id <id> --file <shape.json> [--apply]
 //   empirical workspace shape edit      --workspace-id <id> --file <edit.json>  [--apply]
 //   empirical workspace shape add-type  --workspace-id <id> <label> [--statuses "A,B,C (done)"] ...
-//   empirical workspace shape add-status --workspace-id <id> <type-key> <label> [--done]
+//   empirical workspace shape add-status --workspace-id <id> <type-key> <label> [--done] [--after <key> | --before <key>]
+//   empirical workspace shape reorder-statuses --workspace-id <id> <type-key> <key,key,...>
 //   empirical workspace shape add-field  --workspace-id <id> <type-key> <label> --kind <kind> ...
 //
 // The interview is charged (100 Empirical Tokens, plus 25 per change to a draft) and takes nine
@@ -16,23 +17,24 @@
 //
 // Every change is a DRY RUN until --apply. A change goes to /shape/preview first, which validates it
 // against the active shape and returns a confirmDigest; --apply sends that digest back, so an edit
-// is only ever applied to the shape that was shown. The commands here only ADD (a type, a status, a
-// field); removing needs a mapping for the stored values, which `edit --mapping-file` accepts.
+// is only ever applied to the shape that was shown. The commands here ADD (a type, a status, a field)
+// and REORDER statuses; removing needs a mapping for the stored values, which `edit --mapping-file`
+// accepts. A new status goes just before the first finished one unless --after or --before says where.
 
 const fs = require('fs');
 const { log, warn } = require('./ui');
 const { httpJson } = require('./http');
 const { parseOption, parseFlag } = require('./env');
 
-const SHAPE_ACTIONS = ['show', 'set', 'edit', 'add-type', 'add-status', 'add-field'];
+const SHAPE_ACTIONS = ['show', 'set', 'edit', 'add-type', 'add-status', 'add-field', 'reorder-statuses'];
 const FIELD_KINDS = ['text', 'longText', 'number', 'date', 'select', 'multiSelect', 'person', 'link', 'url'];
 const VALUE_OPTIONS = new Set([
   '--workspace-id', '--file', '--mapping-file', '--purpose', '--plural', '--category', '--node-type',
-  '--icon', '--color', '--statuses', '--fields', '--nest-under', '--kind', '--options'
+  '--icon', '--color', '--statuses', '--fields', '--nest-under', '--kind', '--options', '--after', '--before'
 ]);
 
 const SHAPE_USAGE = [
-  'Usage: empirical workspace shape <show|set|edit|add-type|add-status|add-field> --workspace-id <id> ...',
+  'Usage: empirical workspace shape <show|set|edit|add-type|add-status|add-field|reorder-statuses> --workspace-id <id> ...',
   '  show                                          print the workspace\'s item types, statuses and fields',
   '  set --file <shape.json> [--apply]             give a workspace with no shape its first shape',
   '  edit --file <edit.json> [--mapping-file <m.json>] [--apply]',
@@ -40,7 +42,9 @@ const SHAPE_USAGE = [
   '  add-type <label> [--statuses "A,B,C (done)"] [--fields "Email:text:required;Wave:number"]',
   '           [--plural <label>] [--category <cat>] [--node-type <type>] [--icon <i>] [--color <c>]',
   '           [--nest-under <type-key,...>] [--purpose <text>]   (--purpose only when the workspace has no shape yet)',
-  '  add-status <type-key> <label> [--done]',
+  '  add-status <type-key> <label> [--done] [--after <status-key> | --before <status-key>]',
+  '                                                without --after/--before it goes just before the first finished status',
+  '  reorder-statuses <type-key> <key,key,...>     every status key of that type once, in the new order',
   '  add-field <type-key> <label> [--kind text|longText|number|date|select|multiSelect|person|link|url]',
   '            [--required] [--options "Yes|No|Not asked"]',
   'Changes are a dry run until you add --apply. Running the interview instead: `empirical workspace shape` with no action.'
@@ -116,8 +120,15 @@ function buildTypeFromFlags(args, label) {
   return type;
 }
 
-function buildAddStatusEdit(typeKey, label, isDone) {
-  return { itemTypes: { update: [{ key: typeKey, statuses: { add: [isDone ? { label, isDone: true } : { label }] } }] } };
+function buildAddStatusEdit(typeKey, label, isDone, position = {}) {
+  const status = isDone ? { label, isDone: true } : { label };
+  if (position.after) status.after = position.after;
+  if (position.before) status.before = position.before;
+  return { itemTypes: { update: [{ key: typeKey, statuses: { add: [status] } }] } };
+}
+
+function buildReorderStatusesEdit(typeKey, keys) {
+  return { itemTypes: { update: [{ key: typeKey, statuses: { order: keys } }] } };
 }
 
 function buildAddFieldEdit(typeKey, field) {
@@ -278,8 +289,18 @@ async function runManualShapeCommand({ args, baseUrl, authHeaders, resolveBound
 
   if (action === 'add-status') {
     const [typeKey, label] = positionals(args);
-    if (!typeKey || !label) throw new Error('Usage: empirical workspace shape add-status <type-key> <label> [--done] --workspace-id <id> [--apply]');
-    return previewAndMaybeApply({ baseUrl, workspaceId, authHeaders, edit: buildAddStatusEdit(typeKey, label, parseFlag(args, '--done')), mapping, apply, asJson });
+    if (!typeKey || !label) throw new Error('Usage: empirical workspace shape add-status <type-key> <label> [--done] [--after <key> | --before <key>] --workspace-id <id> [--apply]');
+    const after = parseOption(args, '--after', '');
+    const before = parseOption(args, '--before', '');
+    if (after && before) throw new Error('Use --after or --before, not both.');
+    return previewAndMaybeApply({ baseUrl, workspaceId, authHeaders, edit: buildAddStatusEdit(typeKey, label, parseFlag(args, '--done'), { after, before }), mapping, apply, asJson });
+  }
+
+  if (action === 'reorder-statuses') {
+    const [typeKey, list] = positionals(args);
+    const keys = String(list || '').split(',').map((k) => k.trim()).filter(Boolean);
+    if (!typeKey || !keys.length) throw new Error('Usage: empirical workspace shape reorder-statuses <type-key> <key,key,...> --workspace-id <id> [--apply]   (`shape show` prints the keys)');
+    return previewAndMaybeApply({ baseUrl, workspaceId, authHeaders, edit: buildReorderStatusesEdit(typeKey, keys), mapping, apply, asJson });
   }
 
   if (action === 'add-field') {
@@ -307,6 +328,7 @@ module.exports = {
   parseFieldList,
   buildTypeFromFlags,
   buildAddStatusEdit,
+  buildReorderStatusesEdit,
   buildAddFieldEdit,
   formatShape,
   runManualShapeCommand

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@empirical-gauzza/cli",
-  "version": "1.0.40",
+  "version": "1.0.41",
   "description": "Persistent cross-tool memory for AI agents. Give Claude Code, Codex, Copilot, Cursor, and ChatGPT one shared memory: save project context once, recall it everywhere via CLI or MCP.",
   "keywords": [
     "memory",