Properties: a header row over the slot table

Names the four columns -- Name, Type, Value, Unit -- in grey at row size over a
hairline rule, so it labels the table without competing with it.

A fifth column of raw flags= letters was tried alongside it and taken out
again. c, a, s and o are the manifest's own shorthand, and a column of them
told the reader nothing the row was not already saying: c is what the white
field means, a is what an "action" value means. What the flags decide is still
decided by them; it is just not spelled out twice.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

README.md

@@ -5,7 +5,7 @@ component hierarchy as a navigation tree, paints the selected folder's children
 wiresheet of draggable component boxes, draws the links between them, and writes box
 positions back into each component's `meta` property on save.
 
-Current version: **0.0.0.051** (see [Versioning](#versioning)).
+Current version: **0.0.0.053** (see [Versioning](#versioning)).
 
 ## Requirements
 
@@ -166,6 +166,14 @@ Each row carries the slot's declared type between its name and its value, writte
 a slot sheet writes it: the manifest stores the primitives bare and everything else already
 qualified, so `int` is shown as `sys::int` and `sys::Buf` is left as it stands.
 
+A column of raw `flags=` letters was tried here and taken out again: `c`, `a`, `s` and `o`
+are the manifest's own shorthand, and a column of them told the reader nothing the row was
+not already saying -- `c` is what the white field means, `a` is what an `action` value
+means. What the flags decide is still decided by them; it is just not spelled out twice.
+
+The **header row** stays. It is deliberately quiet -- row-sized, grey, over a hairline
+rule -- so it labels the table without competing with it.
+
 Which rows can be typed into is the slot's own business, not the view's:
 
 | Slot | Field |