neuvikon 0.2.32 → 0.2.33

package/README.md

@@ -45,6 +45,10 @@ as being worked on, by whom, with which tool.
 | `neuvikon create "Title" [--ticket EWWQ-1]` | File something you noticed as a new ticket, same project |
 | `neuvikon create "Title" --sub [--ticket EWWQ-1]` | ...or as a sub-ticket of the ticket you're on |
 | `neuvikon create "Title" --parent NS-12` | ...or of a different ticket entirely |
+| `neuvikon update --assignee Ogulcan [--ticket EWWQ-1]` | Change a ticket's fields: assignee, team, sprint, type, priority, labels, title, description |
+| `neuvikon board [--ticket EWWQ-1]` | This project's columns, and where the ticket sits |
+| `neuvikon move --column "Code Review" --comment "why"` | Move the ticket to a column, with a reason |
+| `neuvikon comment --text "..."` | Leave a note without moving the ticket |
 
 `start` also accepts the ticket on stdin, and pulls the reference out of it:
 
@@ -99,6 +103,39 @@ itself, same restriction the app's own "+ sub-ticket" control has. Either way
 the ticket you were on gets an automated comment pointing at the new one, so
 nothing gets filed invisibly.
 
+## Changing a ticket
+
+Anything the board's ticket dialog can change, `update` can change from a
+terminal — so an agent can carry out "assign this to Ogulcan and bump it to
+high" without anyone opening the app:
+
+```sh
+npx neuvikon update --ticket EWWQ-1 --assignee Ogulcan --priority high
+```
+
+One flag per field, any number at once: `--assignee`, `--team`, `--sprint`,
+`--type` (`feature`/`bug`), `--priority` (`low`/`medium`/`high`/`urgent`),
+`--labels` (comma-separated, replaces the whole set), `--title`,
+`--description`.
+
+People, teams and sprints are named the way you'd say them out loud — a first
+name, an email, `"Sprint 1"` — and resolved on the server, which refuses an
+ambiguous name instead of guessing at one. `none` clears one of those three,
+an empty value clears labels or the description, and `--description -` takes
+it from stdin:
+
+```sh
+npx neuvikon update --ticket EWWQ-1 --assignee none --labels ""
+
+npx neuvikon update --ticket EWWQ-1 --description - <<'EOF'
+What this ticket actually turned out to be about.
+EOF
+```
+
+Being assigned a ticket this way notifies the assignee exactly as the board
+does. Two things `update` won't do: move the ticket to another column (that's
+`move`, which requires a reason) or delete it.
+
 ## Project pages
 
 An agent's most useful output often isn't the ticket, it's what it learned

package/dist/index.mjs

@@ -373,7 +373,7 @@ async function comment(flags) {
 }
 //#endregion
 //#region src/commands/create.ts
-const TYPES = /* @__PURE__ */ new Set(["feature", "bug"]);
+const TYPES$1 = /* @__PURE__ */ new Set(["feature", "bug"]);
 const PRIORITIES$1 = /* @__PURE__ */ new Set([
 	"low",
 	"medium",
@@ -419,12 +419,14 @@ async function create(flags, positional) {
 	const title = flags.get("title") ?? positional[0];
 	if (!title) fail("A ticket title is required.", `Pass --title "Invite emails aren't localized", or give it as the first argument.`);
 	const type = flags.get("type");
-	if (type && !TYPES.has(type)) fail(`Unknown type "${type}".`, "Expected feature or bug.");
+	if (type && !TYPES$1.has(type)) fail(`Unknown type "${type}".`, "Expected feature or bug.");
 	const priority = flags.get("priority");
 	if (priority && !PRIORITIES$1.has(priority)) fail(`Unknown priority "${priority}".`, "Expected low, medium, high, or urgent.");
 	const description = (flags.get("description") || await readStdin()).trim() || void 0;
 	const assignee = flags.get("assignee");
 	const sprint = flags.get("sprint");
+	const labelsFlag = flags.get("labels");
+	const labels = labelsFlag ? labelsFlag.split(",").map((label) => label.trim()).filter(Boolean) : void 0;
 	let result;
 	try {
 		result = await post(credentials.url, "/api/agent/tickets/create", {
@@ -434,6 +436,7 @@ async function create(flags, positional) {
 			description,
 			type,
 			priority,
+			labels,
 			parentRef,
 			assignee,
 			sprint
@@ -961,6 +964,35 @@ you're already touching doesn't need a ticket, and not everything you notice
 belongs on the board. File it when it's something the team would actually
 want to see and decide on — not for every passing thought.
 
+## Changing a ticket
+
+Every field the board's own ticket dialog can change, you can change from
+here — when the user asks for it, or when what you learned working the ticket
+makes its own fields wrong:
+
+    npx neuvikon update --ticket EWWQ-1 --assignee Ogulcan --priority high
+
+One flag per field, as many at once as you like: \`--assignee\`, \`--team\`,
+\`--sprint\`, \`--type\` (feature or bug), \`--priority\` (low, medium, high,
+urgent), \`--labels\` (comma-separated, replaces the whole set), \`--title\`,
+\`--description\`. People, teams and sprints are named the way a person says
+them and resolved on the server, which refuses an ambiguous name instead of
+guessing — so pass through what the user actually said rather than an id.
+
+\`none\` clears a reference, an empty value clears free text, and
+\`--description -\` reads stdin, for one too long to put on the command line:
+
+    npx neuvikon update --ticket EWWQ-1 --assignee none --labels ""
+
+    npx neuvikon update --ticket EWWQ-1 --description - <<'EOF'
+    What this ticket actually turned out to be about.
+    EOF
+
+Two changes \`update\` deliberately won't make: moving the ticket to another
+column (that's \`move\`, which makes you say why) and deleting it. And don't
+retitle or rewrite a ticket just to tidy it up — do that when it's actually
+wrong or the user asked, and say what you changed.
+
 ## Auditing the project on request
 
 Sometimes the ask isn't "work this ticket" but "find what's wrong with this
@@ -1919,14 +1951,17 @@ async function stop(flags) {
 }
 //#endregion
 //#region src/commands/update.ts
+const TYPES = /* @__PURE__ */ new Set(["feature", "bug"]);
 const PRIORITIES = /* @__PURE__ */ new Set([
 	"low",
 	"medium",
 	"high",
 	"urgent"
 ]);
-/** What `--assignee none` / `--sprint none` means: clear the field. */
+/** What `--assignee none` / `--sprint none` / `--team none` means: clear the field. */
 const NONE = "none";
+/** `--description -` reads stdin, so a heredoc can carry a long one. */
+const STDIN = "-";
 function requireCredentials() {
 	const credentials = readCredentials();
 	if (!credentials) fail("Not logged in.", "Run `npx neuvikon login` first.");
@@ -1941,23 +1976,46 @@ function resolveTicketRef(flags) {
 function resolveClearable(flags, name) {
 	const value = flags.get(name);
 	if (value === void 0) return void 0;
+	if (!value) fail(`--${name} needs a value.`, `Pass a name, or "${NONE}" to clear it.`);
 	return value.toLowerCase() === NONE ? null : value;
 }
+/** A flag with a fixed set of values — caught here so the error names the choices. */
+function resolveChoice(flags, name, allowed, expected) {
+	const value = flags.get(name);
+	if (value === void 0) return void 0;
+	if (!allowed.has(value)) fail(`Unknown ${name} "${value}".`, `Expected ${expected}.`);
+	return value;
+}
+async function resolveDescription(flags) {
+	const value = flags.get("description");
+	if (value !== STDIN) return value;
+	const piped = await readStdin();
+	if (!piped.trim()) fail("Nothing arrived on stdin for --description.", `Pipe the text in, or pass --description "the text" directly.`);
+	return piped;
+}
 /**
-* Changes fields on a ticket that already exists, e.g.
-* `npx neuvikon update --ticket NS-91 --assignee Ogulcan --sprint "Sprint 1"`.
-* `--assignee none` / `--sprint none` clears that field instead of setting it.
+* Everything the board's ticket dialog can change, from a terminal, e.g.
+* `npx neuvikon update --ticket NS-91 --assignee Ogulcan --priority high`.
+* People, sprints and teams are named the way a person would say them and
+* resolved server-side; `none` clears one of those three, and an empty value
+* clears labels or the description.
+*
+* Which column the ticket sits in is `move`'s job — that one needs a reason.
 */
 async function update(flags) {
 	const credentials = requireCredentials();
 	const ticketRef = resolveTicketRef(flags);
 	const assignee = resolveClearable(flags, "assignee");
 	const sprint = resolveClearable(flags, "sprint");
-	const priority = flags.get("priority");
-	if (priority && !PRIORITIES.has(priority)) fail(`Unknown priority "${priority}".`, "Expected low, medium, high, or urgent.");
+	const team = resolveClearable(flags, "team");
+	const type = resolveChoice(flags, "type", TYPES, "feature or bug");
+	const priority = resolveChoice(flags, "priority", PRIORITIES, "low, medium, high, or urgent");
 	const labelsFlag = flags.get("labels");
 	const labels = labelsFlag !== void 0 ? labelsFlag.split(",").map((label) => label.trim()).filter(Boolean) : void 0;
-	if (assignee === void 0 && sprint === void 0 && priority === void 0 && labels === void 0) fail("Nothing to update.", "Pass at least one of --assignee, --sprint, --priority, --labels.");
+	const title = flags.get("title");
+	if (title !== void 0 && !title.trim()) fail("A ticket can't have an empty title.", `Pass --title "What it should say instead".`);
+	const description = await resolveDescription(flags);
+	if (assignee === void 0 && sprint === void 0 && team === void 0 && type === void 0 && priority === void 0 && labels === void 0 && title === void 0 && description === void 0) fail("Nothing to update.", "Pass at least one of --assignee, --sprint, --team, --type, --priority, --labels, --title, --description.");
 	let result;
 	try {
 		result = await post(credentials.url, "/api/agent/tickets/update", {
@@ -1965,8 +2023,12 @@ async function update(flags) {
 			ticketRef,
 			assignee,
 			sprint,
+			team,
+			type,
 			priority,
-			labels
+			labels,
+			title,
+			description
 		});
 	} catch (error) {
 		if (error instanceof NetworkError) fail("Could not reach Neuvikon.");
@@ -2002,11 +2064,13 @@ ${bold("Board")}
                                    File something you noticed as its own ticket, same project
   npx neuvikon create "Add French copy" --sub
                                    ...or as a sub-ticket (--sub for this one, --parent NS-12 for another)
-  npx neuvikon create "..." --assignee Ogulcan --sprint "Sprint 1"
-                                   File it already assigned and/or planned in a sprint
-  npx neuvikon update --assignee Ogulcan --sprint "Sprint 1" --priority high
-                                   Change assignee, sprint, priority, or labels on an existing ticket
-                                   ("none" clears --assignee/--sprint)
+  npx neuvikon create "..." --assignee Ogulcan --sprint "Sprint 1" --labels "api,auth"
+                                   File it already assigned, planned and labelled
+  npx neuvikon update --assignee Ogulcan --priority high
+                                   Change any field on an existing ticket: --assignee, --team,
+                                   --sprint, --type, --priority, --labels, --title, --description
+                                   ("none" clears assignee/team/sprint, "" clears labels/description,
+                                   --description - reads stdin)
   All five accept --ticket EWWQ-1 instead of relying on a tracked session.
 
 ${bold("Project pages")}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "neuvikon",
-  "version": "0.2.32",
+  "version": "0.2.33",
   "description": "Tell Neuvikon which ticket your coding agent is working on.",
   "keywords": [
     "neuvikon",