Changelog

v1.0.1 — 2026-10-14

Every release carries its documentation as docs-vX.Y.Z.tar.gz: eight guides with real commands and output, the format, the changelog and the API reference.

The first stable release. Format 1 and the API are the same as in v0.1.0, so moving to this tag needs no change.

Three more examples: scene-tree prints a resolved scene, scene-write moves, renames, sets a material or migrates a file, and scene-bench times checking, resolving and editing scenes of any size.

The README shows each feature with a clip, and its measured speed: a 1,000-object scene resolves in 25 ms.
Every push is tested on Linux, Windows and macOS.
The brand reads PITO MD in the README, NOTICE.md and TRADEMARKS.md.

The first public release.

Format 1 for scenes, prefabs, material libraries, proxies and project.toml, specified in docs/format.md: typed tables, ids, references, prefabs with overrides, includes, tunables, collision layers, rigid bodies, character controllers, triggers, camera rigs, animation and tile layers.
Project opens a project, checks it, resolves a scene and reads one file as typed data; check checks an unsaved buffer. Every finding has a file, line, column, span and a stable code.
SceneEdit edits a scene’s files keeping their comments, spacing and order, with undo, redo and dry runs; Project::fix fills missing ids and Project::migrate rewrites format 0 files as format 1.
Includes and prefabs nest at most 64 deep, and a cycle or a deeper chain is refused with its chain of files, however deep a project goes.
The scene-check example and a demo project in examples/.
Before this release the crate was called pito-scene, with the Rust path pito_scene. A dependency on it becomes pfx-scene = { git = "https://github.com/gmrdad82/pfx-scene", tag = "v0.1.0" }, and use pito_scene::… becomes use pfx_scene::…; nothing else changes.