Changelog

This page tracks the 12-day rollout as a historical runbook: what started as broad platform reconstruction, what shipped in the middle, and what got stabilized before the window closed.

Across 800+ non-merge commits (2026-05-02 → 2026-05-14), Alumia moved from broad infrastructure and UI rebuilding to a production-safe, feedback-oriented platform surface.

2026-05 — Deep historical rollout (2026-05-02 → 2026-05-14)

Phase map

The work followed a clear arc across this window:

For the full per-commit trail, use the full ledger:

• Changelog Ledger — every commit from the 12-day window, grouped by date.

2026-05 — Full ledger and coverage map

This section gives a one-commit-per-line view of the same 12-day window:

• it captures refactors and fixes that changed platform behavior,
• it captures API, connector, UI, and security changes,
• and it records the surface each commit touched so missing areas in docs can be checked quickly.

Because the ledger is large, we keep the raw stream in a dedicated page and keep this top-level history focused on outcomes.

2026-05-02 — Day 0: Platform Foundation

This was the first major reset week-start phase.

Alumia shipped foundational product and security work in one sweep:

• docs and public pages migrated to the new fumadocs structure,
• core route protections and auth middleware hardened,
• workspace-sharing and visibility for multi-tenant projects,
• connector onboarding and webhooks expanded,
• API access and artifact-runtime protections tightened,
• initial mobile layout cleanup for tabs, cards, and top bars,
• and a broad uplift in onboarding and app-shell reliability. By the end of the day, Alumia’s base had shifted from “feature-heavy but fragile” to “secure and coherent.”

2026-05-03 — Day 1: Commerce and Expansion

The platform moved from foundation into product breadth, then pulled back quickly to harden each system that landed.

• storefront, store/product/cart/order APIs and webhook flows were introduced,
• connector expansion continued across domains like finance, social, and developer integrations,
• chat and dashboard surfaces were made safer and more consistent,
• model catalog quality improved with pricing/deprecation corrections and routing policy updates,
• and onboarding/navigation got measurable cleanup (first-run checklist, sidebar behavior, home readiness states). The rollout’s center of gravity moved outward: more systems were available, and each one came with early safety constraints.

2026-05-04 to 05 — Day 2-3: Reliability and Operator Surface

This phase was all about operability. We prioritized admin controls, social trust signals, and integration safety.

• admin routes, org invitation/authenticator flow coverage, and management telemetry improved,
• connector categories, options, and credential UX moved toward a compact inline pattern,
• search/deployment evidence tooling and CI checks started catching integration drift earlier,
• and error handling in dashboard actions became more explicit and recoverable. This phase is best seen as the first major operator-quality hardening pass: features existed, but now they became actionable.

2026-05-06 to 07 — Day 4-5: Product Fluency and Collaboration Primitives

At this point, data and canvas behavior stopped being “new features” and became the core of everyday workflow.

• MCP app block runtime and artifact hardening shipped,
• data/table behaviors gained richer sorting controls, render consistency, and stricter security posture,
• canvas tasks gained text/list/timeline controls and title/task affordances,
• and block/tool behavior in chat and artifact generation was tightened for production use. The narrative changed from “adding tools” to “building everyday work habits” on canvas and in tables.

2026-05-08 to 09 — Day 6-7: Collaboration and Public Quality

The rollout shifted from shipping to usability: collaboration flows, public quality, and operational confidence improved together.

• inbound connector events, crawl-page tooling, snapshots, and project prompts entered production-grade shape,
• social/thread-like canvas blocks were visually polished (connectors, bullets, avatars, spacing),
• voice and chat UX got a major quality pass,
• map/chat interactions and media handling were made more resilient,
• and deploy/runtime guardrails were strengthened (smoke, secret checks, and runtime availability checks). By now the system started behaving like a collaborative workspace instead of a set of disconnected experiments.

2026-05-10 — Day 8: Wallets and Safety

Finance moved into the same hardening loop as product reliability.

• Stripe-issued wallet inspection and wallet admin views shipped,
• product trust nudges and signup-credit workflow reliability improved,
• security-sensitive domains (org slugs, telephony secrets, reserved resources) got additional validation,
• and chat/canvas interactions gained better stability under reconnect, duplicate handling, and workspace alignment. This day marked explicit financial and trust-hardening; billing was no longer an exception path, it became baseline behavior.

2026-05-11 to 12 — Day 9-10: Merge, Readiness, and Stabilization

Merges and cross-feature integration became the central work.

• merge/reconciliation flows brought multiple connector and deployment tracks together,
• public SEO/connector surfaces were finalized,
• dashboard and runtime states were hardened for previews and CI,
• and canvas/chat tests were reinforced where end-to-end behavior had regressed. After two days of integration, the focus became consistency: keeping the new product pieces from diverging under load.

2026-05-13 — Day 11: Feedback Quality and Admin Actionability

By now, feedback was no longer a side log; it became part of routine product governance.

• duplicate and burst feedback patterns started grouping for triage,
• phone verification and schedule fallback reliability improved,
• canvas/block/docs terminology was normalized,
• and signup credit / top-up guidance was refined around real billing behavior. Admin workflows crossed the threshold from reactive handling to structured triage.

2026-05-14 — Day 12: Security Operations and Final Polish

The final stretch converted the big surface changes into a calmer, safer, more consistent product state.

• security feedback classification expanded across script/SQL/path/shell probes,
• admin triage gained workflow metadata, secure rendering, and safer action ergonomics,
• canvas interaction consistency improved (text selection, bottom-sheet trash, pin/focus behavior, bottom-aligned action spacing),
• data tables and tasks gained inline editing patterns that now carry into daily workflows,
• and attachment, billing, and schedule recovery flows received safer edge-case handling. The sprint closed with a calmer state: less fragility, clearer actions, and fewer “surprise” surfaces for users.

2026-05 — Feature families

The canvas now feels like Figma / Linear, not a chat log.

Arrangement and navigation

• Smart alignment guides — pink lines + distance pills snap to edges and centers as you drag. Alt suppresses.
• Snap-to-grid (toggleable) — toolbar toggle; positions round to the 24 px dot grid. Alt temporarily disables.
• Drag from anywhere — the whole block surface is a drag handle. When selected, the content becomes interactive (text selection, scrolling, button clicks).
• Native interactive blocks (Excalidraw, Browserbase, Google Workspace) always keep their content interactive so clicks reach the embedded editor.
• Theme-aware MiniMap (bottom-left) — pannable, zoomable, with a viewport-outline ring in the brand primary.
• Dotted background uses theme tokens so dots are visible on both light and dark canvases without going washed-out or harsh.
• Pin focused view — right-click a block → "Pin focused view" zooms to it and persists across refreshes (stored per-project in localStorage). "Show full canvas" exits.
• Auto-fit blocks — single image / video / audio blocks lock height to media aspect ratio; audio playlists, audio tracks, and video playlists fit to content height.

Block UI

• Floating title strip above the bordered card (transparent bg), with the agent avatar pinned top-right. Toggle visibility via context menu → "Hide title".
• Rename dialog — proper shadcn <Dialog> instead of window.prompt.
• Context menu — Rename, Hide title, Add as context, Copy content, Export (PNG/PDF/JSON/Markdown), Zoom to fit, Pin focused view, Bring to front / Send to back, Delete.
• Wheel scroll stays inside the block — never bubbles to canvas pan.
• No double border — nested shadcn <Card> chrome is flattened so the outer block frame is the only visible border.

Media blocks

• Edge-to-edge image, video, audio — no border, no padding. The media is the block.
• Prompt overlay — 2-line clamped gradient overlay on generated images (no inline figcaption clutter).
• Portal lightbox — createPortal to document.body so the lightbox escapes the React Flow transform context and renders truly full-screen with a side panel showing the full prompt.
• ElevenLabs-style audio player — clean pill: solid play/pause button, scrubbable progress bar, elapsed/total time. Custom-built (native <audio controls> styling is ugly across browsers).

Tables

• Sticky header with a 1 px hairline divider.
• Drag-to-reorder columns — the entire column head is the drag handle (6 px activation distance so a quick click still sorts).
• Smooth column resize — hover the right edge of a header for a col-resize strip; drag to set a width that persists across refreshes.

Threads

• Continuous connector line — Twitter / X / LinkedIn / Bluesky / Threads thread layouts use a real flex column for the avatar + connector so the line runs unbroken from one avatar to the next.
• Themed Slack avatars — initials accept bg and color hex on the spec so agents can paint themed circles.
• Proper padding — Slack message thread fragment uses px-4 py-3 with a hover-row treatment instead of cramped px-1.

2026-05 — Emoji shortcodes, simplification rules, color palette

• Slack / GitHub / Discord emoji shortcodes (:tada:, :rocket:, :white_check_mark:, :fire:, ~150 total) render as actual emoji in every markdown surface — chat, document blocks, thread bodies. Applied at the MessageResponse root so it's truly global.
• 2026 colour palette — 12 curated hex values baked into the AI system prompt: slate, azure, iris, emerald, sage, amber, honey, rose, violet, teal, fuchsia, cloud. The agent picks from this list whenever a chart series colour, callout marker, or any field requires a hex. No neon, no invented colours.
• Simplify ruthlessly — the agent system prompt now insists on stripping empty/redundant optional fields, omitting filler copy, keeping tables to 3–5 columns unless asked, using font-medium/font-semibold (never font-bold), and reserving rose/emerald for genuine errors/successes.
• Social media is required for tweets — when drafting a tweet / X / LinkedIn / Bluesky / Threads post, the agent calls image_save and attaches a fileId on media. A tweet without media looks unfinished.

2026-05 — SEO + link previews

• Dynamic Open Graph cards per share route — /share/project/[token]/opengraph-image.tsx and /share/artifact/[token]/opengraph-image.tsx generate per-share PNGs with the project's name and emoji. Tweet a project link and the preview shows the project, not a generic logo.
• Composed static OG image — og-image-1200x630.png rebuilt with the black brand mark, tagline, and proper composition for everything that isn't a share link.
• Organization + WebSite + Article JSON-LD — emitted in app/(public)/layout.tsx and per-blog-post for rich-result eligibility.
• app/robots.ts + app/sitemap.ts — proper allow/disallow + dynamic blog and docs URLs.
• noindex on private surfaces — /[orgSlug]/*, /admin, /auth/*, and every share route emit <meta name="robots" content="noindex,nofollow"> defensively.
• viewport + themeColor export with light/dark variants — affects WhatsApp's preview frame and mobile browser chrome.
• Söhne via next/font/local — replaces three manual <link rel="preload"> blocks for proper font optimization.
• Canonical URLs on every public marketing page, solutions page, products page, and docs route.

Earlier

• Inline canvas blocks in tutorial pages — run an agent against your own org while reading.
• Ask AI — press Cmd/Ctrl + I on any page to ask the docs.
• MCP server at https://alumia.com/docs/mcp — point Cursor or Claude Code at it to query docs live.
• llms.txt + per-page .md via content negotiation. Append .md to any URL or set Accept: text/markdown.