⚡ Bolt: optimize live_catalog_feed constants and aggregation

[google-labs-jules]

⚡ Bolt: optimize live_catalog_feed constants and aggregation

💡 What:

1. Hoisted keyword tuples and sets (SPECIAL_FREE_MODELS, PREFER_KEYWORDS, REVIEW_KEYWORDS) to module-level scope in scripts/live_catalog_feed.py.
2. Consolidated multi-pass iterations in load_eligible into a single linear pass over catalog rows to accumulate eligible models and group by provider concurrently.
3. Added test coverage in tests/test_live_catalog_feed.py and documented learnings in .jules/bolt.md.

🎯 Why:
Instantiating set and tuple literals on every evaluation of _is_free and peer_candidates_for_role causes unnecessary memory allocation and runtime overhead during high-throughput model router evaluations.

📊 Impact:
Eliminates per-row collection allocations and reduces filtering/grouping passes in load_eligible from 2 passes to 1 pass ($O(N)$ runtime efficiency).

🔬 Measurement:
Verified through pytest tests/test_live_catalog_feed.py.

---

PR created automatically by Jules for task 14424034121719561458 started by @timerloggedout-spec

[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.

[blocksorg]

Mention Blocks like a regular teammate with your question or request:

@blocks review this pull request
@blocks make the following changes ...
@blocks create an issue from what was mentioned in the following comment ...
@blocks explain the following code ...
@blocks are there any security or performance concerns?

Run @blocks /help for more information.

Workspace settings | Disable this message

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
termux-monorepo	Ready	Preview, v0	Sep 21, 2026 8:08am UTC

[vercel]

Deployment failed for project help-wanted-dash with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/timerloggedout-5184s-projects?upgradeToPro=build-rate-limit

[ecc-tools]

ECC Tools / Security Evidence

Commit: df3b40712abd3aafa26970a4b48103ecbc8da9f3

Security evidence gate passed (success)

No security-sensitive scanner-evidence gap detected.

Mode: enforce

Scanned 3 changed file(s). No missing scanner-evidence signal was detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[vercel]

Deployment failed for project help-wanted-oversight with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/timerloggedout-5184s-projects?upgradeToPro=build-rate-limit

[vercel]

Deployment failed for project mcp-hub with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/timerloggedout-5184s-projects?upgradeToPro=build-rate-limit

[ecc-tools]

ECC Tools / PR Risk Taxonomy

Commit: df3b40712abd3aafa26970a4b48103ecbc8da9f3

PR taxonomy clear (success)

Scanned 3 changed file(s). No taxonomy bucket signals were detected.

Scanned 3 changed file(s).

No PR taxonomy bucket signals were detected.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / Reference Set Readiness

Commit: df3b40712abd3aafa26970a4b48103ecbc8da9f3

Reference set readiness gaps detected (neutral)

Reference evidence present for 0/7 areas (0%) across 3 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area	Status	Evidence / Next Step
Deep analyzer corpus	Missing	Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison	Missing	Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus	Missing	Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus	Missing	Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility	Missing	Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence	Missing	Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence	Missing	Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[ecc-tools]

ECC Tools / Hosted Promotion Readiness

Commit: df3b40712abd3aafa26970a4b48103ecbc8da9f3

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 3 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

[timerloggedout-spec]

ECC App activity — dual-gate merges; review skills/hooks before merge.

[github-actions]

PR Change Effectiveness Ledger

Measured head: df3b40712abd3aafa26970a4b48103ecbc8da9f3
Measured base: 47eb3a3a9d36b710f2e5cc79c1d56cc7f97b3e02
Merge base: 47eb3a3a9d36b710f2e5cc79c1d56cc7f97b3e02

Signal	Value
commits in PR range	1
commits with no file delta	0
commits with file delta	1
no-op commit rate	0%
gross additions across commits	103
gross deletions across commits	10
final additions vs base	103
final deletions vs base	10
final changed files	3
churn → retained final diff	100%
ahead / behind base	1 / 0

Interpretation: commit count is context, not quality. Empty commits are explicitly measured, not silently treated as productive work. Gross churn describes work performed across history; the final base→head diff describes what remains. Review/comment/check evidence must be evaluated separately and tied to this measured head SHA.

State: 🟢 EFFECTIVE_DIFF_PRESENT; No empty commits observed.

Generated: 2026-09-21T08:07:46Z