chore: purge flywheel branding, launcher install fallback, v1.2.3

- Rename the ml agent's 'flywheel' language to 'model specialization' across the
  prompt and skills; only Atlas skills remain in the bundle.
- npx synsci: when global npm install fails (common on permissions), fall back
  to the standalone installer at openscience.sh/install instead of dead-ending.
- Bump CLI + launcher to 1.2.3.

Author: ishaan1124

backend/cli/package.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
-  "version": "1.2.2",
+  "version": "1.2.3",
   "name": "@synsci/openscience",
   "type": "module",
   "description": "AI-powered CLI for ML research and development workflows",

backend/cli/skills/ml-training/model-economics/SKILL.md

@@ -13,7 +13,7 @@ dependencies: []
 
 ## When to Use This Skill
 
-Use this skill as the **first step** of any flywheel assessment to determine:
+Use this skill as the **first step** of any model-specialization assessment to determine:
 - Is it worth training a specialized model?
 - What will the total investment be?
 - When will the specialized model break even vs frontier APIs?

backend/cli/skills/research/initialize-atlas-graph/SKILL.md

@@ -18,7 +18,7 @@ clone at a different path resolves to the **same** graph.
 Run this skill when:
 - The canvas shows "no graph for this project" / the folder isn't linked yet.
 - The user asks to "initialize", "set up Atlas", or "start tracking" research.
-- You are about to begin research/flywheel work that should be recorded.
+- You are about to begin research work that should be recorded.
 
 ## Steps
 

backend/cli/src/agent/prompt/ml.txt

@@ -7,7 +7,7 @@ evidence: scope the problem, survey prior art, build the data pipeline, design a
 models, evaluate rigorously against real baselines, ablate what matters, and report honestly.
 You cover the full spectrum — classical ML, deep learning, LLMs, RL, and multimodal — and the
 complete experimental lifecycle. When the goal is to replace a frontier API dependency with a
-cheaper specialized model, you run the model flywheel (see the Model Specialization track).
+cheaper specialized model, you run the specialization loop (see the Model Specialization track).
 
 You are NOT a chatbot. You are an autonomous ML agent. Given a task, dataset, or research
 question, you independently produce a complete, reproducible analysis and result.
@@ -141,7 +141,7 @@ Before reporting, run the decoupled critique + reviewer gate. This is a blocking
 
 ---
 
-## Model Specialization Track (the flywheel)
+## Model Specialization Track
 When the goal is to REPLACE a frontier API dependency with a cheaper specialized model, run
 this loop instead of the generic pipeline: **production data → train specialized model →
 deploy → collect more data → retrain**. This is collaborative — present options with

backend/cli/src/openscience/index.ts

@@ -185,8 +185,8 @@ export class InsufficientCreditsError extends Error {
 
 // ── Bundled atlas CLI resolution ─────────────────────────────────────────
 // The @synsci/atlas package ships as a dependency; its `atlas` binary lives in
-// node_modules. The agent shells out to native `atlas` commands (the research /
-// flywheel prompts drive the map + managed-compute path through it), so the
+// node_modules. The agent shells out to native `atlas` commands (the research
+// prompts drive the map + managed-compute path through it), so the
 // binary must be on the subprocess PATH without requiring a separate global
 // install. We resolve the package, prefer the npm-generated `.bin/atlas` shim,
 // and otherwise synthesize a tiny launcher in the openscience data dir that runs the

tooling/launcher/bin/synsci.mjs

@@ -178,10 +178,22 @@ async function main() {
       cliPath = resolveCli()
       if (!cliPath) throw new Error("openscience not on PATH after install")
       s.ok("Installed OpenScience")
-    } catch (e) {
-      s.fail(`Install failed${e && e.message ? ": " + e.message : ""}`)
-      console.log(`\n  Try manually: ${CYAN}npm i -g @synsci/openscience${RESET}\n`)
-      process.exit(1)
+    } catch {
+      // Global npm installs commonly fail on permissions. Fall back to the
+      // standalone installer, which lands in ~/.openscience/bin without sudo
+      // (resolveCli already checks that location).
+      s.update("npm -g failed, trying the standalone installer...")
+      try {
+        execSync("curl -fsSL https://openscience.sh/install | bash", { stdio: "pipe" })
+        cliPath = resolveCli()
+        if (!cliPath) throw new Error("openscience not found after install")
+        s.ok("Installed OpenScience")
+      } catch (e2) {
+        s.fail(`Install failed${e2 && e2.message ? ": " + e2.message : ""}`)
+        console.log(`\n  Try manually: ${CYAN}npm i -g @synsci/openscience${RESET}`)
+        console.log(`  or:           ${CYAN}curl -fsSL https://openscience.sh/install | bash${RESET}\n`)
+        process.exit(1)
+      }
     }
   }
 

tooling/launcher/package.json

@@ -1,6 +1,6 @@
 {
   "name": "synsci",
-  "version": "1.2.2",
+  "version": "1.2.3",
   "description": "Install wizard for OpenScience, the open-source AI research workspace (optionally with Atlas)",
   "license": "Apache-2.0",
   "type": "module",