tribunal-kit 9.2.3 → 9.2.5

package/.agents/skills/huggingface-zerogpu/references/concurrency.md

@@ -0,0 +1,79 @@
+# Concurrency Safety
+
+Gradio handlers run **in parallel by default on ZeroGPU**. Code that works fine in single-user testing can silently corrupt or leak data in production. Always assume handlers execute concurrently.
+
+## No mutable global state
+
+Per-request or per-user data must not live in module-level mutable variables. Concurrent requests will overwrite each other.
+
+```python
+# BAD — concurrent requests overwrite each other
+results = {}
+
+def process(text):
+    results["output"] = expensive_compute(text)  # race condition
+    return results["output"]
+```
+
+```python
+# GOOD — pure function, no shared mutable state
+def process(text):
+    return expensive_compute(text)
+```
+
+For state that must persist within a single user session, use `gr.State`:
+
+```python
+with gr.Blocks() as demo:
+    history = gr.State(value=[])
+
+    def add_message(msg, hist):
+        hist.append(msg)
+        return hist, hist
+
+    btn.click(fn=add_message, inputs=[msg, history], outputs=[chatbot, history])
+```
+
+Note that on ZeroGPU, `gr.State` is pickled across the worker boundary on every yield — see "Process Isolation and Pickle" in SKILL.md for the implications.
+
+## No fixed file paths for outputs
+
+Hardcoded output filenames cause concurrent requests to overwrite each other's files. This corrupts outputs and, worse, can leak one user's data to another.
+
+```python
+# BAD — concurrent calls clobber the same file
+def generate_image(prompt):
+    image = pipe(prompt).images[0]
+    image.save("output.png")
+    return "output.png"
+```
+
+```python
+# GOOD — unique path per invocation
+import tempfile
+
+def generate_image(prompt):
+    image = pipe(prompt).images[0]
+    with tempfile.NamedTemporaryFile(suffix=".png", delete=False) as f:
+        image.save(f.name)
+        return f.name
+```
+
+The same applies to any intermediate files (audio, video, CSV exports). Always generate a unique path per invocation.
+
+## Read-only globals are safe
+
+Model objects, tokenizers, and configs loaded once at startup and only read during requests are safe and encouraged. This is the standard ZeroGPU pattern: load at module scope, read inside `@spaces.GPU` handlers.
+
+```python
+# SAFE — loaded once at module scope, read-only during requests
+model = load_model().to("cuda")
+tokenizer = load_tokenizer()
+
+@spaces.GPU
+def predict(text):
+    tokens = tokenizer(text, return_tensors="pt").to("cuda")
+    return model.generate(**tokens)
+```
+
+The "no mutable global state" rule targets *writes* from handlers, not reads. A handler that only reads from a global is concurrency-safe.

package/.agents/skills/huggingface-zerogpu/references/cuda-and-deps.md

@@ -0,0 +1,66 @@
+# CUDA Dependencies on ZeroGPU
+
+Detailed guidance for installing CUDA-dependent packages on ZeroGPU. SKILL.md establishes the bottom line — wheels are the recommended path because the ZeroGPU build phase has no `nvcc`. This document covers wheel filename tag reading, the kernels-community fallback, and torch-family side-car drift.
+
+## When no wheel is available on PyPI
+
+Common workarounds, in preference order:
+
+1. **Pre-built wheel via direct URL.** For `flash-attn`, the upstream project ships a fairly complete matrix at https://github.com/Dao-AILab/flash-attention/releases — check there first and pin the matching wheel URL.
+2. **Build the wheel yourself and host it** (e.g. on a public HF Hub repo) when no upstream wheel matches the Space environment.
+3. **Use a kernels-community kernel** (see below) — handles ABI matching for you, no version pinning needed.
+
+## Reading a CUDA wheel filename
+
+A wheel filename like
+
+```
+flash_attn-2.8.0.post2+cu12torch2.8cxx11abiFALSE-cp312-cp312-linux_x86_64.whl
+```
+
+encodes four build-time choices:
+
+| Tag | Meaning |
+|-----|---------|
+| `cu12` | CUDA major version |
+| `torch2.8` | torch major.minor the wheel was compiled against |
+| `cxx11abiFALSE` | C++ stdlib ABI choice (`TRUE` or `FALSE`) |
+| `cp312-cp312` | CPython version (3.12) |
+
+The wheel's compiled C-extension will `ImportError` on ABI/symbol mismatches if any of these drift at install time.
+
+If you hand pip a wheel URL without pinning the surrounding environment, pip may resolve `torch` to a version different from the wheel's build target, and the Space will fail on first import. Therefore:
+
+- Pin `torch==X.Y.Z` in `requirements.txt` to match the wheel's `torch2.X` tag.
+- Set `python_version:` in the Space frontmatter to match the `cp3XX` tag.
+- Check the runtime's cxx11-ABI choice against the wheel; if unsure, try the opposite ABI wheel.
+
+## Prefer kernels-community when unsure
+
+If you are not sure about the ZeroGPU runtime's torch / Python / ABI combination, prefer a [kernels-community](https://huggingface.co/kernels-community) kernel (e.g. `kernels-community/flash-attn2`) instead of a raw wheel URL. The kernels runtime handles ABI matching on your behalf, so no version pinning is required in your Space.
+
+## torch-family side-car drift
+
+`torchvision`, `torchaudio`, `torchcodec`, and similar side-car packages are built against a specific `torch` major.minor (and CUDA major). On ZeroGPU, the runtime's supported `torch` list lags behind PyPI, so projects often pin a non-latest `torch` — and a bare `uv add <side-car>` can silently resolve to a newer release that targets a different `torch` / CUDA, producing ABI/import failures even though `uv lock` succeeded without warnings.
+
+Concretely observed (2026-04) with `torch==2.9.1` pinned:
+
+- `torchaudio` resolves to `2.11.0`, which targets torch 2.11 / CUDA 13. The `2.11.0` release **dropped the `Requires-Dist: torch==X.Y.Z` line** that every earlier release had, so uv sees no constraint and picks it.
+- `torchcodec` resolves to a release targeting torch 2.11. No torchcodec release on PyPI declares a `torch` dependency at all; the compatibility table lives only in the project README.
+- `torchvision` happens to resolve correctly because torchvision still declares `Requires-Dist: torch==X.Y.Z`. Which side-cars are affected changes over time — treat every torch-family package as suspect, not just these.
+
+### Verify at add/upgrade time
+
+After any `uv add <torch-side-car>` or `uv lock --upgrade`, verify the resolved version targets the same `torch` major.minor as pinned. Two-step fallback because PyPI metadata is not always sufficient:
+
+1. Query PyPI for the resolved version's `requires_dist`:
+   ```bash
+   curl -s https://pypi.org/pypi/<pkg>/<version>/json \
+     | python3 -c "import json,sys,re; rd=json.load(sys.stdin)['info'].get('requires_dist') or []; print('\n'.join(x for x in rd if re.match(r'^torch(?![a-z])', x)) or '(no torch constraint declared)')"
+   ```
+   If a `torch==X.Y.Z` line appears and matches the pinned torch, good. If it appears and does NOT match, the side-car is wrong — pin it down explicitly.
+2. If the query prints `(no torch constraint declared)`, PyPI metadata is silent and cannot be trusted. Fall back to the project's own compatibility table (GitHub README / docs site) — torchcodec, for example, maintains one at https://github.com/pytorch/torchcodec. Pick the side-car version the table maps to the pinned torch major.minor, and pin it explicitly.
+
+### Preventive pin
+
+Once the correct side-car version is known, pin it in `pyproject.toml` alongside torch so uv cannot drift on future `uv lock --upgrade`. The side-car version numbers for a given torch major.minor change each release; always re-verify, do not copy a mapping from an older project.

package/.agents/skills/huggingface-zerogpu/references/how-quota-works.md

@@ -0,0 +1,74 @@
+# How ZeroGPU duration and quota are checked
+
+Mechanism for `duration` validation and quota pre-checks. Useful when choosing `duration` values, debugging `illegal duration` vs `quota exceeded` errors, and understanding why the default 60s is pessimistic for short tasks.
+
+For per-tier numerical thresholds (free vs Pro vs Team vs Enterprise quota minutes), the daily quota window length, runs-per-day limits, and pay-as-you-go pricing, see [the ZeroGPU docs](https://huggingface.co/docs/hub/spaces-zerogpu) — those values change over time and are deliberately kept out of this skill.
+
+## What `duration` actually requests
+
+Whatever value is passed to `@spaces.GPU(duration=N)` (or the default 60s when unspecified) becomes the `requested duration` the platform checks against. For `xlarge`, the request is doubled internally:
+
+```
+requested = N * 2 if size == "xlarge" else N
+```
+
+So `@spaces.GPU(duration=60, size="xlarge")` is internally a 120-second request — both for the tier-max check and the quota pre-check below.
+
+## Two distinct error modes
+
+Two failure messages can come back from the scheduler before the call runs:
+
+| Error | Trigger | What helps |
+|---|---|---|
+| **`ZeroGPU illegal duration`** | `requested duration > visitor's tier per-call cap` | Lower `duration`. Sign in / upgrade tier. **Waiting does not help.** |
+| **`ZeroGPU quota exceeded`** | `remaining quota < requested duration`, OR runs-per-day cap reached | Wait for the quota window to reset. For Pro / Team / Enterprise, pay-as-you-go credits cover the overflow. |
+
+The error wording for `quota exceeded` includes the explicit numbers, e.g.:
+
+```
+You have exceeded your Pro ZeroGPU quota
+(60s requested vs. 30s left). Try again in 1:23:45.
+```
+
+The comparison is **`requested` vs `remaining`** — not `actual run time` vs `remaining`. A 10-second task left at the default 60s requests 60s of quota; once `remaining < 60s` the call fails even though the actual work would have fit.
+
+## Why the default 60s is pessimistic for short tasks
+
+`DEFAULT_SCHEDULE_DURATION` in the `spaces` package is **60 seconds**. So an undecorated `@spaces.GPU` (or `@spaces.GPU()` with no `duration=`) requests 60s of quota.
+
+For a task that actually takes ~10 seconds:
+
+- The user's 60s quota gets reserved up front.
+- Once their remaining quota drops below 60s, your Space fails for them — even though they could have run many more 10s tasks if the request matched reality.
+- Your call also ranks lower in the queue than equivalent calls declaring smaller durations.
+
+The fix is to declare the realistic duration explicitly:
+
+```python
+@spaces.GPU(duration=15)
+def fast_task(...):
+    ...
+```
+
+For workloads where runtime depends on inputs, use a callable (per-request estimator):
+
+```python
+def estimate_duration(prompt, steps):
+    return int(steps * 3.5)
+
+@spaces.GPU(duration=estimate_duration)
+def variable_task(prompt, steps):
+    ...
+```
+
+This preserves quota for light inputs and reserves more only when needed.
+
+## Quota window: 24h fixed from first use
+
+The quota window's TTL is set when the first call of a fresh window lands and counts down unconditionally — it is not a sliding window, not a calendar-day reset, and not extended by subsequent use. A user who runs a call at 14:00 sees their next reset at 14:00 the following day, regardless of how heavily or lightly they use the Space in between.
+
+For exact tier thresholds, runs-per-day caps, and pay-as-you-go billing rates, see the [ZeroGPU docs](https://huggingface.co/docs/hub/spaces-zerogpu).
+
+## Queue priority
+
+The queue is **node-level** — requests from every Space scheduled on the same physical node compete for that node's GPU slots. Among queued requests, **shorter declared `duration` ranks higher**. So tight per-request `duration` estimates serve two goals at once: they preserve the user's quota and move the request up the queue.

package/.agents/skills/huggingface-zerogpu/references/how-zerogpu-works.md

@@ -0,0 +1,50 @@
+# How ZeroGPU works (mechanism)
+
+Conceptual lifecycle of model weights, processes, and worker reuse on ZeroGPU. Useful when reasoning about cold-starts, why module-scope warmup does not carry over to requests, why returning CUDA tensors hangs the call, or why `gr.State` mutations do not persist across the worker boundary.
+
+For numerical limits (concurrency slots per Space, queue priority by tier, etc.), see [the ZeroGPU docs](https://huggingface.co/docs/hub/spaces-zerogpu) — those values change over time and are deliberately kept out of this skill.
+
+## Two processes, two lifetimes
+
+A ZeroGPU Space runs as **two separate processes**:
+
+- **Main web process** — long-lived. Imports `app.py`, launches Gradio, stays up for the life of the Space. Holds no VRAM and, after the startup "pack" step, holds no model weights in RAM either.
+- **GPU worker processes** — short-lived. Forked per `@spaces.GPU` request (or reused if warm). Run the task and are eventually killed by the ZeroGPU scheduler when another Space needs the GPU slot. Your Space code never kills its own worker.
+
+## Module-scope `.to("cuda")` is captured to disk
+
+When `import spaces` is active, `model.to("cuda")` at module scope is intercepted. The call is rewritten to `to("cpu")`, so the tensor data physically lives in main process RAM at this point. A "fake" CUDA-presenting tensor is registered alongside the original CPU tensor.
+
+At a startup "pack" step, the backend writes those original CPU tensors to disk via direct I/O (`O_DIRECT`), then frees the corresponding RAM. After pack, the main process holds no model weights anywhere — the data lives only on disk.
+
+This is why module-scope `pipe(...)` / `model.generate(...)` / `model(...)` calls do not run on a real GPU: there is no GPU attached to the main process, and after pack there are no weights to compute against either. Such calls either fail or silently fall back to CPU on the fake tensors.
+
+## Worker init: disk → pinned memory → VRAM
+
+When a `@spaces.GPU` call lands, the scheduler routes it to a worker:
+
+1. **Cold worker** — forked from the main process. The patched torch is unpatched, real CUDA is initialized, and weights are read from the disk offload directory into pinned host memory and streamed onto VRAM through a double-buffered pipeline (essentially `pin_memory().cuda(non_blocking=True)` per batch). This is the "cold-start" cost.
+2. **Warm worker (reused)** — an alive worker bound to the same GPU slot is reused if the scheduler reports it idle. Init is skipped; weights stay on VRAM from the previous call. Subsequent requests within a burst hit this path.
+
+A warm worker is eventually killed by the scheduler when another Space needs the GPU slot. The next call after that point pays the disk → VRAM cost again. Occasional cold-starts on a low-traffic Space are normal.
+
+## Why module-scope warmup does not help
+
+A common instinct is to call `pipe("warmup")` at module scope to "prepare" the model. This does not work on ZeroGPU:
+
+- At module scope, no real GPU is attached. The fake CUDA tensors do not have data after pack, so `pipe(...)` either fails or silently runs on something other than a real GPU.
+- Even if you wrap the warmup in `@spaces.GPU`, the worker that ran the warmup will eventually be killed before the first real user request lands — leaving them with a cold worker anyway.
+
+The right answer is to load eagerly at module scope (`pipe = pipeline(..., device="cuda")`) and accept that the first user request after a quiet period will be a cold worker. Cold-start is fast on ZeroGPU because of the pinned-memory disk pipeline; it is not free, but it is not "minutes of model download" either.
+
+## Why returning CUDA tensors hangs the call
+
+The main process never has a CUDA context — it has no GPU attached and its torch never initialized CUDA. When a worker returns a CUDA tensor, unpickling it in the main process triggers `torch.cuda._lazy_init()`, which would attempt to initialize CUDA in the main process. ZeroGPU blocks this, and the call hangs.
+
+The fix is purely client-side: convert to CPU before returning (`.cpu()`, `.cpu().numpy()`, etc.). See "Process Isolation and Pickle" in SKILL.md.
+
+## Why `gr.State` does not share by reference across the boundary
+
+Worker processes are forked separately and exchange data with the main process via pickle. `gr.State` values cross this boundary on every yield, so mutations inside a `@spaces.GPU` generator are local to the worker until the mutated state is explicitly yielded back. The main process gets a fresh deserialized copy each time — `id()` differs, in-place mutations are invisible across the boundary.
+
+See "Process Isolation and Pickle" in SKILL.md for the practical implications and `references/concurrency.md` for related parallel-handler concerns.

package/.agents/skills/human-gate-negotiation/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: human-gate-negotiation
+description: "Use when preparing concise impact reports before approval requests for high-risk, non-idempotent actions."
+version: 1.0.0
+last-updated: 2026-09-25
+skills:
+  - fabel-protocol
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/harness_manager.js
+---
+
+# Human Gate Negotiation
+
+## Context
+When an agent attempts a high-risk operation (deploying to production, running `rm -rf`, running a database migration), it MUST be paused, and explicit approval must be sought from the Human Gate. 
+
+## The Impact Report Format
+Never just ask "Can I run this?". You must provide a structured report outlining the consequences of the action so the human can make an informed decision.
+
+**Mandatory Report Structure:**
+1. **Proposed Action**: The exact command or script to be executed.
+2. **Purpose**: Why this is necessary.
+3. **Files/Resources Affected**: Which systems will be mutated.
+4. **Expected Side Effects**: Downtime, data loss, irreversible state changes.
+5. **Verification Status**: Proof that tests passed before reaching this gate.
+6. **Rollback Instructions**: How to undo this action if it fails in production.
+
+## Agent Behavior
+Once the report is generated, the agent must enter a sleep/wait state and CANNOT proceed until the human explicitly provides an approval token.

package/.agents/skills/i18n-localization/SKILL.md

@@ -1,134 +1,134 @@
----
-name: i18n-localization
-description: "Use when Internationalization (i18n) and localization mastery. Abstracting hardcoded strings, managing JSON/YAML translation dictionaries, bidirectional routing (RTL support for Arabic/Hebrew), Pluralization algorithms, date/currency formatting, and SSR locale detection in Next.js/React. Use when preparing an application for global multilingual scaling."
-version: 5.0.0
-last-updated: 2026-09-13
-skills:
-  - nextjs-react-expert
-  - adapt
-  - baseline-ui
-tools: Read, Grep, Glob, Bash, Edit, Write
-scripts-binding:
-  - .agent/scripts/lint_runner.js
-  - .agent/scripts/verify_all.js
----
-
-# i18n & Localization — Global Scale Mastery
-
----
-
-## 🛠️ Technical Architecture & Reference Recipes
-
----
-
-## Hallucination Traps (Read First)
-
-- ❌ Concatenating translated strings (`'Hello ' + name`) -> ✅ Use interpolation: `t('greeting', { name })` to handle word order differences
-- ❌ Hardcoding date/number formats -> ✅ Use `Intl.DateTimeFormat` and `Intl.NumberFormat` with the user's locale
-- ❌ Assuming all languages read left-to-right -> ✅ Arabic, Hebrew, Farsi are RTL; use CSS `dir='auto'` and logical properties
-- ❌ Using string length for validation on translated text -> ✅ Translations can be 30-200% longer than English; design for expansion
-
----
-
----
-
-## 1. The i18n Architecture (Next.js / React)
-
-Do not hardcode strings inside UI components. Use a standardized library (e.g., `next-intl` or `react-i18next`).
-
-### Step 1: Dictionary Abstraction
-
-```json
-// messages/en.json
-{
-  "Dashboard": {
-    "welcomeMessage": "Welcome back, {name}!",
-    "unreadAlerts": "{count, plural, =0 {No unread alerts} one {You have 1 unread alert} other {You have # unread alerts}}"
-  }
-}
-```
-
-### Step 2: Component Implementation
-
-```tsx
-// ❌ BAD: Hardcoded English text and manual variable interpolation
-export function Header({ user, alertCount }) {
-  return (
-    <h1>
-      Welcome back, {user.name}! You have {alertCount} alerts.
-    </h1>
-  );
-}
-
-// ✅ GOOD: i18n Abstraction (using next-intl)
-import { useTranslations } from 'next-intl';
-
-export function Header({ user, alertCount }) {
-  const t = useTranslations('Dashboard');
-
-  return (
-    <header>
-      <h1>{t('welcomeMessage', { name: user.name })}</h1>
-      <p>{t('unreadAlerts', { count: alertCount })}</p>
-    </header>
-  );
-}
-```
-
----
-
-## 2. Advanced Native Formatting (`Intl`)
-
-Do not install `moment.js` or write massive regex string parsers to format currencies in Euros vs Dollars. The browser handles this natively with the `Intl` API.
-
-```typescript
-// Data/Currency Formatting correctly tied to the active locale
-const locale = 'de-DE';
-
-// ✅ Currency
-const price = new Intl.NumberFormat(locale, { style: 'currency', currency: 'EUR' }).format(1200.5);
-// Output in Germany: "1.200,50 €"
-
-// ✅ Dates
-const date = new Intl.DateTimeFormat(locale, { dateStyle: 'full' }).format(new Date());
-// Output in Germany: "Freitag, 2. April 2026"
-
-// ✅ Relative Time
-const rtf = new Intl.RelativeTimeFormat(locale, { numeric: 'auto' });
-rtf.format(-2, 'day'); // Output: "vorgestern" (the day before yesterday)
-```
-
----
-
-## 3. Bidirectional Architecture (RTL)
-
-For languages like Arabic and Hebrew, the UI must fundamentally flip horizontally. Right-To-Left (RTL) breaks standard CSS `marginLeft` and `marginRight`.
-
-**The Solution:** Logical CSS Properties.
-Tailwind v4 (and modern CSS) natively supports logical direction.
-
-```css
-/* ❌ BAD: Hardcoded physical space */
-.btn {
-  margin-left: 10px;
-} /* Will break layout in Hebrew */
-
-/* ✅ GOOD: Logical spacing (Tailwind: ms-4, me-4) */
-.btn {
-  margin-inline-start: 10px;
-} /* Automatically flips in RTL mode */
-```
-
-_In React HTML tag:_ `<html lang="ar" dir="rtl">`
-
----
-
-## 4. Routing and SSR Detection
-
-Users should not face English UI natively in Japan. Detect their browser headers at the edge routing layer.
-
-In Next.js Middleware:
-
-1. Parse the incoming `Accept-Language` header.
-2. Intercept requests to `/dashboard`.
-3. Rewrite URL to the detected locale (e.g., `/ja/dashboard`).
+---
+name: i18n-localization
+description: "Use when Internationalization (i18n) and localization mastery. Abstracting hardcoded strings, managing JSON/YAML translation dictionaries, bidirectional routing (RTL support for Arabic/Hebrew), Pluralization algorithms, date/currency formatting, and SSR locale detection in Next.js/React. Use when preparing an application for global multilingual scaling."
+version: 5.0.0
+last-updated: 2026-09-13
+skills:
+  - nextjs-react-expert
+  - adapt
+  - baseline-ui
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
+---
+
+# i18n & Localization — Global Scale Mastery
+
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
+
+---
+
+## Hallucination Traps (Read First)
+
+- ❌ Concatenating translated strings (`'Hello ' + name`) -> ✅ Use interpolation: `t('greeting', { name })` to handle word order differences
+- ❌ Hardcoding date/number formats -> ✅ Use `Intl.DateTimeFormat` and `Intl.NumberFormat` with the user's locale
+- ❌ Assuming all languages read left-to-right -> ✅ Arabic, Hebrew, Farsi are RTL; use CSS `dir='auto'` and logical properties
+- ❌ Using string length for validation on translated text -> ✅ Translations can be 30-200% longer than English; design for expansion
+
+---
+
+---
+
+## 1. The i18n Architecture (Next.js / React)
+
+Do not hardcode strings inside UI components. Use a standardized library (e.g., `next-intl` or `react-i18next`).
+
+### Step 1: Dictionary Abstraction
+
+```json
+// messages/en.json
+{
+  "Dashboard": {
+    "welcomeMessage": "Welcome back, {name}!",
+    "unreadAlerts": "{count, plural, =0 {No unread alerts} one {You have 1 unread alert} other {You have # unread alerts}}"
+  }
+}
+```
+
+### Step 2: Component Implementation
+
+```tsx
+// ❌ BAD: Hardcoded English text and manual variable interpolation
+export function Header({ user, alertCount }) {
+  return (
+    <h1>
+      Welcome back, {user.name}! You have {alertCount} alerts.
+    </h1>
+  );
+}
+
+// ✅ GOOD: i18n Abstraction (using next-intl)
+import { useTranslations } from 'next-intl';
+
+export function Header({ user, alertCount }) {
+  const t = useTranslations('Dashboard');
+
+  return (
+    <header>
+      <h1>{t('welcomeMessage', { name: user.name })}</h1>
+      <p>{t('unreadAlerts', { count: alertCount })}</p>
+    </header>
+  );
+}
+```
+
+---
+
+## 2. Advanced Native Formatting (`Intl`)
+
+Do not install `moment.js` or write massive regex string parsers to format currencies in Euros vs Dollars. The browser handles this natively with the `Intl` API.
+
+```typescript
+// Data/Currency Formatting correctly tied to the active locale
+const locale = 'de-DE';
+
+// ✅ Currency
+const price = new Intl.NumberFormat(locale, { style: 'currency', currency: 'EUR' }).format(1200.5);
+// Output in Germany: "1.200,50 €"
+
+// ✅ Dates
+const date = new Intl.DateTimeFormat(locale, { dateStyle: 'full' }).format(new Date());
+// Output in Germany: "Freitag, 2. April 2026"
+
+// ✅ Relative Time
+const rtf = new Intl.RelativeTimeFormat(locale, { numeric: 'auto' });
+rtf.format(-2, 'day'); // Output: "vorgestern" (the day before yesterday)
+```
+
+---
+
+## 3. Bidirectional Architecture (RTL)
+
+For languages like Arabic and Hebrew, the UI must fundamentally flip horizontally. Right-To-Left (RTL) breaks standard CSS `marginLeft` and `marginRight`.
+
+**The Solution:** Logical CSS Properties.
+Tailwind v4 (and modern CSS) natively supports logical direction.
+
+```css
+/* ❌ BAD: Hardcoded physical space */
+.btn {
+  margin-left: 10px;
+} /* Will break layout in Hebrew */
+
+/* ✅ GOOD: Logical spacing (Tailwind: ms-4, me-4) */
+.btn {
+  margin-inline-start: 10px;
+} /* Automatically flips in RTL mode */
+```
+
+_In React HTML tag:_ `<html lang="ar" dir="rtl">`
+
+---
+
+## 4. Routing and SSR Detection
+
+Users should not face English UI natively in Japan. Detect their browser headers at the edge routing layer.
+
+In Next.js Middleware:
+
+1. Parse the incoming `Accept-Language` header.
+2. Intercept requests to `/dashboard`.
+3. Rewrite URL to the detected locale (e.g., `/ja/dashboard`).