Pinky TT: the mobile deck + the role-true genesis slug — S-39, UU-1, UU-2 (v1.56.0) #84
Loading…
Reference in a new issue
No description provided.
Delete branch "oss-oo/pinky-tt-deck"
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?
Round TT — four lanes, one branch.
S-39 (steer #41, REQUIRED — the owner’s first own genesis spawn surfaced it): the auto-created worktree said “pinky” for a BRAIN spawn because the round-NN auto-resolution cut it on cwd blur under the form’s DEFAULT role. The cut now fires at REVIEW ENTRY (the role is final there), the slug is role-true in both directions (
…-brain-…/…-pinky-…), the redirect derivation’s org/repo mirror form is unchanged, and a role change after a cut (Back from review, or a click racing an in-flight probe) hands the stale home back assupersede—genesis_retire_homeremoves it refusal-laddered (scratch-root confinement, journal-recorded creations only, no live spawn record, no queue reference, git’s own dirty-tree refusal, genesis branches only), journaled asmode: retired. No never-spawned worktree/branch zombie lingers in the owner’s project repos.Lane P2b — the mobile deck: usable at 390–430 CSS px (responsive compact layout, no service worker). Under a 560px breakpoint: the session tables become family-hued row-cards (actions + context% + state + unread + title; the whole card taps into the response panel — the primary surface), the header collapses to the KK slim line BY DEFAULT (matchMedia-driven; the persisted wide-screen choice never clobbered; 🌱 rides the line), tap targets meet the 44px convention, the steer composer docks with the panel (expand/fold toggles intact), quota/graph sections stack, wide data tables scroll in their own box, the lineage graph keeps touch-drag pan (wheel zoom degrades to ⌖ fit — documented). Desktop ≥561px byte-untouched. Remote access documented as a station prerequisite (the unit binds 0.0.0.0).
A desktop bug the mobile rig caught: an expired toast kept
opacity: 0but stayed in the hit-test tree — an invisible box swallowing clicks over the rows beneath (reproduced deterministically over the genesis footer). Toasts now retire from pointer events after their fade, and lift clear of dialog footers at narrow widths.UU-1 (MED): the deterministic release asset is pinned IN-REPO —
scripts/make-release.shruns EXACTLY the pinnedgit archive --format=tar.gz --prefix=zcode-dispatch-observatory/ <tag> > zcode-dispatch-observatory-<tag>.tar.gz;make release-asset TAG=…/make check-asset TAG=… [FILE=…]wrap it; a suite test byte-matches the script’s output against a direct git archive in a rig checkout; the README recipe points at it. Third slip was one too many — no round hand-builds assets.UU-2 (LOW): the rename ✎ and genesis NAME rails now count 55 CODE POINTS client-side (
[...name].length;maxlengthdropped — it counts UTF-16 units and silently chopped emoji-bearing names the dispatcher accepts); emoji-bearing tests included.Evidence: offline suite 754 green (23 new tests: role-true slugs both directions, the retire ladder, the release-asset byte-match, the code-point rails, the mobile surfaces); pinned Super-Linter green with the lane set (BASH, BASH_EXEC, MARKDOWN, PYTHON_PYLINT, PYTHON_RUFF, YAML), tripwire-tested; the round’s Xvfb CDP rig 40/40 — real-500px-window interaction gates (trusted taps: card → panel, steer send through the fake dispatcher, question answer delivering the answer file, 🌱 dialog, the FULL S-39 supersede dance live: pinky re-cut retires the brain worktree), exactly-390 and exactly-430 device-metrics loads (desktop Chrome cannot render below 500px — the honest-500px reality, verified live), and the 1177px desktop unregression spot boxes.