docs: update roadmap with custom view markers

[jkasprzyk17]

No description provided.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0f5601d6-e678-4e48-8340-d5c91d100810

📥 Commits

Reviewing files that changed from the base of the PR and between 36f8472 and a911e4d.

📒 Files selected for processing (3)

• .github/CODEOWNERS
• docs/adr/0004-custom-view-markers.md
• docs/roadmap.md

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation

  • Added a new architecture note describing the planned support for custom map view markers.
  • Updated the roadmap with a new decision area and phased implementation checklist for marker behavior.

• Chores

  • Added default code owners for the repository to help route future changes.

Walkthrough

This PR is entirely documentation and repo governance: it adds a CODEOWNERS wildcard rule assigning default ownership, introduces ADR 0004 documenting a proposed opt-in MarkerView HybridView API for custom markers, and updates the roadmap with a corresponding decision entry and phased checklist.

Changes

Documentation and Ownership Updates

Layer / File(s)	Summary
CODEOWNERS wildcard rule .github/CODEOWNERS	Adds a default wildcard rule assigning repository ownership to two maintainers.
ADR 0004: custom view markers docs/adr/0004-custom-view-markers.md	New ADR documenting the current bitmap-only descriptor pipeline, proposing an opt-in MarkerView Nitro HybridView with MarkerViewProps/MarkerViewMethods, a 3-phase implementation plan, open verification items, and stated consequences.
Roadmap update docs/roadmap.md	Adds a "Custom view markers" open decision row referencing ADR 0004 and a phased checklist subsection.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: piotr-graczyk-dev

Since you asked so nicely: this "PR" is three markdown files and a text config — there is no logic to break, no tests to skip, and nothing here should require more than a skim. If you spend more than five minutes on this, you're the problem, not the diff.

🚥 Pre-merge checks | ✅ 5 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided, so there is nothing meaningful to assess.	Add a short description summarizing the roadmap, ADR, and codeowners changes.

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise, type-prefixed, and matches the roadmap and custom view markers changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Security Check	✅ Passed	Only docs and CODEOWNERS changed; no attacker-controlled input, sink, or executable code path was introduced.

---

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

[github-actions]

React Doctor found 9 issues in 7 files · 2 errors & 7 warnings · score 55 / 100 (Critical) · full project

Errors

• ❌ App.tsx:556 Missing key in list jsx-key
• ❌ App.tsx:567 Missing key in list jsx-key

7 warnings

App.tsx

• ⚠️ L2 React 19 API migration can break callers no-react19-deprecated-apis

examples/advancedFeatures.ts

• ⚠️ L115 unused-export

src/components/MapView.tsx

• ⚠️ L1 React 19 API migration can break callers no-react19-deprecated-apis

src/hooks/index.ts

• ⚠️ L0 unused-file

src/hooks/useCollectedOverlays.ts

• ⚠️ L204 Ref initializer runs on every render rerender-lazy-ref-init

src/providers.ts

• ⚠️ L11 unused-export

src/utils/enteringAnimation.ts

• ⚠️ L33 unused-export

_{Reviewed by React Doctor for commit a911e4d. See inline comments for fixes.}