@stage5/lumine 0.3.33 → 0.3.34

package/lib/builderStance.generated.js

@@ -0,0 +1,3 @@
+// GENERATED from CORE_VALUES.md ("For building agents") by
+// scripts/generate-builder-stance.mjs. Do not edit by hand.
+export const LUMINE_BUILDER_STANCE = "You are a tool for the creator. Your job is to understand what they want to make, or seem to want to make, and help them make the best version of it.\n\n- What to make is the creator's call. Never steer them toward or away from a kind of project, genre, mechanic or style because of your own taste.\n- Be opinionated about how to make their idea great. Like a trusted senior collaborator, point out the loose ends: gaps between what they asked for and what exists, unfinished parts, edge cases, and things that will break or feel off. Then say clearly what you would do next if you were them, and why. Let them decide.\n- When they ask for ideas, offer a few options that fit what they're making, say which one you'd pick for their goal and why, and don't push.\n- When their direction is vague or feeling-based (\"make it more epic\", \"it feels empty\", \"I don't like this\"), work out what they mean and make the result visibly respond to it. Ask one short question only when you genuinely can't tell.\n- Make it well: aim for the best, most complete and polished version of their idea, within what they asked.\n- Don't coach, lecture or comment on the creator themselves; let the work speak.";

package/lib/constants.js

@@ -1,5 +1,6 @@
 import os from "os";
 import path from "path";
+import { LUMINE_BUILDER_STANCE } from "./builderStance.generated.js";
 
 export const DEFAULT_API_URL = "https://api.twinkle.network";
 export const DEFAULT_SITE_URL = "https://www.twin-kle.com";
@@ -173,6 +174,10 @@ export const LUMINE_AGENT_INSTRUCTIONS = `${LUMINE_AGENT_INSTRUCTIONS_MARKER}
 This directory contains Twinkle Build project files pulled by Lumine CLI. Use
 Lumine CLI as the source of truth for saving this workspace back to Twinkle.
 
+## Building For The Creator
+
+${LUMINE_BUILDER_STANCE}
+
 ## Source Of Truth
 
 - Read .twinkle/lumine-project.json before changing files.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stage5/lumine",
-  "version": "0.3.33",
+  "version": "0.3.34",
   "description": "Command line tools for launching Lumine builds on Twinkle.",
   "type": "module",
   "bin": {
@@ -13,7 +13,8 @@
     "README.md"
   ],
   "scripts": {
-    "test": "node --test"
+    "test": "node --test",
+    "prepublishOnly": "node --test test/builderStanceSync.test.js"
   },
   "publishConfig": {
     "access": "public"

package/sdk/LUMINE_ADMIN.md

@@ -2673,6 +2673,12 @@ never previously been Featured from canonical evidence.
 
 ### Exact approved refresh and resumable comment encouragement
 
+Keep current manual pins from the past two days (Mikey, October 13, 2026).
+Verify canonical pin history and exclude those subjects from removal proposals.
+Subject 3529, “What is special about Twinkle?”, also has an explicit keep
+instruction. An absent pin is still never restored. This supersedes the older
+instruction to offer yesterday's manual pins for rotation.
+
 For the daily old-to-new proposal, prepare a canonical plan without changing pins:
 
 ```bash
@@ -2982,6 +2988,14 @@ to join in. Games, art, puzzles, friendships, shared reflections, and community
 discussions can all supply good stories; read the actual source to find the
 substance.
 
+**Community significance (Mikey, 2026-10-13):** substantive messages about
+Twinkle's shared values, purpose and direction deserve explicit front-page
+priority, including the lead when they are the day's most consequential story.
+Judge what the message means for members, regardless of who wrote it. Immediate
+entertainment, likely comments and opportunities to join in are not the only
+measures of importance. Explain the values being communicated; do not reduce
+them to founder biography or an administrative announcement.
+
 Use clear, lively language that respects readers' intelligence. Give enough
 context for someone who missed the original post, and make the interesting
 part clear in the headline and opening. Avoid talking down to readers, forced
@@ -3101,7 +3115,9 @@ make the call by reading:
 
 - **Choose the lead for readers aged 10–15.** Lead with the eligible front
   event whose substance is most likely to catch their interest and reward
-  reading. A thoughtful conversation, a funny or relatable reflection, a
+  reading, weighing community significance as well as immediate appeal.
+  A substantive statement of shared values or purpose, a thoughtful
+  conversation, a funny or relatable reflection, a
   striking creation, or an inviting community challenge can all qualify.
   Read the source and any supplied replies to understand the appeal; priority,
   recency, and the mere presence of an argument do not decide the lead.