Skip to content

v0.7.0 — Unity forensic replay viewer

Choose a tag to compare

View all tags
@MichalPlanetaDev MichalPlanetaDev released this 06 Jul 10:10
· 29 commits to main since this release
v0.7.0
e9ed680
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v0.7.0 — Unity forensic replay viewer

Tickline v0.7.0 adds a deterministic, read-only Unity Editor investigation client for evidence archives verified and exported by the native C++ layer.

Added

  • Deterministic investigation-bundle JSON export from the SQLite investigation repository.
  • Schema-versioned native-to-Unity compatibility contract.
  • Lossless decimal-string transport for unsigned 64-bit values.
  • Export-time evidence-count, chain-head, session-summary, and replay-metadata checks.
  • Unity file and in-memory JSON loading.
  • Stable validation findings for malformed investigation bundles.
  • Schema, identity, integer, digest, ordinal, session-reference, evidence-chain, trusted-head, and replay-count validation.
  • Deterministic replay timeline and nearest-tick selection.
  • Play, pause, step, seek, reset, and configurable playback speed.
  • Session, command, replay, archive, and evidence-chain inspection.
  • Accepted and rejected outcome filtering.
  • Exact client and session filtering.
  • Stable mapping between filtered evidence and original timeline positions.
  • Transactional loading that preserves the active investigation after a rejected replacement.
  • Unity Editor forensic replay window.
  • Native exporter compatibility tests.
  • Unity EditMode coverage.
  • WSL-compatible Unity test execution through a disposable Windows project mirror.

Verification

Run from the repository root:

bash scripts/check-local.sh
bash scripts/check-unity.sh

The local repository gate covers documentation validation, normal C++ tests, sanitizer tests, Python tests, Go tests and vet, developer-console version verification, and the Docker smoke build.

The Unity gate opens the staged project in batch mode, executes the EditMode suite, writes NUnit-compatible XML results, and fails unless Unity reports a passing test run.

Security and trust boundary

The C++ implementation remains authoritative for evidence verification, archive storage, deterministic replay, and investigation-bundle export.

The Unity viewer consumes immutable exported investigation bundles. It does not execute authoritative commands, modify evidence, repair malformed input, or replace native replay decisions.

Limitations

  • The viewer runs inside the Unity Editor; no standalone viewer build is included.
  • Unity verification requires an installed and licensed Windows Unity Editor.
  • Hosted Unity execution is not configured in GitHub Actions.
  • Investigation bundles are not digitally signed.
  • The viewer does not prove evidence authorship.
  • No remote investigation service is included.
  • Authentication, transport encryption, key management, collision validation, and production anti-cheat deployment remain out of scope.
Assets 2
Loading