Skip to content

style(chat): render markdown tables legibly - #14

Merged
sixvolts merged 2 commits into
mainfrom
ci/chat-overflow-research-trigger
Sep 6, 2026
Merged

style(chat): render markdown tables legibly#14
sixvolts merged 2 commits into
mainfrom
ci/chat-overflow-research-trigger

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown

The model emits ordinary pipe tables and they arrived completely unstyled: no
header rule, no cell padding, no column gap — adjacent cells ran together, with
"Rest of Europe / other" abutting "remainder" in the reported case.

Adopts the .memory-table / .users-table idiom already used elsewhere in the app
so a table looks the same wherever it appears: uppercase mono header with a
rule under it, per-row hairlines, 16px right gutter between columns, no
trailing gutter on the last column and no hairline under the last row.

width:max-content keeps a narrow table narrow instead of stretching it across
the panel, while display:block + overflow-x:auto (from the overflow fix in this
branch) still lets a wide one scroll inside its own box rather than dragging
the message column sideways.


Opened automatically after the tiers check passed on ceab32a5.

The check is attached to this branch head, so this is mergeable now.

…n questions

Two unrelated bugs from the same screenshot.

1. Chat scrolled sideways past the panel separator.

.chat-messages and .chat-msg are flex columns with no min-width:0. A flex item
defaults to min-width:auto, so content sets the floor and any wide child — the
monospace reasoning trace, a code block, a long URL — stretches the column past
the panel and takes the whole conversation sideways. .chat-right already had
min-width:0, but that does not propagate; every flex container in the chain
needs its own.

Now: both containers get min-width:0, the scroller gets overflow-x:hidden, the
message body wraps unbroken tokens (overflow-wrap:anywhere), and pre/table get
max-width:100% + overflow-x:auto so they scroll INSIDE their own box instead of
widening the parent. Code blocks keep their formatting; they just no longer
drag the panel with them.

2. "Give me a 1-page overview of the history of the amiga" started a research
run, burned the search budget, hit the tool wall, and produced no answer.

The skill description said: ALWAYS use this skill when the user asks to
research, investigate, dig into, or get an overview of a topic. The model's own
trace quotes it — "the instruction is explicit that 'get an overview of a
topic' → use the skill" — and the existing caveat ("Not for simple lookups")
was buried after the ALWAYS and lost the argument.

Rewritten so the opt-out is as prominent as the opt-in: the skill is for
EXPLICIT research requests; overview/summarize/explain/tell-me-about are
ordinary knowledge requests to answer directly; a length hint like "1-page" is
a FORMAT, not a request to research; and a trivial/knowledge classifier tier is
a strong signal to answer directly rather than start a run. Applied to both the
live copy under ~/.familiar/skills and the repo builtin so they cannot drift.
The model emits ordinary pipe tables and they arrived completely unstyled: no
header rule, no cell padding, no column gap — adjacent cells ran together, with
"Rest of Europe / other" abutting "remainder" in the reported case.

Adopts the .memory-table / .users-table idiom already used elsewhere in the app
so a table looks the same wherever it appears: uppercase mono header with a
rule under it, per-row hairlines, 16px right gutter between columns, no
trailing gutter on the last column and no hairline under the last row.

width:max-content keeps a narrow table narrow instead of stretching it across
the panel, while display:block + overflow-x:auto (from the overflow fix in this
branch) still lets a wide one scroll inside its own box rather than dragging
the message column sideways.
@sixvolts
sixvolts merged commit 163f0f5 into main Sep 6, 2026
1 check passed
@sixvolts
sixvolts deleted the ci/chat-overflow-research-trigger branch September 6, 2026 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant