Rename unusable memory codec context guard

[AriusII]

Summary

• Follow-up to Expire memory codec contexts per invocation #44: rename the private memory-codec context guard to ThrowIfUnusable so its name matches its throwing condition.
• Update its three internal call sites only; no runtime behavior or public contract changes.

Validation

• dotnet restore CheatEngine.Client.slnx --locked-mode
• dotnet test --project .\tests\CheatEngine.Client.Core.Tests\CheatEngine.Client.Core.Tests.csproj --configuration Release --no-restore --fail-skips on — Passed: 254, Failed: 0, Skipped: 0.
• dotnet build CheatEngine.Client.slnx --configuration Release --no-restore --warnaserror — 0 warnings, 0 errors.

Summary by CodeRabbit

• Refactor
  • Clarified internal validation terminology for memory access operations.
  • Existing validation behavior remains unchanged, including checks for expired, inactive, stale, cross-thread, and incorrectly dispatched contexts.
  • No user-facing functionality, API behavior, or capabilities were added, removed, or modified.

[coderabbitai]

Understand this PR’s impact

Explore downstream dependencies and potential security impact with Blast Radius.

View blast radius →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 47dbfb45-b263-459f-a903-5d7b3c2ca2d9

📥 Commits

Reviewing files that changed from the base of the PR and between 02077c0 and 4804425.

📒 Files selected for processing (1)

• libs/CheatEngine.Client.Core/Domains/MemoryClient.cs

Included review availability: Your plan provides up to 10 included reviews per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The private TargetMemoryCodecContext validation method was renamed to ThrowIfUnusable. The PointerSize, TryReadBytes, and TryWriteBytes call sites now use the renamed method. Validation behavior is unchanged.

Changes

Memory context validation

Layer / File(s)	Summary
Rename context validation method libs/CheatEngine.Client.Core/Domains/MemoryClient.cs	ThrowIfUsable was renamed to ThrowIfUnusable. PointerSize, TryReadBytes, and TryWriteBytes now call the renamed method. Validation conditions and failure behavior remain unchanged.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Refactor

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 4 functions across 1 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: renaming the memory codec context guard to reflect its throwing condition.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}