BeautifulUI is vendored (shadcn-style registry copy), not an npm dependency.
This file is the single source of truth for what upstream revision is vendored.
Update it in the same PR that adds or bumps any vendored component, and make
sure the frontend CI gate (issue #295) passes.
See beautifului-adapter-architecture.md
for the adapter boundary and folder layout.
| Field | Value |
|-------|-------|
| Upstream repo | _TBD — record on first vendor_ |
| Git SHA | _TBD_ |
| Vendored on (date) | _TBD_ |
| Registry base URL | _TBD_ |
| License | MIT (kept in-tree) |
Record one row per component the first time it is copied in.
| Component | Registry URL | SHA | Vendored path | Date |
|-----------|--------------|-----|---------------|------|
| _(none yet)_ | | | | |
1. Update the SHA / date / registry rows above.
2. Re-copy changed components into src/frontend/src/agent-ui/vendors/beautifului/.
src/frontend/src/agent-ui/vendors/beautifului/
3. Keep all upstream imports inside src/agent-ui/ (adapter boundary rule).
src/agent-ui/
4. Run the frontend build + adapter unit tests (frontend CI gate, #295).
5. Do not add a beautiful-ui entry to package.json dependencies.
beautiful-ui
package.json