feat(timing): add AI pipeline timing budget instrumentation

[zjwjing]

Summary

Adds per-stage timing instrumentation to the AI training pipeline, fulfilling all acceptance criteria in issue #5.

Changes

• New tools/ai_pipeline_timing_summary.py: Records elapsed time per stage, identifies the slowest stage, flags over-budget stages (optional threshold), and writes both JSON and human-readable summaries. Does NOT log raw prompts or secrets.
• Modified ai_pipeline.sh: Each pipeline phase now wrapped with record_stage_start / record_stage_end. Includes EXIT trap to capture partial timing data on failure. Calls the summary generator on completion.
• New tests/test_ai_pipeline_timing_summary.py: 12 unit tests covering structure, total duration calc, slowest stage detection, budget threshold enforcement, empty/single-stage edge cases, text output format, and secret redaction - all passing.

Acceptance Criteria Coverage

1. Per-stage elapsed time - record_stage_start/end captures wall-clock ms per phase
2. Text summary - format_text_summary produces per-stage breakdown
3. JSON summary - build_summary outputs structured JSON with total + slowest + per-stage
4. Total duration + slowest stage identified - both in JSON and text output
5. Optional budget threshold - budget-secs parameter flags over-budget stages
6. No raw prompts or secrets - summary outputs only name, elapsed, and status
7. Unit tests - 12 tests, all green

Diagnostic

Diagnostic .logd generated at commit 3774a0c (encryptly not available in WSL, .no-encryptly marker created).

Closes #5

[zjwjing]

Implementation Complete

This PR adds AI pipeline timing budget instrumentation.

Key Features:

• Timing budget tracking for AI pipeline stages
• Performance metrics collection
• Integration with existing monitoring

Please review and let me know if any changes are needed.

Thank you!

[zjwjing]

Hi @Soengkit — I understand this is your working fork. My work here (AI pipeline timing instrumentation) addresses Issue #5 on your fork. If the bounty intake is tracked on a different upstream, please let me know where to redirect. Happy to re-submit to the correct repo if needed.

[Soengkit]

Thanks for the PR. I am closing this because Soengkit/zeroeye is only my working fork of the upstream repository, not an official bounty intake or payment queue. The fork parent/source is NemoMi/zeroeye: https://github.com/NemoMi/zeroeye. Please use the upstream owner current process for any submission or claim, and do not post payment details here.