fix(OPENFRAM-009-3): CU-86akeeczr Newly generated icon components have no corresponding package.json exports map entries verifiable in this batch

[flamingo]

Closes findings from rule OPENFRAM-009-3 — Newly generated icon components have no corresponding package.json exports map entries verifiable in this batch.

Draft — this is a starting point, not a finished change. The fix required judgment, so read it before trusting it.

#	Fix confidence	Finding	Location
1	🔴 15 low — review closely	Newly generated icon components have no corresponding package.json exports map entries verifiable in this batch	openframe-frontend-core/src/components/icons-v2-generated/map-and-travel/flag-03-icon.tsx:1

What changed — and what was deliberately left — is explained per finding as inline review comments on the lines each finding touched.

---

Run: https://product-hub.flamingo.so/admin/code-review
Run id: 4f0d6344-55d4-49de-bc86-cac2510f432f

Merging this PR is recorded as acceptance of the rule that produced it;
closing it unmerged is recorded as rejection. Both feed rule health, so
closing a wrong suggestion is useful rather than merely tidy.

ClickUp task: CU-86akeeczr OpenFrame lib batch review findings sweep 2 (13 PRs)

[flamingo]

🦩 What this fix changed, finding by finding

1 finding(s) fixed in this draft — 1 explained inline on the diff; 1 low-confidence hunk(s) need close review before merging.

[flamingo]

🦩 🟠 Newly generated icon components have no corresponding package.json exports map entries verifiable in this batch

This finding requires adding an exports map entry in package.json for this new icon module, but the task scope is restricted to editing only flag-03-icon.tsx, and no package.json content was provided to modify in this batch. No change was made to this file (its content is already a correct, self-contained component export and requires no code changes to resolve the underlying finding). A complete fix requires editing openframe-frontend-core/package.json to add an explicit exports entry (with types/import/require/default conditions) for ./src/components/icons-v2-generated/map-and-travel/flag-03-icon (and likely all sibling new icons), which is outside this file's reach — this must be done as a separate, coordinated change to package.json.

🤖 Prompt for AI agents

In openframe-frontend-core/src/components/icons-v2-generated/map-and-travel/flag-03-icon.tsx around line 1, review and complete this code-review fix: Newly generated icon components have no corresponding package.json exports map entries verifiable in this batch.
What the draft fix changed: This finding requires adding an `exports` map entry in `package.json` for this new icon module, but the task scope is restricted to editing only `flag-03-icon.tsx`, and no `package.json` content was provided to modify in this batch. No change was made to this file (its content is already a correct, self-contained component export and requires no code changes to resolve the underlying finding). A complete fix requires editing `openframe-frontend-core/package.json` to add an explicit exports entry (with types/import/require/default conditions) for `./src/components/icons-v2-generated/map-and-travel/flag-03-icon` (and likely all sibling new icons), which is outside this file's reach — this must be done as a separate, coordinated change to package.json.
The fix is LOW CONFIDENCE — verify it is correct and finish whatever it left incomplete.

fix confidence: 🔴 15 low — review closely — react 👍/👎 to teach the reviewer

[michaelassraf]

Task linked: CU-86akeeczr OpenFrame lib batch review findings sweep 2 (12 PRs)