chore(deps): bump umm-actually to v0.4.0

[aliasunder]

Summary

Bump umm-actually from v0.3.14 to v0.4.0 (65ccbe7).

Changes in v0.4.0

• feat: staged review phases — parallel and sequential modes (#79)
• feat: content-based cross-run dedup for shifted/reworded findings (#85)
• fix: content dedup follow-ups — coalesceAnchors, titleSimilarity, logging (#86)
• fix: filter self-negating findings (#84)
• chore: bump default context_budget_tokens from 80K to 300K (#87)
• docs: drop the early-development status section (#83)

[umm-actually]

Align context_budget_tokens default with the action's v0.4.0 default
Medium severity · correctness · high confidence

.github/workflows/umm_review.yml:104 — beyond the diff's line ranges, in code the changes touch or depend on.

The workflow passes '80000' as the default for context_budget_tokens, but v0.4.0 of the action changed its default to 300K (per PR #87). The comment on lines 102–103 also states the old default. Repos relying on the workflow default will see a smaller context budget than the action's advertised default, and the comment is a stale factual claim in changed code.

Failure scenario: A repo that does not set the UMM_CONTEXT_BUDGET_TOKENS variable runs the review with an 80K token budget while the action's v0.4.0 default is 300K — priority docs and related files are truncated or dropped from context, degrading review quality compared to the action's advertised default.

Suggested fix

Change `context_budget_tokens: ${{ vars.UMM_CONTEXT_BUDGET_TOKENS || '80000' }}` to `... || '300000'` and update the comment to state the new default.

---

umm-actually · deepseek/deepseek-v4-flash-0731

[umm-actually]

umm-actually re-reviewed at 1cb2b21

No new findings (1 tracked finding(s) across all runs).

---

umm-actually · deepseek/deepseek-v4-flash-0731

[aliasunder]

Fixed — context_budget_tokens fallback updated from '80000' to '300000' to align with v0.4.0's new default.

---

🔍 ship-check · pr-monitor · claude-opus-4-6