Giraffe Changelog

We've been rebuilding Giraffe from the ground up, and it's almost ready. Giraffe 6.0 is scheduled to land in your browser in a little over a week.

Giraffe 6.0 will be opt-in to start - you can choose to stay on Giraffe 4.0 as long as you wish.

TL/DR version:

• Configurable layouts you can drag, resize, save, and revisit, plus dark mode
• A home screen and admin workspace that finally makes sense
• A drawing toolbar rebuilt from first principles, alongside a stack of smaller fixes that make it feel snappier
• One searchable library holding every asset you've got
• True generative design for multi-family and parking
• Brand new apps like scenes and spreadsheet, plus many paper enhancements

Here's a first look at what's coming.

A brand new interface

Giraffe's whole workspace has been redesigned. Panels are dockable and resizable, so you can arrange Map, Layers, Properties, and every other app exactly how you work. Save your arrangement as a layout, switch between layouts with a click, and share your favorite setups with your team. A new top bar and a redesigned drawing toolbar make everything easier to find.

A new place to start

Manage your projects, workspace settings, and account from one place. Sort and filter your projects table, batch edit properties, and add custom branding to your workspace home page. Plus, curated templates for multifamily, industrial, and mixed-use.

A heftier drawing toolset

A new two-row toolbar puts every drawing tool, plus a searchable command menu, within reach. Under the hood, dozens of fixes make drawing and editing feel tighter across the board.

A rebuilt Content Library

Your blocks, usages, flows, and layers now live in one rebuilt Content Library, with clear sections for your workspace, the marketplace, and anything you publish. Preview items before you use them, organize your own packs, and find what you need faster.

New generative design tools

Two new tools do the heavy lifting for you. The Garden tool lays out landscaping along a site edge in seconds. The Wrap tool generates a full building wrap, complete with garages, corridors, courtyards, and residential units.

New apps, built right in

Giraffe is growing. A new Excel-style spreadsheet app pulls numbers straight from your live project. A Multi-Family Cockpit generates a matching site plan as you adjust the deal. And a new Industrial site planner finds the largest building footprint that fits your lot.

Want Giraffe 6.0 now?

Sign up here for early access.

For a long time, every new project in Giraffe started the exact same way: a blank map, and a blank slate. We built it that way on purpose. Flexibility felt like the safer bet, don't assume what someone's building, just give them everything and let them figure it out.

Spotting what needs fixing

We look at three things together:

• Usage patterns. Anonymised data on how people actually move through Giraffe, no personal info, just where people click, pause, or get stuck.
• Support conversations. Every chat with GiraffeBot, plus every direct conversation Holly and Adam have with customers.
• Direct feedback. Calls and check-ins with the people using Giraffe day to day.

We also weigh what we find against established usability principles, like Jakob Nielsen's classic ten heuristics, so we're fixing things that genuinely help, not just reacting to noise.

For this one, the clearest signal came from a simple question we already ask at signup: what are you building? Residential, industrial, and mixed-use came back as the three most common answers by a clear margin, which is exactly why those are the three templates we built first.

What we found in the data

An open-ended blank canvas sounds like the flexible choice. In practice, it just moves the same setup work onto every single person, every single project, and the numbers back that up from a few different angles.

• People tried to configure this by hand, and it often didn't go well. Close to half of everyone who opened the usage editor to set up a building type from scratch left without saving anything. A similar pattern showed up in the content library: most people who browsed it left without importing anything, roughly 7 in 10. A smaller group found their own workaround, cloning an existing usage and adapting it by hand, essentially building a makeshift template because a real one didn't exist.
• A lot of people never make it to actually drawing. Meaningfully fewer people ever get to editing and refining geometry than get to creating it in the first place. Usage configuration sits right at that drop-off point, the step between opening a project and doing real work on it.
• The support data mirrors this exactly. Well over 1,000 conversations in a single period were procedural questions, people asking how to set up an industrial usage, or what to use for a warehouse, the kind of question a curated starting point answers before it's even asked. None of this reflects the product being broken. It reflects people arriving with a specific project in mind and having to navigate a generic library to figure out what applied to them.

What we built

New workflow-specific templates, built for multifamily, industrial, and mixed-use projects, preloaded with the usages, flows, apps, and layouts that actually fit that kind of work. Even the lightning bolt flows reflect the template's content, so nothing in the toolkit feels generic. It's all tailor-made for the workflow you've selected. Choose the template that matches the deal in front of you, and skip straight past the setup that a blank canvas would have made you do from scratch.

What this means for you

Less time recreating the same setup you've built a dozen times before, more time on the parts of the deal that actually need your judgement. A multifamily template won't make you sift through warehouse uses. An industrial template won't bury you in dwelling types. It's a small change with a compounding effect: every new project starts closer to real work instead of further from it.

Part of a series on the reasoning behind Giraffe 6.0. See also our posts on the new home screen, configurable layouts, project creation, properties palette, content consolidation, the rebuilt drawing toolbar, and drawing quality of life improvements.

When we first built Giraffe, we made a sneaky little assumption: that everyone thinks in maps. Open a map, find your site, start drawing. Great if you're hunting for a new site. Not so great if you're not. So a fair few people were stuck wading through a map just to check on a project they already had.

Spotting what needs fixing

Here's how we know it wasn't just a handful of people finding this awkward.

• Usage patterns. Anonymised data on how people actually move through Giraffe, no personal info, just where people click, pause, or get stuck.
• Support conversations. Every chat with GiraffeBot, plus every direct conversation Holly and Adam have with customers.
• Direct feedback. Calls and check-ins with the people using Giraffe day to day.

We also weigh what we find against established usability principles, like Nielsen's heuristics, so we're fixing things that genuinely help, not just reacting to noise.

What we found in the data

In this case, all data pointed the same way: people getting stuck in a Space when they just wanted their project list, and admins asking, in plain terms, for a simpler view of their own workspace.

• Getting your bearings. People kept getting lost, and not just a little. Chats with GiraffeBot show it clearly: more than 50 conversations where it had to explain "you're in a Space, that's why you can't draw." Not a one-off. A proper pattern.
• Finding what you've already done. Close to 180 conversations were just people trying to track down projects they'd already made. Most never even found the project switcher on their own.
• Doing things the way other tools do. Most software gives you a simple home screen, not a map. If site search isn't your main job, you shouldn't need a map just to see your own project list.
• Staying in control. Admins told us straight: "I just need to see all of our projects." Right now that meant building a whole space just for a list. Way too many steps for something this simple.
• Getting basic numbers without a spreadsheet. We've heard the same thing from bigger teams too, admins wanting an easy way to check basic numbers, like how many projects got made last month, without digging through spreadsheets or manual exports.

What we built

The new home screen shows your recent projects and quick actions the second you log in. No map required. Admins get a clear view of the whole workspace too, without needing to open a project first.

What this means for you

If your day is mostly about projects, not hunting for new sites, you don't need to think in maps anymore. Your recent work, your quick actions, everything you need is right there when you log in. That includes your own stuff, your admin tools if you've got them, and your personal settings too.

This is one part of a broader look at what's changing in Giraffe 6.0. Curious about the thinking behind the changes? We put together a bigger-picture look at why we're making these changes across the whole product.

Read the full story →

Some of the best fixes are the ones you never notice, until they're gone. Nothing about drawing in Giraffe was broken. It just had small frictions that added up: control points only ever landing at the centre of an edge, no dedicated mode for reshaping what you'd drawn, no quick way to bump levels or base height without opening a panel.

Spotting what needs fixing

We look at three things together:

• Usage patterns. Anonymised data on how people actually move through Giraffe, no personal info, just where people click, pause, or get stuck.
• Support conversations. Every chat with GiraffeBot, plus every direct conversation Holly and Adam have with customers.
• Direct feedback. Calls and check-ins with the people using Giraffe day to day.

We also weigh what we find against established usability principles, like Jakob Nielsen's classic ten heuristics, so we're fixing things that genuinely help, not just reacting to noise.

For this one, there wasn't a single big red flag the way there was with some of the other 6.0 changes. It showed up as a pattern of small, recurring gripes, the kind of thing people mention almost in passing rather than filing as a proper complaint.

What we found in the data

None of these were "Giraffe is broken" problems. They were "this is more annoying than it needs to be" problems.

• The default should protect against mistakes, not cause them. Edit mode used to be the default, so an accidental click could add a point or drag one when someone meant to move the whole shape. More than a dozen conversations show the fallout: unintended changes with no clean way back beyond undo. Nobody names the mechanic directly, but the damage is clear.
• Precision shouldn't require a workaround. Adding a control point only ever landed at the centre of an edge by default, so placing one anywhere else meant dropping it there first and then dragging it into position, rather than placing it exactly right on the first click. Many support conversations touch on exactly this, and the usage data backs it up: active users trigger Edit Section close to 800 times a month on average, with the median edit firing within 5 seconds of creating a section, before they've moved on to anything else. Precision needs to be available in that same instant, not after a workaround.
• Small adjustments shouldn't need a detour. Well over 150 messages across dozens of conversations asked about setting levels and/or floor-to-floor. At least ten people asked where the properties palette had gone. Levels, floor-to-floor, and base height were the most-asked-about properties overall, almost always some version of "where is this" or "I changed it and something broke."

What we built

Scale and move become the default. Flip into edit mode to reshape an edge, and alt-click to drop a point exactly where you want it, not just the centre. New shortcuts drag levels and base height up in one motion, no detour required. Push/pull gets a spot on the draw bar as a bonus, alongside a new integrated command line.

What this means for you

Precision where you want it, without a workaround. A clear mode for reshaping, instead of guessing. Fewer trips out of the drawing flow for small, repeated adjustments. Nothing flashy, just drawing that's snappier, faster, and harder to get wrong.

Flows and Blocks from your project's content library are also coming to the drawing toolbar itself, so grabbing something you've already built is a click away.

Part of a series on the reasoning behind Giraffe 6.0. See also our posts on the new home screen, configurable layouts, project creation, properties palette, content consolidation, and the rebuilt drawing toolbar.

At the end of the day, real estate is just polygons on a map. A building is a shape. A driveway is a shape. A patch of grass is a shape.

But Giraffe didn't treat it that way; it sorted everything by type first. A driveway was infrastructure. A building was a use class. A patch of grass was its own category.

Classification is important for the data and calculations underneath, but it's a pretty confusing way to ask someone to start drawing.

Spotting what needs fixing

Here's how we know that typology-based drawing tools were actually getting in people's way.

• Usage patterns. Anonymised data on how people actually move through Giraffe, no personal info, just where people click, pause, or get stuck.
• Support conversations. Every chat with GiraffeBot, plus every direct conversation Holly and Adam have with customers.
• Direct feedback. Calls and check-ins with the people using Giraffe day to day.

We also weigh what we find against established usability principles, like Nielsen's heuristics, so we're fixing things that genuinely help, not just reacting to noise.

For this one, the pattern was hard to miss: people asking how to draw basic shapes, and usage data showing the same drawing mistakes happening over and over, right alongside each other.

What we found in the data

In this case, the pattern was hard to miss: people asking how to draw basic shapes, and usage data showing the same drawing mistakes happening over and over, right alongside each other.

• Letting you work the way you naturally think. People think in shapes, rectangles, circles, lines, not in Giraffe's internal categories. More than one person asked outright how to draw a basic rectangle. Simple as that sounds, the old toolbar didn't make a plain shape like that the obvious first step.
• Making it quick to draw the same thing again. We've heard this show up as wanting to draw several of the same thing in a row without resetting everything each time. People were working around it with things like the eyedropper tool, or drawing a throwaway shape off to the side just to copy its settings.
• Not making you memorise a whole system just to start. The old toolbar made you recall which category something fell under before you could even draw it. Is a driveway a road? A landscape feature? A building part? That's a lot of thinking before you've drawn a single line.
• Keeping your most-used tools close by. Nearly three out of four people opened the properties panel within five minutes of drawing something. Over 90 days, that added up to more than 70,000 edits. Properties aren't an afterthought, they're part of the same act of creating.
• Avoiding easy mistakes. People kept making the same two errors, wrong layer, wrong use type, then correcting them right after. One person put it well: "How am I supposed to know what kind of layer it is? I drew a 3D boardwalk and that's under the Infrastructure dropdown." We also saw people deleting drawing layers about as often as they made them, a pretty good sign folks weren't always sure what a layer was for until well after they'd made it.

What we built

The rebuilt drawing toolbar leads with plain shapes, polygon, line, point, instead of selecting from a categorized tool first.

With the pet palette, you don't need to already know how Giraffe classifies a use to start drawing. You can pick from a list instead of having to remember whether something counts as a building, a landscape feature, or a road. Search the same usage list no matter what type of thing you're creating, instead of a different setup for every category.

What this means for you

You'll sketch faster, because you're not stuck figuring out Giraffe's categories before you've even drawn the shape in your head. Less wrestling with the tool, more time actually exploring the design options that matter.

This is one part of a broader look at what's changing in Giraffe 6.0. Curious about the thinking behind the changes? We put together a bigger-picture look at why we're making these changes across the whole product.

Read the full story →

A handful of fixes landed this week to smooth out some rough edges across projects, scenarios, and flows. Here's what's changed:

• Content Library now imports usages correctly from "import from another project."
• Scenarios are now available in view-only mode.
• Fixed a crash when setting Type to Building Section with a scalar dwelling count. We've also added a warning in the property editor when a Type is set, with a button to clear it if needed.
• Baking flows no longer incorrectly writes dwelling units from the usage to the geometry.

Want to see what else we're working on? Check out our Giraffe 6.0 release series.

Real estate software has a tough job. It has to work for architects doing massing studies, planners doing site analysis, and developers crunching numbers on a deal, all on the same platform.

Giraffe used to have one fixed layout for everyone. It meant everyone was stuck working around a setup that wasn't really built for their job. The fixed layout was holding people back, and it needed to go.

Spotting What's Worth Fixing

Here's how we know wasn't just a hunch.

• Usage patterns. Anonymised data on how people actually move through Giraffe; where people click, pause, or get stuck.
• Support conversations. Every chat with GiraffeBot, plus every direct conversation Holly and Adam have with customers.
• Direct feedback. Calls and check-ins with the people using Giraffe every day.

We also weigh what we find against established usability principles, like Nielsen's heuristics, so we're fixing things that genuinely help, not just reacting to noise.

What we found in the data

In this case, the usage data was the loudest signal: constant panel switching, especially on smaller screens, backed up by a steady stream of "where do I find X" messages that pointed to the same root cause.

• Matching how people actually work. Different jobs need different tools. One person put it simply: "how do I use for site analysis." We saw dozens of messages like that just this year. Close to 200 messages asked some version of "where do I find X." A clear sign the old layout wasn't easy to navigate.

• Working without constant back and forth. People switched between panels more than four times a session on average, with more than a quarter of sessions clocking up five or more switches. Not choice. The layout getting in the way.
• Staying in control of your own setup. People on smaller screens switched panels around half again as often as people on big monitors. A fixed layout just doesn't work the same for everyone.
• Seeing more than one app at a time. This one's been on our radar a while, people wanting to view data or run a function from a couple of different apps at once, instead of only ever seeing one at a time.

What we built

App locations aren't fixed anymore. Create, split, and merge panels. Drag them, resize them, dock them wherever you need. Create multiple layouts in every project for different workflows. Your setup sticks around for next time too. Plus, a redesigned top bar makes getting around easier, no matter how you've set things up.

• Merge, split, and drag apps where you want them.

• Save multiple panel layouts in templates and projects to swap between different types of work.

• Only see what you use - remove what you don't!

What this means for you

Less time messing with your screen, more time doing the actual work. The analysis, the massing study, the client meeting.

Deep in site analysis? Put Map and Layers side by side. Meeting a client? Clear the clutter and show only what matters. Working from a laptop on-site instead of a big office monitor? The layout actually fits now, instead of you squinting to find things.

And once you build a setup you like, Giraffe remembers it. You shouldn't have to rebuild your canvas every single time you open a project. Nobody's got time for that.

This is one part of a broader look at what's changing in Giraffe 6.0. Curious about the thinking behind the changes? We put together a bigger-picture look at why we're making these changes across the whole product.

Read the full story →

This release brings two major additions — nested block editing and a new dwelling section type — alongside a batch of fixes across blocks, apartment layouts, and space navigation.

Nested Block Editing

Edit a block definition from inside another block edit!

The block editor header now shows a breadcrumb trail (Project › parent block › current block) with unsaved-change indicators at each level, click-to-rename on the current block, and context-aware Save & Return / Save & Exit buttons (Discard only appears when there are unsaved changes).

Entering and exiting nested edits is fully undoable, saving with no changes no longer rewrites the block definition, and a failed save (e.g. block too large) shows an error and keeps the edit open.

Dwelling Usage Type

A new "dwelling" type, selectable from the Usage Type dropdown, behaves like a building section but represents individual dwellings.

Assign a usage and the section counts as one dwelling per level or a fixed count (toggle in the new Dwellings editor), with per-dwelling residents, price, and parking rates; a warning appears if no usage is assigned. Dwelling sections participate in stacking, site clipping, the Urban dashboard, and Precinct scenario tables alongside regular building sections.

Other Updates

• A new info modal (ⓘ button on the Block property group) explains how block propagation modes work.
• The levels property now always propagates from block instances to their contents by default.
• Fixed an issue with the isTopOfStack property not calculating properly.
• Fixed mirrored block instances producing polygons with reversed winding order, which broke urban/analytics.
• Duplicating a project now keeps its scenarios, including section-to-scenario assignments.
• Auto-generated apartment mixes now use a seed derived from the outline's geometry instead of the feature id, so identical or copy/pasted outlines produce the same mix, and the mix no longer re-shuffles while dragging outline vertices.
• Dwelling-type slices in the Urban app's Residential pie chart are now colored with their usage colors instead of a generic palette.
• Fixed a coordinate-precision issue in apartment layouts (values were being rounded to the nearest meter) that made clicking and resizing apartment subdivisions unreliable.
• Fixed an issue where the "Draw Polygon" method in Lightning Bolt flows wasn't applying the flow
• Navigating from a project back to a space no longer re-zooms the camera — the view stays where it was.
• Fixed an issue with loading image features
• Fixed an issue where the solar preview would render above the actual building geometry instead of aligning with it
• Hover / left click select only chooses one lensed feature. Works for outline only polygon layers too (you used to have to click on the line)
• Fixed single-click selection not working on GeoJSON layers when using the lens tool
• Added the option to proxy WMS servers that don't natively support HTTPS
• Features whose image URL fails to load now show the broken-image placeholder instead of never rendering.
• Fixed the checkout Purchase button staying enabled over an empty payment form after the payment form reloads.
• Refreshed checkout styling: the payment form now uses a compact layout with fonts and colors consistent with the rest of the app.
• SDK calls to setIsolatedFeatures / clearIsolatedFeatures are now ignored (with a console warning) while a block edit is in progress, instead of corrupting the edit session.
• useGiraffeState('projects') stale value fix (SDK)
• Fixed an issue with project geometry created by SDK

This release focuses on stability and polish across the map, drawing tools, and workflows, with fixes for lens filtering, polygon merging, temporary layers, and parking layouts, plus a few new capabilities like always-on snapping and modify-property workflow nodes.

Drawing & Snapping

• Added an "Always on" snapping option — keeps snapping enabled by default and hold S to temporarily disable it (instead of holding S to snap). Find it in the snap settings!
• Fixed extrude end-of-line issue.
• Improved polygon feature-merger precision and reliability (higher coordinate precision, proper handling of ring closure and degenerate rings).
• Fixed right-click merge of surrounding polygons across tile boundaries.
• Faster, more reliable label placement on very large polygons.

Map, Layers & Styling

• Fixed legacy lens filters crashing the data table's set filter and causing them to diverge from map filtering.
• Colors now auto-populate correctly when styling a layer by a data property.
• Fixed lens (conditional/data-driven) styling not applying to multi-style and tiled temporary layers, including incorrect lens-table headers/formatting.
• Fixed temporary layers flickering or vanishing on quick view reloads; show/hide now updates reliably.
• Properties in the lens and selection panel now display in the correct configured column order with proper formatting.
• Improved lens-table filtering performance (no more lag while typing).
• Match lens / right-click outlines fixed.

Flow

• Added "modify property" and "modify feature property" nodes for applying math operations (add, subtract, multiply, divide, modulo, power, set) to numeric properties, including across lists.
• Fixed a crash affecting stroke dash and parking algorithms.
• Parking bays now lay out against the actual edges of holes/exclusions instead of a buffered offset.
• Fixed grouping of list-valued properties (e.g. scenarios) so each value is counted separately.

SDK

• Added updateLayerTreeVisibility for pushing layer visibility/opacity/group state changes to the map.
• Camera tilt/rotation from flyTo/fitBounds now works correctly when transitioning from 2D to 3D view.
• Project creation via SDK now rejects invalid layer trees with a clear error instead of corrupting the project.

Enterprise & Workspace

• Home app is no longer installed by default for Enterprise, but remains available in the app library to add/remove as needed.
• Workspace member list is now visible to all admins on the access-restricted screen, not just billing admins.

Reliability & Misc.

• Added a new command-line command to recalibrate stack order, fixing property values on geometries that get too high.
• Fixed engine status bar overflow on narrow screens.
• Fixed image feature opacity control.
• Minor UI tweaks to the block editor.
• Removed the ability to create a project directly on lines.
• Content pack import now validates layer structure and shows a clear error instead of silently breaking.
• Links are now only auto-detected when text starts with http://, https://, or www..

Giraffe v5.8.0 brings a significantly expanded flow system, a rebuilt Content Library with a new feature picker, and a suite of new drawing and modelling tools. This release also includes a raft of quality-of-life improvements — from project cleanup tools and a save status indicator to a faster engine and a friendlier crash experience.

✨ New features

Design Library, rebuilt inside Content Library Your saved designs now live inside the Content Library. When importing from a project, you can pick exactly the features you want using a combined map and table view — marquee-select on the map, hover highlighting, column filtering, and zoom-to-extents.

Access Design Library functions from Content Library > Import from Project.

Patch drawing tool A new Patch tool lets you draw a polygon where each corner has its own height, making it easy to model sloped slabs and wedge-shaped surfaces. Edit slab/wedge type and per-corner values in the property editor; hovering a corner input highlights the corresponding vertex on the map.

Project cleanup tools A new cleanup menu in project settings lets you bulk-delete empty draw layers, unused usages, unused flows, unused blocks, and unused scenarios — each showing a live count with a confirmation prompt before deletion. You can also reset usages to Giraffe defaults.

Context layers auto-exclude the project area New projects now have "excludes project boundary" applied by default on 3D building and trees context layers.

💅Enhancements

Saved views simplified Saved views now always capture camera, layer state, and scenarios together — no more per-item toggles or "update layers from map" buttons. The editor warns before discarding unsaved changes, shows a preview of saved layers, and surfaces views shared with your team. Noisy success alerts have been removed.

3D primitives: pitch & bearing rotation Primitive rotation can now be set using pitch and bearing (elevation + azimuth) in addition to raw XYZ angles. Toggle between modes in the property editor.

Flow inputs for usages, blocks, and flows Flow input parameters now support Usage, Block, and Flow types, each with a dedicated picker in the flow controls panel.

Flow picker Selecting a flow for a feature is now a searchable dropdown. You can also create a new flow inline — including directly from the properties panel — with an option to add it to your currently selected features.

Flow defaults Flows can now carry default property values — including usage. Set them in the new Flow Defaults editor, and the on-map generative editors (envelope, subdivisions, parking, skeleton) will respect those defaults when parameters haven't been overridden.

Other improvements

• The status bar now shows your project's save state: a green "Project Saved" icon, a "Saving…" state while changes sync, and a red offline icon when your connection drops.
• A new info popover next to the unit count in Urban breaks down exactly how dwelling and unit numbers are calculated
• Parking provided/required and efficiency in Urban are now grouped by usage, so custom parking usages are counted correctly
• Pattern book flow node and app have been reworked
• Multi-geometry support added in Giraffe Nodes
• The envelope block form gains a configurable Simplify Tolerance setting
• Apply-usage flow node: the usage input is now optional, defaulting to each feature's own usage — so one node can restyle mixed-usage feature sets
• Merge lines command combines selected lines into a single multi-line feature
• Feature table: numeric columns respect precision settings, area columns round sensibly, and empty columns are hidden by default
• Measurement warnings in the status bar are now clickable — click to select the offending features so you can find and fix them
• Pressing Escape while drawing a project boundary now asks for confirmation before discarding your work
• If flow examples fail behind a corporate firewall, the error now tells you exactly which domain to whitelist
• Engine recalculations triggered by UI changes are now batched, making the app noticeably snappier on large projects
• If you sign in via a different identity provider than your account already uses, you're now guided through a clear flow to switch your login method
• "Show all of my projects" is now hidden when you only belong to one workspace
• Clicking inside nested enclosed regions now selects the innermost shape
• The project grid can no longer be edited while a block is open, preventing conflicts; a warning is shown instead

🛠 SDK updates

• Workspace API — new functions for approved apps: fetchWorkspaceDetails, updateWorkspaceDetails, getProjectBundle, and createRawSection (single and bulk)
• evaluateFeatures stacking — output options now resolve stacking (_baseHeight, _height, _stackOrder) in one call, removing the need for a separate stackFeatures call. Polygon winding requirements are now documented.
• Lens style validation — new validateLensStyle helper returns a list of problems in a lens style object
• Lens table control — embedded apps can now set lens table mode via the SDK layout API
• App credentials & user data — new fetchAppCredentials, fetchCredentials, and setUserData functions
• App isolation & permissions — each embedded iframe app now gets its own RPC dispatcher (no cross-app crosstalk) and runs under a per-app permission model
• Layer content access — getLayerContents now serves features from already-loaded map layers (with optional lens filtering); project layers resolve by more ID forms; activateLensLayer throws a clear error when the layer doesn't exist
• Concurrent-safe user data — per-app user data writes are now row-locked so concurrent SDK apps can't overwrite each other; size limits raised

🐛 Bug fixes

• Subscription Screen - The subscription/payment screen now works correctly on small windows
• Published apps — publishing a project now snapshots each embedded app's URL and logo so viewers see them without needing authentication
• Flows: recursion — flows containing loops no longer misclassify nodes that take an external input and feed an external output
• Straight skeleton: holes — straight-skeleton generation now correctly handles polygons with holes
• Cut & Fill: Mapbox terrain — the terrain mesh offset slider now works with Mapbox terrain; terrain can be enabled for any project boundary shape
• Crash screen — unrecoverable errors now show a friendly crash screen instead of a blank white page
• Spaces: left drawer restored — the queried-feature drawer is available again in Spaces; the disableLensSelectionDrawer option now also disables the black selection outline on the map
• Oversized selections — creating projects from, or importing, large lens selections no longer fails; geometry is automatically simplified before saving
• Lens table filters — filters no longer break when a filter group is empty, has no operator, or contains a geometry filter
• Selected-only mode — selection highlighting in the lens table is restored when "selected only" mode is active