chore: Cleanup

[michael-weigelt]

Some renaming and comments.

[zeropath-ai]

✅ No security or compliance issues detected. Reviewed everything up to 4009c54.

Security Overview

• 🔎 Scanned files: 11 changed file(s)
• 🔗 Scan Link: https://zeropath.com/app/repositories/f5e9d2bb-29a4-4b64-902a-391d65fd8b2d?scanId=f30f5135-9583-4099-a8d8-da716063630f&codeScanTypes=PrScan&tab=issues

Detected Code Changes

Change Type

Relevant files

Enhancement

► rs/embedders/src/wasm_utils/system_api_replacements.rs     Mark written pages in bytemap and enforce page limits; update documentation comments ► rs/embedders/src/wasmtime_embedder.rs     Remove outdated comment about dirty wasm heap pages charging ► rs/embedders/tests/instrumentation.rs     Rename overhead calculations to reflect OS-page based charging; adjust function names and comments accordingly ► rs/embedders/tests/wasmtime_random_memory_writes.rs     Introduce and use new dmt_instructions_per_wasm_page function; update tests to compute charges via DMT per OS page ► rs/execution_environment/EXECUTION_COST.md     Update documentation to reflect per-OS-page charging by the deterministic memory tracker and unify heap/stable memory overhead narrative ► rs/execution_environment/benches/lib/src/common.rs     Rename and redefine overhead computation to dmt_access_instructions and dmt_write_instructions ► rs/execution_environment/benches/system_api/execute_inspect_message.rs     Update benchmarks to use dmt_access_instructions(1) instead of previous overhead function ► rs/execution_environment/benches/system_api/execute_query.rs     Update benchmarks to use dmt_access_instructions(1) instead of previous overhead function ► rs/execution_environment/benches/system_api/execute_update.rs     Update benchmarks to use dmt_access_instructions and dmt_write_instructions in place of previous overhead functions ► rs/execution_environment/benches/lib/src/common.rs (additional changes)     Adjust comments and function names to reflect new dmt_* naming