fix: cyrillic fonts, dev certs, page head, and ru-text typography (#67)

🤖 PR generated for branch `fix/cyrillic-fonts-dev-certs-and-page-head`.

### Changes Summary
- **Fonts**: Add Cyrillic glyph subsets for Lato, EB Garamond, and Fira
Code.
- **Dev**: Support remote Root CA and encrypted dev CA key in
`.env.dev`.
- **UI & Kits**: Add size variant to `Breadcrumbs` component and enlarge
`PageHead` breadcrumbs with tuned collapse scroll threshold.
- **ESLint**: Add `no-hanging-particles` i18n & markdown typography rule
with auto-fixer.
- **Content & i18n**: Apply `ru-text` editorial and typography polish
(em dashes, number ranges, «ё» restoration, non-breaking spaces) across
`services/www` and `services/docs`.

services/docs/content/en/quetza/concepts/_index.md

@@ -3,7 +3,7 @@ title: Concepts
 weight: 4
 ---
 
-**Quetza** concepts explain the _Why_ and _How_ behind the framework's design. These documents cover the underlying philosophy and architectural decisions.
+**Quetza** concepts explain the _Why_ and _How_ behind the framework's design. These documents cover the underlying philosophy and architectural decisions.
 
 ## Key Topics
 

services/docs/content/en/quetza/concepts/architecture.md

@@ -3,38 +3,38 @@ title: Architecture & Philosophy
 weight: 1
 ---
 
-**Goal:** Understand the core design principles that drive Quetza's modularity.
+**Goal:** Understand the core design principles that drive Quetza's modularity.
 
 ## Design Philosophies
 
 ### Convention Over Configuration
 
-Quetza minimizes boilerplate by relying on strict folder structures.
+Quetza minimizes boilerplate by relying on strict folder structures.
 
-- **No central registry:** The filesystem _is_ the registry.
-- **Result:** You don't update a config file to add a module; you just create the folder.
+- **No central registry:** The filesystem _is_ the registry.
+- **Result:** You don't update a config file to add a module; you just create the folder.
 
 ### Composition Over Inheritance
 
-Modules are composed of capabilities, not inherited from a base class.
+Modules are composed of capabilities, not inherited from a base class.
 
-- **Flexibility:** Modules can use any internal architecture (Functional, OOP) as long as they export the required interfaces.
+- **Flexibility:** Modules can use any internal architecture (Functional, OOP) as long as they export the required interfaces.
 
 ### Isolation Over Integration
 
 Modules cannot directly invoke each other.
 
 - **Why:** Prevents tight coupling.
-- **Benefit:** You can delete any module without breaking the rest of the bot.
+- **Benefit:** You can delete any module without breaking the rest of the bot.
 
 ## Core Entities
 
 | Entity         | Role                           | Lifecycle                     |
 | :------------- | :----------------------------- | :---------------------------- |
-| **Client**     | Service Locator & Orchestrator | Singleton. Runs the show.     |
-| **Module**     | Namespace for features         | Loaded at startup.            |
+| **Client**     | Service Locator & Orchestrator | Singleton. Runs the show.     |
+| **Module**     | Namespace for features         | Loaded at startup.            |
 | **Command**    | User Interaction Endpoint      | Stateless. Request/Response.  |
-| **Event**      | Reactive Observer              | Subscribed at startup.        |
+| **Event**      | Reactive Observer              | Subscribed at startup.        |
 | **Controller** | State Manager                  | Persists across interactions. |
 
 ---

services/docs/content/en/quetza/concepts/module-system.md

@@ -1,15 +1,15 @@
 ---
-title: The Module System
+title: The Module System
 weight: 2
 ---
 
-**Goal:** Define the vocabulary and mechanics of Quetza's primary abstraction unit.
+**Goal:** Define the vocabulary and mechanics of Quetza's primary abstraction unit.
 
 ## System Vocabulary
 
 ### Module Declaration
 
-The `module.ts` file acts as the manifest. It is the entry point for discovery.
+The `module.ts` file acts as the manifest. It is the entry point for discovery.
 
 ```typescript
 export const name = 'my-module'; // ID
@@ -18,36 +18,36 @@ export const description = '...'; // Doc
 
 ### Command Registration
 
-Occurs during the `ready` event.
+Occurs during the `ready` event.
 
 1.  Quetza scans all `commands/` folders.
 2.  Compiles `ApplicationCommandData`.
-3.  PUTs the payload to Discord's API.
+3.  PUTs the payload to Discord's API.
 
 ### Controller Injection
 
-State is injected, not imported.
+State is injected, not imported.
 
 ```typescript
 // The framework calls this:
 execute(client, interaction, controller);
 ```
 
-- **Why?** Allows the framework to manage the controller's lifecycle (singleton per module).
+- **Why?** Allows the framework to manage the controller's lifecycle (singleton per module).
 
 ## State Management Philosophy
 
-### Ephemeral by Default
+### Ephemeral by Default
 
 Quetza provides **no built-in database**.
 
-- **Memory:** Controllers store state in JS `Map` or `Set` objects.
-- **Restart:** All state is lost when the process exits.
-- **Persistence:** Must be implemented manually (e.g., SQLite, Redis) inside the Controller.
+- **Memory:** Controllers store state in JS `Map` or `Set` objects.
+- **Restart:** All state is lost when the process exits.
+- **Persistence:** Must be implemented manually (e.g., SQLite, Redis) inside the Controller.
 
-### Scope as Key
+### Scope as Key
 
-State must be keyed by its boundary.
+State must be keyed by its boundary.
 
 - `Map<GuildID, ...>` - Server specific (Most common).
 - `Map<UserID, ...>` - User specific (DM bots).
@@ -58,7 +58,7 @@ State must be keyed by its boundary.
 
 - **Validation:** Check permissions/inputs immediately.
 - **User-Facing:** "You don't have permission" (Not "Error: 403").
-- **Isolation:** A crash in `/ping` catches itself and doesn't kill the bot.
+- **Isolation:** A crash in `/ping` catches itself and doesn't kill the bot.
 
 ---