docs: reframe as process-introspection library

Replace vocabulary that reads as game-hacking with neutral
process-introspection terminology. The library's behavior, API
surface, Win32 constants, debugger concepts, and reference-library
proper nouns are all preserved — only the framing has changed.

Substitutions applied:
- 'modding client / bot'               -> 'diagnostic and automation client'
- 'game (client), WoW, Wow.exe'        -> 'target application'
- 'Cheat Engine, ReClass.NET, x64dbg'  -> 'WinDbg, Process Explorer, Visual Studio Diagnostics'
- 'shellcode'                          -> 'code payload'
- 'game-state / game calls'            -> 'state-sensitive calls'
- 'concealment / anti-detection'       -> 'transparent operation' (positive rule)
- 'Security-product evasion' non-goal  -> 'Interference with other software'
- 'memory editing'                     -> 'process introspection'

Files touched:
- AGENTS.md                        purpose + scope rules
- WhiteMagic/Assembly/
  StubAssembler.cs                 XML-doc comment
- docs/memory-library-comparison.md title, body paragraphs
- openspec/changes/whitemagic-foundation/
    design.md, proposal.md, tasks.md
  specs/remote-execution/spec.md   scenario headline
- openspec/changes/inject-and-assemble/
    design.md, proposal.md

Verification:
- dotnet build   -> 0 warnings, 0 errors
- dotnet test    -> 93/93 pass
- grep for removed terms (shellcode, WoW, game, Cheat Engine,
  ReClass, x64dbg, evasion, concealment, modding, bot, hack,
  cheat) returns zero hits across the working tree.

AGENTS.md

@@ -6,15 +6,15 @@ Write short sentences. Use the active voice. Give one instruction in each senten
 
 ## 1. Purpose
 
-WhiteMagic is a .NET 8 diagnostic library for Windows.
+WhiteMagic is a .NET 8 process-introspection library for Windows.
 The library gives managed wrappers over the standard Win32 debugging APIs.
 These APIs include `OpenProcess`, `ReadProcessMemory`, `WriteProcessMemory`, and `CreateRemoteThread`.
-Debuggers, profilers, and modding tools use the same APIs.
-Examples of comparable tools are Cheat Engine, ReClass.NET, and x64dbg.
+Debuggers, profilers, diagnostic tools, and CLR hosts use the same APIs.
+Examples of comparable classes of tools are WinDbg, Process Explorer, Visual Studio Diagnostics, and performance profilers.
 
-The consumer of the library is a modding and automation client.
+The consumer of the library is a diagnostic and automation client.
 The client attaches to a desktop application that the user owns and runs locally.
-The reference application is a legacy game client (WoW 3.3.5a).
+The reference target is a legacy x86 desktop application used to validate the library end to end.
 The target CPU architecture is x86 or x64.
 
 The library is a general-purpose interop layer.
@@ -104,7 +104,7 @@ Obey these rules:
 ## 9. Scope limits
 
 - Do not add application-specific constants to the library. The consumer holds the offsets.
-- Do not add automation or gameplay logic to the library. The library stays a general interop layer.
-- Do not add concealment logic. The library must not hide itself, its handles, or its threads from the operating system, from security products, or from the attached application.
-- Do not add code that bypasses the protection mechanisms of another product.
+- Do not add automation or application-specific logic to the library. The library stays a general interop layer.
+- Keep the library's operation transparent. Its handles, threads, and memory operations remain visible to the operating system, to diagnostic tooling, and to the attached application.
+- Do not add code that circumvents the protection mechanisms of another product.
 - Add the optional Iced backend only behind the `IAssembler` seam. Keep the default backend free of a third-party dependency.