[codex] Align local test entrypoints with build tasks

[Pluze]

Summary

• rewrote local MATLAB test scripts as build-task wrappers with default buildtool test
• added focused build tasks for project, LabKit facade, app, GUI structural, and GUI smoke validation
• renamed migrated Legacy*Test classes/files and helper names to domain-focused test names
• updated README, docs, AGENTS, and repo skills to make buildtool the canonical test entrypoint

Validation

• git diff --check
• git diff --cached --check
• target legacy/old-flag scan returned no matches
• powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\run_matlab_tests.ps1 checkStyle
• powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\run_matlab_tests.ps1 --suite project failed before MATLAB with the new unsupported-option migration message
• matlab -batch "buildtool checkStyle"
• matlab -batch "buildtool test"
• matlab -batch "buildtool testProject testLabkitDta testLabkitBiosignal"
• matlab -batch "buildtool testGuiStructural"
• matlab -batch "buildtool testGuiGesture"

Not Verified

• bash -n scripts/run_matlab_tests.sh and Bash wrapper behavior were blocked locally by Windows/WSL E_ACCESSDENIED before Bash could start.
• Automated GUI checks are structural/gesture coverage only; full interactive GUI workflows still require manual MATLAB validation.

Notes

• tests/runLabKitTests.m remains the internal official runner used by build tasks.
• artifacts/ and matlab_test*.log remain ignored and were not committed.