web: shared chat stars, pipeline mini graphs and agent questions
- Persist chat stars in the operator-session registry (chat_star) so every browser/device shows the same Starred group; migrate old local stars once. - Add a compact pipeline graph shape to list responses and draw a lightweight list miniature; replace the cryptic id/version line with the stage count. - Surface OpenCode form questions as a chat card (chat_answer), replay a pending form to late subscribers, and notify for background questions. - Make the mobile dock's Search cell equal to every destination, keep the tab row visible with 100svh, and let Source use the full pane height. - Let a fresh sign-in auto-connect to its own origin; use a Lax session cookie with Expires so Remember me survives app/link launches. - Keep shipped starters and the skill agnostic: no repository paths, project areas or personal device commands; add Diagnose/Fix and Research starters. - Refresh the installed skill and document the new browser conventions.
This commit is contained in:
+26
-5
@@ -408,8 +408,23 @@ body {
|
||||
padding: 0 var(--space-xs);
|
||||
font-size: 11px;
|
||||
}
|
||||
.dock-row { display: flex; align-items: stretch; gap: 2px; min-width: 0; }
|
||||
.dock-tabs { display: flex; flex: 1 1 auto; min-width: 0; gap: 2px; }
|
||||
/* One equal cell per destination, then one for Search. Subgrid keeps the
|
||||
tablist a real element (and a real ARIA tablist) while its tabs line up with
|
||||
the search cell instead of Search taking a whole flex share of its own. */
|
||||
.dock-row {
|
||||
display: grid;
|
||||
grid-template-columns: repeat(var(--dock-count, 1), minmax(0, 1fr)) minmax(0, 1fr);
|
||||
align-items: stretch;
|
||||
gap: 2px;
|
||||
min-width: 0;
|
||||
}
|
||||
.dock-tabs {
|
||||
display: grid;
|
||||
grid-template-columns: subgrid;
|
||||
grid-column: 1 / span var(--dock-count, 1);
|
||||
min-width: 0;
|
||||
gap: 2px;
|
||||
}
|
||||
|
||||
.dock-item {
|
||||
position: relative;
|
||||
@@ -456,18 +471,20 @@ body {
|
||||
}
|
||||
.dock-badge[hidden] { display: none; }
|
||||
.dock-search {
|
||||
flex: 0 0 56px;
|
||||
min-width: 0;
|
||||
min-height: 48px;
|
||||
display: flex;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
justify-content: center;
|
||||
gap: 2px;
|
||||
padding: 4px 2px;
|
||||
border: 0;
|
||||
border-radius: var(--radius-control);
|
||||
background: transparent;
|
||||
color: var(--color-muted);
|
||||
font-size: 11px;
|
||||
line-height: 14px;
|
||||
}
|
||||
.dock-search .icon { width: var(--icon-list); height: var(--icon-list); }
|
||||
.dock-search[aria-expanded="true"] { background: var(--tint-selected); color: var(--color-text); }
|
||||
@@ -610,8 +627,12 @@ body {
|
||||
|
||||
/* A phone always shows the destination bar; pane collapse is a wide affordance. */
|
||||
@media (max-width: 599px) {
|
||||
/* The small viewport is the one that is actually visible while a phone's
|
||||
browser toolbar is showing. A dynamic-viewport bottom bar can sit under the
|
||||
toolbar until it hides, leaving only the status row on screen. */
|
||||
body,
|
||||
.app-root { height: 100svh; }
|
||||
#listCollapse { display: none; }
|
||||
.dock-tabs { flex: 1 1 auto; }
|
||||
.dock-item,
|
||||
.dock-search { flex: 1 1 0; width: auto; min-width: 0; }
|
||||
.dock-search { width: auto; min-width: 0; }
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user