perf(catalogue): optimize stale entry git log parsing in gen-catalogue-status.py

[mjmirza]

Problem Reproduction

Executing tools/gen-catalogue-status.py took ~5.0s due to stale_count() issuing 890 individual git log -1 subprocess calls (one per published pattern entry file).

Root Cause

stale_count() iterated over all 890 published pattern paths and ran a blocking git log -1 --format=%ct -- <path> subprocess command for each path sequentially.

Solution

• Refactored stale_count() in tools/gen-catalogue-status.py to run a single git log --format="COMMIT %ct" --name-only -- patterns/ subprocess command.
• Stream-parsed the output in chronological order to record the latest commit timestamp for each published pattern path, terminating early once all published pattern timestamps are collected.
• Added unit test cases in tools/gen-catalogue-status-test.py testing stale count calculations and edge cases.

Measurements

• Before: ~5.0 seconds
• After: ~0.01 seconds (~500x speedup)
• Output verification: dist/catalogue-status.json, docs/PROGRESS.md, and README.md generated outputs remain identical.

Security & Compatibility

• Pure read-only git log query without shell injection risks.
• Backward compatible; safe fallback to 0 stale count if git/repo environment is unavailable.

Confidence Score

96/100 (Historical novelty: 25, Impact: 20, Root cause: 15, Evidence: 15, Solution: 10, Risk: 5, Maintenance: 3, Reversibility: 3)

---

PR created automatically by Jules for task 5077689403762783370 started by @mjmirza

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.