Follow-up from Copilot review on PR #39.
Problem
Heartbeat staleness is opt-in via last_updated frontmatter. That is good for v0.2 compatibility, but legacy scaffolds with no last_updated fields can make mex heartbeat report a clean status even though no files are actually eligible for staleness checks.
Suggested fix
When heartbeat scans zero scaffold files with parseable last_updated, print a short hint explaining that staleness checks are inactive until files opt in with last_updated.
Example intent:
No scaffold files include last_updated; staleness checks are currently skipped.
Acceptance criteria
- mex heartbeat surfaces a hint when zero files participate in staleness checks.
- The hint does not turn an otherwise healthy heartbeat into an error.
- Existing v0.2 scaffolds remain compatible.
- TUI/doctor behavior is updated if they surface heartbeat status.
Source: #39 (comment)
Follow-up from Copilot review on PR #39.
Problem
Heartbeat staleness is opt-in via last_updated frontmatter. That is good for v0.2 compatibility, but legacy scaffolds with no last_updated fields can make mex heartbeat report a clean status even though no files are actually eligible for staleness checks.
Suggested fix
When heartbeat scans zero scaffold files with parseable last_updated, print a short hint explaining that staleness checks are inactive until files opt in with last_updated.
Example intent:
No scaffold files include last_updated; staleness checks are currently skipped.
Acceptance criteria
Source: #39 (comment)