VIGO v0.3.1

VIGO 0.3.1

0.3.1 stabilizes VIGO Engine, Studio, and the separate Python interface. API 1.0, City format 1, and Result schema 1 are unchanged.

• Reuse prepared City files after copying and extraction, without depending on filesystem timestamps. Timetable snapshots work across Node and the packaged runtime; station-access preparation is retained, and ride geometry is loaded only when selected.
• Build Studio for macOS Apple Silicon/Intel, Linux ARM64/x64, and Windows x64. Each archive contains the matching native runtime. Linux artifacts target glibc on Ubuntu 24.04; macOS requires 13.5 or newer. Native Windows ARM64, 32-bit, and musl builds are not provided.
• Update MapLibre to the patched 6.4.1 release for GHSA-jrc7-96c5-q579, and verify map rendering, source updates, and attribution sanitization through the Studio protocol.
• Fix City-build resource use, source-change detection, station-access reporting, and current-format test fixtures. Remove provisional metadata aliases and redundant opening work.
• Close compilation stores before publishing rebuilt project directories on Windows.
• Align the Engine / Studio / Python narrative and keep Python installation and API details in its own repository.
• Restrict realtime claims to Studio Route's bounded overlay of supported, matched Trip Updates. Vehicle Positions and Alerts are displayed, not routing constraints. CLI/Python live Scenarios, realtime Matrix, and realtime Reach are unsupported.

Copy the complete City directory. Retained preparation is reusable; a new service pattern, changed policy, evicted cache, or older timetable format may need preparation again. Missing or corrupt required street files require restoring or rebuilding the City. Studio library settings and drafts do not travel with CLI Cities, and Studio does not directly open those directories.

Review known routing limits before interpreting results. In particular, incomplete station pathways, parent-station transfer assumptions, omitted GTFS semantics, and unmodeled drive turn restrictions limit what a computed journey establishes.

Release gates run the complete engine suite on five OS/CPU targets, exchange prepared synthetic Cities between them, check packaged runtime build/query behavior, compile the Developer Guide, and attest release artifacts. This remains pre-release software; stabilization does not establish operational or passenger-information suitability. macOS signatures are ad-hoc, and archives are not notarized or backed by a publisher certificate.