layerling 1.60.0

• Fill modes for the Text shape, and "Wider": A text can now be drawn as sketches and SVGs are since 1.47: Stroke Outside, Inside or Centred with a line width and corner style, and as a Silhouette without the counters of its letters. New for text, sketches and SVG alike is the fill mode Wider: the filled shape grown outwards by the line width all round, with sharp, round or bevelled corners - the piece that was missing for a filled base layer under a text or logo. A name tag for a multicolour print is three copies of one text: the letters, the same text 1.5 mm wider in a second colour, and 3 mm wider as a silhouette (no holes) carrying the key ring. The box of the text grows with an outside, centred or wider stroke, so the letters keep their size and the layers line up; the letters are exact bodies for the edge tool and STEP in every mode, and letters that run together become one piece. The MCP bridge takes stroke (with align: "grow") and silhouette on a text as on a sketch body. Asked for by @plazmabokor in #215.
• Layered text and name tags: The properties of a text have a Layers card: Split into layers turns the text into a stack - white letters on top, the same text 1.5 mm wider in red under them, 3 mm wider as a dark plate without holes at the bottom - as a bundle that moves as one, every layer a text of its own with its own colour and height, the way a slicer wants them for a multicolour print. With the stack selected the card edits text, font, the number of layers (up to six) and, per layer, how much wider it is, its height, colour and whether it keeps the holes; every change builds the stack again, and new words run through all layers. The card also takes a name list, one name per line, up to a hundred, and makes a tag like the selected text or stack for each, in rows with a chosen gap. The MCP bridge does the same with layerling_layer_text. Asked for by @plazmabokor in #215.
• The static export builds with Next.js 16: npm run export stopped with "This build is using Turbopack, with a webpack config and no turbopack config" on a machine that had Next.js 16. Next.js 16 builds with Turbopack by default and refuses a webpack hook without a turbopack entry; next.config.ts now carries an empty one. Next.js 15, which package.json pins, ignores it for webpack builds. With that fixed, Next.js 16 built with Turbopack, and the export check then failed with "Could not find the generated CAD worker runtime": the CAD worker is bundled by webpack. The export script now builds with --webpack when Next.js is 16 or newer (15 does not know the flag). Reported by @ARSoderberg in #217 and #218, who found both fixes.