Implement a Cluster with a Custom Page for a Specific Model

Context:

• I have a ProjectProject model, and each project is accessible via a slug (e.g. /my-cool-project/my-cool-project).
• I want to create a Cluster around this model so that each project acts like a cluster root.
• Inside this cluster, I need a custom page called settingssettings, so that the full path looks like:
  
  /{project-slug}/settings

  /{project-slug}/settings

1. Should this path ({project-slug}/settings{project-slug}/settings) be registered via routes.phproutes.php, or should it be part of the discoverClusterdiscoverCluster setup?
2. How do I properly link this custom page to the cluster so it respects the project context (e.g., fetching the correct project based on slug)?
3. Are there any best practices for structuring custom cluster pages like settingssettings under a model-driven path like this?
4. If I want to include additional pages in the future like /edit/edit, /analytics/analytics, etc., should those also live under the same cluster or be managed differently?

• I looked into discoverClusterdiscoverCluster usage but it seems limited in terms of defining nested pages.
• Attempted adding it directly to the routesroutes config, but it doesn't seem to automatically respect the model context unless I manually fetch the ProjectProject by slug.