chore: sync OWNERS from maintainers.yaml

[mergeraptor]

Generated by projectbluefin/.project sync-owners.yml from maintainers.yaml. Prow uses OWNERS for /approve and reviewer requests.

[github-actions]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull request changes no files, so there is nothing to approve.

[hivecommons-hive]

Routing to a maintainer — OWNERS roster change, not approving from the bot lane.

What this PR does (OWNERS:3-10 at 73cca12): adds bketelsen to approvers and removes tulilirockz. That is the list Prow consults for /approve, so it is a trust-surface edit.

What I verified:

• Generated by sync-owners.yml from projectbluefin/.project maintainers.yaml (per the file header and PR body). I cannot read that source repo from this lane, so the upstream roster change itself is unverified here.
• projectbluefin/common OWNERS on main already lists bketelsen and not tulilirockz, so this is consistent with the org-wide roster; hplip-printer-app and gutenprint-printer-app still list tulilirockz and presumably have the same sync pending.
• The same generated change is open as projectbluefin/ps-printer-app#106 (different repo, same roster — not a duplicate).

Question for @castrojo: is the maintainers.yaml change (add bketelsen, drop tulilirockz) intended for the printer-app forks? If yes, this is safe to merge as-is; the file is otherwise unchanged.

Confidence: 3/5 (needs attention) — 1 medium finding; 5 perspectives requires a human decision

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

73cca12

⚠️ Sentinel alert — maintainer review required

Hive flagged this PR (author @mergeraptor[bot], head 73cca1292415) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

• sensitive_path — changes 1 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
  • OWNERS

Hive added the sentinel-alert label. While it is present, Hive will not approve this PR, apply LGTM/approval labels, or merge it through any auto-merge lane. Remove the label once reviewed; Hive will not re-apply it unless new commits are pushed. Tune paths and behaviors under sentinel in hive.yaml or the dashboard Security tab.

[Danathar]

/approve

Same change as the closed #120: adds bketelsen and removes tulilirockz as approvers, following castrojo's projectbluefin/.project commit dc005b74 to maintainers.yaml.