Skip to content

dinah v0.1.0

Latest

Choose a tag to compare

@lecodev-26 lecodev-26 released this 19 Oct 08:17
· 3 commits to main since this release

First tagged release. v0.1 milestone complete — the v0.1 scope (puntos 001–277 of puntos.md) is closed and the v0.2 design cycle (puntos 278–287) is recorded in roadmap2.md / puntos2.md.

What's in 0.1.0

  • Modular Rust foundation: runtime scheduling/execution, memory buffers, sequential/parallel compute, generational ECS, fixed-step deterministic simulation (five bounded models), initial networking (reliable TCP wrappers, prediction/reconciliation/replay primitives), storage (KV store + CRC-32 journal), opt-in observability, and a CLI with a starter manifest subset.
  • Frozen v0.1 API and architecture (docs/public-api-review.md § v0.1 freeze decision, docs/integration-matrix.md § v0.1 architecture freeze decision) with a documented compatibility policy (SemVer 0.x).
  • Checklist status: 279 of 287 points complete; the 8 remaining points are deferred by design and tracked as v0.2 goals in puntos2.md (puntos 288–326).

Release verification (this commit)

  • cargo fmt --all -- --check clean
  • cargo clippy --workspace --all-targets --all-features -- -D warnings clean
  • cargo test --workspace --all-features: 293 tests green, 0 failures (285 unit/integration/determinism/contract/robustness + 8 doc-tests)
  • All 8 runnable examples executed successfully (cargo run --example <each>, exit 0)
  • Full benchmark suite (7 suites) executed locally and archived via CI on five platforms
  • cargo package verified: dinah-0.1.0.crate (210 KB) compiles from the packaged file; cargo publish --dry-run passes
  • MSRV verified empirically: Rust 1.95 (the workspace fails to compile on 1.94 — AtomicU64::try_update — and all tests pass on 1.95)
  • CI green on this commit: CI, quality and security (≥85% line coverage), documentation audit, benchmarks

Package

  • No runtime dependencies; dual-licensed MIT OR Apache-2.0
  • Crate ready for crates.io: cargo add dinah (publication is an explicit owner decision)

Known limitations (unchanged, documented)

Starter manifest subset (not full TOML), unsandboxed explicit task execution, no wire framing/auth/event codec, no parallel ECS systems or public component queries, no transactional storage, line coverage only (no branch coverage/fuzzing). See the README and docs/security-review.md.

Next

v0.2 cycle: wire framing + versioned event codec, public ECS queries, full TOML, optional sandboxing, atomic journal transactions, branch coverage, coverage-guided fuzzing and evidence-based optimization — see roadmap2.md.