fix: world-at-ruin labels are stuck Observe-only, so its issues cannot be triaged

[devantler]

🤖 Generated by the Daily AI Engineer

Evidence

world-at-ruin is the only one of 21 repositories whose IssueLabels CR is still
managementPolicies: [Observe]. Every other repo carries the full
[Observe, Create, Update, LateInitialize] set, so only world-at-ruin never has the canonical
taxonomy applied.

Measured on the live cluster (admin@prod, read-only):

• issuelabels/world-at-ruin — Synced=True, Ready=True, spec.managementPolicies: ["Observe"]
• observed labels: 5 — blocked, enhancement, next, released, roadmap
• issuelabels/ksail (full-policy peer): 35 observed labels
• the shared patch in deploy/labels/kustomization.yaml declares a 22-label canonical taxonomy
  and targets every IssueLabels, so world-at-ruin already declares all 22 — it just never
  applies them

Problem

World at Ruin is a first-class product, but its issues cannot be triaged honestly: it has no bug,
documentation, refactor, performance, security, needs triage or duplicate label. #124
("cave.tscn is unreferenced — delete it or mark it a preview harness") is a cleanup task with no
label that fits, so it sits untriaged — not an oversight, but the only available outcome.

The adoption gate is met

The CR's own comment states the promotion condition:

Promote to the full policy set (all except Delete) once Synced/Ready shows the observed state
matches the declared one.

Synced=True / Ready=True on the live resource satisfies exactly that. The repo was bootstrapped
2026-07-16 with the deliberate Observe-first stance (per the #43–#46 convention); the promotion step
was simply never taken afterwards.

Proposed change

Promote deploy/labels/world-at-ruin.yaml to [Observe, Create, Update, LateInitialize], matching
all 20 peers. Purely additive: all five existing labels (blocked, enhancement, next,
released, roadmap) are already members of the canonical 22, and no Delete policy is claimed,
so nothing is removed or recoloured.

Acceptance criteria

• deploy/labels/world-at-ruin.yaml uses the full policy set; the Observe-only caveat comment
  is replaced with the adoption evidence.
• kubectl kustomize deploy/ still builds and the repo's tests pass.
• After reconcile, world-at-ruin exposes the canonical taxonomy and #124 can be labelled.

Size: XS. Part of #56.

[coderabbitai]

🔗 Related PRs

#78 - feat(repositories): declare provider-upjet-unifi (net-new Library repo) [merged]
#79 - feat(labels): bring devantler-tech/monorepo under declarative IssueLabels management [merged]
#82 - feat: declare the devantler-tech/aws config-tenant repo [merged]
#88 - feat: archived-repo pattern + reusable-workflows archival groundwork [merged]
#100 - docs(repositories): correct kyverno bootstrap contract [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[devantler]

🤖 Generated by the Daily AI Engineer

Post-merge verification — it works in production

Merged as cba05dc48; Release cut v1.20.1 and CD published the signed artifact, which the
github-config tenant reconciled.

Observed, not inferred — world-at-ruin live labels went 5 → 22:

automation, blocked, breaking change, bug, documentation, duplicate, enhancement,
good first issue, help wanted, needs investigation, needs triage, next, off topic,
performance, question, refactor, released, repo-assist, roadmap, security, spam, wontfix

All five pre-existing labels (blocked, enhancement, next, released, roadmap) survived, so
the superset condition held and IssueLabels' authoritative delete behaviour removed nothing — the
hazard AGENTS.md warns about did not fire.

The outcome that motivated this: #124 was untriaged because no label fitted a cleanup task. It
is now labelled refactor. World at Ruin's issues can be triaged like every other product's.