Release/5.0.0 (#10)

- Rework the aggregate roots (event-sourced and eventual) with aggregate
  versioning, reflection-based reconstitution, and snapshot support.
- Rework domain events, event records, revisions, and upcasting.
- Add the Utc, Uuid, and Ordinal value objects with their dedicated
  exceptions and comparison behavior.
- Add the tiny-blocks Claude skills, rules, and CLAUDE.md.
- Refresh the CI workflows, tooling config, and README.

Author: gustavofreze

.claude/CLAUDE.md

@@ -38,10 +38,10 @@ outputting.
     concept.
 11. Test fixtures representing domain concepts live in `tests/Models/`. Test doubles for system
     boundaries live at the root of `tests/Unit/` or `tests/Integration/`. No dedicated `Mocks/`
-    or `Doubles/` subdirectory exists. `tests/Drivers/<Vendor>/` is permitted when the library
-    exposes a port exercised against multiple third-party implementations (PSR adapters,
-    framework integrations). Each `<Vendor>/` subdir holds tests against one specific
-    implementation.
+    or `Doubles/` subdirectory exists. Vendor compatibility (driver) tests, verifying the
+    library against specific external libraries/frameworks, are optional and have no `src/`
+    counterpart. They exist only as tests, under `tests/Integration/Drivers/<Vendor>/`,
+    grouped by vendor. Never a top-level `Drivers/` under `tests/`.
 12. The `tests/Integration/` folder exists only when the library interacts with external
     infrastructure (filesystem, database, network). Otherwise, the folder is absent.
 
@@ -68,6 +68,8 @@ tests/
 │   ├── <SomeMock>.php        # test doubles at root of Unit/
 │   └── <SomeSpy>.php
 └── Integration/              # only present when the library interacts with infrastructure
+    ├── Drivers/              # only present when the library exposes vendor-specific drivers
+    │   └── <Vendor>/         # tests against one specific third-party implementation
     └── <SomeMock>.php        # test doubles at root of Integration/ when needed
 ```