🤖 Generated by the Daily AI Engineer
Evidence
The Platform tenant contract says tenants own their gethomepage.dev/* dashboard annotations and that Homepage discovers them from each tenant's HTTPRoute. The scaffold's deploy/httproute.yaml currently carries none of those annotations, so a tenant can follow the documented adoption path, reconcile successfully, and remain absent from the platform's main dashboard.
Audience and impact
Every new tenant adopter inherits this gap. They must already know the platform-specific Homepage convention and reproduce seven coordinated annotations by hand; missing the href or pod selector also loses the direct link or workload health indicator.
Expected behavior
A freshly adopted scaffold should publish a safe, generic dashboard tile by default. The one-shot rename helper should repoint its name, URL, and pod selector together with the existing resource placeholders, while tenant-owned presentation fields remain easy to customize.
Acceptance criteria
- The scaffold
HTTPRoute carries enabled, name, description, group, icon, href, and pod-selector Homepage annotations.
- The existing rename helper rewrites the app identity consistently in the tile name, production URL, and pod selector without corrupting annotation keys or custom presentation values.
- The onboarding contract covers both the unrenamed annotation shape and the renamed result, and rejects mutations that remove the URL or pod selector.
- The unrenamed and renamed
deploy/ manifests still render successfully.
- The README adoption guidance tells tenants which presentation fields to tailor.
Size
Small: one scaffold manifest, the existing onboarding contract, and adoption documentation.
Part of #6
Evidence
The Platform tenant contract says tenants own their
gethomepage.dev/*dashboard annotations and that Homepage discovers them from each tenant'sHTTPRoute. The scaffold'sdeploy/httproute.yamlcurrently carries none of those annotations, so a tenant can follow the documented adoption path, reconcile successfully, and remain absent from the platform's main dashboard.Audience and impact
Every new tenant adopter inherits this gap. They must already know the platform-specific Homepage convention and reproduce seven coordinated annotations by hand; missing the
hrefor pod selector also loses the direct link or workload health indicator.Expected behavior
A freshly adopted scaffold should publish a safe, generic dashboard tile by default. The one-shot rename helper should repoint its name, URL, and pod selector together with the existing resource placeholders, while tenant-owned presentation fields remain easy to customize.
Acceptance criteria
HTTPRoutecarries enabled, name, description, group, icon, href, and pod-selector Homepage annotations.deploy/manifests still render successfully.Size
Small: one scaffold manifest, the existing onboarding contract, and adoption documentation.
Part of #6