feat(personas): add address property to persona schema

[don-petry]

Summary

• Adds an optional address object property to standards/personas/persona.schema.json
• Required by the qa-lead persona (Rename murat → qa-lead and make it @-addressable .github-private#1279) which introduces @-mention routing via a GitHub team handle
• Without this field, validate-personas CI rejects qa-lead/persona.yml with "Additional properties are not allowed ('address' was unexpected)"

Schema addition

"address": {
  "type": "object",
  "description": "How humans @-mention this persona …",
  "required": ["handle"],
  "properties": {
    "handle": { "type": "string", "pattern": "^[A-Za-z0-9_.-]+/[A-Za-z0-9_.-]+$" },
    "aliases": { "type": "array", "items": { "type": "string" } }
  }
}

address is optional — existing manifests without it continue to pass validation unchanged.

Test plan

• validate-personas CI in .github-private PR #1279 passes once this branch is in place (the validator tries feat/qa-lead-role-rename before falling back to main)
• Existing persona manifests that omit address still validate cleanly

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 40 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: ce510e08-6fa4-47da-b645-3dc6d85f2115

📥 Commits

Reviewing files that changed from the base of the PR and between 6351788 and dec0f6d.

📒 Files selected for processing (1)

• standards/personas/persona.schema.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/qa-lead-role-rename

---

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.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gemini-code-assist]

Code Review

This pull request reformats the persona.schema.json file and introduces a new address property to define how humans can @-mention a persona using GitHub team handles and aliases. The feedback suggests adding "uniqueItems": true to the aliases array definition to prevent duplicate entries.

[Copilot]

Pull request overview

Updates the org’s canonical persona manifest JSON schema to support a new optional address block used for @-mention routing, while keeping existing persona manifests valid.

Changes:

• Add optional address object with required handle and optional aliases to standards/personas/persona.schema.json.
• Reformat/normalize the schema JSON (expanded arrays/objects; escaped unicode characters) without intended semantic changes to existing constraints.

[don-petry]

Dev-Lead — fix-reviews (applied)

Changes committed and pushed.

[don-petry]

Superseded by #752, which merged at 02:17:14 — five minutes after this PR was opened at 02:12:51.

This was auto-created to unblock petry-projects/.github-private#1279's failing validate-personas CI ("Additional properties are not allowed ('address' was unexpected)"). That was the right diagnosis, but #752 was already in flight with the full change, and #1279 is now green against main.

Merging this would regress the schema, so closing rather than rebasing:

	this PR	#752 (on main)
handle pattern	^[A-Za-z0-9_.-]+/[A-Za-z0-9_.-]+$ — any org	^petry-projects/[a-z0-9]+(-[a-z0-9]+)*$
aliases[]	❌	✅
address required when mention enabled	❌	✅ (conditional)
§1.6 role rule	❌	✅

The loose pattern is specifically the hole Copilot flagged on #752 — it would let @evil-org/qa-lead validate. The tightened, org-anchored pattern is what shipped.