docs: reserve TypeScript bindings for 0.5.0

[0xgleb]

Record TypeScript bindings as the 0.5.0 direction and clarify the relationship between this experimental fork and the ST0x-owned original project.

Closes #85.

---

This is part 31 of 32 in a stack made with GitButler:

•  32  feat: reconcile Haskell aggregate schemas #52
•  31  docs: reserve TypeScript bindings for 0.5.0 #51 👈
•  30  test: property-check protocol invariants #49
•  29  test: discover Haskell specs with Hspec #48
•  28  refactor: use the Event.Sorcery module namespace #47
•  27  feat: expose schema recovery over the C ABI #46
•  26  refactor: expose schema recovery through engine facade #45
•  25  bench: add Haskell engine benchmarks #43
•  24  test: share cross-binding encoding vectors #42
•  23  feat: renew Haskell job leases #41
•  22  feat: deliver Haskell dispatch verdicts #40
•  21  feat: settle Haskell job executions #39
•  20  feat: route Haskell job executions #38
•  19  feat: seal Haskell dispatch outcomes #37
•  18  feat: load Haskell entities from snapshots #36
•  17  feat: execute typed Haskell commands #35
•  16  feat: restore the typed Haskell domain model #34
•  15  feat: run jobs from the Haskell binding #33
•  14  refactor: package the Haskell binding by feature #32
•  13  feat: expose job operations over the C ABI #31
•  12  feat: expose the existing job runtime #30
•  11  feat: call the shared engine from Haskell #29
•  10  feat: add deterministic Haskell engine codecs #28
•  9  feat: expose stream operations over the C ABI #27
•  8  feat: add the C ABI lifecycle #26
•  7  api: expose the shared engine facade #25
•  6  refactor: route job storage through the engine facade #24
•  5  refactor: extract the serialized engine facade #23
•  4  test: pin atomic event and job persistence #22
•  3  chore: update 0.4.0 ownership metadata #18
•  2  build: unify the Rust and Haskell toolchain #17
•  1  docs: specify the 0.4.0 monorepo engine #14

Summary by CodeRabbit

• Documentation
  • Clarified the repository’s experimental status, ownership, and relationship to the original project.
  • Added a roadmap for a planned typed TypeScript binding in version 0.5.0.
  • Confirmed that TypeScript support is not included in version 0.4.0 and requires future compatibility decisions.

[coderabbitai]

Walkthrough

The documentation now identifies the repository as an experimental Data Clique-maintained fork, clarifies its relationship to ST0x, and documents planned typed TypeScript bindings over the shared Rust engine for release 0.5.0.

Changes

Fork scope and TypeScript roadmap

Layer / File(s)	Summary
Fork ownership and specification scope README.md, SPEC.md	README.md and SPEC.md clarify the experimental fork’s ownership, maintenance boundaries, and relationship to the original ST0x project.
TypeScript binding direction ROADMAP.md, SPEC.md	Documentation records planned typed TypeScript bindings for 0.5.0, reusing the shared Rust engine while remaining outside 0.4.0 scope.

Possibly related PRs

• dataclique/event-sorcery#14: Updates release documentation around versioned engine contracts referenced by the planned TypeScript binding.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main documentation change: reserving TypeScript bindings for version 0.5.0.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/0.5-typescript-bindings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@ROADMAP.md`:
- Around line 41-45: Update the Release 0.5.0 statement in ROADMAP.md to
describe the typed TypeScript binding as intended or planned rather than
guaranteed. Preserve the existing details about the shared Rust engine and the
pending runtime, packaging, public API, specification, and compatibility
decisions.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 76fa5b71-361e-4b25-88cd-c9aae9763739

📥 Commits

Reviewing files that changed from the base of the PR and between f6f39bc and 62c0cc2.

📒 Files selected for processing (3)

• README.md
• ROADMAP.md
• SPEC.md

📜 Review details

⏰ Context from checks skipped due to timeout. (6)

• GitHub Check: clippy
• GitHub Check: hooks
• GitHub Check: examples
• GitHub Check: fmt
• GitHub Check: check
• GitHub Check: test

🧰 Additional context used

📓 Path-based instructions (4)

**/*.{rs,toml,sql,md}

📄 CodeRabbit inference engine (AGENTS.md)

Read SPEC.md and docs/domain.md before doing work; update README.md and relevant docs when implementation or architecture changes.

Files:

• README.md
• ROADMAP.md
• SPEC.md

**/*

📄 CodeRabbit inference engine (AGENTS.md)

**/*: Generated files must be placed under .tmp/; do not add ad-hoc top-level generated entries to .gitignore.
Do not read secret-bearing files such as .env*, credentials.json, *.key, *.pem, *.p12, or *.pfx without explicit permission.
Never bypass, disable, or suppress quality-control mechanisms without explicit permission; fix lint and test failures at their root.
Before handover, review the diff, revert unjustified changes, and check for scope creep.

Files:

• README.md
• ROADMAP.md
• SPEC.md

*

⚙️ CodeRabbit configuration file

Focus on providing constructive criticism. Whenever you see a suboptimal approach, suggest more idiomatic or robust alternative(s). Flag potential footguns. Suggest FP alternatives to mutable/imperative code. Point out architectural flaws like leaky abstractions, tight coupling, wrong level of abstraction, poor type modeling, over-abstraction, unclear domain boundaries. Code should generally be organized based on business concerns rather than technical aspects - suggest improvements if you find violations. Point out gaps in test coverage but suggest tests that are not too coupled to the implementation and actually test domain invariants and business logic

Files:

• README.md
• ROADMAP.md
• SPEC.md

**/*.md

⚙️ CodeRabbit configuration file

Focus on the contents of the docs and not on cosmetic things like markdown formatting. We use markdown files for various docs including but not limited to guidelines for AI contributors (AGENTS.md), project overview and instructions for human contributors (README.md), and topic-focused references under docs/ (cqrs.md, sqlx.md, ttdd.md). Think about the target audience of a document when deciding what comment to leave. For instructions, suggest better rules and guidelines and point out missing instructions. For topic references, suggest improvements that would make non-obvious framework behavior or pitfalls easier to discover. In all cases, flag needless bloat, prefer clear concise writing, and consider the structure of the document and order of the sections

Files:

• README.md
• ROADMAP.md
• SPEC.md

🔇 Additional comments (2)

README.md (1)

24-32: LGTM!

SPEC.md (1)

20-24: LGTM!

Also applies to: 69-79