@floless/app 0.48.0 → 0.48.1

package/package.json

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

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

@@ -1,120 +0,0 @@
----
-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 (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
----
-
-# Steel from Drawings — read a steel drawing into an interactive 3D model
-
-## What this is
-
-`steel-from-drawings` is a FloLess app that renders an interactive, **licence-free 3D model** of a
-steel frame (the `viewer-3d` agent) from a scene that **you, the terminal AI, bake from a drawing**.
-The drawing is read **at compose time** with your own vision — there is **no model in the run path
-and no AI API key**: the brain is you, in the terminal (the FloLess thin-UI contract). This is the
-**bake** strategy (`floless-app-rebake` is the generic version; this skill is the steel-specific one,
-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 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
-> `GET /api/requests` (match the id), don't run the pasted line verbatim, and `DELETE` it when done.
-
-## The loop
-
-1. **Find the drawing.** From a `rebake` request: `GET http://localhost:<port>/api/requests` → the
-   entry with `type:"rebake"` and `appId:"steel-from-drawings"` carries `snapshots: ["<abs path>"]`.
-   (Or the user just attaches/points at a drawing in prose — same procedure, skip the lookup.)
-2. **Read the drawing with your own vision.** Open the file (PDF or image) and READ it. If it's a
-   large multi-sheet PDF, focus on one framing plan / GA sheet (say which). This is the compose-time
-   extraction — your vision is the reader, not any API.
-3. **Extract a schematic 3D scene** in the schema below (§ Scene schema), following § Reading a steel
-   drawing. Aim for a complete, plausible stick model — the user confirms/nudges it in 3D.
-4. **Bake it INLINE into the app.** Replace the entire `scene:` mapping under the `view` node's
-   `config:` in the app's `.flo` with your extracted scene — in BOTH the installed copy
-   `~/.aware/apps/steel-from-drawings/steel-from-drawings.flo` AND the editable
-   `demos/steel-from-drawings/steel-from-drawings.flo` if present. Change ONLY the `scene:` block;
-   leave `inputs`, `requires`, the node id/agent/command, and everything else identical.
-5. **Recompile.** `aware app compile ~/.aware/apps/steel-from-drawings` → rewrites the `.lock`. The
-   source-hash changes, so FloLess's Run gate disarms until the user approves. Copy the fresh `.lock`
-   to `demos/steel-from-drawings/` if you keep the editable copy in sync.
-6. **Bake the SAME scene into `steel-to-ifc` (the IFC bake-out), if it's installed.** Check
-   `~/.aware/apps/steel-to-ifc/`. If present, replace the `scene:` mapping under that app's `bake-ifc`
-   node `config` (the `ifc` agent's `scene` input — NOT `config.args`; the app now calls the host-free
-   `ifc` AWARE agent, not an exec) with the IDENTICAL scene (the installed copy and `demos/steel-to-ifc/`
-   if 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. **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` (the `tekla` `bake-scene` verb's `scene` input — NOT `config.args`; the app now calls the
-   first-class `bake-scene` verb, not an exec) 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** 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)
-
-```yaml
-scene:
-  meta: { name: "<sheet title / drawing no.>", units: mm, up: z }
-  groups:                       # one per group you use; drives legend + colour
-    - { key: column, label: Columns, color: "#60a5fa" }
-    - { key: beam,   label: Beams,   color: "#94a3b8" }
-    # rafter #38bdf8, brace #818cf8 — add others as needed
-  elements:                     # one per member, kind: box (a from→to bar)
-    - { id: COL-A1, group: column, kind: box, from: [x,y,z], to: [x,y,z],
-        section: { w: 150, d: 150 }, meta: { profile: "HSS6x6x3/8", mark: "C1", grid: "A-1" } }
-  grids:                        # grid labels placed just outside the framing
-    - { label: A, at: [x,y,0] }
-  panels:                       # generic side tables; build a Takeoff
-    - title: Takeoff
-      note: "<assumptions, e.g. heights assumed — plan view, H=4.5 m>"
-      columns: [Section, "No.", Length]
-      rows: [["HSS6x6x3/8", 6, "27.0 m"]]
-```
-
-`from`/`to` are `[x,y,z]` in mm. `meta` is free-form (shown in the click-to-inspect panel) — put
-`profile`, `mark`, `grid` there. `section.w`/`d` are visual thickness only.
-
-## Reading a steel drawing (the method)
-
-1. **Grid.** Find the grid (A,B,C… one way, 1,2,3… the other, plus half-grids). Read the dimension
-   strings to place grids in mm; if a spacing is unreadable, assume a regular ~6000 mm bay and say so.
-2. **Sheet type & heights.** A PLAN view (top-down) shows no heights — pick one eave/storey height H
-   (a level/height note if present, else ~4500 mm) and note it; columns run z:0→H, beams/rafters sit
-   at z:H. An ELEVATION/SECTION gives real heights — read them.
-3. **Members.** One `elements` entry per member, size label exactly as drawn. Columns → `column`,
-   `from:[gx,gy,0] to:[gx,gy,H]`. Beams/rafters → `beam`/`rafter`, along the grid at z:H. Braces →
-   `brace`, the diagonal. Put the size in `meta.profile`, the mark in `meta.mark`, the grid ref in
-   `meta.grid`; approximate `section.w`/`d` from the profile (W12≈300×310, HSS6x6≈150×150, L≈90×90).
-4. **Takeoff.** One row per distinct profile (count + total length in m). Assumptions in the note.
-5. **meta.name** = the sheet title / drawing number. Never invent grids or members the drawing does
-   not show; if a sheet has no readable steel framing, bake an empty `elements` with a note saying so.
-
-## Guardrails
-
-- **Compose-time only.** The drawing is read HERE, by you, then baked. Never add a runtime node that
-  reads the drawing — `aware app validate` rejects it and it breaks determinism.
-- **Scene, not logic.** Re-bake only the `view.scene` block. A different output (new columns, a
-  schedule) is a workflow change — use `floless-app-workflows`, not this.
-- **Schematic + honest.** ~90% is the goal; the user tidies the last 10% in 3D. State your
-  assumptions (heights, assumed bays) in the takeoff note. Don't fabricate sizes the drawing lacks.
-- **Thin-UI contract.** The browser only recorded intent + the drawing; the brain is you, in the
-  terminal. The UI never reads the drawing and never bakes.
-- **Resolve the port** from the running floless.app the same way the other floless-app skills do.

package/dist/templates/steel-from-drawings.flo

@@ -1,73 +0,0 @@
-app:           steel-from-drawings
-version:       0.1.0
-display-name:  Steel from Drawings
-description: |
-  Turn a structural steel drawing into an interactive, licence-free 3D model — no Tekla, no
-  modelling, no AI API key. Your terminal AI (Claude Code / Codex) reads the drawing once and
-  bakes a schematic 3D scene into this app; the viewer-3d agent renders it as an interactive
-  document anyone can orbit, click to inspect, and take off (counts + length by section) — so an
-  estimator, PM, fabricator or client can understand and price the steel before opening a seat.
-
-  The reading is a COMPOSE-TIME act — the FloLess way: the app is the prompt in your terminal, so
-  the brain is your AI terminal, never this server, and there is never a model in the run path.
-  Attach a drawing and use "Re-read & re-bake ▸" (or just ask your terminal AI to read it). The AI
-  reads the grids, members and sizes and bakes them straight into the `view` node's `scene` below
-  (the viewer-3d scene schema), recompiles, and asks you to approve; the deterministic run then
-  only renders the approved scene. Ships with a small example scene so it renders out of the box —
-  the `floless-app-steel-from-drawings` skill teaches your terminal AI how to read your own drawing in.
-exposes-as-agent: false
-inputs:
-  # BAKED at compose time: the terminal AI reads this drawing and writes the `view.scene` block
-  # below (the run never reads the drawing). read-strategy: bake surfaces "Re-read & re-bake ▸" so
-  # you can swap the drawing and have your AI re-read it. No runtime input node.
-  drawing:
-    type: image
-    widget: file
-    accept: [pdf, png, jpg]
-    read-strategy: bake
-    description: A structural steel drawing (framing plan / GA / elevation) — baked into the scene below; swap it to re-read & re-bake.
-requires:
-  - viewer-3d@0.1.x
-layout: linear
-nodes:
-  # The viewer-3d render node IS the terminal. Ships with a small EXAMPLE scene (a sample 3x2 bay
-  # frame, schematic) so the app renders out of the box. Re-bake — or the
-  # floless-app-steel-from-drawings skill — replaces this whole `scene` with a reading of YOUR drawing.
-  - id: view
-    agent: viewer-3d
-    command: render
-    config:
-      scene:
-        meta: { name: "Example — steel framing (sample, not your drawing)", units: mm, up: z }
-        groups:
-          - { key: column, label: "Columns (HSS6x6x3/8)", color: "#60a5fa" }
-          - { key: beam,   label: "Beams (W10x33)",       color: "#94a3b8" }
-        elements:
-          # 6 columns (z 0 -> 4500) on a 3 x 2 grid
-          - { id: COL-1A, group: column, kind: box, from: [0,0,0],       to: [0,0,4500],       section: { w: 150, d: 150 }, meta: { profile: "HSS6x6x3/8", grid: "1-A" } }
-          - { id: COL-2A, group: column, kind: box, from: [6000,0,0],    to: [6000,0,4500],    section: { w: 150, d: 150 }, meta: { profile: "HSS6x6x3/8", grid: "2-A" } }
-          - { id: COL-3A, group: column, kind: box, from: [12000,0,0],   to: [12000,0,4500],   section: { w: 150, d: 150 }, meta: { profile: "HSS6x6x3/8", grid: "3-A" } }
-          - { id: COL-1B, group: column, kind: box, from: [0,6000,0],    to: [0,6000,4500],    section: { w: 150, d: 150 }, meta: { profile: "HSS6x6x3/8", grid: "1-B" } }
-          - { id: COL-2B, group: column, kind: box, from: [6000,6000,0], to: [6000,6000,4500], section: { w: 150, d: 150 }, meta: { profile: "HSS6x6x3/8", grid: "2-B" } }
-          - { id: COL-3B, group: column, kind: box, from: [12000,6000,0],to: [12000,6000,4500],section: { w: 150, d: 150 }, meta: { profile: "HSS6x6x3/8", grid: "3-B" } }
-          # roof beams at z 4500 (W10x33): along each row, then tie beams along each grid line
-          - { id: BM-12A, group: beam, kind: box, from: [0,0,4500],      to: [6000,0,4500],      section: { w: 150, d: 250 }, meta: { profile: "W10x33", grid: "A" } }
-          - { id: BM-23A, group: beam, kind: box, from: [6000,0,4500],   to: [12000,0,4500],     section: { w: 150, d: 250 }, meta: { profile: "W10x33", grid: "A" } }
-          - { id: BM-12B, group: beam, kind: box, from: [0,6000,4500],   to: [6000,6000,4500],   section: { w: 150, d: 250 }, meta: { profile: "W10x33", grid: "B" } }
-          - { id: BM-23B, group: beam, kind: box, from: [6000,6000,4500],to: [12000,6000,4500],  section: { w: 150, d: 250 }, meta: { profile: "W10x33", grid: "B" } }
-          - { id: BM-1AB, group: beam, kind: box, from: [0,0,4500],      to: [0,6000,4500],      section: { w: 150, d: 250 }, meta: { profile: "W10x33", grid: "1" } }
-          - { id: BM-2AB, group: beam, kind: box, from: [6000,0,4500],   to: [6000,6000,4500],   section: { w: 150, d: 250 }, meta: { profile: "W10x33", grid: "2" } }
-          - { id: BM-3AB, group: beam, kind: box, from: [12000,0,4500],  to: [12000,6000,4500],  section: { w: 150, d: 250 }, meta: { profile: "W10x33", grid: "3" } }
-        grids:
-          - { label: "1", at: [0,-3000,0] }
-          - { label: "2", at: [6000,-3000,0] }
-          - { label: "3", at: [12000,-3000,0] }
-          - { label: "A", at: [-3000,0,0] }
-          - { label: "B", at: [-3000,6000,0] }
-        panels:
-          - title: Takeoff
-            note: "EXAMPLE — not your drawing. A sample steel frame on a 1-3 x A-B grid; sizes & heights are illustrative. Use 'Re-read & re-bake ▸' (or ask your terminal AI) to read your own drawing."
-            columns: [Section, "No.", Length]
-            rows:
-              - ["HSS6x6x3/8", 6, "27.0 m"]
-              - ["W10x33", 7, "42.0 m"]

package/dist/templates/steel-to-ifc.flo

@@ -1,294 +0,0 @@
-app:           steel-to-ifc
-version:       0.1.0
-display-name:  Steel to IFC
-description: |
-  Bake a read steel model OUT to a universal IFC file — open it in Tekla, SDS2, Revit or
-  Navisworks. Companion to steel-from-drawings: that app reads a drawing into a 3D scene and shows
-  it; this one writes the SAME scene to an IFC file (IfcColumn/IfcBeam as extruded sections on the
-  real grid) so you can take the schematic model straight into your detailing tool and finish there.
-
-  Same terminal-bake pattern — the FloLess way: your AI terminal bakes the scene inline
-  (read-strategy: bake); a deterministic, MODEL-FREE exec node writes the .ifc (no Tekla needed to
-  export — it never touches a Tekla model, just writes the file). Ships with the same EXAMPLE
-  frame so it runs out of the box; the floless-app-steel-from-drawings skill bakes your drawing's
-  scene into both apps so the IFC matches what you saw in 3D.
-exposes-as-agent: false
-inputs:
-  # BAKED at compose time: the terminal AI reads this drawing and writes the `scene` block below
-  # (the run never reads the drawing). read-strategy: bake surfaces "Re-read & re-bake ▸".
-  drawing:
-    type: image
-    widget: file
-    accept: [pdf, png, jpg]
-    read-strategy: bake
-    description: A structural steel drawing — baked into the scene below, then written out as IFC; swap it to re-read & re-bake.
-  output_path:
-    type: string
-    default: steel-from-drawings.ifc
-    description: Where to write the .ifc — FloLess fills this with your Downloads folder; editable per run.
-requires:
-  - ifc@0.1.x
-layout: linear
-nodes:
-  # Model-free exec: reads the baked `scene` and writes a valid IFC4 file (IfcColumn/IfcBeam as
-  # extruded rectangle sections on the real grid), returning a summary report. NEVER derefs `model`
-  # (no Tekla needed); writes the .ifc via System.IO to the user's Downloads (or home). Re-bake —
-  # or the floless-app-steel-from-drawings skill — replaces `scene` with YOUR drawing's read.
-  - id: bake-ifc
-    agent: ifc
-    command: write
-    config:
-      scene:
-        meta:
-          name: "Example \u2014 steel framing (sample, not your drawing)"
-          units: mm
-          up: z
-        groups:
-        - key: column
-          label: Columns (HSS6x6x3/8)
-          color: '#60a5fa'
-        - key: beam
-          label: Beams (W10x33)
-          color: '#94a3b8'
-        elements:
-        - id: COL-1A
-          group: column
-          kind: box
-          from:
-          - 0
-          - 0
-          - 0
-          to:
-          - 0
-          - 0
-          - 4500
-          section:
-            w: 150
-            d: 150
-          meta:
-            profile: HSS6x6x3/8
-            grid: 1-A
-        - id: COL-1B
-          group: column
-          kind: box
-          from:
-          - 0
-          - 6000
-          - 0
-          to:
-          - 0
-          - 6000
-          - 4500
-          section:
-            w: 150
-            d: 150
-          meta:
-            profile: HSS6x6x3/8
-            grid: 1-B
-        - id: COL-2A
-          group: column
-          kind: box
-          from:
-          - 6000
-          - 0
-          - 0
-          to:
-          - 6000
-          - 0
-          - 4500
-          section:
-            w: 150
-            d: 150
-          meta:
-            profile: HSS6x6x3/8
-            grid: 2-A
-        - id: COL-2B
-          group: column
-          kind: box
-          from:
-          - 6000
-          - 6000
-          - 0
-          to:
-          - 6000
-          - 6000
-          - 4500
-          section:
-            w: 150
-            d: 150
-          meta:
-            profile: HSS6x6x3/8
-            grid: 2-B
-        - id: COL-3A
-          group: column
-          kind: box
-          from:
-          - 12000
-          - 0
-          - 0
-          to:
-          - 12000
-          - 0
-          - 4500
-          section:
-            w: 150
-            d: 150
-          meta:
-            profile: HSS6x6x3/8
-            grid: 3-A
-        - id: COL-3B
-          group: column
-          kind: box
-          from:
-          - 12000
-          - 6000
-          - 0
-          to:
-          - 12000
-          - 6000
-          - 4500
-          section:
-            w: 150
-            d: 150
-          meta:
-            profile: HSS6x6x3/8
-            grid: 3-B
-        - id: BM-12A
-          group: beam
-          kind: box
-          from:
-          - 0
-          - 0
-          - 4500
-          to:
-          - 6000
-          - 0
-          - 4500
-          section:
-            w: 150
-            d: 250
-          meta:
-            profile: W10x33
-        - id: BM-23A
-          group: beam
-          kind: box
-          from:
-          - 6000
-          - 0
-          - 4500
-          to:
-          - 12000
-          - 0
-          - 4500
-          section:
-            w: 150
-            d: 250
-          meta:
-            profile: W10x33
-        - id: BM-12B
-          group: beam
-          kind: box
-          from:
-          - 0
-          - 6000
-          - 4500
-          to:
-          - 6000
-          - 6000
-          - 4500
-          section:
-            w: 150
-            d: 250
-          meta:
-            profile: W10x33
-        - id: BM-23B
-          group: beam
-          kind: box
-          from:
-          - 6000
-          - 6000
-          - 4500
-          to:
-          - 12000
-          - 6000
-          - 4500
-          section:
-            w: 150
-            d: 250
-          meta:
-            profile: W10x33
-        - id: BM-1AB
-          group: beam
-          kind: box
-          from:
-          - 0
-          - 0
-          - 4500
-          to:
-          - 0
-          - 6000
-          - 4500
-          section:
-            w: 150
-            d: 250
-          meta:
-            profile: W10x33
-        - id: BM-2AB
-          group: beam
-          kind: box
-          from:
-          - 6000
-          - 0
-          - 4500
-          to:
-          - 6000
-          - 6000
-          - 4500
-          section:
-            w: 150
-            d: 250
-          meta:
-            profile: W10x33
-        - id: BM-3AB
-          group: beam
-          kind: box
-          from:
-          - 12000
-          - 0
-          - 4500
-          to:
-          - 12000
-          - 6000
-          - 4500
-          section:
-            w: 150
-            d: 250
-          meta:
-            profile: W10x33
-        grids:
-        - label: '1'
-          at:
-          - 0
-          - -3000
-          - 0
-        - label: '2'
-          at:
-          - 6000
-          - -3000
-          - 0
-        - label: '3'
-          at:
-          - 12000
-          - -3000
-          - 0
-        - label: A
-          at:
-          - -3000
-          - 0
-          - 0
-        - label: B
-          at:
-          - -3000
-          - 6000
-          - 0
-      output-path: "{{ inputs.output_path }}"