# Registry Consumer Changelog

A running list of changes to the Aavya registry that affect **downstream projects that already
consume it**. This is the migration record the `aavya-registry` Claude Code skill will check a
consuming repo against (see [consuming-the-registry.md](./consuming-the-registry.md)).

**How to read it** — each entry is tagged:

- **🔴 Adopt now** — consumer action required; something breaks or silently degrades until you do it.
- **⚪ Informational** — portal-side improvement; no action needed in consuming projects.

Newest first. Every registry PR that changes the manifest, item names, dependencies, or the
install/consume contract must append an entry here.

> **Planned:** serve this file as a GET endpoint (like `/api/registry/markdown`) and have the
> skill fetch it to flag needed migrations in a consuming repo automatically.

---

## 2026-06-17 — `@aavya` namespace for registry dependencies · 🔴 Adopt now

Branded blocks and layouts now declare their dependencies with the `@aavya/*` namespace
(e.g. `@aavya/ui-button`, `@aavya/ui-avatar`) instead of bare shadcn names.

**Why it matters:** bare dependency names resolve against the *default* shadcn registry, so a
consumer installing a branded block (e.g. `profile-dropdown`, `aavya-header`) would get **stock
shadcn primitives inside a branded block** instead of the Aavya versions.

**What to do:** add the namespace to your project's `components.json`, then reinstall affected
blocks:

```json
"registries": { "@aavya": "https://brand.aavya.com/r/{name}.json" }
```

Full setup: [consuming-the-registry.md](./consuming-the-registry.md).

---

## 2026-06-17 — Registry credibility fixes · ⚪ Informational

- **Manifest `homepage`** corrected from `http://localhost:3000` to `https://brand.aavya.com`.
  Only matters if your tooling reads `homepage` from the manifest; no install change.
- **Usage snippets** on item pages and the markdown export now use the correct import
  (named vs default) with no file extension. If you copied an old snippet, re-copy — but this
  doesn't change any installed component.
- **Registry index** now shows each item's `status` (ga/beta/alpha) and `version` as badges.
  Portal-only; no consumer impact.
