feat: add profile lexicon

[Kzoeps]

Summary

Add profile lexicon for Hypercert account profiles with support for display name, description, pronouns, website, avatar, banner, and self-labels.

Note

This profile lexicon is adapted from Bluesky's actor.profile with some fields removed that aren't relevant to hypercerts profiles.

Edit by Sharfy: The removed fields are joinedViaStarterPack and pinnedPost

Summary by CodeRabbit

• New Features
  • Added Hypercert account profile support with customizable fields for display name, description, pronouns, website, avatar, and banner.

[changeset-bot]

🦋 Changeset detected

Latest commit: 6752cad

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@hypercerts-org/lexicon	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request introduces a new profile lexicon for Hypercert account profiles, including changeset documentation, schema definitions, and a new lexicon file. The profile supports displayName, description, pronouns, website, avatar, banner, and createdAt fields.

Changes

Cohort / File(s)	Summary
Profile Lexicon Definition lexicons/app/certified/profile.json	New lexicon file defining the app.certified.profile record schema with fields for displayName, description, pronouns, website, avatar, banner, and createdAt timestamps.
Documentation and Release Metadata SCHEMAS.md, .changeset/add-profile-lexicon.md	Added schema documentation block describing the new profile lexicon and changeset file declaring a minor version bump for the lexicon package.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• auto-generate lexicon schema Markdown tables #97: Auto-generation of SCHEMAS.md from lexicon files; this PR's manual SCHEMAS.md updates directly relate to that automation work.

Suggested reviewers

• s-adamantine
• aspiers

Poem

🐰 A profile so neat, with a lexicon flair,
Names, avatars, websites with care,
Banners and badges, pronouns so true,
The rabbit declares: "Profiles are new!" ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Lexicons Styleguide Compliance	⚠️ Warning	The profile.json lexicon violates the style guide by missing descriptions for three properties: displayName, website, and createdAt.	Add description fields to displayName, website, and createdAt properties to comply with the AT Protocol style guide requirements.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat: add profile lexicon' accurately describes the main change—adding a new profile lexicon for Hypercert account profiles with support for multiple fields.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Lexicon Documentation Sync	✅ Passed	The pull request properly synchronizes the new app.certified.profile lexicon with required documentation in lexicons and SCHEMAS.md.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch profile

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@lexicons/app/certified/profile.json`:
- Around line 11-46: Add an optional "labels" property to the profile schema's
"properties" object: define "labels" as a union with a ref to
"com.atproto.label.defs#selfLabels" and include a brief description (e.g., "User
self-assigned labels"), ensuring it's optional (no required entry) and follows
the same schema style as existing "avatar"/"banner" union fields so tools
consuming profile.json will recognize self-labels.

[aspiers]

Thanks!