docs: drop archived reusable-workflows sync comment

[cursor]

🤖 Generated by the Agentic Engineer (Cursor cloud instance)

Why

monorepo#2221 tracked leftover references to the archived reusable-workflows repo. The doc links in this repo already point at devantler-tech/actions; one comment still claimed the Kyverno samples were "synced via reusable-workflows".

What

Rewords that comment to say the upstream kyverno/policies samples are vendored locally and patched below.

Part of devantler-tech/monorepo#2221

  

[devantler]

🤖 Generated by the Agentic Engineer

@coderabbitai review

[coderabbitai]

The PR description image shows two dark rounded action buttons: “↗ Open in Web” and “View Automation.”

@devantler, I’ll review the changes in #111.

✅ 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]

Warning

Review limit reached

@devantler, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 23 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 1f11e669-f53b-4fe0-b2e9-c2e98b61b4da

📥 Commits

Reviewing files that changed from the base of the PR and between a743ed7 and 002ad8d.

📒 Files selected for processing (1)

• k8s/bases/infrastructure/cluster-policies/kustomization.yaml

---

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

@codex review

[devantler]

🤖 Generated by the Agentic Engineer

User evaluation at 002ad8ddf54d3f2569a866a9a2aa32f52fcdbc2d

I exercised this as a template consumer/operator rather than relying on the text diff alone:

• both ksail.yaml and ksail.prod.yaml schema-aware validations completed successfully (100 Kustomizations and 265 YAML files each);
• the shared-policy and naming contracts passed;
• local and production Kustomize overlays rendered successfully; and
• the cluster-policy bundle rendered byte-for-byte identically to main, while the five sample files are present in the repository and no matching reusable-workflows reference remains.

Result: the revised comment accurately describes the user-visible ownership model and changes no rendered resource. The draft still awaits a green review at this exact head before promotion.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Delightful!

Reviewed commit: 002ad8ddf5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".