fix: accumulated values lost when reused tracked fn skips re-execution

[SAY-5]

When a tracked fn's inputs haven't changed, maybe_changed_after_cold fast-paths through deep_verify_memo and returns the VerifyResult directly. That result carries the accumulated flag from the fn's edge inputs only; if the fn itself pushed accumulated values, those are ignored. Callers upstream then see Empty and skip traversing this subtree, so accumulated values are silently dropped.

Fix: after deep_verify succeeds, check whether the memo's own AccumulatedMap is non-empty and return Any in that case, matching what the re-execute path already does (lines 229-232).

Fixes #923.

[netlify]

👷 Deploy Preview for salsa-rs processing.

Name	Link
🔨 Latest commit	16ab655
🔍 Latest deploy log	https://app.netlify.com/projects/salsa-rs/deploys/6a1554255469c80008d7267c

[netlify]

✅ Deploy Preview for salsa-rs canceled.

Name	Link
🔨 Latest commit	16ab655
🔍 Latest deploy log	https://app.netlify.com/projects/salsa-rs/deploys/6a1554255469c80008d7267c

[codspeed-hq]

Merging this PR will improve performance by 10.65%

⚡ 1 improved benchmark
✅ 25 untouched benchmarks

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
⚡	Simulation	amortized[InternedInput]	2.1 µs	1.9 µs	+10.65%

Tip

Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing SAY-5:fix-accumulator-wrongresult-issue-923 (16ab655) with master (7e77c49)}