@stage5/lumine 0.2.26 → 0.2.28

package/README.md

@@ -181,6 +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 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

@@ -12,6 +12,11 @@ const MAX_COMPOSED_COMMENT_LENGTH = 10_000;
 // its model and no AI Energy is spent.
 function readComposedCommentFile(filePath) {
   const normalizedPath = String(filePath || "").trim();
+  if (!normalizedPath) {
+    throw cliValidationError(
+      "Pass composed comment text with --file <comment.md>.",
+    );
+  }
   let contents;
   try {
     contents = readFileSync(normalizedPath, "utf8");
@@ -580,6 +585,24 @@ export function parseAdminOperation(options) {
     );
   }
 
+  if (namespace === "notable" && action === "add") {
+    const rawTarget = String(target || "").trim();
+    if (!rawTarget) {
+      throw cliValidationError(
+        "Usage: lumine admin notable add <userId|username>.",
+      );
+    }
+    const body = /^\d+$/.test(rawTarget)
+      ? { userId: parseRequiredInteger(rawTarget, "user ID", 1) }
+      : { username: rawTarget };
+    return writeOperation(
+      "notable.add",
+      "POST",
+      "/cli/admin/notable-users",
+      body,
+    );
+  }
+
   if (namespace === "brief" && !action) {
     if (options.adminDays) {
       const days = Number(options.adminDays);
@@ -638,6 +661,30 @@ export function parseAdminOperation(options) {
         },
       );
     }
+    if (action === "edit") {
+      const rawTarget = String(target || "").trim();
+      let commentId;
+      if (/^\d+$/.test(rawTarget)) {
+        commentId = parseRequiredInteger(rawTarget, "comment id", 1);
+      } else {
+        const parsedTarget = parseRecommendationTarget({
+          target,
+          explicitType: options.adminType,
+        });
+        if (parsedTarget.type !== "comment") {
+          throw cliValidationError(
+            "comment edit targets a comment: lumine admin comment edit <commentId> --file <comment.md>.",
+          );
+        }
+        commentId = parsedTarget.id;
+      }
+      return writeOperation(
+        "comment.edit",
+        "PUT",
+        `/cli/admin/comments/${commentId}`,
+        { content: readComposedCommentFile(options.adminFile) },
+      );
+    }
     if (action === "post") {
       const draftId = parseRequiredInteger(
         options.draftId || target,
@@ -654,7 +701,7 @@ export function parseAdminOperation(options) {
   }
 
   throw cliValidationError(
-    "Usage: lumine admin identity|daily-run|recommendations|post|subjects|subject|featured|comment|news|audit|brief ...",
+    "Usage: lumine admin identity|daily-run|recommendations|post|subjects|subject|featured|comment|news|audit|brief|notable ...",
   );
 }
 
@@ -1059,6 +1106,12 @@ function printAdminResult({ operation, result }) {
     }
     return;
   }
+  if (data.notableUser) {
+    console.log(
+      `${result.status || "success"}: ${data.notableUser.username || "unknown"} (#${data.notableUser.userId}).`,
+    );
+    return;
+  }
   if (data.skip) {
     console.log(
       `${result.status}: ${data.skip.contentType}:${data.skip.contentId} skipped.`,

package/lib/commands.js

@@ -2526,7 +2526,9 @@ export function printHelp() {
   lumine admin comment draft <target> [--type subject|comment|aiStory|dailyReflection] [--identity zero|ciel|auto] [--json]
   lumine admin comment reply comment:<id> [--identity zero|ciel|auto] [--json]
   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 audit [list] [--run current|last|<run-id>] [--target <target>] [--actions <a,b>] [--full] [--cursor <cursor>] [--json]
 
 Examples:
@@ -2607,6 +2609,7 @@ Options:
   --reward-twinkles 3   Pair a recommendation with exactly 3 Twinkles
   --twinkles 3          Give exactly 3 Twinkles through the normal economy
   --draft-id <id>       Canonical delegated comment draft ID
+  --file <path>         Editorial JSON or composed comment text file
   --reason <text>       Reason when marking an admin run failed
   --force               Overwrite server files even if this workspace is stale or missing filesHash
   --search <text>       Search public open-source Builds

package/package.json

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

package/sdk/LUMINE_ADMIN.md

@@ -1041,6 +1041,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
 ```
 
 Read-only management insights for the delegated workflow, windowed since the
@@ -1062,24 +1064,39 @@ Four sections (Mikey's chosen cut, 2026-08-10):
 - `aiSpending` — a compact projection of the management AI-cost report:
   `summary`, top spending accounts, top risk groups. Unlike the other sections'
   exact `window.sinceTs`, this existing report is bucketed into whole UTC days;
-  `aiSpending.days` includes today and may begin up to one day before the exact
-  brief window. Flag accounts that jumped tiers or dominate that report period.
-  May be `{ unavailable: true }` if the cost report fails; say so rather than
-  guessing.
+  `aiSpending.startDayIndex` and `endDayIndex` are its canonical bounds. The
+  report period can begin up to one day before or after the exact brief window,
+  so use those bounds when describing it. Flag accounts that jumped tiers or
+  dominate that report period. May be `{ unavailable: true }` if the cost
+  report fails; say so rather than guessing.
 - `notableCandidates` — kids (never bots, staff `userType`s, or users already
   on the Notable Users list) ranked by authored activity in the window, with
   `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 — the run never edits that list
-  itself.
-- `teachers` — every `userType='supermod'` account with per-window
-  `subjectsPosted`, `commentsPosted`, `recommendationsGiven`, `rewardsGiven`,
-  `rewardTwinklesGiven`, `lastActive`/`daysSinceActive`, ordered by an
-  engagement score. Mikey's standing question here: which teachers genuinely
-  use the website to its fullest and which only work through it. Authored
-  posts and comments signal personal engagement; recommendations and rewards
-  are the "work" verbs — report the contrast, not just the totals, and treat
-  it as notable-users-but-for-teachers.
+  Mikey's Notable Users list in the report. When Mikey approves additions,
+  execute them with `lumine admin notable add <userId|username>` (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.
+- `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
+  expected and deliberately excluded. Mikey's standing question here: which
+  teachers genuinely use the website for themselves and which only work
+  through it. Recommendations and rewards are classroom "work" verbs and
+  count for nothing toward interest; genuine personal interest is measured by
+  what a teacher does for themselves — authored subjects/comments,
+  `reflections` (Daily Reflections answered), `dailyTasksCompleted`,
+  `wordlePlays`, `buildsTouched` (Lumine builds they own that changed in the
+  window), `aiStories`, and bounded `xpEvents` (XP-ledger activity). Shape:
+  `genuinelyInterested` (interestScore > 0, ordered by it, each row carrying
+  all the per-window counters plus `rank: mentor|sage` and `workScore`),
+  `workOnly` (classroom verbs only, zero personal signals), `activeButSilent`
+  (window-active log-ins with nothing at all, capped at 40), and `totals`.
+  Daily-task counts use canonical whole-day indices and can begin up to one
+  calendar day before the exact `window.sinceTs`.
+  Report the contrast between the buckets, and treat `genuinelyInterested` as
+  notable-users-but-for-teachers.
 
 The command needs only an active run's `content:read` scope and mutates
 nothing; reading the brief is not audited content action. Window boundaries
@@ -1088,6 +1105,27 @@ on the big append-only ledgers are found by binary-searching the PRIMARY key
 is still bounded to the selected 1–30 day window.
 
 ```ts
+type TeacherInsight = {
+  userId: number;
+  username: string | null;
+  rank: 'mentor' | 'sage';
+  lastActive: number | null;
+  daysSinceActive: number | null;
+  subjectsPosted: number;
+  commentsPosted: number;
+  reflections: number;
+  dailyTasksCompleted: number;
+  wordlePlays: number;
+  buildsTouched: number;
+  aiStories: number;
+  xpEvents: number;
+  recommendationsGiven: number;
+  rewardsGiven: number;
+  rewardTwinklesGiven: number;
+  interestScore: number;
+  workScore: number;
+};
+
 type InsightsBrief = Success<{
   window: {
     sinceTs: number;
@@ -1123,21 +1161,21 @@ type InsightsBrief = Success<{
     isNewUser: boolean;
     lastActive: number | null;
   }>;
-  teachers: Array<{
-    userId: number;
-    username: string | null;
-    lastActive: number | null;
-    daysSinceActive: number | null;
-    subjectsPosted: number;
-    commentsPosted: number;
-    recommendationsGiven: number;
-    rewardsGiven: number;
-    rewardTwinklesGiven: number;
-    engagementScore: number;
-  }>;
+  teachers: {
+    genuinelyInterested: TeacherInsight[];
+    workOnly: TeacherInsight[];
+    activeButSilent: TeacherInsight[];
+    totals: {
+      total: number;
+      activeInWindow: number;
+      interestedInWindow: number;
+    };
+  };
   aiSpending:
     | {
         days: number;
+        startDayIndex: number;
+        endDayIndex: number;
         summary: unknown;
         topAccounts: unknown[];
         topRiskGroups: unknown[];
@@ -1146,6 +1184,24 @@ type InsightsBrief = Success<{
 }>;
 ```
 
+**Editing the bot's own comments.** `comment edit <commentId> --file
+<comment.md>` replaces the text of a comment the ACTING bot itself authored —
+for correcting a factual error, an unfulfillable claim, or outdated guidance
+in Zero/Ciel's own words. It is deliberately not a moderation verb: comments
+by the other bot, by any human, and hidden notification records are all
+rejected (`CLI_ADMIN_EDIT_NOT_OWN_COMMENT`,
+`CLI_ADMIN_EDIT_NOTIFICATION_COMMENT`). The replacement text follows the
+composed-comment rules (plain UTF-8, 10,000-character limit, truth about what
+the session actually did) and publishes through the website's canonical
+comment-edit pipeline — mentions are reprocessed (a newly added `@mikey`
+notifies him), and Earn-candidate projections resync. Submitting identical
+text returns `already_done`. Requires the `comment:post` scope of a
+comment-mode `post` run, and is audited as `comment.edit` with the previous
+content in `beforeState` and `data.edit.previousContent`. Edit sparingly:
+kids may have already read the original, so a comment that changed meaning
+(not just wording) usually deserves a follow-up reply instead of a silent
+rewrite.
+
 ## Audit history
 
 ```bash
@@ -1216,6 +1272,9 @@ lumine admin comment reply comment:456 --json
 
 lumine admin comment post --draft-id 77 \
   --idempotency-key comment-123-post-v1 --json
+
+# Correct the acting bot's OWN published comment.
+lumine admin comment edit 342752 --file corrected.md --json
 ```
 
 **Compose in persona by default (Mikey's standing direction, 2026-08-10).**
@@ -1237,6 +1296,24 @@ from memory:
   decisions are yours to make and record with `post skip` or in the run
   report).
 
+**Lumine Build app posts are composed-only, and only after actually looking
+(Mikey's direction, 2026-08-10).** When a post is about a Build app — the
+author shares their app, announces an update, or asks for feedback on their
+build — never use the server-generated draft path: the API persona cannot
+open an app, so its drafts either stay generic or fabricate first-hand
+experience (a real Ciel draft claimed "I clicked over to check it out" on an
+app nobody had opened). The day's management agent comments instead, and
+looks first: pull the project with lumine-cli when it is open source (or
+yours to pull) and read the code, or open the app and actually try it; then
+compose a comment whose specifics come from what you genuinely saw — a
+mechanic you liked, a nice touch in their code, a concrete suggestion. Be
+truthful about what you did: "I read through your code" and "I played a few
+rounds" are different claims, and a comment must only make the one that
+happened. If you could not access the app at all, say nothing about having
+tried it — ask the author about it instead. This is the standing rule for
+every composed comment, applied to apps: never claim an experience the
+session did not actually have.
+
 A composed draft (`--file`, plain UTF-8 text, at most the website's 10,000
 character comment limit) flows through the identical draft lifecycle —
 reservation, idempotency, context-revision CAS, publish fencing, audit