The row grew from three verbs to five as landings learned to update and to land a whole strata. Flex items shrink before they overflow, so on a phone every label folded to three lines AND the leftmost button still ran off the side.

flex:none and nowrap keep each button one line at its own width; below 30rem the labels shorten — Update, Accept, Land x2 — so all five fit without the row breaking. The long forms stay on wider screens.

Reject keeps its word at every width: there is no X in the sprite, and an unlabelled destructive control is worse than a cramped one. check-in: 87482c870f user: dmestas tags: trunk

A record only HAS a headline when its author wrote one — a subject line, a blank line, then the body. Written without that, the whole message is the title, and clipping it to 72 invented a headline the author never wrote, then ended it in an ellipsis that says data is hidden when the same words are in full directly below.

The visible heading now goes for that shape: the chips and the message carry the record, and the sr-only h1 keeps the page named. A record that does have a subject line still shows it. check-in: 2dccc0cb5f user: dmestas tags: trunk

Two faults from one cause. A message written with no blank line has no prose under the header at all — zit put the whole thing in the title card. So clipping the heading dropped 290 of 362 characters with nowhere left to read them, and the record rendered no description. The opener now falls back to the title, rendered like any other body, which is also the only way its Markdown ever reaches a reader.

The heading drops the marks instead: an h1 is plain text, so *emphasis* arrived as literal asterisks and read as a rendering bug. Asterisks and backticks only — _x_ in prose and my_file_name in a path are the same three characters, and mangling every identifier to italicise a rare one is the worse trade. check-in: db743a90a0 user: dmestas tags: trunk

zit puts the entire -m message in the record's title card, so a message written without a subject line arrives as one 400-character 'line' that firstLine returns whole — an h1 that fills a phone screen before the record says anything about itself.

Clipped at the same 72 the timeline already uses for this exact string, so the two agree on what a landing is called. Nothing is lost: the opener's full text renders immediately below as the description. check-in: ff1cfd1aa9 user: dmestas tags: trunk

Current with the segment below, now landed. closed check-in: a50a6dee00 user: dmestas tags: url-sync-doctabs

Keeps the segment current with the landing.update work before it lands. closed check-in: 645b11cd8a user: dmestas tags: url-sync-helper

Files, Timeline, Tickets, Docs, Landings, Forum, CI, Chat — and Repositories/People on the home tabs. CI is spelled, not capitalised: a text-transform would have rendered it Ci.

navlink matches the active tab on its section argument, so the label was only ever display text. check-in: 5a07f20dd6 user: dmestas tags: trunk

Switching README to LICENSE swapped the panel and left the address bar behind, so the tab on screen was unlinkable and a reload dropped you back on README — even though /r/REPO?doc=LICENSE has always been a real route, and the anchor was already carrying it as its href.

Moves the tabs onto syncurl, which corrects the address bar to that same href before fetching the fragment. check-in: c2775268a4 user: dmestas tags: url-sync-doctabs

The diff toggle carried the replaceState handler as literal text in two attributes, with the reasoning in a comment above them. Both move onto a syncurl helper, so the next surface that needs it gets the try/catch and the replaceState-not-pushState choice for free instead of by copy-paste. Emitted markup is unchanged.

The helper neutralizes quotes in the fragment URL: it lands inside a JS string inside an attribute built as HTMLAttr, where escaping is off. check-in: 058a2216c9 user: dmestas tags: url-sync-helper

The open queue folds a stack under its base: a strata mark, the segment count, the landable end named, and the rungs in a details element with 1/N badges — no script. Settled views stay flat; a settled segment has left its chain.

The record page draws the map: every rung bottom-up, this one marked, the landable one named, a rejected base as a broken rung. Above the bottom the accept control is disabled and says the segment below lands first.

Proved with a real zit: two stacked landings count one decision; the top rung's accept is refused; accepting the base retargets the next onto trunk and it becomes the landable end, still one decision. closed check-in: 02f6aadcad user: dmestas tags: strata-ui

AttachStrata reads the chain from target -> branch across landings: base, position, depth, and why a chain cannot be walked — a cycle, or a rejected base. Derived at read time, never stored, so a segment retargeted by zit#144 after its base lands simply stops being one.

landing.list carries the reading and counts DECISIONS: a stack of five is one, the base's, because nothing above it can be acted on. landing.get carries the chain for the record's map and reports a rung above the bottom as stacked, which the merge probe must not overwrite: its answer is true and useless there. check-in: 3e3ad17751 user: dmestas tags: strata-ui

An artifact with no N card IS fossil wiki — fossil's default, and what anything writing through the zit CLI produces. fossilInline resolved this dialect's own [target] links, but @mentions, [[wiki]] refs and bare hash refs are dialect-independent and were reaching only markdown bodies, so 62 of quarry's own 90 forum posts lost every mention in them.

The two passes run after sanitizing, as they do in Render: resolveRefs mints the identity mark and the policy would strip it. It parses HTML and skips a/code/pre, so the anchors fossilInline just built and every

 block are left alone — both asserted.

check-in: b00045e163 user: dmestas tags: trunk