new
Architecture: automatic background bands group nodes by type
Architecture diagrams now synthesize background bands that cluster nodes by their declared type (services, databases, queues, and so on) without any author input. The grouper picks contiguous per-layer clusters and aligns them across ranks so related components read as a single region, and any input that prevents grouping surfaces an AUTOGROUP_* diagnostic explaining why.
new
Fan-in convergence indicator on collapsing edge groups
When multiple edges converge onto a single target, the renderer draws a junction dot and a thickened trunk segment so the collapsing relationship is visible at a glance. The indicator is scoped to genuine fan-in groups, so unrelated edges that happen to share a corner are not decorated.
new
Sign in with Google or GitHub
Both providers are now available on the login and signup pages alongside the existing email and password flow, using OAuth 2.0 with PKCE and a signed state cookie. New accounts created via OAuth inherit the same workspace, API key, and plan setup as email signups, and a visible consent disclosure under the provider button records terms and privacy acceptance at click time.
new
Forgot-password reset flow
A "Forgot password?" link on the login page now starts a reset flow that emails a one-hour single-use link to the account address, lets the user set a new password, revokes every existing session, and emails a confirmation with the request IP and user agent. The initiation response is always 202 regardless of whether the email is registered, so the endpoint cannot be used to enumerate accounts.
new
createNode no longer requires shape
shape is now optional on createNode and on inline node elements: the normalizer fills the canonical glyph from nodeType (services and tasks get rounded rectangles, databases get cylinders, gateways and decisions get diamonds, BPMN events get ellipses, object storage gets the bucket glyph, and so on). Author-set shape values always win, so existing scenes are unaffected.
new
zIndex is now optional and auto-assigned per kind
Agents no longer have to pick paint-order numbers. Containers sit at the back, edges above them, nodes above edges, and overlays (text, image, guide) on top, with monotonic offsets within each tier so source order is preserved. Any explicit zIndex the author sets (including zero or negatives) is honored exactly as written.
new
dsp_validate_scene and dsp_normalize_scene accept a sceneId
Both tools now mirror dsp_render_scene's polymorphic shape: pass sceneId to validate or normalize a persisted scene at its current revision, or pass scene for an inline document. The response tags the result with {sceneId, revision} so agents know which version was checked without a separate dsp_get_scene round-trip.
new
Plan-limit reached affordance on the dashboard
When an account has hit its API-key, scene, monthly-update, or monthly-render cap, the relevant create button is now visibly disabled and an adjacent card explains why with a single "Upgrade plan" link to billing. The dashboard overview's inventory cards also surface an inline upgrade pointer below any usage bar that is at-cap, so the limit is discoverable before the next action attempt.
improved
Edges anchor on the true silhouette of curved shapes
Edges to and from cylinders, ellipses, hexagons, parallelograms, and cloud shapes now terminate on the shape's actual outline rather than its bounding box, so arrowheads sit flush against the stroke instead of floating in the corner gap. A post-routing projection pass also re-seats endpoints whose routes were rewritten so the final geometry stays on the silhouette.
improved
Routing keeps clearance from frame strokes
The edge router now treats frame strokes as obstacles with their own clearance band, so edges and labels no longer crowd or overlap pool, lane, and container borders. Diagrams with nested frames read more cleanly without any author tuning.
improved
Expanded Inter glyph coverage with a visible fallback
The bundled Inter subset now covers a wider range of Latin, punctuation, and symbol glyphs commonly used in diagram labels. Any character still outside the subset renders as a visible tofu box and emits a MISSING_GLYPH diagnostic so agents can detect and substitute the offending character instead of shipping invisible text.
improved
Validation errors name the rejected value and the canonical fix
Schema errors from POST /v1/ops, POST /v1/scenes/validate, and POST /v1/scenes/normalize now quote the rejected value, list the allowed alternatives, and (where applicable) name the canonical op to use instead. Invented op types like addColumn point at the updateNode + extensions.columns replacement pattern, wrong-but-plausible field names like data, patch, or kind point at their canonical counterparts, and a malformed layout block collapses to a single diagnostic naming what each mode requires.
improved
MCP tools surface full API diagnostics instead of a generic error
dsp_apply_ops, dsp_validate_scene, and dsp_normalize_scene now forward the API's per-op diagnostics (op index, op type, error code, JSON pointer path, message, severity) directly to the agent. Tools previously collapsed every 4xx to "Operation validation failed" with no detail, forcing agents to brute-force the validator; the structured response makes the right correction visible in one retry.
improved
Router shifts back-edge descents away from edge labels
A post-routing pass walks every back-edge polyline and nudges the descent or ascent column away from any placed edge label that sits within the clearance band, then re-verifies the shifted route against node obstacles before applying the change. The pass is surgical (only the conflicting column moves, and only by the minimum needed) and reverts cleanly when a shift would introduce a new conflict.
improved
OpenAPI nodeType and edgeType enums in sync with the canonical schema
The OpenAPI spec's nodeType enum now matches scene.schema.json verbatim (18 missing values added including actor, decision, process, storage, objectStorage, iconNode, the org.* family, and the uiflow.* family; four stale values dropped). A new edgeType enum declaration mirrors the canonical 17-value set so code-generated clients accept every edge type the API does.
fixed
Persisted render endpoint honors canvas auto-extension
GET /v1/scenes/:id/render now respects the CANVAS_AUTO_EXTENDED diagnostic and returns the extended canvas, matching the behavior of the inline render endpoint. Previously a persisted scene whose layout exceeded the declared canvas could render clipped at the original bounds.
fixed
Architecture: every dependency arrow reaches its target
Architecture diagrams: dependency edges that previously stopped short of their target node now route all the way through, regardless of where the target sits relative to its containing group. The fix removes a class of "arrow points at nothing" artifacts in larger architecture diagrams.
fixed
Styled label runs no longer overprint themselves
Inline tspans inside a styled label now lay out sequentially instead of stacking at the same anchor, so labels mixing bold, italic, or colored runs render with correct spacing. Plain single-style labels are unaffected.
fixed
MCP --version reports the published package version
Running @zindex-ai/mcp --version now reads from the package manifest at runtime, so the reported version always matches the installed release. Earlier builds could surface a stale string baked in at build time.
fixed
dsp_apply_ops returns diagnostics instead of a server error when every op fails
When every op in a batch fails its target check (for example deleteElement naming an id that does not exist), POST /v1/ops now returns the structured 422 with per-op diagnostics the executor already produced. The previous behavior was a 500 because the runtime tried to persist a zero-op revision, which gave agents no signal about what to fix and could cascade into retry loops on the same broken batch.
breaking
Version field now uses semver with a build counter
The version string returned by the API root and the info.version field in the OpenAPI spec now follow semver with a build counter (1.0.0+build.989) instead of the previous 1.0.661 shape. If you parse the version field, treat the segment before + as the semver release and the segment after as an opaque build identifier. Most consumers will not need to make changes.