Capture the unexpected build-index exit so the next session starts from failure analysis
Constraint: Both observable and legacy build-index jobs exited without producing reference_* or evaluate artifacts Rejected: Keep treating the run as slow linear progress | no longer matches the fresh ps/pgrep evidence Confidence: high Scope-risk: narrow Directive: Start the next cycle with build-index exit-path diagnosis before launching more long runs Tested: Verified ps/pgrep show no active build/evaluate process; verified observable directory still only has chromaprint progress/cache files; reviewed updated handoff docs Not-tested: No root-cause reproduction or fix yet
Showing
5 changed files
with
109 additions
and
143 deletions
-
Please register or sign in to post a comment