Failures while computing history / delta / flaky / perf analytics are logged via core.debug(), which is invisible unless the consumer enables Actions step debug logging.
A user can therefore silently lose run history or analytics with no indication anything went wrong.
Suggested fix
- Promote data-affecting failures (history load/save, delta/flaky/perf computation) to
core.warning() so they're visible.
- Keep verbose tracing at
core.debug().
- Must still never call
core.setFailed() and always exit 0 (FR5).
Flagged during the AI-native docs revamp; tracked in .agents/known-issues.md (item E).
Failures while computing history / delta / flaky / perf analytics are logged via
core.debug(), which is invisible unless the consumer enables Actions step debug logging.A user can therefore silently lose run history or analytics with no indication anything went wrong.
Suggested fix
core.warning()so they're visible.core.debug().core.setFailed()and always exit 0 (FR5).Flagged during the AI-native docs revamp; tracked in
.agents/known-issues.md(item E).