docs: mention the Advisory Age poster badge

[zZebrahz]

Problem

Closes #47

Silo-Server/silo-server#1672 added an Advisory Age poster badge in the web app. The profiles guide still said advisory ages appear only on title pages.

Pages changed

Page	Change	Preview
Profiles, PINs, and shared devices	Section renamed to "Show advisory ages" and covers the new badge	Open

What changed on each page

Profiles, PINs, and shared devices

• Heading "Show advisory ages on title pages" is now "Show advisory ages". No page linked to the old anchor.
• New paragraph: open Settings > Card Overlays and, under Ratings & Certifications, turn on Advisory Age. Cards show the age, such as 13+, in the bottom-right corner, and titles without an advisory age show no badge.
• Says the badge doesn't depend on Show advisory age.
• The display-only sentence now covers both settings.

Left out on purpose

• That the Apple and Android apps don't show the badge yet: support is planned in Show the Advisory Age poster badge and keep it when saving badge settings silo-apple#548 and Show the Advisory Age poster badge and keep it when saving badge settings silo-android#416, so the note would go stale.
• Admin server-wide defaults: "Customize the web appearance" already covers badge defaults under Card overlays without listing individual badges, as the issue suggested.
• Settings manifest revision 13 and the older-server behaviour (the row is hidden when the server doesn't accept the badge): no other page goes to that level.

Evidence

Source reviewed, not tested on a live server or device:
silo-server 17eced443 (includes #1672, merge 19e81846): web/src/lib/overlays/registry/ratings.ts, web/src/lib/overlays/ui-constants.ts, web/src/pages/settings/CardOverlaySettings.tsx, web/src/pages/SettingsLayout.tsx, web/src/pages/settings/PlaybackSettings.tsx.

Needs a hands-on check: Nothing.

• bun run test:docs: pass 8, fail 0
• bun run build: 98 pages built, all internal links valid
• git diff --check: clean

Risks

None identified. Documentation only.

Checklist

• I read and can explain the complete diff.
• This pull request addresses one concern.

AI Disclosure

• Harness: T3 Code, running the Claude Code agent harness
• Tool(s): Claude Code
• Model(s): claude-opus-5-5
• Involvement: Fully AI-generated, human verified
• Adversarial review: n/a

Note

Document the Advisory Age card overlay badge

Renames the advisory age docs section from title-page-specific to general, and covers both display options. Explains the bottom-right 13+ badge, the missing badge when no advisory age exists, and that the Playback and Card Overlays settings work independently. Notes that profile age limits apply regardless of these settings, in profiles.md.

^{Macroscope summarized 301f6ab.}

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 98ae3384-3015-485f-96e0-cbffcbea4957

---

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

[kody-ai]

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the `@kody start-review` command at the root of your PR.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Providing Context (Files & MCPs)

Add these hints in your PR description (or a comment) to unlock deeper checks:

• Ticket / Acceptance Criteria: `Refs: ABC-123` (Linear/Jira/Asana/ClickUp/Trello) or a direct ticket link.
• Bugfix Validation: a Sentry/Datadog/Bugsnag event link (or paste the stack trace/error message).
• Endpoint Risk: mention the route (e.g., `POST /api/payments`) or controller/action name.
• Attach a repo file as context: use an explicit marker like `@file:docs/guide.mdx#L10-L50` (replace with your real path).
• API Contract Docs: include `@file:openapi.yaml` or `@file:swagger.json` when changing routes/schemas.
• Definition of Done / Standards: include `@file:DOD.md` or `@file:CONTRIBUTING.md` if your repo has them.
• Design System Source of Truth: include `@file:ui/index.ts` (replace with your DS entrypoint path).
• Feature Flags: include the flag key/name and `@file:flags.ts` / `@file:config.json` (and optionally the PostHog flag name).
• Edge/CDN Rules: link the Cloudflare rule/zone or describe the intended redirect/header behavior.
• Attach an MCP tool output: use `@mcp<provider|tool>` (replace with an installed MCP provider + tool, e.g., `@mcp<sentry|events.search>`).

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	❌

Access your configuration settings here.

[kody-ai]

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the `@kody start-review` command at the root of your PR.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Providing Context (Files & MCPs)

Add these hints in your PR description (or a comment) to unlock deeper checks:

• Ticket / Acceptance Criteria: `Refs: ABC-123` (Linear/Jira/Asana/ClickUp/Trello) or a direct ticket link.
• Bugfix Validation: a Sentry/Datadog/Bugsnag event link (or paste the stack trace/error message).
• Endpoint Risk: mention the route (e.g., `POST /api/payments`) or controller/action name.
• Attach a repo file as context: use an explicit marker like `@file:docs/guide.mdx#L10-L50` (replace with your real path).
• API Contract Docs: include `@file:openapi.yaml` or `@file:swagger.json` when changing routes/schemas.
• Definition of Done / Standards: include `@file:DOD.md` or `@file:CONTRIBUTING.md` if your repo has them.
• Design System Source of Truth: include `@file:ui/index.ts` (replace with your DS entrypoint path).
• Feature Flags: include the flag key/name and `@file:flags.ts` / `@file:config.json` (and optionally the PostHog flag name).
• Edge/CDN Rules: link the Cloudflare rule/zone or describe the intended redirect/header behavior.
• Attach an MCP tool output: use `@mcp<provider|tool>` (replace with an installed MCP provider + tool, e.g., `@mcp<sentry|events.search>`).

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	❌

Access your configuration settings here.

[github-actions]

Preview deployed: https://pr-59.siloserver-org.pages.dev

Commit	301f6ab

The alias updates after a successful build and deployment. The preview is removed when this pull request closes.