chore(tokens): sync Figma tokens

.changeset/accordion-single-mode.md

@@ -0,0 +1,5 @@
+---
+"@sipe-team/accordion": minor
+---
+
+Add single/multiple open mode support to Accordion component. When `type="single"` is set on `Accordion.Root`, only one item can be open at a time. Also supports controlled mode via `value` and `onValueChange` props.

.changeset/add-card-ghost-variant.md

@@ -0,0 +1,5 @@
+---
+"@sipe-team/card": minor
+---
+
+Add ghost variant to Card component with transparent background, no border, and no padding

.changeset/beige-cows-know.md

@@ -0,0 +1,5 @@
+---
+"@sipe-team/tooltip": major
+---
+
+Refactor tooltip API: replace trigger prop with disableHoverListener, add controlled mode (open/onOpen/onClose), improve WCAG compliance, and fix animation on mount

.changeset/chip-normalize-package-json.md

@@ -0,0 +1,5 @@
+---
+"@sipe-team/chip": patch
+---
+
+Normalize `@sipe-team/chip` package.json to match the canonical structure used across other `@sipe-team/*` packages. Adds `publishConfig` with `access`/`registry`/`exports`, moves source `exports` to `./src/index.ts`, adds `type: "module"`, `repository`, `sideEffects: ["**/*.css"]`, and aligns scripts/dependencies. Consumer module resolution now uses the `import`/`require` branches declared under `publishConfig.exports`.

.changeset/package-json-divergence-cleanup.md

@@ -0,0 +1,14 @@
+---
+"@sipe-team/accordion": patch
+"@sipe-team/avatar": patch
+"@sipe-team/checkbox": patch
+"@sipe-team/divider": patch
+"@sipe-team/plugin-figma-codegen": patch
+"@sipe-team/radio": patch
+"@sipe-team/side": patch
+"@sipe-team/switch": patch
+"@sipe-team/theme": patch
+"@sipe-team/typography": patch
+---
+
+Align existing `@sipe-team/*` `package.json` metadata with the canonical shape. Adds `publishConfig.registry` to divider/radio/side/switch, unifies `lint` scripts on `pnpm exec biome lint`, normalizes `workspace:^` → `workspace:*` in avatar/switch/typography, and moves accordion/theme/checkbox direct `react`, `@types/react`, `react-dom`, and `@vanilla-extract/css` specifiers to the pnpm catalog.

.changeset/semantic-tokens-foundation.md

@@ -0,0 +1,30 @@
+---
+"@sipe-team/tokens": major
+"@sipe-team/button": patch
+---
+
+redesign token contract structure with semantic color, spacing, and radius hierarchy
+
+## Breaking Changes
+
+### `vars` path changes
+
+| Token | Before | After |
+|-------|--------|-------|
+| color | `vars.color.primary` `vars.color.background` `vars.color.text` | `vars.color.accent.{default\|hover\|subtle}` `vars.color.background.{base\|subtle\|muted}` `vars.color.foreground.{default\|subtle\|muted\|onAccent}` `vars.color.border.{default\|strong\|focus}` `vars.color.status.{success\|warning\|danger\|info}.{foreground\|background\|border}` |
+| spacing | `vars.spacing.{xs\|sm\|md\|lg\|xl}` | `vars.spacing.component.{xs\|sm\|md\|lg\|xl}` `vars.spacing.layout.{sm\|md\|lg\|xl}` |
+| radius | `vars.radius.{none\|sm\|md\|lg\|xl\|full}` | `vars.radius.component.{sm\|md\|lg\|xl\|full}` `vars.radius.layout.{sm\|md\|lg}` |
+
+`vars.color.gradient` and `vars.color.secondary` have been removed.
+
+### `defaultTheme` export removed
+
+`defaultTheme` is no longer exported from `@sipe-team/tokens`. Theme variables are now applied automatically via `createGlobalTheme` on `:root`. Remove any explicit `defaultTheme` import or usage.
+
+### Default color mode changed to dark
+
+The `:root` theme now defaults to `mode: 'dark'` (previously `mode: 'light'`). If your app relied on the light-mode defaults from `:root`, you will need to apply a `[data-theme]` attribute or supply your own light-mode overrides.
+
+### Deprecated named exports
+
+`opacity`, `zIndex`, `borderWidth`, `borderStyle`, `shadows`, `breakpoints`, `breakpointQuery`, `responsiveStyle`, `grid` and their associated types are deprecated and will be removed in a future release.

.changeset/spicy-wasps-clap.md

@@ -0,0 +1,20 @@
+---
+"@sipe-team/accordion": patch
+"@sipe-team/checkbox": patch
+"@sipe-team/skeleton": patch
+"@sipe-team/divider": patch
+"@sipe-team/tooltip": patch
+"@sipe-team/button": patch
+"@sipe-team/switch": patch
+"@sipe-team/badge": patch
+"@sipe-team/input": patch
+"@sipe-team/radio": patch
+"@sipe-team/reset": patch
+"@sipe-team/card": patch
+"@sipe-team/flex": patch
+"@sipe-team/grid": patch
+"@sipe-team/side": patch
+"@sipe-team/typography": patch
+---
+
+Preserve CSS imports in `sideEffects` so consumer bundlers don't tree-shake `./styles.css`.

.changeset/wet-pants-train.md

@@ -0,0 +1,5 @@
+---
+"@sipe-team/tooltip": patch
+---
+
+improve accessibility and refactor styles for Tooltip

.github/CONTRIBUTING.md

@@ -100,36 +100,36 @@ Before proposing changes, please **open an issue** to discuss the bug or feature
 ### Create a Pull Request
 
 1. **Create a Branch**  
-   Follow the branch naming convention: `<CATEGORY>/<ISSUENUMBER>-<SUBJECT>` (`ISSUENUMBER` is optional)
+   Follow the branch naming convention: `<CATEGORY>/<SUBJECT>-<USERNAME>`
+   - `USERNAME` is required (at least one hyphen must be present)
    ```bash
-   git checkout -b your-branch
+   git checkout -b feature/button-john
     ```
 
-    | **Category** | **Description**                                     |
-    |--------------|-----------------------------------------------------|
-    | **feat**     | Developing a new feature                            |
-    | **fix**      | Fixing a bug                                        |
-    | **hotfix**   | Emergency fixes for immediate release               |
-    | **chore**    | Maintenance tasks or minor updates                  |
-    | **refactor** | Code refactoring without functional changes         |
-    | **release**  | Preparing for a new release version                 |
-    | **test**     | Writing or modifying test cases                     |
-    | **docs**     | Documentation updates or additions                  |
-    | **ci**       | CI/CD pipeline updates                              |
-    | **build**    | Changes to the build system or dependencies         |
+    | **Category**  | **Description**                                     |
+    |---------------|-----------------------------------------------------|
+    | **feature**   | Developing a new feature                            |
+    | **fix**       | Fixing a bug                                        |
+    | **docs**      | Documentation updates or additions                  |
+    | **style**     | Code style changes (formatting, no logic change)    |
+    | **refactor**  | Code refactoring without functional changes         |
+    | **test**      | Writing or modifying test cases                     |
+    | **deploy**    | Deployment-related changes                          |
+    | **chore**     | Maintenance tasks or minor updates                  |
+    | **settings**  | Configuration or settings changes                   |
 
 2. **Commit Changes**  
    Write meaningful commit messages using the [Conventional Commits](https://www.conventionalcommits.org/) format:
    ```bash
    git commit -m "<type>(<scope>): <subject>"
    ```
-   We recommend following the Conventional Commits standard for clear and consistent commit messages. Below is the suggested structure:
- 
+   We follow the [Conventional Commits](https://www.conventionalcommits.org/) standard with [`@commitlint/config-conventional`](https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional):
+
    | Element      | Requirement  | Description                                                                                                                                                                    |
    |--------------|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-   | `<type>`     | **Required** | Describes the purpose of the commit. Examples: `feat`, `fix`, `docs`, `style`, `refactor`, `test`                                                                              |
-   | `<scope>`    | **Optional** | Specifies the affected module, file, or functionality. Limited to **20 characters** (e.g., `auth`, `header`).                                                                  |
-   | `<subject>`  | **Required** | A concise summary of the changes<br/> - Starts with a lowercase letter<br/> - Avoid ending with a period (.)<br/> - Limited to **50 characters**<br/> - Must contain only English characters, numbers, and basic punctuation (!@#$%^&*(),.?":{}|<>_-)<br/> - Cannot be empty |
+   | `<type>`     | **Required** | Describes the purpose of the commit: `build`, `chore`, `ci`, `docs`, `feat`, `fix`, `perf`, `refactor`, `revert`, `style`, `test`                                             |
+   | `<scope>`    | **Optional** | Specifies the affected module, file, or functionality (e.g., `auth`, `header`).                                                                                                |
+   | `<subject>`  | **Required** | A concise summary of the changes<br/> - Starts with a lowercase letter<br/> - Avoid ending with a period (.)<br/> - Cannot be empty                                           |