Adopt the cloudflare and data-product-controller repositories declaratively #306

🤖 Generated by the Agentic Engineer

Evidence

On 2026-09-27 the cloudflare and data-product-controller repositories are live and public but absent from every deploy/ dimension: no Repository, IssueLabels, team grants or RepositoryPermissions. Live, neither has any team: maintainers and admins hold nothing on them, unlike every other active repository.

Audience and problem

Both are portfolio products. Without the declarations they miss the org's merge, signoff and Actions-pinning settings, carry no canonical labels, and are reachable only by individual access.

Hypothesis and success signal

Adopting both Observe-first, the way world-at-ruin was adopted, brings them under the same governance as the rest. Success: both appear in every rendered dimension and the live coverage check passes; the drift check clears once #308 promotes them.

Acceptance criteria

• Each repository has a Repository adopted Observe-first with its live settings, an IssueLabels that is a superset of its live labels, admins and maintainers grants, and RepositoryPermissions.
• tests/declarative-coverage.sh passes with no new exemption.
• After reconciliation, the live coverage check passes. The drift check passing for both repositories needs the Observe-only resources promoted, which is tracked on Promote the cloudflare and data-product-controller repositories to managed settings #308.

Size

M — two adoptions, each read against its live settings and labels first.