UI Bug: RTL/LTR text formatting issue with "days left" and Hebrew course names in Weekly Schedule

[AdzAhm]

In the "Weekly Schedule" (Homework) view, there is a text rendering issue when combining Hebrew course names (RTL) with the time remaining text (LTR). The string concatenation breaks, causing the number of days to detach from the "d left" text and wrap around the Hebrew course name.

Actual Behavior
The subtitle text renders in a mixed, confusing order. For example, instead of keeping the remaining time together, it renders as · d left.

Specific examples from the UI:

8 · מערכות ספרתיות ומבנה המחשב d left

11 · מבוא למדעי המחשב מ' d left

Expected Behavior:

8d left · מערכות ספרתיות ומבנה המחשב ( or something orgnized and good )

Steps to Reproduce
Navigate to the Weekly Schedule > Homework section.

Ensure there are tasks with a course name in Hebrew (RTL).

Ensure the deadline is several days away so the "d left" string is triggered.

Observe the subtitle text under the task name.

screenshot:

[itabajah]

Fixed in #143.

Cause: the subtitle is a single bidi paragraph, so the Hebrew course name and the LTR badge were reordered against each other. Digits are a weak bidi type — the 8 in 8d left inherited the direction of the Hebrew run and got carried to the far side of it, stranding d left behind. Hence 8 · <name> d left.

Auditing for the same pattern turned up a quieter second case in the same view: a class block's tooltip reversed its time range next to a Hebrew name — a 10:00–12:00 class read as 12:00–10:00. Fixed too.

Fix: isolate the name so nothing can be reordered across it — a <bdi> element in JSX, and the equivalent U+2068/U+2069 controls for the plain-text tooltip. It now renders as <name> · 8d left, with the Hebrew reading correctly RTL. I kept the existing order (course name, then badge) rather than your 8d left · <name>, since it matches the rest of the LTR UI — the bug was the scrambling, not the ordering. Happy to flip it if you'd rather.

Guarded by a Playwright test that measures the badge's client rects in a real browser: unisolated it fragments into 2 boxes, isolated it stays 1. jsdom has no layout engine, so it can't see bidi reordering at all — unit tests alone would never have caught this.