History

Orkuncakilkaya 377b6d1186 All checks were successful bootstrap / cfree-fixpoint (push) Successful in 18s Details ci / build-and-test (push) Successful in 1m19s Details commit-lint / conventional-commits (push) Successful in 4s Details docs / build-and-deploy (push) Successful in 20s Details feat(input): action maps + deterministic record/replay (#7 ) The two ideas the input revamp leads with, built in Ludic over the single-key poll every target already provides: - Action maps: gameplay reads named actions, not physical keys, so keys are rebindable and a scheme is data. Input.bind(action, key), Input.down/pressed(action), Input.rebind(action, from, to). - Deterministic record/replay: Input.poll() is the one per-frame input read; Input.record() captures the key each frame and Input.replay() feeds the tape back, so a run reproduces exactly — the seed of lockstep netcode. "Read input" and "read a recorded snapshot" are the same call. runtime/native/input.ludic (spliced when the new Input.* methods are used; pulls in core.ludic for rt_poll). emit_ns_call routes the methods to the @fn_input_* runtime; parse.ludic gates the splice. Seven docs/language pages; worked example + regression examples/library/input_actions.ludic (1 0 1 1 0 1 0). Full suite 75 passed, self-host fixpoint intact, no golden drift. The device layer (multi-key held, gamepads, touch, analog) needs a platform key-state backend and is tracked separately. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-08-31 16:03:56 +03:00
..
coverage.md	feat(testing): line coverage via --coverage + bin/x test --coverage (#45 )	2026-08-31 14:51:14 +03:00
engine-systems.md	feat(ecs): engine-owned systems auto-tick user components (#43 )	2026-08-31 15:41:44 +03:00
error-handling.md	feat(errors): panic(msg) + assert(cond, msg) with file:line — no raw crashes (#8 )	2026-08-31 14:33:37 +03:00
input-actions.md	feat(input): action maps + deterministic record/replay (#7 )	2026-08-31 16:03:56 +03:00
light-ecs-components.md	feat(ecs): Light2D/Occluder/Ambient as auto-consumed components (#47 )	2026-08-31 15:49:50 +03:00
light-namespace.md	feat(rendering): add Light.* — deterministic 2D light accumulation with hard shadows (#4 )	2026-08-31 14:07:19 +03:00
README.md	feat(release): SemVer + ludicc --version, changesets, and x release	2026-08-30 23:46:59 +03:00
recover.md	feat(errors): recoverable failures as values — try/else over ok/err results (#46 )	2026-08-31 15:04:14 +03:00
testing-framework.md	feat(testing): built-in test blocks + expect assertions, auto-run with pass/fail (#12 )	2026-08-31 14:27:45 +03:00
value-tree.md	feat(reflect): generic value tree + Reflect.serialize/apply + JSON bridge (#44 )	2026-08-31 15:19:21 +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.