feat(repositories): declare the doggy-countdown repository

[devantler]

🤖 Generated by the Agentic Engineer

Why

A new app repository, doggy-countdown, was created for a personal project — a countdown to the day a puppy comes home. The standing rule is that GitHub configuration is managed declaratively, so a repository that exists only imperatively is drift from the moment it is created.

What

Declares the new repository in the same shape as the other private tenants: actively managed, visibility pinned private, never deletable, never archivable.

This is the adoption half of the documented bootstrap — the repo itself had to be created imperatively because the provider cannot send the org's five required custom properties on create. Everything after this is declarative.

Part of setting up the doggy-countdown tenant.

[devantler]

🤖 Generated by the Agentic Engineer

CI is green at 54f4d25e — 🧹 Validate manifests and CI - Required Checks both pass, and all three of the repo's validate commands pass locally. Requesting review.

@coderabbitai review

[coderabbitai]

@devantler: Starting the review for #122.

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds Crossplane declarations for the private, unarchived doggy-countdown repository, its authoritative issue-label configuration, and team access grants for admins and maintainers. The new resources are included in their Kustomizations. The admin policy test now expects the additional repository and corresponding generated policy and grant counts.

Possibly related PRs

• devantler-tech/.github#78: Adds the same repository, label, team grant, and Kustomization declaration pattern.
• devantler-tech/.github#79: Adds a repository-specific IssueLabels resource and Kustomization entry.
• devantler-tech/.github#103: Updates admin policy test expectations for repository grants.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly summarizes the main change: declaring the doggy-countdown repository.
Description check	✅ Passed	The description matches the changeset and explains the new repository adoption and declarative management.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[devantler]

🤖 Generated by the Agentic Engineer

Readiness at 54f4d25e — all three conditions met.

Condition	Evidence
Programmatically tested	All three commands from AGENTS.md ## Maintenance pass locally: kubectl kustomize deploy/ builds clean, tests/admin-team-policy.sh exits 0, tests/declarative-coverage.sh reports OK — 22 repositories across 4 rendered dimensions. RED proof is run 30207647011 on the previous head, which named exactly the three undeclared pairs this PR closes.
Reviewed	cr@54f4d25e — CodeRabbit summary updated 15:30:38Z, after the authenticated request, naming this head, "No actionable comments were generated". Zero threads, zero body findings.
Tried and evaluated	See below.

Evaluation. These manifests reconcile on-cluster through Crossplane, so there is no local runtime surface to exercise; what is observable pre-apply is the rendered output, and that is what I checked rather than reasoning from the source. Rendering deploy/ and reading back the doggy-countdown IssueLabels gives exactly the 22 canonical org labels — the empty extras list correctly receives the shared patch, matching world-at-ruin's count. The repository's three live labels (blocked, next, released) are all inside that canonical set, so making the set authoritative strips nothing in use. Both TeamRepository grants render with the intended admin / maintain permissions.

Access impact: both admins and maintainers currently contain only devantler, so no additional person gains access to this private repository.

One judgement call worth naming: the guard demanded a team-maintainers entry, and the two comparable private repos (wedding-app, ascoachingogvaner) are exempted from that dimension rather than exempt by policy — their exemptions are recorded as gaps to close. I therefore declared the grant rather than adding a fourth exemption. Happy to swap it for an exemption if you would rather private app repos stay admins-only.