⚡ Bolt: O(N) 배열 검색을 O(1) 딕셔너리 키 조회로 교체

[seonghobae]

Supersession receipt

This automatically-created PR is not a new canonical chart-export owner.

Its valid semantic intent is fully represented by existing canonical lanes:

• Chart-export de-duplication: perf(chart): preserve ordered export de-duplication in linear time #1076 exact 7cda784883efea60f6070c24c591660dcddfcbd0 owns the same four list-to-insertion-ordered-dictionary substitutions in exports/chart.py, plus _hashable_text containment and dedicated regressions for duplicates, first-occurrence ordering, unhashable/hashable/truthiness-overriding str subclasses, and rehearsal-priority normalization. This is strictly safer and more complete than this PR's direct arbitrary-str dictionary-key implementation.
• The .jules/bolt.md performance lesson adds no product/test/fixture contract beyond perf(chart): preserve ordered export de-duplication in linear time #1076's canonical note.
• services/analysis-engine/tests/test_supply_chain_policy.py is unrelated to chart export. This PR reproduces exactly the one-line Ruff formatting repair canonically owned by repair(ci): format consolidated supply-chain policy test #1176; it must not create a second formatter owner.

This PR has no focused chart regression, no unique fixture/contract, and no review finding or evidence that must be retained separately. Its successful predecessor CI/build/SBOM checks do not transfer to #1076 or #1176.

#1076 was repaired first as an ordinary non-force descendant onto current protected develop, and its fresh protected-base compare is exactly five canonical chart-owner files. No workflow, lockfile, supply-chain-policy, security-policy, or formatter delta remains there.

Closing this PR unmerged is therefore a complete-succession close, not deletion of unique work. Canonical owners remain #1076 for chart-export performance/correctness and #1176 for the protected formatter defect.

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

[coderabbitai]

Warning

Review limit reached

Next included review available in 57 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 8e2e7e8d-dcfb-4d53-bf83-f6e10d0eb5b9

📥 Commits

Reviewing files that changed from the base of the PR and between 314ddea and df19a04.

📒 Files selected for processing (3)

• .jules/bolt.md
• services/analysis-engine/src/bandscope_analysis/exports/chart.py
• services/analysis-engine/tests/test_supply_chain_policy.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}