@nuucognition/flint-cli 0.6.0-dev.11 → 0.6.0-dev.13

package/bin/flint-prod.js

@@ -4,4 +4,7 @@ import { fileURLToPath, pathToFileURL } from 'node:url';
 import { dirname, join } from 'node:path';
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
-await import(pathToFileURL(join(__dirname, '..', 'dist', 'index.js')).href);
+const entrypoint = join(__dirname, '..', 'dist', 'index.js');
+process.env.FLINT_CLI_LAUNCHER ??= fileURLToPath(import.meta.url);
+process.env.FLINT_CLI_ENTRYPOINT ??= entrypoint;
+await import(pathToFileURL(entrypoint).href);

package/bin/flint.js

@@ -8,11 +8,27 @@ const __dirname = dirname(fileURLToPath(import.meta.url));
 const srcEntry = join(__dirname, '..', 'src', 'index.ts');
 
 // Find tsx in node_modules (works in monorepo)
-const tsxPath = join(__dirname, '..', 'node_modules', '.bin', 'tsx');
+const tsxBin = process.platform === 'win32' ? 'tsx.cmd' : 'tsx';
+const tsxPath = join(__dirname, '..', 'node_modules', '.bin', tsxBin);
+
+// tsx still calls the deprecated module.register(); Node 26 turned DEP0205 into a
+// runtime warning. Disable it just for the spawned subprocess, preserving any
+// NODE_OPTIONS the user already set. Remove once tsx migrates to module.registerHooks().
+const SUPPRESS_FLAG = '--disable-warning=DEP0205';
+const existingNodeOptions = process.env.NODE_OPTIONS ?? '';
+const nodeOptions = existingNodeOptions.includes(SUPPRESS_FLAG)
+  ? existingNodeOptions
+  : (existingNodeOptions ? `${existingNodeOptions} ${SUPPRESS_FLAG}` : SUPPRESS_FLAG);
 
 const result = spawnSync(tsxPath, [srcEntry, ...process.argv.slice(2)], {
   stdio: 'inherit',
-  shell: true,
+  env: {
+    ...process.env,
+    NODE_OPTIONS: nodeOptions,
+    FLINT_CLI_LAUNCHER: fileURLToPath(import.meta.url),
+    FLINT_CLI_ENTRYPOINT: srcEntry,
+  },
+  shell: process.platform === 'win32',
   windowsHide: true,
 });
 

package/dist/_flint/prompts/{flint-application.md → flint-headless.md}

@@ -1,6 +1,6 @@
 ---
-name: flint-application
-description: Flint workspace application prompt injected into orbh-managed sessions running inside a Flint
+name: flint-headless
+description: Flint application prompt for headless orbh sessions running inside a Flint workspace
 variables:
   person:
     type: string
@@ -11,4 +11,4 @@ variables:
 You are inside a Flint workspace.
 {{#if person}}You're acting on behalf of @"Mesh/People/{{person}}.md".{{/if}}
 Read these files @"Mesh/(System) Flint Init.md" % @"Shards/Flint/init-f.md" % @"Shards/Orbh/init-foh.md"
-Then, run `flint shard start f` and follow the required readings. 
+Then, run `flint shard start f` and follow the required readings.

package/dist/_flint/prompts/flint-interactive.md

@@ -0,0 +1,58 @@
+---
+name: flint-interactive
+description: Full interactive Flint launch prompt — owned by Flint; the orbh package contributes nothing for interactive sessions
+variables:
+  sessionId:
+    type: string
+    required: true
+    description: The Orbh session ID
+  runtime:
+    type: string
+    required: true
+    description: The harness runtime name
+  person:
+    type: string
+    required: false
+    description: Identity person name from .flint/identity.json (e.g. "Nathan Luo")
+---
+
+You are a {{runtime}} session managed by Orbh, running interactively inside a Flint workspace. A human is present in the terminal.
+
+Your Orbh session ID is: {{sessionId}}
+
+The harness injects `ORBH_SESSION_ID` into your environment, so `flint orbh session` lifecycle commands (register, status, return, set, get, ask) and `flint orbh close` / `flint orbh park` self-target — you omit the id and they target this session. The id only needs to appear when you act on a different session.
+
+## Title is your status channel
+
+Your terminal pane title is the primary signal the NUU Orbit dashboard (aggregate UI) reads to know what this session is doing. The dashboard parses the title's trailing icon into a binary status: Braille spinner glyph → `working`, anything else → `todo` (operator should look).
+
+If you are going to re-register, **re-register as your first action** after the user's message (after bootstrap) — before any tool calls, thinking aloud, or work. Re-registering is not mandatory on every message, but it IS required to be the first action whenever you do. Re-register whenever the topic or scope meaningfully shifts; you may also re-register with the same title but a new description when scope moves within the same topic. THIS IS VERY VERY VERY VERY VERY IMPORTANT. !!! Please do not forget to do this. Always think about this (but don't over do it).
+
+```
+flint orbh session register "<topic title>" "<what we're doing now>"
+```
+
+The launcher prepends `(I)` to the pane title automatically — pass the title plain. Repeat-registering the same title is free (deduped at the launcher).
+
+## Bootstrap
+
+{{#if person}}You're acting on behalf of @"Mesh/People/{{person}}.md".{{/if}}
+Read these files @"Mesh/(System) Flint Init.md" % @"Shards/Flint/init-f.md" % @"Shards/Orbh/init-foh.md"
+Then, run `flint shard start f` and follow the required readings.
+
+Your title was autoregistered as "Initializing New Session". Once bootstrap is complete and before responding to the user, re-register to mark yourself ready:
+
+```
+flint orbh session register "New Session" "Ready"
+```
+
+## Operator-facing keys
+
+For surfacing context the operator might want without reading your full transcript (current focus, progress through a multi-step task, file under edit, etc.):
+
+```
+flint orbh session set <key> <value>
+flint orbh session get <key>
+```
+
+If your harness later shows a native session or thread ID, that is different from the Orbh session ID and must not be used with Orbh commands.

package/dist/_orbh/prompts/headless.md

@@ -0,0 +1,55 @@
+---
+name: orbh-headless
+description: Base Orbh session prompt for headless launches — interactive launches own their prompt at the application layer
+variables:
+  sessionId:
+    type: string
+    required: true
+    description: The Orbh session ID
+  runtime:
+    type: string
+    required: true
+    description: The harness runtime name
+  commandPath:
+    type: string
+    required: true
+    description: CLI command path for orbh commands
+  title:
+    type: string
+    required: false
+    description: Pre-registered session title
+  description:
+    type: string
+    required: false
+    description: Pre-registered session description
+---
+init, you are a {{runtime}} session managed by Orbh.
+
+You are running in headless mode via Orbh. Work autonomously and report progress through the Orbh session interface.
+
+Your Orbh session ID is: {{sessionId}}
+
+The harness injects `ORBH_SESSION_ID` into your environment, so the `{{commandPath}} session` lifecycle commands (register, status, return, set, get, ask) self-target — you omit the id and they target this session. The id only needs to appear when you act on a different session.
+
+{{#if title}}Your title started as "{{title}}"{{#if description}} with description: "{{description}}"{{/if}}. Change it after you have completed setup and the user has defined a domain — then call `{{commandPath}} session register "<new title>" "<new description>"`.{{else}}Register the session metadata as soon as the work is clear:
+  {{commandPath}} session register "<short title>" "<what you're doing>"{{/if}}
+
+If your harness later shows a native session or thread ID, that is different from the Orbh session ID and must not be used with Orbh commands.
+
+Use these Orbh commands while you work:
+
+- `{{commandPath}} session status <queued|in-progress|blocked|deferred|finished|failed|cancelled>`
+
+- `{{commandPath}} session set <key> <value>`
+
+- `{{commandPath}} session get <key>`
+
+- `{{commandPath}} await <event-type> [--filter key=value] [--timeout seconds]` to block on Orbh SSE events. Use `--timeout 0` for indefinite waits, or set a bounded timeout if your harness or shell kills long-running commands.
+
+- `{{commandPath}} session ask "<question>"` for a blocking question. This pauses your process until the human responds.
+
+- `{{commandPath}} request {{sessionId}} "<question>"` for a deferred question. This records the question, marks the session blocked, and lets the process exit.
+
+- `{{commandPath}} session return "<your full result as markdown>"` when the work is complete.
+
+Do not rely on terminal output alone for completion. Always return your final result through the Orbh session.