v0.6.2

[pnxenopoulos]

Two fixes and a workspace version bump 0.6.1 → 0.6.2.

active_modifiers reported stale stack counts

First reported on Discord. The active_modifiers change-detector read a modifier's stack_count once, the first tick it saw the modifier, and never again. Every later in-place update hit the already-tracked branch and was dropped, so:

• a stacking modifier that climbed (e.g. a Spellslinger Headshots debuff going 2 → 3 → 4) kept reporting its first-seen value
• the removed row echoed that stale value, not the final total (every apply/remove pair had identical stacks — the tell-tale sign).

In-place stack changes are now captured: a new event value "changed" is emitted on the tick a live modifier's stacks moves, and removed reports the final count. applied / removed semantics are otherwise unchanged. The boon-dev active-modifiers command gains the same changed events.

Opening a demo no longer requires a match ID

Demo(path) used to resolve the match ID (and game mode) from CCitadelGameRulesProxy on the first tick and raise
DemoMessageError: could not resolve match ID … if it couldn't — rejecting a demo that was otherwise fully parseable (partial captures, sandbox / custom content).

• Demo.match_id is now int | None — recorded when present, None otherwise.
• Demo.game_mode (previously resolved in the same step, so it failed together with the match ID) now falls back to 0 when the game-rules entity is absent.

Such demos now open normally, instead of failing during construction.