Pinky TTTT: one true word + zero hides — the chips regression cure (v1.106.0, #61) #141

Merged
ClaudiuSchuster merged 1 commit from oss-oo/pinky-tttt-chips into main 2026-10-24 17:27:32 +00:00
Owner

The dock marker resolves to ONE value (primary +N); zero-state chips HIDE like the unread badge (owner law); structural tripwire /[a-z]+[.,][a-z]+/; discriminating pins; the takeover law in both READMEs. Validated SHIP (local audit under W20).

The dock marker resolves to ONE value (primary +N); zero-state chips HIDE like the unread badge (owner law); structural tripwire /[a-z]+[.,][a-z]+/; discriminating pins; the takeover law in both READMEs. Validated SHIP (local audit under W20).
Pinky TTTT: one true word + zero hides — the chips regression cure, owner finding #61 (v1.106.0)
All checks were successful
Checks / Functional checks (pull_request) Successful in 50s
566c203569
R1: the dock's not-in-filter marker resolves ONE value again — the
PRIMARY active counter's word (canonical chip order) plus a '+N'
count when more join it; never the v1.77.0-era glued fragment list.
R2: the owner's display law, everywhere — 'Chips bei 0 NICHT
sichtbar, so wie die Ungelesen-Blase': every census chip renders
only when nonzero (v1.77.0 residue condition restored, generalized
past the v1.92.0 #54 always-render annex); the fleet chip drops its
zero parts and hides at all-zero; the slim line's twins obey; the
MMM/YYY always-show inheritance is superseded (documented).
T3: Papa's structural tripwire (one data-census per element; no
glued two-state-word pair in any rendered text/title/aria-label),
discriminating pins (mutation-proven red both directions), the
12-leg CDP rig specimen (rich→quiet→empty stages), and the
takeover-discipline law written into both READMEs — applied to this
round's own migrations (IIII/YYY/slim-line pins proven red first).
ClaudiuSchuster deleted branch oss-oo/pinky-tttt-chips 2026-10-24 17:27:32 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
OSS-Singularity/zcode-dispatch-observatory!141
No description provided.