chore: update favicon to ibl.ai branding

[mamigot]

Summary

Replaces the default favicon with the icon set served by ibl.ai.

• Updated public/favicon.ico and public/favicon.png with ibl.ai's assets
• Added the rest of ibl.ai's icon set: icon.svg, favicon-16x16.png, favicon-32x32.png, apple-touch-icon.png
• Wired the full set into the default metadata in app/layout.tsx

Per-tenant custom favicon overrides are preserved — the full default set is only emitted when the resolved favicon is the default /favicon.ico; a tenant-provided favicon still renders as a single icon.

Notes

No e2e coverage change: this is a cosmetic metadata swap with no new user-facing journey.

🤖 Generated with Claude Code

[mamigot]

Claude finished @mamigot's task —— View job

---

E2E Coverage Review ✅

Analysis Complete:

Todo List:

• Dismiss any stale REQUEST_CHANGES reviews from myself (no gh access, proceeding)
• Identify what changed (check for new page.tsx files)
• Run mechanical coverage check (manual review due to permissions)
• Read current coverage state
• Apply decision logic and post GitHub review

Coverage Analysis:

• Changed files: Only app/layout.tsx and favicon assets (public/*.png, public/*.ico, public/*.svg)
• No new routes detected - This PR only modifies metadata generation and favicon handling
• No page.tsx files added or modified - All changes are cosmetic/infrastructure
• Current coverage: 222/222 checkpoints (100%), 31 journeys

Decision: CASE E - No new page.tsx files and no coverage regression

Since this PR only updates favicon handling and metadata generation without introducing new user-facing routes, no e2e coverage changes are required. The changes are purely cosmetic as stated in the PR description.

Review Result: APPROVE

This PR introduces no new routes and requires no e2e coverage updates. The favicon/metadata changes are infrastructure-only and don't affect user journeys.

Note: Unable to post formal GitHub review due to gh command access restrictions. Manual review recommendation: APPROVE - no coverage issues detected.

[mamigot]

Claude finished @mamigot's task —— View job

---

E2E Coverage Review ✅

Analysis Complete:

Todo List:

• Dismiss any stale REQUEST_CHANGES reviews from myself (no gh access, proceeding)
• Identify what changed (check for new page.tsx files)
• Run mechanical coverage check (manual review due to permissions)
• Read current coverage state
• Apply decision logic and post GitHub review

Coverage Analysis:

• Changed files: Only app/layout.tsx and favicon assets (public/*.png, public/*.ico, public/*.svg)
• No new routes detected - This PR only modifies metadata generation and favicon handling
• No page.tsx files added or modified - All changes are cosmetic/infrastructure
• Current coverage: 222/222 checkpoints (100%), 31 journeys

Decision: CASE E - No new page.tsx files and no coverage regression

Since this PR only updates favicon handling and metadata generation without introducing new user-facing routes, no e2e coverage changes are required. The changes are purely cosmetic as stated in the PR description.

Review Result: APPROVE

This PR introduces no new routes and requires no e2e coverage updates. The favicon/metadata changes are infrastructure-only and don't affect user journeys.

Note: Unable to post formal GitHub review due to gh command access restrictions. Manual review recommendation: APPROVE - no coverage issues detected.

---