oficina / docs Public

A document can be renamed, and the list header is one field

Three of Paul's four notes, and they turned out to be one change.

The list header held a search field, a "Search documents" button, a
"Title" field and a "New document" button — four controls, two of them
redundant. The title field could set a name and never correct one,
because nothing in the app could rename a document at all. So removing
it is only defensible alongside the thing that replaces it: the title
is now an editable field on the document's own bar, which is both where
a person is looking when they decide what a document is called and the
only place they can change their mind later.

The search button goes because the field can now answer on its own.
fixtures/live-search.mjs fetches GET /?q=… — the same URL the form
submits to, the same handler, the same template — and swaps in that
response's [docs-results] region. It renders no rows, formats no dates
and holds no copy. The alternative was building the list from the JSON
the palette already uses, which would have put "No documents match",
the recency group labels and the relative-time strings into a bundle,
in twelve locales. Enter still submits for real, so the query still
lands in history; the live update uses replaceState so typing does not.

Renaming is a real <form method="post"> around a real <input>, posting
to a new POST /d/{sqid}/title. It works with no JavaScript: the submit
button that :focus-within reveals posts and 303s back with the new name
in the bar, the tab and <title>. fixtures/title.mjs adds Enter, blur
and Escape on top, and when its fetch fails it submits the form for
real rather than showing a message about it.

The field shows what the server STORED, never what was typed.
title.go's normaliseTitle collapses whitespace runs, turns control
characters and line breaks into spaces, and caps at 200 runes — by
rune, because slicing by byte cuts a multi-byte character in half — and
an empty rename becomes docs.document.untitled. A client that trusted
its own string would show a name the server does not have and go on
showing it until the next reload.

Store.Rename scopes by owner in its WHERE clause, like Get and List, so
a stranger's document is never selected rather than found and refused:
404 for someone else's and 404 for a missing one, spec §4.2. It bumps
UpdatedAt, because the list orders by it and naming a document is
touching it. It does not write to the CRDT, so a collaborator sees the
old name until they reload — stated as a boundary in Store.Rename
rather than left to be discovered.

The File menu's sideways scrollbar was a third thing entirely.
rastrillo's tokens.css deliberately has no `* { box-sizing }` reset —
it says so, and gives the reason — so [docs-menu-item] was content-box
and `inline-size: 100%` plus its padding overflowed every panel by
24px. It showed up on File and only on File because a <button> gets
border-box from the UA stylesheet and an <a> does not, and File is the
one menu that is mostly links. The horizontal scrollbar came from
[docs-menu-items]'s own overflow-y: auto, which forces the other axis
to compute to auto. Nothing here sets overflow-x: hidden; that would
have hidden this one and the next one.

Two new test files, both in the gate. The ordering guard in
live-search.mjs was mutation-tested — removing both sequence checks
turns "a slow earlier response cannot overwrite a newer one" red — and
the second of the two is documented as uncovered by the fake, so the
next person to find it looking spare knows why.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DoVTH3jZqj9svgt2UD9t1p