docs: Add documentation for step logging fix

Author: Copilot

STEP_LOGGING_FIX.md

@@ -0,0 +1,45 @@
+# Step Logging Fix Documentation
+
+## Problem Statement
+Steps were not printed in logs when running either `--verbose` or `--debug` when the I actor method is called not directly in Scenario test file (e.g., in custom steps or page objects) and the custom step doesn't call any child I steps.
+
+## Root Cause
+The `MetaStep.run()` method in `lib/step/meta.js` never emitted `event.step.started` and `event.step.finished` events for itself. It only registered a listener to attach itself to child steps. If no child steps were called, the MetaStep was never printed in verbose/debug output.
+
+## Solution
+Modified `lib/step/meta.js` to track whether child steps are registered and conditionally emit events only if no children are registered. This prevents duplicate printing while ensuring standalone MetaSteps are visible in output.
+
+## Files Changed
+1. `lib/step/meta.js` - Core logic fix
+2. `test/unit/step/meta_step_logging_test.js` - Comprehensive unit tests
+
+## Testing
+- ✅ 6 new unit tests (all passing)
+- ✅ Manual testing with custom steps (verified fix works)
+- ✅ Existing tests (no regression)
+- ✅ Security scan (CodeQL: 0 alerts)
+- ✅ Linting (ESLint: 0 errors)
+
+## Example Output
+
+### Before Fix
+```
+  test with custom step WITHOUT I calls
+  Scenario()
+This is just a console.log
+  ✔ OK in 5ms
+```
+❌ Step name "I customStepWithoutI" is NOT printed
+
+### After Fix
+```
+  test with custom step WITHOUT I calls
+  Scenario()
+This is just a console.log
+    I custom step without i 
+  ✔ OK in 6ms
+```
+✅ Step name is now visible!
+
+## Known Limitation
+For synchronous MetaSteps without child steps, the step name appears after the function executes (because events are emitted in the finally block). This is an acceptable trade-off to avoid the complexity of predicting whether child steps will be registered.