Fixissue874

[razeprasine]

Description

All content routes (/activity, /settings, /incoming, /streams/create, /streams/[id]) started with "use client", preventing them from exporting per-route metadata. Every page shared the root <title>FlowFi | Real-time Payment Streams</title> regardless of content.

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)

Related Issues

Closes #874

Changes Made

For each of the 5 affected routes, split the page into a server component (page.tsx) and a client component (*-content.tsx):

• activity/page.tsx — server component with title: "Activity | FlowFi", delegates to activity-content.tsx
• settings/page.tsx — server component with title: "Settings | FlowFi", delegates to settings-content.tsx
• incoming/page.tsx — server component with title: "Incoming Streams | FlowFi", delegates to incoming-content.tsx
• streams/create/page.tsx — server component with title: "Create Stream | FlowFi", delegates to create-stream-content.tsx
• streams/[id]/page.tsx — server component with generateMetadata returning title: "Stream #[id] | FlowFi", passes streamId as prop to stream-details-content.tsx (replacing useParams())

Testing

Test Coverage

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed

Test Steps

1. Navigate to /activity, /settings, /incoming, /streams/create, and /streams/[id]
2. Check the browser tab title or <title> tag for each — each should show a distinct title
3. Verify all interactive functionality still works (wallet connection, settings toggles, stream actions, etc.)

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published
• I have checked for breaking changes and documented them if applicable

Additional Notes

No breaking changes. All interactive logic is preserved — only the "use client" directive and metadata export were separated. Each new client component is colocated with its page for clarity.