Add release notes for December 5, 2025

apps/framework-docs/src/pages/release-notes/2025-12-05.mdx

@@ -0,0 +1,176 @@
+---
+title: December 5, 2025
+description: Release notes for December 5, 2025
+---
+
+import { Callout } from "@/components";
+
+# December 5, 2025
+
+Flexible Streaming Ingest, Web App Integration, and Infra Visibility Upgrades. This two-week release pushes MooseStack forward on three fronts: flexible high-volume ingestion, developer experience for full-stack apps, and operational visibility.
+
+Moose gained the ability to handle arbitrary JSON ingest, Kafka-backed streaming, IcebergS3 for data lake integration, and powerful modeling tools like materialized columns and per-column codecs. Meanwhile, Boreal added storage visualizations so teams can see how their data grows.
+
+<Callout type="info" title="Highlights">
+* **New:** [Arbitrary JSON fields in ingest APIs](#arbitrary-json-fields-in-ingest-apis) for flexible schema evolution
+* **New:** [Kafka engine support](#kafka-engine-support-for-streaming-ingestion) for real-time ClickHouse ingestion
+* **New:** [IcebergS3 engine](#icebergs3-engine-for-data-lake-storage) for Apache Iceberg data lake integration
+* **New:** [Materialized columns](#materialized-columns-in-data-models) for precomputed fields at ingestion time
+* **New:** [Fastify web app template](#fastify-web-app-template) with automatic async initialization
+* **New:** [Boreal database storage visualization](#database-storage-visualization-experimental) for capacity planning
+</Callout>
+
+## Moose
+
+### Arbitrary JSON fields in ingest APIs
+
+Accept payloads with extra fields beyond your defined schema while still validating known fields. Extra fields automatically pass through to streaming functions and land in a JSON column.
+
+**Why it matters:** Schema flexibility without chaos. Teams can ship events even when they don't fully agree on every property yet. Known fields still get enforceable validation, while "extra" properties land in a JSON column for later exploration. This is ideal for product analytics, logging, and gradual schema evolution.
+
+```typescript filename="app/ingest/models.ts" copy
+// TypeScript: Use index signature to accept arbitrary fields
+export type UserEventInput = {
+  timestamp: DateTime;
+  eventName: string;
+  userId: Key<string>;
+  [key: string]: any;  // Allows any additional properties
+};
+```
+
+In Python, use `extra='allow'` in your Pydantic models to achieve the same flexibility.
+
+PR: [#3047](https://github.com/514-labs/moosestack/pull/3047) | Docs: [Data models](/moose/data-models)
+
+### Kafka engine support for streaming ingestion
+
+Define tables with ClickHouse's Kafka engine as an alternative consumer that reads directly from Kafka topics into ClickHouse, bypassing Moose's built-in streaming consumer. Use materialized views to transform and route the data.
+
+**Why it matters:** Direct Kafka → ClickHouse ingestion. When you need ClickHouse to consume from Kafka natively—without going through Moose's streaming layer—Kafka engine tables give you that option. This is useful for high-throughput scenarios or when you want ClickHouse to manage its own consumer offsets.
+
+```typescript filename="app/ingest/kafka.ts" copy
+// Create a Kafka engine table that consumes from a topic
+export const KafkaSourceTable = new OlapTable<KafkaTestEvent>(
+  "KafkaTestSource",
+  {
+    engine: ClickHouseEngines.Kafka,
+    brokerList: "redpanda:9092",
+    topicList: "KafkaTestInput",
+    groupName: "moose_kafka_consumer",
+    format: "JSONEachRow",
+  },
+);
+```
+
+PR: [#3066](https://github.com/514-labs/moosestack/pull/3066) | Docs: [OlapTable](/moose/olap) | [ClickHouse Kafka Engine](https://clickhouse.com/docs/integrations/kafka/kafka-table-engine)
+
+### IcebergS3 engine for data lake storage
+
+Configure tables to use Apache Iceberg format with S3 storage for better data lake integration and columnar storage capabilities.
+
+**Why it matters:** Data lake integration without the glue. IcebergS3 enables columnar storage on S3 with Parquet or ORC format, AWS credential management, and compression options. This bridges Moose's real-time pipelines with existing data lake infrastructure for analytics workloads.
+
+```typescript filename="app/tables/analytics_events.ts" copy
+export const AnalyticsEventsTable = new OlapTable<AnalyticsEvent>(
+  "AnalyticsEvents",
+  {
+    engine: ClickHouseEngines.IcebergS3,
+    path: "s3://my-data-lake/analytics/events/",
+    format: "Parquet",
+    awsAccessKeyId: "{{ AWS_ACCESS_KEY_ID }}",
+    awsSecretAccessKey: "{{ AWS_SECRET_ACCESS_KEY }}",
+    compression: "zstd",
+  },
+);
+```
+
+PR: [#2978](https://github.com/514-labs/moosestack/pull/2978) | Docs: [OlapTable](/moose/olap) | [ClickHouse Iceberg Engine](https://clickhouse.com/docs/engines/table-engines/integrations/iceberg)
+
+### Materialized columns in data models
+
+Define materialized columns to automatically compute derived values at ingestion time—date extractions, hash functions, JSON transformations—without separate aggregations.
+
+**Why it matters:** Cheaper, faster queries at scale. Materialized columns move expensive expressions into ingestion time so queries become simple scans over precomputed fields. This directly impacts infrastructure cost and query latency for time-series, metrics, and logs.
+
+```typescript filename="app/ingest/models.ts" copy
+export interface MaterializedTest {
+  id: Key<string>;
+  timestamp: DateTime;
+  userId: string;
+  // Materialized columns - computed at ingestion time
+  eventDate: string & ClickHouseMaterialized<"toDate(timestamp)">;
+  userHash: UInt64 & ClickHouseMaterialized<"cityHash64(userId)">;
+}
+```
+
+PR: [#3051](https://github.com/514-labs/moosestack/pull/3051) | Docs: [Supported types](/moose/olap/supported-types) | [ClickHouse Materialized Columns](https://clickhouse.com/docs/sql-reference/statements/alter/column)
+
+### Fastify web app template
+
+New project template demonstrating Fastify framework with Moose, plus fixed WebApp support for Fastify's async initialization.
+
+**Why it matters:** Fast path to production web APIs. The Fastify template + WebApp fix give a working, idiomatic example for building Moose-backed services. Fastify's performance and schema support pair nicely with Moose's data models, lowering the barrier for new services.
+
+```typescript filename="app/apis/analytics.ts" copy
+import Fastify from "fastify";
+import { WebApp } from "@514labs/moose-lib";
+
+const app = Fastify({ logger: true });
+app.get("/health", async () => ({ status: "ok" }));
+
+// Export as WebApp - Moose handles Fastify's ready() automatically
+export const analyticsApp = new WebApp("analyticsApi", app, {
+  mountPath: "/analytics",
+});
+```
+
+PR: [#3068](https://github.com/514-labs/moosestack/pull/3068), [#3061](https://github.com/514-labs/moosestack/pull/3061) | Docs: [Fastify integration](/moose/app-api-frameworks) | [Fastify template](https://github.com/514-labs/moosestack/tree/main/templates/typescript-fastify)
+
+### Other improvements
+
+- **Custom PRIMARY KEY expressions** – Define custom PRIMARY KEY with hash functions like `cityHash64` for better data distribution in high-cardinality scenarios. PR [#3031](https://github.com/514-labs/moosestack/pull/3031) | [ClickHouse Primary Keys](https://clickhouse.com/docs/best-practices/choosing-a-primary-key)
+- **Per-column compression codecs** – Specify codecs (ZSTD, LZ4, Delta, Gorilla) per column using `ClickHouseCodec<"...">` type annotations. PR [#3035](https://github.com/514-labs/moosestack/pull/3035) | [ClickHouse Compression](https://clickhouse.com/docs/data-compression/compression-in-clickhouse)
+- **Python LSP autocomplete for SQL** – Get IDE autocomplete for column names in f-strings using `MooseModel` with `{Column:col}` format. PR [#3024](https://github.com/514-labs/moosestack/pull/3024)
+- **Next.js client-only mode (experimental)** – Set `MOOSE_CLIENT_ONLY=true` to import Moose data models without runtime, fixing HMR errors. PR [#3057](https://github.com/514-labs/moosestack/pull/3057)
+- **Web apps in `moose ls`** – List web applications alongside tables, streams, and APIs with `moose ls --type web_apps`. PR [#3054](https://github.com/514-labs/moosestack/pull/3054)
+- **Lifecycle inheritance in IngestPipeline** – Top-level lifecycle settings automatically propagate to table, stream, and deadLetterQueue components, reducing config duplication. PR [#3088](https://github.com/514-labs/moosestack/pull/3088)
+- **MCP query result compression** – Results compressed using toon format for better IDE/AI integration performance. PR [#3033](https://github.com/514-labs/moosestack/pull/3033)
+- **Renamed --connection-string to --clickhouse-url** – CLI now uses `--clickhouse-url` for ClickHouse commands (old flag still works). Improved connection string parsing for native protocol URLs. PR [#3022](https://github.com/514-labs/moosestack/pull/3022)
+
+### Bug fixes
+
+- **Security updates in templates** – Updated Next.js (15.4.7 → 16.0.7) and React (19.0.0 → 19.0.1) to patch security vulnerabilities in frontend templates. [#3089](https://github.com/514-labs/moosestack/pull/3089)
+- **MCP template build failures** – Fixed missing/empty `.npmrc` files that caused `npm install` and Docker builds to fail when creating new MCP server projects. [#3084](https://github.com/514-labs/moosestack/pull/3084), [#3082](https://github.com/514-labs/moosestack/pull/3082), [#3081](https://github.com/514-labs/moosestack/pull/3081)
+- **MCP SDK compatibility** – Updated MCP template to work with SDK v1.23+ which changed its TypeScript types. Migrated to new `server.tool` API with Zod validation. [#3075](https://github.com/514-labs/moosestack/pull/3075)
+- **ORDER BY parsing with projections** – Fixed incorrect ORDER BY extraction when tables contain projections. The CLI was picking up projection ORDER BY clauses instead of the main table's. [#3052](https://github.com/514-labs/moosestack/pull/3052)
+- **Array literals in views** – Views containing ClickHouse array syntax like `['a', 'b']` would fail to parse. Added fallback parser to handle ClickHouse-specific SQL. [#3034](https://github.com/514-labs/moosestack/pull/3034)
+- **LowCardinality columns in peek/query** – `moose peek` and `moose query` failed on tables with [`LowCardinality(String)`](https://clickhouse.com/docs/sql-reference/data-types/lowcardinality) columns. Switched to HTTP-based ClickHouse client which supports all column types. [#3025](https://github.com/514-labs/moosestack/pull/3025)
+- **DateTime precision preservation** – JavaScript Date objects drop microseconds/nanoseconds. Added `DateTimeString` and `DateTime64String<P>` types that keep timestamps as strings to preserve full precision. [#3018](https://github.com/514-labs/moosestack/pull/3018)
+
+## Boreal
+
+### Database storage visualization (experimental)
+
+New experimental page showing table storage usage over time with interactive charts. When enabled, a "Database" tab appears in your branch navigation with per-table storage area charts, date range filters, and granularity options (minute/hour/day).
+
+**Why it matters:** Watch storage growth over time. Time-series charts of table sizes are crucial for capacity planning, catching runaway growth, and understanding which workloads drive storage cost.
+
+![Database storage visualization](/release-notes/database-storage-visualization.png)
+
+*This feature is behind an experimental flag. Contact support to enable it for your organization.*
+
+### Other improvements
+
+- **Log drain performance** – Reuses database connections instead of creating new ones per batch, reducing connection overhead.
+- **ClickHouse query performance** – Optimized table structure and indexing for faster loading of query performance data.
+- **Temporarily removed "Build from Existing Database"** – Option removed from project creation flow while being improved. Users can still import from GitHub or templates.
+
+### Infrastructure
+
+- **Extended deployment startup timeouts** – Increased from 60 to 180 seconds to reduce failures for larger applications during high-load periods.
+
+### Bug fixes
+
+- **GitHub authentication** – Fixed issues preventing repository connections and operations.
+- **Security updates** – React 19.2.0 → 19.2.1, Next.js 16.0.1 → 16.0.7.
+- **Function names display** – Fixed missing function names in metrics table.

apps/framework-docs/src/pages/release-notes/_meta.tsx

@@ -7,6 +7,9 @@ const rawMeta = {
       breadcrumb: false,
     },
   },
+  "2025-12-05": {
+    title: "December 5, 2025",
+  },
   "2025-11-22": {
     title: "November 22, 2025",
   },

apps/framework-docs/src/pages/release-notes/index.mdx

@@ -12,6 +12,7 @@ Welcome to the Moose, Sloan, and Boreal release notes. Here you'll find informat
 
 ## Latest Updates
 
+* [December 5, 2025](/release-notes/2025-12-05)
 * [November 22, 2025](/release-notes/2025-11-22)
 * [November 14, 2025](/release-notes/2025-11-14)
 * [November 7, 2025](/release-notes/2025-11-07)