1 files changed, 19 insertions, 4 deletions

diff --git a/CONTEXT.md b/CONTEXT.md
index 375bf57..f068035 100644
--- a/CONTEXT.md
+++ b/CONTEXT.md
@@ -113,10 +113,13 @@ Workspace version is `a.b.c` (single version for all crates):
 
 Bump the workspace version in the root `Cargo.toml` when a change of
 that class lands — do not leave the version to drift.  Current:
-`0.5.1` — the GUI era landed with 0.5.0 (graphics layer + cursor
-compositor) and the canvas was fixed at 800×600 as a `c` bump; a
-future major GUI overhaul (graphics windows beyond the text surface)
-would be the `a` bump (1.0.0).
+`0.5.2` — the GUI era landed with 0.5.0 (graphics layer + cursor
+compositor); 0.5.1 fixed the canvas at 800×600; 0.5.2 added fault
+diagnostics (screen + serial dumps for every CPU exception) and
+real-hardware hardening (framebuffer-size clamping, fb-region exclusion
+from the allocators, authoritative fb geometry logging).  A future
+major GUI overhaul (graphics windows beyond the text surface) would be
+the `a` bump (1.0.0).
 
 ## Project layout
 
@@ -388,6 +391,18 @@ Workspace of four crates, all built for the `x86_64-unknown-uefi` target:
     hardware pushes only 24 bytes at same privilege, so the extra
     fields are inert there; the synthetic frames set them
     explicitly either way.
+- `interrupts`/`sched` fault dumps (0.5.2): every CPU exception
+    vector 0-31 has an IDT entry (macro-generated stubs; 8/14 keep
+    their ISTs).  Any fault in the shell (task ≤ 1) prints a
+    white-on-red band via `gop::dump_lines` (raw fb, bypasses vt,
+    clamped) *and* a parseable serial line — `!!! <kind> vec=N
+    err=… rip=… cr2=… rsp=… rflags=… task=N "name"` — then halts;
+    faults in background tasks abort the task instead.  Real
+    hardware has no serial console, so the screen band is how a
+    crash reports itself; a non-canonical write shows vec=13 (GP,
+    cr2=0), an unmapped canonical address shows vec=14 with cr2=
+    the address.  `fault` shell command + `make test-fault` verify
+    the path.
 - Panic handling: a task panic (or guard-page overflow) is caught,
     logged as `sched: task N "name" panicked: …`, the task is marked
     Done, and the scheduler switches away — the shell keeps running.