Matlab Change Verification

Goal

Make MATLAB edits safer and less guessy.

Required workflow

1. Identify the exact MATLAB entrypoints touched by the task.

   • name the modified functions, scripts, classes, and test files
   • identify whether the code lives in +pkg, @Class, private, or plain folders

2. Check path and dispatch risks before editing.

   • package resolution
   • class method dispatch
   • private/ visibility
   • startup.m, pathdef.m, addpath, or project setup logic

3. Prefer matlab -batch validation.

   • use the narrowest real test or smoke command first
   • if a full suite is too expensive, run the smallest command that exercises the changed path

4. If no test exists, state that explicitly and propose the smallest defensible smoke check.