Fixissue872 - #934

Description

The project had no robots.txt or sitemap.xml, so crawlers received no crawl directives and no sitemap for public routes. This left search engines unable to discover or properly index the site.

Type of Change

• ✨ New feature (non-breaking change which adds functionality)

Related Issues

Closes #872

Changes Made

• frontend/src/app/robots.ts: New Next.js robots route — allows all crawlers (userAgent: "*", allow: "/") and points to https://flowfi.app/sitemap.xml
• frontend/src/app/sitemap.ts: New Next.js sitemap route — lists 6 public routes (/, /dashboard, /streams/create, /activity, /incoming, /settings) with appropriate priority and change frequency

Testing

Test Coverage

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

Test Steps

1. Run npm run build in the frontend
2. Start the production server
3. Verify http://localhost:3000/robots.txt returns the robots policy with a sitemap URL
4. Verify http://localhost:3000/sitemap.xml returns valid XML listing all public routes

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

Dynamic routes like /streams/[id] are intentionally omitted from the static sitemap (standard practice). No existing files were modified — only two new files were created.