v0.1.0-alpha.12

Add strict Prometheus metric parsing and a separate playerbot observer for private LyraCore acceptance. It captures confirmed transactions, scheduler order and lag, movement completion, decision durations and transaction counters. Long runs retain bounded gzip archives and preserve capture failures.

Linux and macOS CI passed all 81 generic tests, 29 observer tests, strict lint, formatting, release builds and the five offline adapter checks. Three ten-bot private movement runs established the observer's inputs and movement accounting; the final persistent 10, 25 and 100 bot matrix and imported-world hour remain pending. This release does not establish deployment capacity.

Sources: #14, #15 and #16. Release commit b57904f.

v0.1.0-alpha.9: Account ownership cleanup arguments

Updates LyraCore's party and Transfer cleanup calls for durable Account ownership. The matching LyraCore checkout selects the new SessionActor argument; older checkouts retain their existing calls. Transfer keeps its separate id argument. Operator cleanup uses null ownership and does not adopt a replacement World Session's token.

A refused party cleanup stops before changing the local mirror. Running fixture World Sessions must release or expire before this cleanup can proceed.

PR #11 passed independent review, all four offline shell checks and Ubuntu/macOS/coverage CI. The command-boundary regression covers all three changed callers, both argument layouts and a Character guid above 2^53. No Realm was accessed.

v0.1.0-alpha.8: dive and drowning acceptance adapter

Adds the dive protocol scenario and LyraCore acceptance adapter. It sends typed swimming movement, verifies the Breath timer, waits through the advertised window, and requires an own Character Drowning log whose damage matches the observed health drop. Surfacing must stop the Breath timer before logout.

The adapter verifies the imported liquid cell before changing a clearly named disposable Character. Credentials enter through stdin. Invalid identity, coordinates, database names, and unsuitable terrain stop before Character changes.

PR #10 passed parent review, 75 tests, strict clippy, release builds, offline adapter checks, ShellCheck, and Ubuntu/macOS/coverage CI. Coordinate selection, live Realm execution, head-height calibration, and stock-client acceptance remain with the Operator.

v0.1.0-alpha.7: bank flow acceptance adapter

Adds the bank-flow protocol scenario and LyraCore acceptance adapter. It checks bank activation, item identity through deposit, logout/login and withdrawal, and the first bank bag purchase. Credentials enter through stdin.

Own Character inventory observations preserve sparse CREATE defaults and partial VALUES updates. Setup failures stop the adapter.

PR #9 passed parent review, 69 tests, strict clippy, release builds, offline shell checks and Ubuntu/macOS/coverage CI. Live Realm execution and stock-client bank-window acceptance remain with the Operator.

v0.1.0-alpha.6: sparse Character snapshot defaults

Benchmark death counts now apply the protocol's zero defaults to sparse Character CREATE snapshots. New login and replacement CREATE packets clear the previous Character observation. Partial VALUES packets still leave absent fields unchanged.

Includes PR #8 and the dead/unknown reporting from alpha.5. The correction passed parent review, 65 tests, strict clippy, release builds, and Linux, macOS and coverage CI.

v0.1.0-alpha.5: benchmark death counts

Raid benchmark reports now show connected, dead, and death-unknown clients at each measured window close. Counts include login snapshots, later health updates, ghosts, revival, and disconnects.

Report schema v3 adds the two counts. Older reports keep missing values unknown. The additive ramp is unchanged.

Includes PR #7. Reviewed commit a8398ba passed Linux, macOS and coverage checks, 62 local tests, strict clippy and release builds.

Known limitation found after review: a sparse login CREATE that omits zero health or player flags can leave the initial death state unknown. Corrected in alpha.6 by PR #8. Later partial updates remain supported.

v0.1.0-alpha.4: reliable suite dispatch

The LyraCore suite now resolves scenario scripts from the adapter checkout, accepts a named subset, and reports scenario startup failures as errors. Offline shell checks run on Linux and macOS.

This release also includes the merged fixture preparation and bot scenario updates since alpha.3.

Validation: 55 Rust tests, formatting, clippy, release builds, coverage, and offline suite dispatch checks passed in PR #6. Live realm acceptance remains separate.

Changes reviewed and released by GPT-6 Astra through Codex in T3 Code.

v0.1.0-alpha.11

Scope LyraCore party scenarios to their owned Character and party IDs. Remove the global party reset, fail closed on authority lookup failures, and verify Character deletion preserves survivors and an unrelated party on Realm-core and the World Shard. Character creation and deletion wait briefly for the next Character-list update while retaining protocol success checks and exact deleted-GUID assertions.

Linux, macOS, coverage, all five offline adapter tests, strict lint, formatting, and independent review passed. The owned two-Shard deletion scenario passed twice. The full eight-scenario Playerbots run remains pending a compatible Package-enabled Module and Gateway pair.

Source: #13, merge 30a2dd2.

v0.1.0-alpha.10

Fix LyraCore Operator cleanup against the durable Account ownership API. Structured GUID fields are JSON numbers, preserving the decimal digits without float conversion. Release alpha9 encoded them as JSON strings, which the Module refuses.

Legacy reducer calls remain compatible. All four offline shell suites, Linux/macOS tests and coverage CI pass. A real SpacetimeDB 2.7.1 call preserves GUID 9007199254740993 exactly.

v0.1.0-alpha.2 — restart bridge + DB overridability

Bumps the pin past two commits landed on main since v0.1.0-alpha.1:

• 6b40a43 — bridge GW_* -> LYRACORE_* when relaunching a harvested gateway (the #265
  restart bridge). Until pinned, the pinned adapters' restart_gateway silently dropped all
  topology against a post-rename stack — the exact silent-single-database trap.
• 30e1808 — DB=${DB:-lyracore} overridability across the adapters, what makes
  run-suite.sh --database reachable.

Verified at this commit

CI green on Linux and macOS (cargo fmt --check, cargo clippy --all-targets -- -D warnings,
cargo test, a release build of both binaries, bash -n over all adapter scripts).

Build support: 5875 (1.12.1) only.

Full Changelog: v0.1.0-alpha.1...v0.1.0-alpha.2