Added ZoneX to the documentation site

[fdesbiens]

ZoneX is a deterministic partitioning hypervisor for Armv8-R and a new component of the suite, so it gets its own place in the navigation rather than a subsection of the ThreadX port pages. Six pages, following the shape the Cortex-R52 Modules documentation settled: the index stays a bare index, and each piece of detail gets its own page beneath it.

Page	What it is for
Overview	what the component is, and how a partitioned system is put together
What Phase 0 demonstrates, and what it does not	the claim, the measurements, and the non-claim — where the index sends a reader first
Platform requirements and the region budget	read before choosing a board
Writing a partition manifest	the configuration reference, with a compiled example
Later phases	marked throughout as not shipped

Two pages are written to be quoted rather than summarised.

The claim page states the temporal result split by cause, because the halves have different causes and only one is the partitioning: nothing a partition does through the schedule reaches its neighbour, and what does reach it is the hypervisor's own console driver, at up to one line tag per run — 22 bytes at 115,200 8N1, 17,640 counts of the board's 8 MHz counter. That is a defect in ZoneX rather than a limit of the partitioning, bounded and derived rather than observed. The page carries the non-claim in full, including that interrupt latency is not measured at all and that there is no structural coverage of the port.

The platform page states the region budget as a hard portability limit. A Cortex-R52 configured with no EL2 memory protection unit cannot run ZoneX at all, and there is no software fallback — on Armv8-R both stages of address control are region-based, so there is nothing else to fall back on. It also records that the fixed virtual platform cannot show a reader this constraint, since its console and interrupt controller cost no regions where a real part's do.

The manifest example is a constant, not the harness's shape. The demonstrator images build their manifests at run time from linker symbols so that a harness never restates an address the linker chose, but a real system's manifest is a constant, so that is what the page shows. The snippet was extracted from the rendered page and compiled against the real headers under -Wall -Wextra -Wpedantic; the three validator results quoted beneath it came from running the real validator rather than reading the error codes.

Scope of the wiring. Adding a component touches more than its own directory: the site playbooks, the component list on the home page, and the navigation of every other component, since each lists them all and a component present in its own nav but absent from the others is a half-landed change. The PDF assemblers need no change — they filter component versions rather than naming them.

Prose is unwrapped, one paragraph per line, matching the rest of the repository. Built locally with npm run build:html: no unresolved cross-references, all six pages render, and ZoneX appears in every component's navigation.

The companion code pull request introduces the component itself.

[fdesbiens]

Companion code pull request: eclipse-threadx/zonex#5 — it introduces the component these pages document.