History

Orkuncakilkaya c9ee303b69 All checks were successful bootstrap / cfree-fixpoint (push) Successful in 22s Details ci / build-and-test (push) Successful in 2m51s Details commit-lint / conventional-commits (push) Successful in 1s Details docs: rewrite the README for someone meeting the language The README opened with three restatements of "no C", then a limitations table, then a repo-layout map, and closed with Chrono Rift's keybindings — P2/Mage `I`/`K` select, `J` confirm — which is a game manual, not a language README. It never showed the language itself. It now leads with what Ludic is, a compiling code sample, how to build, what the language offers, and an honest status. The layout table is contributor material and CONTRIBUTING already covers that ground. Two things were not merely stylistic: - Nine links pointed at wiki pages that no longer exist. - "Language at a glance" advertised `system` with `reads`/`writes`, plus `requires`/`ensures`. None of those are keywords — the grammar has `handler`, and `System.*` is a namespace. That bullet described a vocabulary retired several releases ago. The sample is verified to compile, every internal link resolves, and every command named is one `x help` actually offers. Also makes commit-lint survive a force-push: it linted `event.before..sha` without checking that `before` still resolves, so rewriting or gc'ing that commit failed the job with "Invalid revision range" on a push whose messages were all valid. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>		2026-09-05 14:25:07 +03:00
..
ci-runner-dns.md	docs(ci): document the runner network a self-hosted CI needs	2026-09-05 02:57:09 +03:00
commit-lint-force-push.md	docs: rewrite the README for someone meeting the language	2026-09-05 14:25:07 +03:00
docs-deploy-concurrency.md	ci(docs): serialise the pages deploy	2026-09-05 03:37:33 +03:00
per-artifact-checksums.md	fix(release): per-artifact checksums so a release can span hosts	2026-09-05 14:14:00 +03:00
readme-rewrite.md	docs: rewrite the README for someone meeting the language	2026-09-05 14:25:07 +03:00
README.md	fix(release): keep a changeset's markdown in the changelog	2026-09-05 01:47:49 +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 decides which group the change lands in: feat → Features, fix → Fixes, perf → Performance, and so on, in that order. A type with no known heading gets one named after itself.

Writing the body

The body is markdown and reaches the changelog as markdown: it becomes one list item, with continuation lines indented to stay inside it. Nested bullets, blank lines between paragraphs and inline code all survive.

bump: minor
type: feat
**Tiled map support** — load and draw Tiled maps.

- **TMX/TSX** — the XML formats, decoded to the same intermediate as JSON.
- **Collision** — the `collision` layer projects onto the engine tilemap.

Lead with the thing that changed, not with the mechanism. A reader scanning the release should be able to stop after your first clause.

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.

Preview how the next release will read before cutting it — this writes nothing:

x release --dry-run