@floless/app 0.22.0 → 0.23.0

package/dist/floless-server.cjs

@@ -52729,7 +52729,7 @@ function appVersion() {
   return resolveVersion({
     isSea: isSea2(),
     sqVersionXml: readSqVersionXml(),
-    define: true ? "0.22.0" : void 0,
+    define: true ? "0.23.0" : void 0,
     pkgVersion: readPkgVersion()
   });
 }
@@ -52739,7 +52739,7 @@ function resolveChannel(s) {
   return "dev";
 }
 function appChannel() {
-  return resolveChannel({ isSea: isSea2(), define: true ? "0.22.0" : void 0 });
+  return resolveChannel({ isSea: isSea2(), define: true ? "0.23.0" : 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

@@ -1125,9 +1125,17 @@
     overflow-y: auto;
     display: grid;
     grid-template-columns: 1fr 1fr;
+    /* align-items:start so a collapsed card isn't stretched to match an
+       expanded sibling in the same row (the accordion-in-grid pattern). */
+    align-items: start;
     gap: 6px;
     padding-right: 4px;
   }
+  /* One grid cell per agent: holds the card header + its command list, so the
+     commands nest directly under the picked card (see renderLibrary). */
+  .lib-card { min-width: 0; }
+  .lib-card.expanded .lib-item { border-color: var(--accent-dim); }
+  .lib-card.expanded .lib-fav { transform: rotate(180deg); }
   .lib-item {
     background: var(--surface-2);
     border: 1px solid var(--border-strong);
@@ -1162,6 +1170,7 @@
     border-radius: 3px;
     flex-shrink: 0;
     line-height: 1;
+    transition: transform 0.15s ease, color 0.15s, border-color 0.15s;
   }
   .lib-item .lib-fav.faved { color: var(--star); border-color: var(--star); }
 

package/dist/web/aware.js

@@ -3681,15 +3681,20 @@
   renderLibrary = function renderLibraryReal() {
     const q = ($libSearch.value || '').toLowerCase().trim();
     const items = agentCatalog.filter((a) => !q || a.id.toLowerCase().includes(q) || (a.kind || '').toLowerCase().includes(q));
+    // Each agent is ONE grid cell: the card header + its (lazy) command list live
+    // in the same `.lib-card`, so expanding nests the commands directly under the
+    // picked card instead of scattering them into a neighbouring grid slot.
     $libList.innerHTML = items.map((a) => `
-      <div class="lib-item" data-agent="${escapeAttr(a.id)}">
-        <div class="info">
-          <div class="name">${escapeHtml(a.id)} <span style="color:var(--text-dim);font-weight:400">v${escapeHtml(String(a.version))}</span></div>
-          <div class="meta">${escapeHtml(a.kind || 'agent')} · ${a.commands} command${a.commands === 1 ? '' : 's'} · ${a.skills} skill${a.skills === 1 ? '' : 's'}</div>
+      <div class="lib-card" data-agent="${escapeAttr(a.id)}">
+        <div class="lib-item">
+          <div class="info">
+            <div class="name">${escapeHtml(a.id)} <span style="color:var(--text-dim);font-weight:400">v${escapeHtml(String(a.version))}</span></div>
+            <div class="meta">${escapeHtml(a.kind || 'agent')} · ${a.commands} command${a.commands === 1 ? '' : 's'} · ${a.skills} skill${a.skills === 1 ? '' : 's'}</div>
+          </div>
+          <button class="lib-fav" data-expand="${escapeAttr(a.id)}" data-tip="Show commands">⌄</button>
         </div>
-        <button class="lib-fav" data-expand="${escapeAttr(a.id)}" data-tip="Show commands">⌄</button>
+        <div class="lib-commands" id="cmds-${escapeAttr(a.id)}" hidden></div>
       </div>
-      <div class="lib-commands" id="cmds-${escapeAttr(a.id)}" hidden></div>
     `).join('') || '<div class="empty-state">No agents match.</div>';
     $libList.querySelectorAll('[data-expand]').forEach((btn) => {
       btn.onclick = () => expandAgent(btn.dataset.expand);
@@ -3699,8 +3704,10 @@
   async function expandAgent(id) {
     const box = document.getElementById(`cmds-${id}`);
     if (!box) return;
-    if (!box.hidden) { box.hidden = true; return; }
+    const card = box.closest('.lib-card');
+    if (!box.hidden) { box.hidden = true; if (card) card.classList.remove('expanded'); return; }
     box.hidden = false;
+    if (card) card.classList.add('expanded');
     box.innerHTML = '<div class="cmd-desc">loading…</div>';
     try {
       const { agent } = await api(`/api/agent/${encodeURIComponent(id)}`);

package/package.json

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