/**
 * Rajgir Parent Theme
 *
 * Design System — Radius Tokens
 *
 * File:
 * assets/css/tokens/radius.css
 *
 * Responsibility:
 * - Centralized border-radius tokens.
 * - Consistent UI shape language.
 * - Component / layout radius consumption.
 *
 * This file does NOT:
 * - style individual components;
 * - define page-specific styles;
 * - contain responsive rules;
 * - contain business logic;
 * - introduce arbitrary component-level radius values.
 *
 * @package Rajgir
 */


/* ==========================================================================
   RAJGIR RADIUS TOKEN SYSTEM
   ========================================================================== */

:root {

	/* ----------------------------------------------------------------------
	   BASE RADIUS SCALE
	   ---------------------------------------------------------------------- */

	/*
	 * Approved conceptual scale:
	 *
	 * SM
	 * MD
	 * LG
	 * XL
	 * Pill
	 *
	 * Exact numerical values are governed by the approved Rajgir
	 * Design System and must not be invented at component level.
	 */


	--rajgir-radius-sm:
		var(--wp--preset--radius--sm, initial);

	--rajgir-radius-md:
		var(--wp--preset--radius--md, initial);

	--rajgir-radius-lg:
		var(--wp--preset--radius--lg, initial);

	--rajgir-radius-xl:
		var(--wp--preset--radius--xl, initial);

	--rajgir-radius-pill:
		var(--wp--preset--radius--pill, 9999px);


	/* ----------------------------------------------------------------------
	   SEMANTIC RADIUS ALIASES
	   ---------------------------------------------------------------------- */

	--rajgir-radius-control:
		var(--rajgir-radius-md);

	--rajgir-radius-card:
		var(--rajgir-radius-lg);

	--rajgir-radius-panel:
		var(--rajgir-radius-lg);

	--rajgir-radius-modal:
		var(--rajgir-radius-xl);

	--rajgir-radius-badge:
		var(--rajgir-radius-pill);

	--rajgir-radius-button:
		var(--rajgir-radius-md);

	--rajgir-radius-input:
		var(--rajgir-radius-md);

	--rajgir-radius-avatar:
		var(--rajgir-radius-pill);


	/* ----------------------------------------------------------------------
	   MEDIA RADIUS
	   ---------------------------------------------------------------------- */

	--rajgir-radius-media:
		var(--rajgir-radius-lg);


	/* ----------------------------------------------------------------------
	   FULL / ZERO RADIUS
	   ---------------------------------------------------------------------- */

	--rajgir-radius-none:
		0;

	--rajgir-radius-full:
		var(--rajgir-radius-pill);

}


/* ==========================================================================
   RADIUS USAGE CONTRACT
   ========================================================================== */

/*
 * Preferred:
 *
 * border-radius:
 *     var(--rajgir-radius-card);
 *
 *
 * Do not introduce repeated arbitrary values when an approved token
 * already represents the required visual role.
 *
 * Examples of preferred semantic usage:
 *
 * Card:
 *     var(--rajgir-radius-card)
 *
 * Button:
 *     var(--rajgir-radius-button)
 *
 * Input:
 *     var(--rajgir-radius-input)
 *
 * Badge:
 *     var(--rajgir-radius-badge)
 *
 * Modal:
 *     var(--rajgir-radius-modal)
 *
 * Avatar:
 *     var(--rajgir-radius-avatar)
 */


/* ==========================================================================
   COMPONENT BOUNDARY
   ========================================================================== */

/*
 * This token file defines SHAPE VALUES only.
 *
 * It does not decide:
 *
 * - which component is visible;
 * - which component is interactive;
 * - authorization;
 * - state;
 * - business rules;
 * - page structure.
 */


/* ==========================================================================
   DESIGN SYSTEM GOVERNANCE
   ========================================================================== */

/*
 * Radius changes are centralized.
 *
 * Correct:
 *
 * Design System
 *      ↓
 * Radius Token
 *      ↓
 * Component
 *
 *
 * Incorrect:
 *
 * Component
 *      ↓
 * Random radius value
 *      ↓
 * Global visual inconsistency
 */


/* ==========================================================================
   ACCESSIBILITY / USABILITY NOTE
   ========================================================================== */

/*
 * Radius must remain subordinate to:
 *
 * - readable content;
 * - usable controls;
 * - clear focus states;
 * - responsive layout;
 * - accessibility;
 * - consistent visual hierarchy.
 *
 * Radius must not be used as a substitute for proper component
 * structure or interaction feedback.
 */