📌 Description
src/app/page.tsx exports no metadata at all (unlike dashboard/page.tsx, anchors/page.tsx, anchors/[id]/page.tsx, settlements/page.tsx, and settlements/[id]/page.tsx, which all define a Metadata object with title/description), so the homepage inherits only the generic root metadata from src/app/layout.tsx with no page-specific Open Graph tags for link previews when the URL is shared.
🧩 Requirements and context
- Add a
Metadata export to src/app/page.tsx with a page-specific title/description, consistent in style with the other route metadata exports.
- Add basic Open Graph fields (
openGraph.title, openGraph.description) using Next.js's Metadata type.
- No visual/runtime change to the rendered page content.
🛠️ Suggested execution
- Update
src/app/page.tsx to export a Metadata object following the pattern already used in src/app/dashboard/page.tsx.
✅ Acceptance criteria
🔒 Security notes
No new attack surface; a metadata/SEO documentation-style task.
📋 Guidelines
- Minimum 95% test coverage
- Clear documentation
- Timeframe: 96 hours
📌 Description
src/app/page.tsxexports nometadataat all (unlikedashboard/page.tsx,anchors/page.tsx,anchors/[id]/page.tsx,settlements/page.tsx, andsettlements/[id]/page.tsx, which all define aMetadataobject withtitle/description), so the homepage inherits only the generic rootmetadatafromsrc/app/layout.tsxwith no page-specific Open Graph tags for link previews when the URL is shared.🧩 Requirements and context
Metadataexport tosrc/app/page.tsxwith a page-specifictitle/description, consistent in style with the other route metadata exports.openGraph.title,openGraph.description) using Next.js'sMetadatatype.🛠️ Suggested execution
src/app/page.tsxto export aMetadataobject following the pattern already used insrc/app/dashboard/page.tsx.✅ Acceptance criteria
🔒 Security notes
No new attack surface; a metadata/SEO documentation-style task.
📋 Guidelines