Pinky XXX: the blessed polish round — affordance symmetry, state grammar, fleet-scope unread (v1.81.0) #114
Loading…
Reference in a new issue
No description provided.
Delete branch "oss-oo/pinky-xxx-polish"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Three families, one polish round (roadmap-blessed order 1-of-3):
X1 — affordance symmetry (item-8 completion + #17): every failed steer card carries BOTH affordances — Retry gated on the prompt file's survival (the dam-quarantined corpse class renders no dead promise), Dismiss ALWAYS (dismissedAt settles the result durably; no card waits for age-out housekeeping). The #17 hide audit answered: the per-row Hide exists on main-table non-keep-close rows; the errored corpse row lacked it because it was PINNED (verified live); the exclusion is now surfaced in the pin/star tooltips and the census chip names both semantics (filter view vs row Hide).
X2 — state grammar (#14 + sibling): resolveRowState is the ONE grammar every status surface derives through — running says running, terminal says its word, resting rows say idle (never a defaulted running), brand-new says nothing; a live error episode rides its own labeled chip, compounds never join the state word.
X3 — the VVV fleet-scope: usage-ledger pairing extends to bell-visible fleet children (album-persisted) and the consumed cutoff (newest bell delivery + 2s grace) keeps belled round output off the owner's unread even in lane sessions; genuine post-bell conversation still counts. Live dry-run over copied station state: B² 60 → 0; a synthetic post-bell reply counts 1.
Gates: tests/test_round_xxx.py (30 legs incl. the node state-grammar harness); full suite 1286 green; Super-Linter station recipe green on the final tree (BASH/BASH_EXEC/MARKDOWN/PYTHON_PYLINT/PYTHON_RUFF/YAML).