chore: route reviews to maintainer team

[TabishB]

What changed

• route repository-wide code ownership to @Fission-AI/openspec-maintainers
• add Clay Good to the documented core maintainers

Why

Review requests currently route only to Tabish. The new visible maintainer team has Maintain access to OpenSpec and is configured to auto-assign one reviewer using load balancing.

Impact

Once merged, new ready-for-review pull requests will route to an available maintainer instead of always requesting Tabish. The existing one-approval policy remains unchanged.

Validation

• git diff --check
• verified the team is visible
• verified the team has Maintain repository access
• verified auto-assignment is enabled for one load-balanced reviewer

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 4e4cdeb9-5f1c-429e-9d24-c8ed03a5919c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/maintainer-approvals

---

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