Frozen in this run’s source manifest
Foundation week
The foundation
moved forward.
A dense week of language, runtime, and authoring work made Neo projects easier to express, safer to evolve, and more dependable to ship.
2,000 changed-file touches
Open at the collection snapshot
2 issues opened this window
What matters this week
Two changes capture the direction beneath the volume.
NeoScript crossed a capability threshold.
Constructors, initializer expressions, addressable fields, animation, and same-push references turn complex authored graphs into coherent source rather than multi-step coordination.
Unity parity became a release discipline.
Companion SDK changes landed beside their web implementations, while automated package releases and Linux authentication tightened the path from authoring to a running game.
See what shipped.
Selected directly from the pull requests and preserved with this report.

Authored motion, visible immediately
The new animation model reaches all the way into a live authoring preview, backed by the matching deterministic Unity runtime.
View PR #184
Executable defaults have a first-class home
Literal values and NeoScript initializers share a focused editor instead of hiding executable behavior inside serialized state.
View PR #252
The full language service follows
Completions, hover, signatures, navigation, and authored-coordinate diagnostics work inside initializer expressions.
View PR #252The week, repository by repository
Grouped by product meaning, with direct links back to the merged work.
Neo Compose
NeoScript became dramatically more expressive.
A richer language
The largest product-facing steps make authored Neo source feel less like serialized data and more like a capable, composable language.
Constructors and initializer expressions
P43Classes can declare overloads and executable initialization logic, with matching server validation, Monaco authoring support, export, and SDK behavior.
References that resolve inside the same push
P47New value rows can be referenced by key or root path across files and declaration order, eliminating UUID handoffs and multi-push workflows.
Animation arrived end to end
P29NeoObject animation clips gained an authored model, deterministic frame resolution, actions, child tracks, export, and the web-side editing experience.
Safer structure, smoother authoring
A coordinated run of schema and client work reduced hidden identity state, made async work visible, and improved recovery when something goes wrong.
Neo Compose · .NET
The Unity SDK kept pace—and learned to ship itself.
One language, both runtimes
Companion changes kept generated C# and the Unity runtime aligned with the web implementation.
Animation runtime
Deterministic playback, sparse overrides, actions, child tracks, cancellation, and hot-reload behavior shipped with deep Unity coverage.
Rendering contracts replaced reflection
Sorting groups and sprite-renderer metadata now flow through typed generated contracts, including nested compositions and refreshed samples.
Release confidence
Operational work made the package easier to authenticate, validate, and release from the supported environments.
Neo Compose · Specs
Two rollout decisions were tightened before implementation drifted.
Decisions made explicit
Small spec changes with large sequencing consequences.
Silence is recorded explicitly—no ambiguity between zero activity and a failed collection.
Neowyn
The Unity game and product experience
Neo Compose · Site
Public product and documentation site
A weekly memory that cannot quietly drift.
Resume from the last successful cutoff.
Freeze one PR inventory before analysis.
Advance state only after delivery succeeds.
Every merge behind the briefing
Searchable, filterable, and linked directly to GitHub.