Migrate repository context to rabbit.ci and upgrade Worker

[fqjony]

Summary

• Replace the legacy dev.kit repository context with the committed Rabbit CI resolution in .rabbit/repo.yaml.
• Refresh Rabbit CI and Worker-config documentation around the new ownership boundary.
• Upgrade the base Worker image from 0.48.0 to 0.52.0.

Scope

• Supersedes Dependabot PR Bump usabilitydynamics/udx-worker from 0.48.0 to 0.51.0 #76, whose 0.51.0 update is now behind the latest Worker release.
• Does not change tenant lifecycle manifests, environment configuration, or secret values.

Validation

• rabbit.ci
• yq e '.' .rabbit/repo.yaml
• git diff --check
• make test was attempted but could not run because the local Docker daemon is unavailable.

[Copilot]

Pull request overview

This PR migrates Rabbit-facing repository context from the legacy dev.kit generated .rabbit/context.yaml to a committed Rabbit CI resolution file (.rabbit/repo.yaml), refreshes the related documentation, and upgrades the base Worker image used by this repo.

Changes:

• Upgrade usabilitydynamics/udx-worker base image from 0.48.0 to 0.52.0.
• Replace dev.kit-generated repo context with Rabbit CI’s committed .rabbit/repo.yaml (and remove .rabbit/context.yaml).
• Update docs to clarify the ownership boundary and when to run rabbit.ci.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
README.md	Updates Rabbit CI section to point at .rabbit/repo.yaml and clarify regeneration triggers.
docs/worker-config.md	Clarifies worker.yaml is an image-runtime contract and not part of Rabbit CI resolution.
Dockerfile	Bumps base Worker image tag to 0.52.0.
.rabbit/repo.yaml	Adds committed Rabbit CI repo resolution snapshot.
.rabbit/README.md	Reworks Rabbit CI docs to describe repo.yaml resolution boundary and entry points.
.rabbit/context.yaml	Removes legacy dev.kit generated repo context.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

Suppressed comments (3)

.rabbit/repo.yaml:10

• branches includes the current feature branch (chore/rabbit-ci-worker-0.52.0) with empty rules. If this branch is deleted after merge (a common cleanup step), the committed resolution will become stale immediately. Consider configuring rabbit.ci to emit only long-lived/protected branches (or otherwise avoid committing transient branch entries) so repo.yaml remains stable across PR branch churn.

branches:
  - name: chore/rabbit-ci-worker-0.52.0
    rules: {}
  - name: latest

README.md:123

• The regeneration trigger list omits changes to configured secret/variable names, even though .rabbit/repo.yaml explicitly records those names. If secrets/variables are added/renamed, following this guidance would leave the committed resolution stale.

Run `rabbit.ci` after changing a GitHub workflow, branch protection, or GitHub Environment, then review and commit the generated resolution with the source change. See [`.rabbit/README.md`](.rabbit/README.md) for the resolution boundary and delivery entry points.

.rabbit/README.md:14

• This list of when to regenerate the resolution omits changes to configured secret/variable names, but repo.yaml includes those names under configuration. If secrets/variables are added/renamed, the guidance here would produce a stale committed resolution.

Regenerate the resolution after changing a GitHub workflow, branch protection,
or GitHub Environment:

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

Suppressed comments (1)

.rabbit/repo.yaml:10

• branches: includes the current feature branch (chore/rabbit-ci-worker-0.52.0) with empty rules. If this PR branch is deleted after merge (typical), the committed resolution will immediately become stale and create noisy future diffs. Prefer committing a resolution generated from the default branch so branches only tracks long-lived/protected branches.

branches:
  - name: chore/rabbit-ci-worker-0.52.0
    rules: {}
  - name: latest