@stage5/lumine 0.2.30 → 0.2.31

package/README.md

@@ -181,7 +181,7 @@ lumine admin subject feature 123 --json
 lumine admin subject unfeature 123 --json
 lumine admin featured reorder --subject-ids 30,20,10 --json
 lumine admin brief --days 3 --json
-lumine admin notable add Minecrarft_guy --json
+lumine admin notable add Minecrarft_guy --note "Created 8 thoughtful subjects and helped peers in 23 comments this window." --json
 lumine admin post recommend comment:456 --anyone-can-reward --reward-twinkles 3 --json
 lumine admin post reward comment:456 --twinkles 3 --json
 lumine admin daily-run complete --json

package/lib/admin.js

@@ -6,6 +6,7 @@ import { requestJson } from "./http.js";
 const MAX_EDITORIAL_FILE_BYTES = 256 * 1024;
 const MAX_COMPOSED_COMMENT_FILE_BYTES = 64 * 1024;
 const MAX_COMPOSED_COMMENT_LENGTH = 10_000;
+const MAX_NOTABLE_NOTE_LENGTH = 2_000;
 
 // Operator-composed persona comment text (plain UTF-8, not JSON). The agent
 // writes the comment in the bot's persona itself; the server never invokes
@@ -178,10 +179,7 @@ export async function adminCommand(options) {
   return result;
 }
 
-export function assertComposedCommentDraftResult({
-  result,
-  expectedContent,
-}) {
+export function assertComposedCommentDraftResult({ result, expectedContent }) {
   const draft = result?.data?.draft;
   if (
     draft?.decision === "draft" &&
@@ -589,12 +587,26 @@ export function parseAdminOperation(options) {
     const rawTarget = String(target || "").trim();
     if (!rawTarget) {
       throw cliValidationError(
-        "Usage: lumine admin notable add <userId|username>.",
+        "Usage: lumine admin notable add <userId|username> --note <text>.",
       );
     }
     const body = /^\d+$/.test(rawTarget)
       ? { userId: parseRequiredInteger(rawTarget, "user ID", 1) }
       : { username: rawTarget };
+    // --note records what made them notable (the management page's reason
+    // column). On an already-listed user it updates the stored reason.
+    const note = String(options.note || "").trim();
+    if (!note) {
+      throw cliValidationError(
+        "Pass what made this user notable with --note <text>.",
+      );
+    }
+    if (note.length > MAX_NOTABLE_NOTE_LENGTH) {
+      throw cliValidationError(
+        `A notable-user note must be at most ${MAX_NOTABLE_NOTE_LENGTH} characters.`,
+      );
+    }
+    body.note = note;
     return writeOperation(
       "notable.add",
       "POST",

package/lib/commands.js

@@ -2528,7 +2528,7 @@ export function printHelp() {
   lumine admin comment post --draft-id <id> [--json]
   lumine admin comment edit <comment-id> --file <comment.md> [--json]
   lumine admin brief [--days <1..30>] [--json]
-  lumine admin notable add <user-id|username> [--json]
+  lumine admin notable add <user-id|username> --note <text> [--json]
   lumine admin audit [list] [--run current|last|<run-id>] [--target <target>] [--actions <a,b>] [--full] [--cursor <cursor>] [--json]
 
 Examples:
@@ -2591,7 +2591,7 @@ Options:
   --description <text>  Build description for new/describe
   --no-description      Skip New description or clear with describe
   --summary <text>      Save summary
-  --note <text>         Message attached to a branch suggestion
+  --note <text>         Branch-suggestion message or notable-user rationale
   --cursor <id>         Continue an owner suggestion inbox listing
   --after <date>        Admin subjects: inclusive Unix/ISO creation boundary
   --effort unassigned  Admin subjects: show only unassigned effort

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stage5/lumine",
-  "version": "0.2.30",
+  "version": "0.2.31",
   "description": "Command line tools for launching Lumine builds on Twinkle.",
   "type": "module",
   "bin": {

package/sdk/LUMINE_ADMIN.md

@@ -926,7 +926,7 @@ the same priority, so treat a tied score (or recency) as no signal at all and
 make the call by reading:
 
 - **Choose the lead by argument, not by score or recency.** The best lead is
-  the front event where something is actually *at stake*: a claim with
+  the front event where something is actually _at stake_: a claim with
   reasoning, a question with a position behind it — ideally while another
   member is already responding. A claim plus a reply is a conversation in
   motion; a drawing, a greeting, or a link is a share, and shares belong
@@ -1052,8 +1052,8 @@ type NewsSubmit = NewsStatus; // "success"; newspaper includes revisionNumber
 ```bash
 lumine admin brief --json
 lumine admin brief --days 3 --json
-lumine admin notable add 12647 --json
-lumine admin notable add Minecrarft_guy --json
+lumine admin notable add 12647 --note "Top authored-activity kid of the window: 11 subjects, 61 comments." --json
+lumine admin notable add Minecrarft_guy --note "Helped three new builders debug their projects and gave detailed feedback on five posts." --json
 ```
 
 Read-only management insights for the delegated workflow, windowed since the
@@ -1095,10 +1095,19 @@ farm-signal sections added the same day):
   `isNewUser` marking window-new signups. Use it to find the overlooked and
   rising users the editorial priorities exist for, and propose additions to
   Mikey's Notable Users list in the report. When Mikey approves additions,
-  execute them with `lumine admin notable add <userId|username>` (idempotent —
+  execute them with
+  `lumine admin notable add <userId|username> --note "<specific rationale>"`
+  (idempotent —
   an existing member returns `already_done`; requires the `notable:write`
   scope, audited as `notable.add`, and writes through the management page's
   own canonical service). Without his approval the run only proposes.
+  **Always pass `--note`** with a concrete one-or-two-sentence record of what
+  made them notable — real numbers and specifics from the brief window, not
+  "active user". It lands in the management page's reason column, which is
+  where Mikey later reads why a name is on his list. On an already-listed
+  user, `--note` updates the stored reason (status `success` with
+  `data.reasonUpdated: true`; an identical note stays `already_done` without
+  rewriting its timestamp).
 - `teachers` — the mentor/sage achievement holders (the accounts the website
   titles teacher/headteacher): real classroom teachers, NOT the
   `userType='supermod'` Korean operations staff, whose work-only usage is
@@ -1177,7 +1186,7 @@ type WindowDelta = { current: number; previous: number; delta: number };
 type TeacherInsight = {
   userId: number;
   username: string | null;
-  rank: 'mentor' | 'sage';
+  rank: "mentor" | "sage";
   lastActive: number | null;
   daysSinceActive: number | null;
   subjectsPosted: number;
@@ -1199,7 +1208,7 @@ type InsightsBrief = Success<{
   window: {
     sinceTs: number;
     days: number;
-    source: 'requested' | 'since-last-completed-run' | 'default';
+    source: "requested" | "since-last-completed-run" | "default";
     generatedAt: number;
   };
   economy: {