Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Migration overview

This section records how ce-mcp moved from “a full Cheat Engine clone in Rust” to an MCP-first design with a Lua bridge, and what evidence supports each decision.

The migration is documented as a sequence of dated notes, not as a polished after-the-fact story. Where a claim comes from a command, the command and its limits are recorded. Where a conclusion is an inference, it is labelled as such.

Timeline

DateMilestone
2026-10-21Inspected the Cheat Engine 7.7 macOS bundle and measured its surface
2026-10-21Researched the public Cheat Engine source landscape
2026-10-21Researched MCP 2026-07-28 and the Rust SDK
2026-10-21Narrowed the scope from a full clone to an MCP server
2026-10-21Chose a Lua bridge as the first backend
2026-10-21Defined profiles, stateless handles and the tool catalog
2026-10-21Ran a formal REA CLI/Mach-O, plist and signature pass
2026-10-21Mapped three debugger controls and formally deferred the remaining 11 gaps
2026-10-21Defined the F0 bridge and MCP acceptance test plan
2026-10-21Defined JSON Schema contracts for the six F0 tools
2026-10-21Published a documentation-only public preview
TBDF0: bridge and MCP spike
TBDImplementation license selected before code contributions

How to read these documents

DocumentQuestion it answers
01-target-inventory.mdWhat exactly is the Cheat Engine 7.7 build we are targeting?
02-source-landscape.mdWhat public source exists, and what can we rely on?
03-mcp-research.mdWhich MCP revision and transports should we target?
04-decisions.mdWhat did we decide, when, and why?
05-backend-strategy.mdWhy a Lua bridge first, and how does a native backend fit?
06-tool-migration.mdHow do Cheat Engine capabilities become MCP tools?
07-open-source.mdWhat does the project need before it is open source?
08-gap-deferrals.mdWhy are the remaining 11 tools gaps, and what would close them?
09-f0-test-plan.mdHow will the six-tool F0 spike be accepted?
journal/2026-10-21.mdWhat happened in the first design session?

Evidence labels

Every technical claim in this section should be read with one of these labels:

  • Observation — directly measured from the shipped bundle, the public source tree or an official specification.
  • Inference — a conclusion drawn from observations; may be wrong.
  • Unknown — not established by the available evidence.

The initial inventory began with shell tools (file, nm, strings, otool, codesign). A later formal REA 6.7.0 CLI/Mach-O, plist and signature pass strengthened the metadata evidence. Neither pass establishes runtime behavior; that boundary is recorded in 01-target-inventory.md.

Scope of the migration

“Migration” here means two things:

  1. Capability migration: turning Cheat Engine’s operations into stable MCP tools.
  2. Backend migration: moving from the Lua bridge to a native Rust backend without changing the MCP contract.

It does not mean porting the Cheat Engine GUI to Rust. The desktop UI is out of scope for the current roadmap.

Maintenance

When a new investigation or decision is made:

  1. add a dated journal entry under journal/;
  2. update 04-decisions.md;
  3. add or supersede an ADR if the decision is architectural;
  4. update 06-tool-migration.md if the tool catalog changes;
  5. keep the coverage document honest: designed is not implemented.