History

Orkuncakilkaya 0cb57774d7 All checks were successful bootstrap / cfree-fixpoint (push) Successful in 20s Details ci / build-and-test (push) Successful in 1m51s Details commit-lint / conventional-commits (push) Successful in 3s Details docs / build-and-deploy (push) Successful in 28s Details feat(stdlib): Tiled P2 — collision normalisation into the Solids feed (#70 ) Normalise three collision sources into the byte tilemap esys_move / Grid.* / Path.* read, in the design's priority order (§3.5): - per-tile <objectgroup> hitboxes (Tiled.tile_shapes) — the precise source; - the solid/oneway/trigger bool property convention (Tiled.collision_kind); - the designated collision layer — any non-zero GID solid (Tiled.project), the fallback source, applied automatically on load. Tiled.collide drives collision from a visual layer's per-tile metadata alone (a tile with no collision metadata stays passable). tmap_collision_kind classifies a GID (0 none / 1 solid / 2 one-way / 3 trigger) from its metadata; the projection adds the collision-layer fallback. Proven by library/tiled_p2.ludic (14 assertions): kind classification for each source, the property convention and collision-layer fallback producing an identical Solids feed, a per-tile-<objectgroup> floor blocking an esys_move mover, and A* over a loaded map matching the hand-authored baseline. x test: 93 passed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-09-01 14:50:27 +03:00
..
index-addr-member-index.md	feat(engine): Tiled P1 — rt_tmap model + GID resolver + render + projection (#69 )	2026-09-01 14:43:29 +03:00
package-declarable-hooks.md	docs(pkg): document @Namespace / @EngineSystem / @System + package hooks (#62 )	2026-09-01 12:31:47 +03:00
package-manager.md	feat(pkg): package manager — fetch + MVS resolve + namespace registration (#63 )	2026-09-01 07:08:12 +03:00
prebuilt-packages.md	feat(pkg): x build-lib / prebuilt consumption — binary packages end-to-end (#64 )	2026-09-01 07:52:06 +03:00
README.md	feat(release): SemVer + ludicc --version, changesets, and x release	2026-08-30 23:46:59 +03:00
tiled-maps.md	feat(stdlib): Tiled P2 — collision normalisation into the Solids feed (#70 )	2026-09-01 14:50:27 +03:00

README.md

Changesets

A changeset is one small Markdown file describing a single user-facing change, dropped in this directory. x release consumes every changeset here into a new CHANGELOG.md section, bumps VERSION, and deletes the consumed files.

Format

bump: minor
type: feat
One or more lines describing the change, in the past-agnostic imperative used in
the changelog. Markdown is fine.

bump: — major, minor, or patch (SemVer). The release version is bumped by the highest level among the pending changesets (unless x release <level> overrides it).
type: — the Conventional Commit type (feat, fix, perf, docs, …); it becomes the bold prefix of the changelog bullet.

Adding one

Create a file with a short, unique name, e.g. changes/regex-namespace.md. Any filename works except this README.md, which the release step always skips.