neuvikon 0.2.23 → 0.2.24

package/README.md

@@ -42,6 +42,9 @@ as being worked on, by whom, with which tool.
 | `neuvikon logout` | Revoke this machine's token and forget it |
 | `neuvikon pages [--ticket EWWQ-1]` | List the ticket's project pages, flattened to plain text |
 | `neuvikon pages update "Title" [--ticket EWWQ-1]` | Create or update a page by title, body on stdin (or `--text`) |
+| `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 |
 
 `start` also accepts the ticket on stdin, and pulls the reference out of it:
 
@@ -74,6 +77,28 @@ always has. Without a detected agent, or on a platform/terminal this can't
 drive, it just prints the ticket ref and that command for you to paste by
 hand.
 
+## Filing what you notice along the way
+
+Working a ticket turns up other things — a bug, a chunk of related work that
+doesn't belong in the same diff. Rather than silently expanding scope or
+silently dropping it, an agent can file it as its own ticket:
+
+```sh
+npx neuvikon create "Invite emails aren't localized" --ticket EWWQ-1
+```
+
+Or as a sub-ticket, if it's really part of finishing the one you're on:
+
+```sh
+npx neuvikon create "Add French copy" --sub --ticket EWWQ-1
+```
+
+`--parent NS-12` files it under a different ticket instead. Sub-tickets are
+one level deep — a ticket that's already a sub-ticket can't take `--sub`
+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.
+
 ## Project pages
 
 An agent's most useful output often isn't the ticket, it's what it learned

package/dist/index.mjs

@@ -248,12 +248,12 @@ function fail(message, hint) {
 }
 //#endregion
 //#region src/commands/board.ts
-function requireCredentials$3() {
+function requireCredentials$4() {
 	const credentials = readCredentials();
 	if (!credentials) fail("Not logged in.", "Run `npx neuvikon login` first.");
 	return credentials;
 }
-function resolveTicketRef$3(flags) {
+function resolveTicketRef$4(flags) {
 	const ref = flags.get("ticket") ?? readSession()?.ticket;
 	if (!ref) fail("No ticket to look up a board for.", "Pass --ticket EWWQ-1, or run this where `npx neuvikon start` is already tracking one.");
 	return ref;
@@ -263,8 +263,8 @@ function resolveTicketRef$3(flags) {
 * a column name — boards vary per project, and some have no "done" at all.
 */
 async function board(flags) {
-	const credentials = requireCredentials$3();
-	const ticketRef = resolveTicketRef$3(flags);
+	const credentials = requireCredentials$4();
+	const ticketRef = resolveTicketRef$4(flags);
 	let result;
 	try {
 		result = await post(credentials.url, "/api/agent/board", {
@@ -311,20 +311,20 @@ async function readStdin() {
 }
 //#endregion
 //#region src/commands/comment.ts
-function requireCredentials$2() {
+function requireCredentials$3() {
 	const credentials = readCredentials();
 	if (!credentials) fail("Not logged in.", "Run `npx neuvikon login` first.");
 	return credentials;
 }
-function resolveTicketRef$2(flags) {
+function resolveTicketRef$3(flags) {
 	const ref = flags.get("ticket") ?? readSession()?.ticket;
 	if (!ref) fail("No ticket to comment on.", "Pass --ticket EWWQ-1, or run this where `npx neuvikon start` is already tracking one.");
 	return ref;
 }
 /** A note on a ticket that doesn't move it — e.g. explaining a handoff mid-ticket. */
 async function comment(flags) {
-	const credentials = requireCredentials$2();
-	const ticketRef = resolveTicketRef$2(flags);
+	const credentials = requireCredentials$3();
+	const ticketRef = resolveTicketRef$3(flags);
 	const text = (flags.get("text") || await readStdin()).trim();
 	if (!text) fail("No comment text given.", "Pipe the comment in on stdin, or pass --text.");
 	try {
@@ -344,6 +344,79 @@ async function comment(flags) {
 	success(`Commented on ${ticketRef}`);
 }
 //#endregion
+//#region src/commands/create.ts
+const TYPES = /* @__PURE__ */ new Set(["feature", "bug"]);
+const PRIORITIES = /* @__PURE__ */ new Set([
+	"low",
+	"medium",
+	"high",
+	"urgent"
+]);
+function requireCredentials$2() {
+	const credentials = readCredentials();
+	if (!credentials) fail("Not logged in.", "Run `npx neuvikon login` first.");
+	return credentials;
+}
+function resolveTicketRef$2(flags) {
+	const ref = flags.get("ticket") ?? readSession()?.ticket;
+	if (!ref) fail("No ticket to file this against.", "Pass --ticket EWWQ-1, or run this where `npx neuvikon start` is already tracking one.");
+	return ref;
+}
+/**
+* `--sub` means "a sub-ticket of the ticket I'm already on"; `--parent`
+* names a different one. Not both — a new ticket has exactly one parent (or
+* none), and naming it two ways at once is more likely a mistake than intent.
+*/
+function resolveParentRef(flags, ticketRef) {
+	const parentFlag = flags.get("parent");
+	if (parentFlag && flags.has("sub")) fail("Pass --sub or --parent, not both.", `--sub already means "a sub-ticket of ${ticketRef}".`);
+	if (parentFlag) {
+		const [ref] = extractTicketRefs(parentFlag);
+		if (!ref) fail(`"${parentFlag}" is not a ticket reference.`, "Expected something like EWWQ-1.");
+		return ref;
+	}
+	return flags.has("sub") ? ticketRef : void 0;
+}
+/**
+* An agent filing something it noticed that isn't the ticket it's on — a bug
+* spotted mid-fix, a chunk of follow-up work worth tracking on its own.
+* Without `--sub`/`--parent` it's a new standalone ticket in the same
+* project; with one of them, a sub-ticket one level deep, same as the app's
+* own "+ sub-ticket" control.
+*/
+async function create(flags, positional) {
+	const credentials = requireCredentials$2();
+	const ticketRef = resolveTicketRef$2(flags);
+	const parentRef = resolveParentRef(flags, ticketRef);
+	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.");
+	const priority = flags.get("priority");
+	if (priority && !PRIORITIES.has(priority)) fail(`Unknown priority "${priority}".`, "Expected low, medium, high, or urgent.");
+	const description = (flags.get("description") || await readStdin()).trim() || void 0;
+	let result;
+	try {
+		result = await post(credentials.url, "/api/agent/tickets/create", {
+			token: credentials.token,
+			ticketRef,
+			title,
+			description,
+			type,
+			priority,
+			parentRef
+		});
+	} catch (error) {
+		if (error instanceof NetworkError) fail("Could not reach Neuvikon.");
+		if (error instanceof ApiError) {
+			if (error.status === 401) fail(error.message, "Run `npx neuvikon login` again.");
+			fail(error.message);
+		}
+		throw error;
+	}
+	success(result.parentRef ? `Filed ${bold(result.ref)} as a sub-ticket of ${bold(result.parentRef)}` : `Filed ${bold(result.ref)}`);
+}
+//#endregion
 //#region src/usage.ts
 /**
 * Sums token usage out of a JSONL agent transcript, starting from `offset`.
@@ -774,6 +847,42 @@ creating a duplicate, so reuse a title for anything you're extending.
 Reference another page by writing its title in double brackets, e.g.
 \`[[Auth Flow]]\` — it becomes a real link if that page already exists.
 
+## Filing work you notice along the way
+
+Working a ticket often turns up something else — a bug you tripped over, a
+piece of real work that doesn't belong in this diff. Don't silently fix it if
+it's unrelated, and don't silently drop it either — file it:
+
+    npx neuvikon create "Session cookie missing Secure flag" --ticket EWWQ-1
+
+Decide sub-ticket vs. standalone ticket by whether it's part of finishing
+*this* ticket:
+
+- Still part of this ticket — something that has to happen before it's really
+  done, e.g. "write tests for the new endpoint" — file it as a sub-ticket of
+  the one you're on:
+
+      npx neuvikon create "Add tests for the invite endpoint" --sub --ticket EWWQ-1
+
+- Not part of it — a bug, tech debt, an idea that has nothing to do with
+  finishing this ticket — file it as its own ticket and get back to work.
+  Fixing it now just because you're already in the file is how one ticket
+  quietly becomes three:
+
+      npx neuvikon create "Invite emails aren't localized" --ticket EWWQ-1
+
+  \`--parent OTHER-4\` instead of \`--sub\` files it under a different ticket,
+  if that's genuinely where it belongs instead of standing alone.
+
+A sub-ticket can't itself have sub-tickets — if the ticket you're on is
+already one, \`--sub\` will fail; file a standalone ticket instead and say in
+its description what it's related to.
+
+This is judgment, not a rule to apply every turn: a one-line fix in a file
+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.
+
 Before you change the ticket's status, look at what columns this project's
 board actually has — they vary per project, and there may be no column
 literally called "Done":
@@ -1707,7 +1816,11 @@ ${bold("Board")}
                                    Move the ticket to a specific column, with why
   npx neuvikon comment --text "Handing off, blocked on design"
                                    Leave a note without changing the column
-  All three accept --ticket EWWQ-1 instead of relying on a tracked session.
+  npx neuvikon create "Invite emails aren't localized"
+                                   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)
+  All four accept --ticket EWWQ-1 instead of relying on a tracked session.
 
 ${bold("Project pages")}
   npx neuvikon pages                        List the current ticket's project pages
@@ -1768,6 +1881,7 @@ async function main() {
 		case "board": return board(flags);
 		case "move": return move(flags);
 		case "comment": return comment(flags);
+		case "create": return create(flags, positional);
 		case void 0:
 		case "help":
 		case "--help":

package/package.json

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