@floless/app 0.22.1 → 0.23.1

package/dist/floless-server.cjs

@@ -52729,7 +52729,7 @@ function appVersion() {
   return resolveVersion({
     isSea: isSea2(),
     sqVersionXml: readSqVersionXml(),
-    define: true ? "0.22.1" : void 0,
+    define: true ? "0.23.1" : void 0,
     pkgVersion: readPkgVersion()
   });
 }
@@ -52739,7 +52739,7 @@ function resolveChannel(s) {
   return "dev";
 }
 function appChannel() {
-  return resolveChannel({ isSea: isSea2(), define: true ? "0.22.1" : void 0 });
+  return resolveChannel({ isSea: isSea2(), define: true ? "0.23.1" : void 0 });
 }
 
 // oauth-presets.ts

package/dist/skills/floless-app-steel-from-drawings/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: floless-app-steel-from-drawings
-description: This skill should be used to turn a structural steel drawing into an interactive 3D model in floless.app — the "Steel from Drawings" reader. Triggers on a pending floless `rebake` request for the `steel-from-drawings` app (queued from its "Re-read & re-bake ▸" button), or asks like "read this framing plan into 3D", "turn this steel drawing into a model", "bake my drawing into steel-from-drawings". It teaches the host AI to READ a steel drawing (PDF/image) with its own vision, extract a schematic 3D scene (grids, members, sizes, takeoff) in the viewer-3d scene schema, bake it INLINE into the app's `view` node, recompile, and ask the user to approve — all at COMPOSE time (no model in the run path, no API key). Also bakes the same scene into the `steel-to-ifc` companion so the model exports to a universal IFC file (open in Tekla, SDS2, Revit, Navisworks). Triggers also on "export this to IFC", "bake to Tekla/SDS2/Revit".
+description: This skill should be used to turn a structural steel drawing into an interactive 3D model in floless.app — the "Steel from Drawings" reader. Triggers on a pending floless `rebake` request for the `steel-from-drawings` app (queued from its "Re-read & re-bake ▸" button), or asks like "read this framing plan into 3D", "turn this steel drawing into a model", "bake my drawing into steel-from-drawings". It teaches the host AI to READ a steel drawing (PDF/image) with its own vision, extract a schematic 3D scene (grids, members, sizes, takeoff) in the viewer-3d scene schema, bake it INLINE into the app's `view` node, recompile, and ask the user to approve — all at COMPOSE time (no model in the run path, no API key). Also bakes the same scene into the `steel-to-ifc` companion (universal IFC file) and the `steel-to-tekla` companion (native Tekla parts via the Open API, needs Tekla open). Triggers also on "export this to IFC", "bake to Tekla/SDS2/Revit", "bake into Tekla".
 metadata:
   version: 0.1.0
 ---
@@ -17,11 +17,12 @@ and no AI API key**: the brain is you, in the terminal (the FloLess thin-UI cont
 and **for `steel-from-drawings` it supersedes the generic re-bake** — you bake the scene INLINE into
 the `.flo`'s `view` node, not into `config.yaml`).
 
-**Bake-out companion (`steel-to-ifc`).** A sibling app writes the SAME scene to a universal **IFC**
-file (IfcColumn/IfcBeam on the real grid) — open it in Tekla, SDS2, Revit or Navisworks; no Tekla
-needed to export. When you bake a scene, bake the *identical* scene into `steel-to-ifc` too (loop
-step 6) so the IFC matches the 3D the user confirmed. The whole loop: **read the drawing → see it in
-3D (`steel-from-drawings`) → bake it out to IFC (`steel-to-ifc`) → finish in your detailing tool.**
+**Bake-out companions.** Two sibling apps consume the SAME scene: **`steel-to-ifc`** writes a
+universal **IFC** file (open in Tekla, SDS2, Revit, Navisworks; no Tekla needed), and
+**`steel-to-tekla`** creates **native Tekla members** directly via the Open API (needs Tekla open).
+When you bake a scene, bake the *identical* scene into whichever of these are installed (loop steps
+6–7) so every output matches the 3D the user confirmed. The whole loop: **read the drawing → see it
+in 3D (`steel-from-drawings`) → bake it out (an IFC file and/or native Tekla parts) → finish in your tool.**
 
 > **Pasted a request?** If the user pastes a message beginning with a `[floless-request type=rebake
 > id=…]` marker, that's a request copied from the FloLess Dashboard — resolve it via
@@ -51,11 +52,19 @@ step 6) so the IFC matches the 3D the user confirmed. The whole loop: **read the
    present), then `aware app compile ~/.aware/apps/steel-to-ifc`. This keeps the exported IFC matching
    the 3D the user confirmed. (`steel-to-ifc` writes a real IFC file — IfcColumn/IfcBeam on the grid —
    openable in Tekla, SDS2, Revit or Navisworks; it never touches a Tekla model, so no Tekla needed.)
-7. **Hand the approval to the user.** Tell them what you read (e.g. "read 6 columns + 8 beams on grids
+7. **Bake the SAME scene into `steel-to-tekla` (native Tekla parts), if it's installed.** Check
+   `~/.aware/apps/steel-to-tekla/`. If present, replace the `scene:` under that app's `bake-tekla` node
+   `config.args` with the IDENTICAL scene (installed + `demos/steel-to-tekla/`), set `config.version`
+   to the user's RUNNING Tekla version (e.g. "2026.0" — the Open API connects to a version-specific
+   channel, so a wrong version silently finds no model), then `aware app compile
+   ~/.aware/apps/steel-to-tekla`. It creates a real Tekla member per element via the Open API (mode:
+   write, snapshot — Undo reverts the whole bake); needs Tekla OPEN with a model. Profiles fall back
+   to a sized rectangular section when the environment lacks the drawing's catalogue profile.
+8. **Hand the approval to the user.** Tell them what you read (e.g. "read 6 columns + 8 beams on grids
    A–C / 1–2, heights assumed 4.5 m — review in Inspect → Code, then Compile/Approve, then ▶ Run to
-   see the 3D; run **steel-to-ifc** to export the IFC"). The human eyeballing the read in 3D **is the
-   safety gate**. Never auto-run.
-8. **Clear the request.** `DELETE http://localhost:<port>/api/requests/<id>` once done (if from one).
+   see the 3D; run **steel-to-ifc** for an IFC file or **steel-to-tekla** for native Tekla parts").
+   The human eyeballing the read in 3D **is the safety gate**. Never auto-run.
+9. **Clear the request.** `DELETE http://localhost:<port>/api/requests/<id>` once done (if from one).
 
 ## Scene schema (the bake target — exactly what `viewer-3d` renders)
 

package/dist/web/app.css

@@ -1799,6 +1799,9 @@
      `hidden` attribute, so it showed even when unsupported (dev/non-Windows). Restore
      the hide with a class+attribute selector (higher specificity than .menu-theme). */
   .menu-startup[hidden] { display: none; }
+  /* Same footgun: .menu-item is display:flex, so JS-hiding the fullscreen row on
+     browsers without the Fullscreen API needs an explicit hide to win over flex. */
+  #menu-fullscreen[hidden] { display: none; }
   .theme-toggle {
     display: flex;
     gap: 2px;
@@ -1865,6 +1868,66 @@
     to   { opacity: 1; transform: translateY(0); }
   }
 
+  /* ========== FULLSCREEN NUDGE ==========
+     One-time "need more space?" prompt, bottom-right. Deliberately shares the
+     toast/whats-new notification language (surface card + 3px accent left rail)
+     so it reads as a calm FloLess notice, not a marketing card — no glow, no
+     gradient, no oversized shadow. */
+  .fullscreen-nudge {
+    position: fixed;
+    right: 20px;
+    bottom: 60px;            /* clears the footer — matches the toast anchor */
+    z-index: 210;            /* above toasts (200): they share this corner */
+    display: flex;
+    align-items: flex-start;
+    gap: 10px;
+    width: 290px;
+    background: var(--surface);
+    border: 1px solid var(--border-strong);
+    border-left: 3px solid var(--accent);
+    border-radius: 6px;
+    padding: 13px 12px 14px 15px;
+    box-shadow: 0 12px 32px rgba(0,0,0,0.45);
+    animation: fsn-in 0.16s ease-out;
+  }
+  /* .fullscreen-nudge is display:flex, which overrides the UA [hidden]{display:none}
+     — restore the hide (same footgun the .menu-startup row hit). */
+  .fullscreen-nudge[hidden] { display: none; }
+  .fsn-text { flex: 1; min-width: 0; }
+  .fsn-title { font-size: 13px; font-weight: 600; color: var(--text); line-height: 1.35; }
+  .fsn-sub { font-size: 11.5px; color: var(--text-muted); line-height: 1.5; margin-top: 4px; }
+  .fsn-go {
+    margin-top: 11px;
+    background: var(--accent);
+    color: #fff;
+    border: 1px solid var(--accent);
+    border-radius: 4px;
+    padding: 6px 12px;
+    font-size: 11.5px;
+    font-weight: 600;
+    cursor: pointer;
+  }
+  .fsn-go:hover { background: var(--accent-bright); border-color: var(--accent-bright); box-shadow: 0 0 14px var(--accent-glow); }
+  .fsn-dismiss {
+    flex: none;
+    background: transparent;
+    border: none;
+    color: var(--text-dim);
+    font-size: 13px;
+    line-height: 1;
+    padding: 2px 4px;
+    margin: -2px -2px 0 0;
+    cursor: pointer;
+    border-radius: 3px;
+  }
+  .fsn-dismiss:hover { color: var(--text); background: var(--surface-2); }
+  @keyframes fsn-in {
+    from { opacity: 0; transform: translateY(6px); }
+    to   { opacity: 1; transform: none; }
+  }
+  /* Calm, not flashy — honour reduced-motion by appearing without the fade/slide. */
+  @media (prefers-reduced-motion: reduce) { .fullscreen-nudge { animation: none; } }
+
   /* ========== FIND OVERLAY ========== */
   .find-overlay {
     position: absolute;

package/dist/web/app.js

@@ -1042,6 +1042,7 @@ function handleMenuAction(action) {
     case 'integrations': openIntegrations(); break;
     case 'routines': openRoutines(); break;
     case 'report-issue': openReportIssue(); break;
+    case 'fullscreen': toggleFullscreen(); break;
   }
 }
 
@@ -1186,6 +1187,96 @@ if ($startupToggle) {
 // e.g. the user disabling the task in Windows Settings).
 refreshStartup();
 
+/* ============= FULLSCREEN ============= */
+// Browser Fullscreen API on the root element — gives the 3-col workspace the whole
+// screen. The ≡ menu row and a one-time "more space?" nudge both call toggleFullscreen.
+// The row's icon/label are kept honest by `fullscreenchange` (covers Esc and other
+// out-of-band exits). If the API is unsupported we hide the row and never nudge —
+// the app's "hide, never show a dead control" rule (mirrors the startup row).
+
+const FS_NUDGE_KEY = 'floless-fullscreen-nudge-v1';
+const $fsRow   = document.getElementById('menu-fullscreen');
+const $fsIcon  = document.getElementById('menu-fullscreen-icon');
+const $fsLabel = document.getElementById('menu-fullscreen-label');
+const $fsNudge = document.getElementById('fullscreen-nudge');
+
+// Lucide maximize / minimize (same icon family as the other menu rows).
+const FS_ICON_ENTER = '<svg viewBox="0 0 24 24"><path d="M8 3H5a2 2 0 0 0-2 2v3"/><path d="M21 8V5a2 2 0 0 0-2-2h-3"/><path d="M3 16v3a2 2 0 0 0 2 2h3"/><path d="M16 21h3a2 2 0 0 0 2-2v-3"/></svg>';
+const FS_ICON_EXIT  = '<svg viewBox="0 0 24 24"><path d="M8 3v3a2 2 0 0 1-2 2H3"/><path d="M21 8h-3a2 2 0 0 1-2-2V3"/><path d="M3 16h3a2 2 0 0 1 2 2v3"/><path d="M16 21v-3a2 2 0 0 1 2-2h3"/></svg>';
+
+function fullscreenSupported() {
+  return !!(document.fullscreenEnabled && document.documentElement.requestFullscreen);
+}
+function isFullscreen() { return !!document.fullscreenElement; }
+
+function syncFullscreenUi() {
+  const on = isFullscreen();
+  if ($fsLabel) $fsLabel.textContent = on ? 'Exit full screen' : 'Enter full screen';
+  if ($fsIcon)  $fsIcon.innerHTML = on ? FS_ICON_EXIT : FS_ICON_ENTER;
+  // Once the user IS fullscreen (by any means), the nudge has served its purpose —
+  // retire it for good so it never reappears in a later session.
+  if (on) dismissFsNudge(true);
+}
+
+async function toggleFullscreen() {
+  const wasOn = isFullscreen();
+  try {
+    if (wasOn) await document.exitFullscreen();
+    else       await document.documentElement.requestFullscreen();
+  } catch {
+    // The user can't act on a blocked request — a warn toast names what failed.
+    showToast(wasOn ? "Couldn't exit fullscreen" : "Couldn't enter fullscreen", 'warn');
+  }
+}
+
+// Retire the nudge. `remember` persists the one-time flag so it never shows again.
+function dismissFsNudge(remember) {
+  if ($fsNudge && $fsNudge.isConnected) {
+    $fsNudge.hidden = true;
+    $fsNudge.remove(); // keep the a11y tree clean once it's gone
+  }
+  if (remember) { try { localStorage.setItem(FS_NUDGE_KEY, '1'); } catch {} }
+}
+
+function nudgeAlreadySeen() {
+  try { return localStorage.getItem(FS_NUDGE_KEY) === '1'; } catch { return false; }
+}
+
+// One-time nudge: only when the window is clearly under-using the screen, the app
+// isn't already fullscreen, no what's-new strip is competing for the corner, and it
+// was never dismissed/used. Delayed ~2s so the layout settles first.
+function maybeShowFsNudge() {
+  if (nudgeAlreadySeen()) return;
+  setTimeout(() => {
+    if (!$fsNudge || !$fsNudge.isConnected || !$fsNudge.hidden) return;
+    if (nudgeAlreadySeen() || isFullscreen()) return;
+    const wn = document.getElementById('whats-new-panel');
+    if (wn && !wn.hidden) return;               // don't stack on the post-update what's-new strip
+    const h = window.innerHeight;
+    const avail = (window.screen && window.screen.availHeight) || h;
+    if (h < 400) return;                        // genuinely cramped window — a card is just noise
+    if (h > avail * 0.85) return;               // window already uses most of the screen
+    $fsNudge.hidden = false;
+  }, 2000);
+}
+
+if (!fullscreenSupported()) {
+  if ($fsRow) $fsRow.hidden = true; // hide the control; never nudge on an unsupported browser
+} else {
+  document.addEventListener('fullscreenchange', syncFullscreenUi);
+  syncFullscreenUi();
+  // Query the two buttons independently — a present #fullscreen-nudge doesn't by
+  // itself guarantee its children survive a future HTML refactor.
+  const $fsGo = document.getElementById('fsn-go');
+  const $fsDismiss = document.getElementById('fsn-dismiss');
+  if ($fsGo) $fsGo.addEventListener('click', () => {
+    dismissFsNudge(true);
+    toggleFullscreen(); // synchronous within the click → counts as a user gesture
+  });
+  if ($fsDismiss) $fsDismiss.addEventListener('click', () => dismissFsNudge(true));
+  if ($fsNudge) maybeShowFsNudge();
+}
+
 /* ============= TOAST ============= */
 
 function showToast(msg, type) {

package/dist/web/index.html

@@ -168,6 +168,22 @@
       <div class="whats-new-detail"><div class="whats-new-detail-inner"></div></div>
     </div>
 
+    <!-- One-time "need more space?" nudge (mirrors Excel's prompt). Shown ~2s after
+         load ONLY when the window is clearly under-using the screen, the app isn't
+         already fullscreen, the post-update what's-new strip isn't already showing,
+         and it was never dismissed/used (localStorage). position:fixed, so it doesn't disturb the
+         .app grid; placed here so Tab order is main → nudge → footer. Calm
+         notification styling (shares the toast/whats-new accent rail) — never an ad;
+         one dismiss/use retires it for good. aria-live=polite (not alert): passive. -->
+    <aside id="fullscreen-nudge" class="fullscreen-nudge" aria-label="Fullscreen suggestion" aria-live="polite" hidden>
+      <div class="fsn-text">
+        <div class="fsn-title">Need more working space?</div>
+        <div class="fsn-sub">Go fullscreen to give FloLess the whole screen.</div>
+        <button type="button" class="fsn-go" id="fsn-go">Go fullscreen</button>
+      </div>
+      <button type="button" class="fsn-dismiss" id="fsn-dismiss" aria-label="Dismiss fullscreen suggestion">✕</button>
+    </aside>
+
     <footer>
       <div class="status">
         <span class="stat"><span class="dot"></span><span class="stat-val">runtime online</span></span>
@@ -269,6 +285,17 @@
       <span class="menu-icon" aria-hidden="true"><svg viewBox="0 0 24 24"><path d="M4 15s1-1 4-1 5 2 8 2 4-1 4-1V3s-1 1-4 1-5-2-8-2-4 1-4 1z"/><line x1="4" x2="4" y1="22" y2="15"/></svg></span>
       <span class="menu-label">Report an issue</span>
     </button>
+    <!-- Browser fullscreen toggle — gives the 3-col workspace the whole screen.
+         An action (not a stored pref: browsers won't restore fullscreen on load),
+         so it's a .menu-item button, not a switch. Icon + label flip with the live
+         fullscreen state via `fullscreenchange`. Hidden by JS when the Fullscreen
+         API is unavailable — hide, never show a dead control. No F11 kbd hint: F11
+         is the browser's own fullscreen, which is separate from the Fullscreen API
+         and wouldn't keep this control's state in sync. -->
+    <button class="menu-item" data-action="fullscreen" id="menu-fullscreen" role="menuitem">
+      <span class="menu-icon" aria-hidden="true" id="menu-fullscreen-icon"><svg viewBox="0 0 24 24"><path d="M8 3H5a2 2 0 0 0-2 2v3"/><path d="M21 8V5a2 2 0 0 0-2-2h-3"/><path d="M3 16v3a2 2 0 0 0 2 2h3"/><path d="M16 21h3a2 2 0 0 0 2-2v-3"/></svg></span>
+      <span class="menu-label" id="menu-fullscreen-label">Enter full screen</span>
+    </button>
     <!-- Start-on-login + Theme are sibling machine preferences (no divider between
          them — UX review 2026-05-31). Start-on-login toggles the per-user logon
          Scheduled Task that keeps the local server alive across logins; hidden unless

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@floless/app",
-  "version": "0.22.1",
+  "version": "0.23.1",
   "type": "module",
   "description": "Thin localhost host for floless.app — serves web/ and shells the aware CLI. No engine, no LLM.",
   "bin": {