What we shipped.

v0.23.0 — 2026-09-09

The day has a shape, and now you can see it.

The brief's whole summary was one sentence — "Ten papers on protein structure prediction and diffusion models — ten unread." True, and silent about the one thing that decides how long you spend here. A real day looks like this:

0.89 0.89 0.68 0.67 0.66 0.65 0.64 0.64 0.58 0.53

Two papers that genuinely match, a flat middle of six that only roughly do, and a tail. That shape is where you stop reading, and it is invisible in a list where every row is the same height. It is now ten bars under the deck, in the order the page lists them, each as tall as its paper matches — Peer's own number, the one that already chose the order, so the strip explains the order instead of adding a second opinion to it. A bar is a link to its card; hovering one names the paper and its age.

Not a chart of topics. That was the first idea and the data killed it: across a day's ten papers the concepts the sources hand over are arXiv filing codes ("cs.LG", "quant-ph") and OpenAlex categories that land off-domain often enough to matter — "Thermodynamics" on a diffusion-models paper, "Training (meteorology)" on an RNA one. The terms recurring on two or more papers were two filing codes, "computer science", and the reader's own declared topics read back at them. A chart of that would have been confident nonsense. This one is built only from numbers Peer computed itself.

And it is a chart, not a band. Stretched across the board the bars were 124px wide and 34px tall, ten of them in the accent: a solid orange rule under the deck, which is decoration, which is the one thing this interface does not do. At 12px on a 52px baseline the same ten numbers are a shape you read in one look. The bars are neutral — in this palette the hue is a signal and how well a paper matches is data — and a read paper drops to the hairline tone: spent, still counted.

Zero-based against the day's best, because a bar chart that starts anywhere else is the oldest lie in the genre.

v0.22.0 — 2026-09-09

A byline, and the chart moves to the page you actually open.

The byline said "A. Kalisz, J. Simons +5". Initials are what you set when the column is 40mm wide and paper costs money; on screen they cost the one thing a byline is for, which is recognising the people. The names are now written as they are written, three before it asks to be opened, and the "+5" — which read as a typo rather than a control — is a control that says what it does.

And it says where the first author works. OpenAlex returns an institution with every authorship, inside the authorships field Peer has always fetched whole and read exactly one key out of. "University of Bayreuth" under the names was in the payload the entire time. Same shape of miss as the full text in v0.20.0, found the same way — by reading what was already on the wire.

Peer's chart was on the profile, which is the wrong page. The reading calendar is a habit, and a habit belongs on the page you open every morning, not on the page you visit to change a setting. It is now one component in two sizes: the profile's labelled eighteen weeks, and a bare eight-week strip at the foot of the briefing — after the day's papers, because the brief opens on what there is to read and closes on what has been read. Two copies of a chart became one.

And it works signed out. readItems was a set of booleans, so the only reading history Peer had was /api/read, which answers 401 without a session — on a self-hosted, local-first product, its own chart needed an account. The store now keeps the day each paper was first read, and the chart prefers the server's history and falls back to this browser's. Re-opening a paper next week does not move the day it was read.

Nothing is drawn from nothing: with no reading history the strip renders nothing at all, and the streak is still never counted off invented weeks.

canonicalizeHeading reads one heading at a time, so a paper whose results live in "5.1 Model Comparison Across Budgets", "5.2 O3", "5.3 FK-steering" and "5.4 DPO" had exactly one section bucketed results — "5 Results" itself, a 315-character paragraph saying which subsection discusses what. "5.1" was called *methods*, on the strength of the word "model" in its title. The numbering is the document telling us its own structure and it was being stripped and thrown away: numbered subsections now inherit their parent's bucket, unless their own heading is structural — "5.3 Limitations" under "5 Results" is still limitations.

The results are often in the figures. For a great many papers the running text says "Section 5.1 discusses the comparison" and the finding itself is in a caption Peer had already extracted and was only using to label a picture. A caption can now be quoted as a finding — last, after the paper's own prose, and cited as "Figure 6" rather than "§Results", because it is not a section and should not be dressed as one. Captions are also out of the running text now: they were being read twice, and a caption spliced into a Results section is a sentence the splitter cannot tell from prose.

`body` is a pool. A paper whose headings never say "results" — a maths paper with numbered sections and nothing else — had these blocks empty however good its numbers were. The unclassified sections are the last pool for findings and for method; never introduction or related_work, where a number is somebody else's result or a promise about this one.

Rendered mathematics is not prose. LaTeXML writes every formula twice — the MathML and the TeX it came from — so "d = 3" arrived as "d = 3 d=3", "K" as "K K", and every quote, every figure caption and every line of the paper's body carried it. The TeX half is dropped. What is left of an equation still survives a sentence splitter, so a sentence that is under 62% letters and spaces is no longer quotable, and neither is an algorithm listing's step number.

Together, on the three papers checked: findings 0 → 3, 0 → 1, 3 → 3; method 2 → 2 (both sentences now from the method, not an appendix pointer), 0 → 2. No sentence is quoted under two headings any more.

The reading is version 3. It carries a day-long cache in the reader's browser, so a better summary with the same shape is exactly as invisible as a missing field. The version now moves when the derivation changes, not only when a field does. The figure module's cache key moved with it.

v0.20.0 — 2026-09-07

The paper itself, and a title bar that is drawn.

Peer had the whole paper the entire time. getFullText returns an extracted document — every section, capped at 18k characters each and 90k in total — and buildReading read eight sentences out of it and dropped the rest. A reader who opened a paper Peer could reach saw one figure, an abstract, and a few quoted lines, and then had to leave for the publisher to read the thing. The reading now carries body: every section, in the paper's order, under a new block. It opens with the contents — which is also the honest statement of how much of the paper Peer reached — and where it came from. Long papers open on a click; short ones are simply there. The paper's own words, so it is set in the reading serif at the measure; the mono on that page is Peer's voice and none of this is Peer's.

Paragraphs survive extraction now. stripTags turned every tag into a space and every run of whitespace into one space, so a section arrived as a single four-thousand-character line. That was invisible while the only readers were a sentence splitter and a model. Block closers are a blank line and <br> a single one; headings ask for one line explicitly. One paper went from 14 unbroken sections to 65 paragraphs. A line that is only a step number — LaTeXML renders an algorithm listing one cell per line — is dropped.

The reading document is version 2. It has a version gate for exactly this reason, read by both the localStorage cache and the response check, and a document written by an older build is now discarded rather than half-read.

The masthead was the last surface without an edge. Transparent at rest, three sans words and one boxed ? floating on the ground with nothing holding them, while everything under it had become hairlines. It has the hairline at rest now; the glass still arrives on scroll, background only, so the height never changes. The nav is mono with the separators the rest of the machine's lines use — one row rather than three words with air between them — and the ? lost its chip and joined it. The wordmark stays in the display serif: the product's own name is the one thing in that bar that is not the machine talking. The nav at the top and the key legend at the foot of the reading page are now the same object at the two edges of the window.

v0.19.0 — 2026-09-07

TUI.

Peer was a soft-UI product: rounded slabs floating on cast shadows, bevelled top edges, a lift under the pointer, Inter for everything the machine says. The direction now is a terminal — drawn, square, keyboard-first, dense — and most of it turned out to be four values.

Nothing is round. Tailwind compiles its whole radius scale from eight variables; they are all zero now, and the one radius it does not take from a variable — rounded-full — is squared by a single rule beside them. 170 rounded-* classes across the product changed without one of them being touched. Put the eight values back and the shape returns exactly.

A card is drawn, not floated. --shadow-card was a rim, a contact shadow, a cast shadow, an ambient shadow and two bevels. It is one hairline now, and the only thing that happens under a pointer is that the hairline gets brighter — no lift, no press-below. The input well, carved with two inset shadows, is a box you type inside. Held, a card's frame takes the hue: a terminal has no depth to press into, what it has is a selected row.

The machine speaks mono; the paper speaks serif. The reading page's own labels — the section names, the record, the footers, the commands — are in Roboto Mono. The paper's title, its claim and its sentences stay in Newsreader. The rule is not new; it is the one the stylesheet already stated for prose, applied in the other direction.

Sections are bands. A name in mono on the rule it starts, running the width of the column: The claim ────, The abstract ────, How it was done ────. The 22px serif headings are gone — a landmark down the column is now the rule, which is the width of the column, rather than a bigger line of the same colour. The claim's band label carries the one accent on the page.

Commands are named by their key. [o] Open on arXiv ↗, [s] Save, [x] Skip, [c] Copy — the key first, in mono, because on this page the key is the interface and the button is its shadow. Three of the icons added yesterday are gone with the change: a bookmark beside "Save" said nothing the word did not. The one that stayed marks a destination.

The legend. Every key the reading page answers to, on one line along the foot of the screen: j next · k prev · s save · x skip · l like · u undo · o open · c copy · esc briefing. Peer had nine keys here and was telling the reader about the four that also have buttons. It is generated from PAPER_KEYS — the table the keyboard layer and the help sheet already read — so it cannot describe a key that does not exist. Nothing on it is clickable; it is a legend, not a toolbar. Desktop only: a phone has no keyboard and already has the thumb bar.

v0.18.0 — 2026-09-07

The reading page gets a shape.

Without a key the page was an abstract and nothing else: eleven lines of body text at one size, two of them in ink, and under them half a screen of nothing. Everything on it was true and none of it was *arranged* — no second place for the eye to land after the title, no edges between one thing and the next, and on a wide screen a 1032px strip of page with 450px of black on either side.

The claim is lifted. When a model has read the paper, Peer's skim already sits above the abstract as a deck, and the ink below moves to the sentences that are its evidence. Tier 0 now does the same with the paper's own words: the claim sentence — the one the ink was already choosing — is set at display size above the abstract, and its ink is dropped from the abstract below, so exactly one thing on the page is loud and nothing is emphasised twice. It carries the one accent mark on the page: a short rule, because this is the only line on a reading page that Peer chose rather than the paper.

The column has bands. Every block heading now carries the hairline above it, so "How it was done", "Where it is thin" and the rest read as sections with edges instead of as one column of text with bigger lines in it.

The record. A new block, last and always present: published date in full (the page had only "3w ago"), the venue, and every other door the paper has — the publisher's page, Scholar, and the authors' code. A repository was the worst of the omissions, because it is the part of a paper a reader can actually run, and the decision block opens exactly one link.

The end of the paper is a place. The next paper was a 12.5px label over a 19.5px title, the quietest thing on a page that ends early. It is now a band: a rule above it, the title at heading size, and an arrow that travels a couple of pixels under a pointer.

Marks on the actions. Open, save, skip, copy and the DOI line each carry one stroke, drawn at the line's own size so the icon reads as punctuation rather than as an object.

The measure stops growing at 2xl. A line does not get wider because the window did. Above 1536px the reading column is fixed at 560px and every extra pixel goes to the panel, so a wide screen buys a bigger figure and a title with more room. The spread itself is 1200px there rather than 1032.

Also: a figure caption is prose, so it breaks at a word — "…seed samples (top row), sh…" was cut at the character it happened to fall on.

Thirteen sizes between 22px and 52px, typed as literals at 2px intervals, so no two pages agreed on how big a page title is — the briefing said 40, saved said 38, the profile said 44, the changelog said 44 with no small step at all. A continuum is not a scale. There are now five display steps on a ~1.19 ratio, with fixed roles: a section heading inside a page, a panel heading, a page title on a phone, a page title on a desktop, and a cover statement. Every heading in the product is one of them, every page title is now the same size, and the six stray sizes below 20px (9px, 11px, 12px, 18px, 19px) are back on the nine steps that were already there. Nothing types a font size any more.

The plate stops shouting the filing label. When a paper has no figure and no term of its own, the plate used to set the venue and the year in display italic — "Zenodo / 2026", "arXiv / 2026", "Journal of Artificial Intellig…" — which is the meta row directly below it, repeated at three times the size, and truncated mid-word when it did not fit. Display type is the loudest thing on a card; it should not be the one line the reader has already read. Those papers now have no plate at all: the card opens on its own title, and the reading page with it. A quieter paper gets a quieter card. Terms longer than the plate's first line are dropped rather than truncated, so display type never breaks mid-word again.

v0.16.3 — 2026-09-07

The last two hues.

Auditing the deployed stylesheet rather than the source turned up two more colours the greyscale pass had not reached, and they were hiding in different ways than the literals in v0.16.2. The DeepSeek caution note on the AI-key panel was bordered in amber-500 — Tailwind's own palette, which is always there to be reached for and owes nothing to Peer's tokens; a caution is the accent's job now. And --done-light / --done-dark, the blue completion seeds, were still declared on every accent theme after --color-done went grey — dead weight that a grep for the palette still found, because it was still in the CSS.

An audit of the build now reports no colour outside the six accent seeds.

v0.16.2 — 2026-09-07

Eleven colours the palette could not reach.

The greyscale pass changed the tokens, and eleven rings and shadows on the profile and the AI-key panel were not written in tokens — they were typed as raw rgba(185,28,28…), rgba(194,99,14…), rgba(217,122,48…): the old red, the old burnt amber, the old peach. They kept their hue while everything around them lost it, which is exactly the failure a token system exists to prevent, and it survived a release because the values are literals no palette grep would find — they turned up in the deployed stylesheet, not the source. Each is now the ring of the token its element already uses. Nothing hued is hard-coded in a component any more.

v0.16.1 — 2026-09-07

A little material.

Greyscale removed the colour that used to carry the surfaces, and left flat fields behind. What replaces it is light: the interface now has a grain, an edge and a direction.

Grain. A fine tileable noise on the ground and on every card. The ground's is fixed to the viewport, so it stays put under the scroll the way paper does rather than sliding with the content. It is deliberately faint — the tile is mid-grey with a noisy alpha, so it lightens a dark surface and darkens a light one, and at any strength where the texture is obvious on a #1d1d1d card the same tile is a grey veil over a white one. Tooth, not tint. (The ground had a grain already; it was near-black noise, which on #111 was a texture nobody could see.)

An edge. A card catches the light along its top edge and loses it along the bottom, so it reads as a slab with thickness instead of a lighter rectangle.

A cut mat. The figure sits *in* its mat now, not on it: the inset catches on the window's top and left, where a light from the upper left would leave it.

A press. Pressing a card puts it a pixel below where it started, with the cast shadow collapsed to contact and a shallow well under the top edge. A thing under a finger does not merely stop rising.

v0.16.0 — 2026-09-07

Greyscale, and one hue.

Peer was a warm ivory system: every neutral carried a little of the accent and a little more of a warm brown, and the interface answered in six or seven colours — burnt amber tags, peach chips, a green relevance ramp, a blue completion state, a red for failure. Now every neutral is a true grey and the accent is the only coloured thing on any screen, which is what lets it read as a signal instead of as decoration.

The greys are the old values. Each one is the exact lightness of the warm colour it replaces, converted through OKLab with the chroma set to zero, so every contrast the layouts were built on is unchanged and only the hue is gone. Light is a #fafafa ground with white cards — sheets on a table, where before the cards sat darker than the page; dark is #111 with #1d1d1d cards.

What used to arrive in colour. Tags and the profile's signal ramp step down through the greys instead of through amber and peach. Failure states, links and relevance take the accent — a monochrome interface that keeps a second alarm colour has two accents, and the louder one is the one the eye learns to ignore. The one place two states must stay apart is the swipe: keeping is the accent, letting go is ink.

The card. A mat exists to hold a picture. Six cards in ten have no figure, and on those the mat was the brightest object on the page with two words in it — a placeholder wearing a composition's clothes, and worse once the warmth was gone. A figure is still matted, because scientific figures are drawn on white and matting is what stops a chart losing its axis labels to a crop. Type is not: it sits on the card's own surface, at its own proportion rather than a photograph's 16:9, and the numbering that reads "01" beside a lone term is gone — numbering says "several, in an order", and one term is neither. The venue and age line was the last small-caps label in the product; it is sentence case now, in the mono the reading page uses for the same fact.

v0.15.0 — 2026-09-07

The briefing ranks by relevance.

Today's ten opened with two protein-structure papers and then, from the fifth card on, an art installation about diffusion models, a paper on the C/O ratios of Uranus, 3D duet singing animation, and pitch-class steering for music generation. Every one of them had earned its place: they say "diffusion models", and the ranking could not tell them apart from the reader's own field. Measured against a labelled copy of the day's forty candidates — kept in scoring/__fixtures__ so this stays measurable — twenty-four were strangers.

Relevance was outweighed by age. The score was 0.35 keyword + 0.30 TF-IDF + 0.20 recency + 0.15 source, which reads as relevance-first and behaved as recency-first. The keyword term was the same 0.667 for twenty-eight of thirty papers — it counts how many of your topics a paper mentions, not how much it is about them. TF-IDF was the only term that discriminated, and the cosine of two short documents lives around 0.01–0.35, so weighted at 0.30 it could move a score by 0.1 while recency moved it by 0.17. Relevance is now scored against the rest of the day's pool, where the number means something, and leads: 0.55 topicality, 0.30 keyword, 0.10 recency, 0.05 source.

A mention is not a subject. Two papers matched "protein structure prediction" on one sentence apiece — "generative modeling, which has transformed prediction in fields as diverse as weather forecasting and protein structure prediction, holds the potential to forecast earthquake aftershocks" — and that name-drop, counting as a full second topic match, ranked an earthquake paper with the day's real protein work. A match is now weighed by where it falls: title, tags, said repeatedly, or said once in passing. It still counts; it no longer counts the same.

A daily briefing carries news. The reader's freshness window reaches the source queries, but Semantic Scholar's search takes no date parameter and answers with the field's classics: the 2000 PSIPRED paper and the 2020 AlphaFold paper were both in a pool built for today. Nothing caught them afterwards — they stayed out of the briefing only because age outweighed relevance, so the moment relevance was allowed to lead, they led. There is a stated ceiling now, generous about the window (60 days for a reader on "week") and applied both where the pool is built and where it is read, since a pool outlives the request that built it.

Today's briefing, after: six straight papers on protein structure prediction, then diffusion-model work, and the first stranger at card seven instead of card five. Nothing in it is older than three weeks.

v0.14.1 — 2026-09-07

The briefing opens with a dateline.

The page used to start with two lines of small print — the masthead's "Monday, September 7 · 10 papers · 9 unread" and a mono "matching diffusion models, protein structure prediction · synced 4m ago": a status bar where a front page should be. Now the date is the headline, in serif at display size, and everything those lines said is one sentence of reading type under it — "Ten papers on diffusion models and protein structure prediction — nine unread." — with the unread phrase in ink, the one part that changes as the day is read. When everything is read it says so: "all read, back tomorrow." While the day loads it names what it is looking for. The sync state and the refresh button are the only small item, at the right of the headline, because they are status; a failed load is still red there.

The masthead's centre is empty on the briefing, so the day is stated once. On a phone the nameplate sits above the dateline; the mono day line is gone.

v0.14.0 — 2026-09-07

The masthead.

One line of chrome. The 208px sidebar, its floating toggle, the two top-right pills and the phone's row of tabs are replaced by a 48px masthead across the top of every page but the welcome wizard: the Peer wordmark at the left, the day's state on the window's centre line — "Sunday, September 7 · 10 papers · 9 unread" — and Search · Saved · Profile and a ? keycap at the right. It is transparent at the top of the page and takes its glass once the page has scrolled; its height never changes, so nothing on the page moves. Content uses the whole window: the board and the reading spread centre in it, and no page slides sideways any more.

The rail is the masthead. On a paper the centre reads "← Briefing · 3 of 10 · k j", and the two keycaps are the previous and next buttons. The in-content rail is gone, so there is one position counter, and it is always on screen. A deep link shows the way back alone.

The day is stated once. The briefing page's header — date, count, unread, rendered again 208px to the left in the sidebar — is now the masthead's. The page keeps one line under it: the topics it matched and when it synced, with the refresh button at the right; a failed load still says so in red. Before the day's fetch lands the masthead states only the date — the store does not know a count yet, and "0 papers" would have been a claim.

A thumb bar on the phone. Below 768px the shell is a 56px bar at the bottom, in reach: Today, Search, Saved, You, each a 22px icon over a label and well over 44px tall; Saved carries its count when there is one. On a paper the bar is the rail — "← Briefing · 3 of 10 · Next →" — the first way to move on from a paper without judging it. The briefing's top is the wordmark and the day line, which scroll away; the reading page has no top chrome at all, so the plate is the first thing on screen. The page keeps a bottom padding the height of the bar, so the bar never covers the decision.

`/` is honest. From any page it goes to Search and focuses the box; on Search it focuses in place (on a phone the box waits to be tapped, so the keyboard does not rise over the page). It used to look for a box that exists on one route. The dead "g /" the sidebar advertised, the \ sidebar toggle and the help sheet's "View" group are gone; the help sheet's headings are sentence case — Anywhere, Navigate, Briefing, Reading — and its foot reads "Peer 0.14.0 · What's new", the first link to the changelog the app has had.

Account on the You page. Sign in with GitHub, and Sign out, live in an Account section at the top of /profile, shown only when Supabase is configured; signed in, the masthead's "Profile" is the avatar. The GitHub star counter and its hourly fetch are deleted, with the floating pills, the sidebar's persisted open/closed state, the uppercase "SUN · SEP 7" and "V0.13.2", and the undo toast's uppercase label. The undo toast and the copy toast keep fixed corners and sit above the thumb bar on a phone.

v0.13.2 — 2026-09-06

The reading spread.

A paper's page uses the width. From 1280px the page is two columns: the plate, the title and the decision on the left, under the eye; the paper's words and Peer's additions on the right, in a column no wider than a line should be. The left panel stays put while the reader scrolls — when a reading or a model lands, it lands in the right column, and the decision does not move. The spread stops growing at 1352px; on a wider display it sits on the desk with ground either side. Read still means decided: on the spread the decision is on screen at open, so a paper is read when the end of its words has been on screen for a second, not the decision. Phones and tablets are unchanged.

v0.13.1 — 2026-09-06

Keys, swipe, and read-means-decided.

Keys on a paper. j ] → and k [ ← move through today's briefing in its order; s saves, x skips to the next paper (the Undo toast and u restore it), l likes, o and Enter open the source, c copies the page as Markdown, Esc and Backspace return to the briefing. One table (PAPER_KEYS) drives the handler and the help sheet's new "Reading" group. The briefing's own keys are untouched. Arrows never take a live text selection — Shift+Arrow extends one, and a plain arrow on a selection is the reader adjusting it.

Swipe on the plate. On a phone the plate is the card's swipe object: right saves, left marks not interested and advances. Touch and pen only, the same thresholds as the card, pan-y so the page still scrolls. A skip keeps the reader mounted through the fly-out — the dismissed paper is read from the pending dismissal until the route changes, so no loading mat flashes and no request fires for a paper just dismissed.

Read means decided. Opening a paper no longer marks it read. It is read when the Decision block has been on screen for a second, or on any decision — save, skip, like, open, copy, next. A record-only page is therefore read on open; u un-reads.

Assistive technology. The reading article takes focus after a client navigation, so j/k announce the new paper. The authors line keeps the names as its accessible name ("A. Jumper, B. Evans +9, Show 9 more") instead of replacing them. Keycap chips inside buttons are hidden from screen readers ("Save", not "Saves"). The DOI line says it copies and has a 44px touch target; the copy toast's live region is always in the DOM so it is announced. The plate and its caption are a real figure/figcaption.

v0.13.0 — 2026-09-06

The reading surface.

/papers/[id] is rewritten as a reading sheet in a fixed order the reader learns once: rail · plate · title and meta · the paper's own words · the decision · Peer's additions · next in briefing. Nothing on it is invented.

The paper's words. The abstract as written, in its two paragraphs, with the claim and the numbers set in ink; the rest muted. No heading is put over an abstract sentence. A paper with no abstract shows the record and, when Semantic Scholar has one, its TLDR labelled as machine-written.

One sentence about what Peer read. "Abstract only. Method, caveats and what it means for your project need the full text and a key." — or the full text's source and page count, the paywall host, or the plain statement that the PDF is there and only a self-hosted Peer reads it. Every string comes from one table (describeAvailability); none is typed in JSX. The recommendation line under the authors is the briefing's own reason, never the deep-link placeholder a paper resolved by id carries, and never the reranker's generic fill-in.

Model blocks with receipts. With a key, each block is prose whose every claim carries the paper's own sentence: an ink mark when the sentence is in the abstract, a quiet quote with its section heading when it is not. When the reader turned deep reports on and the model still read the abstract alone, the sentence names the wall (paywalled, unreadable here, unfound, or the deep step not finishing) instead of telling them to turn on a setting they already turned on. A model that was asked and could not finish says so.

Copy as Markdown. Frontmatter with the basis the text was read from, the abstract with the marks in bold, every quote with its heading, a "Not on this page" list generated from the typed omissions, and a BibTeX block. A reader who ran the model is never told a block "needs a key".

A PDF's section names arrive in capitals ("MATERIALS AND METHODS"); the attribution sets them in title case for display and export — the shouting is typesetting, not meaning, and the page has no other capitals.

Deleted. The Surface route and its model, the six-pill action row and the Cite modal, the scroll progress bar, ScrambleText, the icon section titles, "At a glance", "Explore further", "More like this", keyword chips, the pull-quote of the scoring string, "Why it fits you", "Related from your feed", the skeletons and shimmer bars, the tier-upgrade block, and every fabricated-report path behind them. The plate figure is resolved once per paper for the card, the page and the caption line together.

v0.12.4 — 2026-09-06

A reading per paper, and evidence-verified reports.

`GET /api/papers/[id]/reading`. The deterministic reading, built server- side from the record and the full text with no profile and no key, so it is one document per paper for every reader and is cached for a day. A full-text attempt that times out answers no-store and is not kept.

Every claim carries a verbatim sentence. The report prompts ask for an evidence sentence copied character-for-character from the abstract (Tier 1) or the full text (Tier 2), and verifyReportEvidence drops — never flags — any claim whose sentence is not in the text the model was given. Drops are counted and shown. The relation to the reader's project is asked for only when the profile has one. At the abstract tier no figure is kept: nothing bound it, so a URL the model emitted is not the paper's; the sanitizer keeps only https and PDF-rendered data images.

Vercel reads no PDFs, and says so. The PDF text extractor is traced into the reading and report functions. Where no interpreter can be spawned, or the helper is missing, the extractor reports a machine reason (no-python, no-extractor) and the reading maps either to "the PDF is there, but only a self-hosted Peer reads PDFs" — never "no full text". The extractor also reports the document's real page count rather than the number of pages it read: a 50-page paper was being called "a 40-page PDF" because 40 is the reading cap.

v0.12.3 — 2026-09-06

The deterministic reading.

reading.ts builds the sheet the reading page shows before, and without, a model: the abstract split into sentences with pickSkimMarks choosing the claim and the numbers; up to three verbatim findings from the results section carrying a number or a comparison; two method sentences; the authors' own limitations, else the hedges in the discussion. Each quote carries the heading it came from. Absence is typed (omitted), never faked.

Provenance. ExtractedDocument.pageCount reaches the reading; a Semantic Scholar TLDR is carried as tldr, labelled, and no longer becomes the abstract; reviewPaperLabel reads the title only. The old fallback report — "Main result", "Key result 2", "Overview / Section N", invented fit reasons — is deleted; the one report without a model is emptyReport.

v0.12.2 — 2026-09-06

Full text reaches Peer again.

Three of today's ten papers could not be read past their abstract for reasons that had nothing to do with access. Fixed on the way to the reading-surface work:

arXiv's own HTML. arXiv has rendered LaTeX submissions at arxiv.org/html/<id> since late 2023, but Peer only knew ar5iv, which now answers recent ids with a redirect to the abstract stub. The native render is tried first (263 ms for a 38,000-character paper). The LaTeXML parser also stopped truncating any section that has subsections: it matched <section>…</section> non-greedily, so "4 Evaluation" ended at the first nested close and 4.4 Results and 4.5 Limitations were lost. It slices between consecutive headings of any level instead, and captures the abstract.

A `limitations` bucket. Heading canonicalisation stripped one leading number, so "4.4 Results" became "body", and no bucket existed for the one section a reader most wants quoted. Numbering of every shape is stripped now, and Limitations / Threats to Validity / caveats have their own bucket. The Python PDF extractor mirrors it.

Zenodo. A Zenodo DOI resolves to a landing page whose "Description" is long enough to pass the full-text check, so the record page was being read as the paper. The records API lists the deposited PDF; it is a source now, ranked above every HTML fallback, and the full-text check requires a recognisable body section or several long ones rather than one long block.

Macs. The PDF extractor shelled out to python, then py -3. macOS ships neither — only python3 — so every PDF on a Mac quietly yielded nothing. python3 is tried first, after PYTHON_BIN when it is set.

Captions. Labels read "Figure Figure1"; tables were labelled as figures; LaTeXML subfigure fragments — "(a) Original image", three of every four captions on a typical page — were emitted as captions of their own. One parser serves all four extractors.

Verified live against real papers: arXiv 2609.02697 (HTML: 16 sections including Limitations, labelled captions), arXiv 2609.02113 (no HTML render; PDF via python3), and today's Zenodo preprint (deposited PDF: Abstract, Introduction, Related Work, Methodology, Results, Discussion, Conclusion). 30 new tests.

v0.12.1 — 2026-09-06

An empty briefing says why.

The empty screen was one block of caption-size text — "Your briefing is still waking up… Set up profile" — shown for every reason the grid could be empty. The screenshot that prompted this was a dead dev server: the fetch failed, fetchRealFeed swallowed the failure into an empty list, and a reader with two topics configured was told to set up their profile under a header that read "synced just now".

Three reasons, three screens. No topics: "What are you working on?" with a real Set up profile button. Sources unreachable: "Couldn't reach the paper sources." with Try again (the underlying error sits on the button's tooltip) and Edit topics, and the header reads "sync failed" in red instead of a sync time. Nothing new: "Nothing new for these topics today." with Refresh and Widen topics. Display serif at 28px, one line of body copy, buttons from the shared button primitive; no caption-size instructions. The block sits in the header's column rather than floating in the middle of the page.

The store records failure. feedError is set when the papers lane throws and cleared at the start of the next load. A failed load no longer stamps lastRefresh, so the header cannot read "synced just now" over an error. The flag is transient — not persisted — so a reload starts clean. Which screen to show is a pure function (emptyReason) with tests.

Also: before the first load the header read "synced not synced yet". It reads "not synced yet".

Verified in the browser: no topics (cleared in storage), nothing new (ten x presses dismissed the whole briefing, no reload fired), sources unreachable (/api/feed rejected at the fetch layer, then r), and recovery — Try again with the network restored brought ten papers back and cleared the red header.

v0.12.0 — 2026-09-06

The touchscreen drives the briefing.

The other half of the principle from v0.11.0: on a phone the interface is the finger, not a row of small buttons. Peer's only touch provision was a media query that forced the three icon buttons permanently visible — the phone got the small-button interface the whole series has been removing.

Swipe a card. Right saves (or unsaves — the reveal says which); left marks it not interested and the card flies out, with the usual Undo toast. The reveal under the card fades in with progress, the card follows the finger and rubber-bands past the threshold, a short drag snaps back, and a completed drag swallows the click that follows it so a swipe never also opens the paper. Commit is 96px or a fast flick in the same direction; a flick back toward the origin cancels.

Only touch and pen. A mouse has hover and the keyboard layer, and a mouse-drag on a link fights text selection. touch-action: pan-y leaves vertical scrolling to the browser; the card only takes a drag once it has locked to the horizontal axis, so a diagonal scroll never moves it.

The buttons are for assistive technology now. On touch devices they stay in the DOM — VoiceOver and switch users navigate by control, not by gesture — but leave the visual.

The gesture arithmetic (axis lock, resistance, commit) is a pure module with tests. The pointer-capture call is guarded: an inactive pointer id throws, and the drag works without capture.

Also fixed on the way: the card's Save button called an idempotent save on every click, so its "Unsave" state re-saved. It toggles now, the same branch the keyboard's s and the swipe use.

Verified with synthesised touch pointer events against the live handlers: right 160px saves and the header counts it, the click after a swipe does not navigate, 40px snaps back, left 160px removes the card and Undo restores it. A physical-finger pass is still owed — the preview pane was not compositing when the real drag was attempted.

v0.11.0 — 2026-09-06

The keyboard drives the briefing.

The designer's principle: on a PC the interface is the keyboard, on a phone it is the touchscreen; a product should not depend on small on-screen buttons. Peer did. The keyboard layer carried only global shortcuts — go-to chords, search, refresh, undo — and not one card-level action, so the only way to save, dismiss or like a paper on a desktop was the three hover-revealed icons.

Card-level keys, on the briefing: j / k (or the arrow keys) move a focus ring between papers in reading order; Enter or o opens the focused paper; s saves or unsaves it; x marks it not interested (the existing u undoes); l asks for more like it. Esc clears the ring. The ? help sheet lists them under a new Paper group.

The ring is painted as a DOM attribute and the index kept in a ref, so moving between ten cards re-renders nothing; the card list is read from the DOM on each press, in document order — which in a CSS-columns masonry is the column-major reading order j/k should follow. The focused card shows its actions as if hovered. After x the ring stays in place and the next paper slides under it.

Also: the g x chord still routed to the persona quiz, which left the nav in v0.8.0. Removed.

Touch is the other half of the principle and is next: swipe right to save, swipe left to dismiss, with the buttons reduced to an assistive-technology fallback on touch devices.

v0.10.1 — 2026-09-06

The loading skeleton catches up with the card.

It still drew the card from three releases ago: a single 820px column, a kind badge and score chip up top, a 3px accent stripe, three body lines, and a hairline footer with three action buttons. Every one of those has since left the real card, so the load-in was a jump cut from one layout to another.

It now mirrors what renders: a three-column masonry the width of the feed, each placeholder a cover card — a 16:9 plate on top (every real card carries one), then meta, a serif-height title of one to three lines, two or three skim lines, an author line. No buttons; the real ones are hidden at rest. Line counts vary per card so the masonry is a masonry before the data arrives, and the cards arrive with the same reading-order stagger the real ones use.

The component is shared with search, which already prints its own "searching…" status; the "Brewing your daily briefing" header is a prop now and search passes none, so the two messages no longer stack.

v0.10.0 — 2026-09-05

Peer is a paper briefing. Events and jobs are gone from the product.

The founders' verdict, verbatim: "先拿掉 event 和 job 我们 focus 在 paper". This release removes every user-facing surface for the two once-a-year verticals. The library code underneath (lib/events, lib/jobs, lib/opportunities) stays for one more release — see the last paragraph.

Removed. The /events and /jobs routes and their detail pages; the /api/events/*, /api/jobs/feed and /api/jobs/report routes; the Events and Jobs entries in the sidebar and mobile bar; the Events and Jobs topic lists on the profile page and in onboarding; the Locations and Work rights profile fields (both existed to filter jobs); the onboarding "Work rights" step — the wizard is seven steps, not eight, and no longer asks for visa status before research topics; the Adzuna and USAJobs connectors, which existed only to widen job coverage. Tavily stays, described as what it now is: optional web discovery for papers.

Saved is a shelf. It carried Papers / Events / Jobs segments and a To-do / Done rail for applications and registrations; its own comment admitted papers "have no completion action" and sat in To-do forever. It is a list of saved papers now.

The daily surface never asks for the other lanes. loadFeed defaults to ["papers"]. The feed tile and the report page's "Related from your feed" list are paper-only, which severs the last paper-side import of lib/opportunities/facets from a rendered surface.

Dead code swept. Deleting the consumers orphaned the event/job report kit (ReportSection, WhyPeerSentThis, timeline, fact tiles, badges), five UI primitives that only the event and job cards used, the dashboard and deadlines board, the visa country picker, the surface-topics composer, the feed "more" tile, the onboarding tour, and the decorative logo halftone. Seventeen test files went with their subjects, including the 1,725-line typography test that asserted Georgia point sizes for the job and event reports. 66 files, −16,801 lines.

Kept on purpose. /api/jobs/dispatch-digests — "jobs" as in cron jobs. It is the daily email entry point, its URL is pinned in .github/workflows/digest-cron.yml, and renaming a production cron endpoint has no product benefit.

Still to do — the library. lib/events, lib/jobs and lib/opportunities are now unreferenced by any product surface but cannot be deleted wholesale: the paper pipeline imports five files from lib/opportunities (shared, pool-cache, pool-cache-runtime, page-fetch, facets), and the event/job fields remain on UserProfile, in the feed store, in /api/profile's column map and in the Supabase schema. That is a separate, deliberate extraction.

v0.9.4 — 2026-09-05

The feed card is a cover card.

The left stripe is gone. The 3px accent rail on every card's left edge encoded paper / event / job on a mixed feed. On a papers-only feed it was the same mark on every card — decoration, and the same kind of chrome the rest of this series has been removing.

The plate bleeds. It used to sit inset inside the card with padding around it and a radius of its own, which reads as "a box with an image in it". It now runs to the top edge and takes the card's own corners, and the text block below it has real air.

The title is set in the display serif. It is the specimen's name, and it now shares a typeface with the terms on the plate above it — plate and title read as one typographic system. Sans is reserved for labels: the venue line and the authors. The footer hairline is gone; spacing separates.

The mat is under both fills, with its own ink. The off-white mat from v0.9.2 had never actually reached the browser (see below), and once it did the typographic plate's near-white type vanished on it. The plate now has its own ink tokens, relative to the mat rather than the card: on dark, dark warm ink on off-white; on light, the ordinary text colours on a 4% tint. Figure and type sit on the same ground, which is what makes the two fills read as one slot.

Infra note: Turbopack's persistent dev cache in .next/dev was serving a compile from before the latest globals.css edit, and a restart re-read the cache rather than the file — each restart was one edit behind. Clearing .next/dev fixed it.

v0.9.3 — 2026-09-05

The sidebar is the spine of a daily ritual, not a list of pages.

Today is the primary object. The one thing that changes every day — the date, how many papers came, how many are unread — now sits at the top of the sidebar as a block, and that block is the Feed link. "SAT · SEP 5 / Today 10 / 10 unread", and when everything is read, "all read · back tomorrow".

Frequency is visible. Search and Saved are reading tools and sit as plain rows. Events and Jobs sit under their own quiet OCCASIONAL label at a lighter weight; a once-a-year need should not look like a daily one. This is the same hierarchy the home page encodes, carried into the nav. Profile is anchored to the bottom.

The active state is a rail that travels. The active nav item used to be a card — bg-surface shadow-card, the same elevation as a content card — which put chrome and content on one level. It is now a 2px accent rail that slides to wherever you went, positioned from the DOM in a layout effect and written back as CSS variables, so moving it never re-renders anything.

Chrome is quieter. Six keyboard-shortcut hints were permanently on screen; they now appear only for the row under the pointer or keyboard focus. The footer — three unrelated things in a bordered strip — is one line: a sync dot, a single ? key, the version.

Also: the Events and Jobs page headers read "0 jobsin today's pool" — JSX swallowed the space after an expression. Template literals now.

v0.9.2 — 2026-09-05

Every card has a plate.

The window is universal. Roughly four papers in ten yield an extractable figure, and "some have an image and some don't" was the loudest thing wrong with the feed. There is now one 16:9 window on every card, at the same offset, always filled. When the extractor finds the paper's own figure, the figure fills it. When it does not, the window holds the paper's own terms set in the display serif over a numbered grid, closed by a rule. Two fills, one slot.

The terms are the paper's, and they are checked. The source field is matchedKeywords ∪ tags, which is hostile in two directions: matchedKeywords ARE the reader's required topics, so unfiltered they would put the reader's own query on all ten plates; tags are OpenAlex concepts, which mis-disambiguate often enough to matter — a live protein-structure briefing carried "Generative grammar" and "Representation (politics)". Allocation now runs once across the whole briefing and a term must survive four gates: it is not the reader's own topic (or a substring of one), it is not an arXiv filing code, it is long enough to set at display size, and it appears somewhere in the paper's own title or abstract. That last gate is what removes mis-disambiguations: a concept the paper never mentions is not a concept the paper is about. No term may headline more than two cards.

Figures are matted, not bled. object-contain on a mat rather than object-cover, because cropping a scientific figure destroys its axis labels. On dark themes the mat is off-white, so a white-ground chart reads as paper instead of glaring like a lightbox, and a colour figure keeps its colours.

v0.9.1 — 2026-09-05

Elevation and motion.

The shadows were soft-UI, and soft-UI cannot work here. Neumorphism reads as extrusion only when the object and its ground are the same material and the ground is a mid-tone that can travel both ways. The dark families have no such ground — bg and surface sit about four points of L* apart — so the highlight had been cut to 4% opacity and the pair had degenerated into one 16px black smudge with no contact edge. Hover made it worse: blur went 16px to 26px and black 45% to 60%, so a card went *softer* under the pointer instead of lifting.

Replaced with three layers doing three jobs: a 1px rim for separation, whose contrast is anchored to the surface so it stops depending on how dark the ground is; a short-offset contact layer; and a wide ambient layer with heavy negative spread, which is what keeps a 26px blur from becoming fog.

Motion. Cards now arrive staggered in reading order — the plumbing had been in globals.css all along and the feed had never used it, so all ten faded up on one frame, which reads as the page reflowing rather than as a delivery. Figures cross-fade in instead of being inserted. The 500ms hover zoom on figures is gone; a Ken Burns on a scientific plot reads as an advertisement and scales the axis labels.

Thirty icon buttons at rest. Ten cards each showed three. The action row keeps its footprint but appears for the card under the pointer, and stays permanently visible on touch, on keyboard focus, and on a card whose state is already on.

A read paper stays readable. The read state was a blanket 70% opacity over the whole card, which faded the title and the summary and, on dark, dragged the card toward the background. Only the cover recedes now.

Figures that cannot be shown no longer leave a hole. Finding a figure URL is not the same as being able to display it — biorxiv answered 401 for every one. Sending no referrer fixes those, and anything still failing drops its cover rather than reserving an empty 16:9 box.

v0.9.0 — 2026-09-05

The briefing has pictures, and ten different papers in it.

Papers show their own figures. Peer has always had a rule-based figure extractor and a route built for exactly this — /api/figure's own header reads "hit per-card after feed loads" — and no card had ever called it. The feed was ten identical blocks of text.

It was also looking in the wrong place: the extractor asked ar5iv alone, and ar5iv now serves a stub for recent preprints. Measured across seven papers from one briefing, ar5iv returned "no figures" for every one while arxiv.org/html carried 26 <figure> elements for the same ids. arXiv's own rendering is tried first now, with ar5iv kept as the fallback for older papers it still covers. Extraction is pure scraping with no model call, so figures appear on a deployment with no credentials configured.

The grid is masonry. Roughly four papers in ten carry an extractable figure, so card heights genuinely differ. A fixed grid either ragged-edged every row or reserved dead space on the six cards without an image.

One researcher can no longer take the whole briefing. A live feed showed six of ten slots held by the same author, all from the same repository. diversify caps per topic, and its key is the first three title tokens — "Graph Neural Networks for Protein Structure Prediction" and "Quantum Machine Learning Protein Structure Prediction" hash differently, so the cap never fired. There is now a per-author cap of two.

Worse, that pass had never run at all for most users: it sat behind requestedTier >= 1 while the client only ever sends 0 or 2. It is deterministic local computation — no model, no network — so it now runs at every tier, which is where PRODUCT_DIRECTION's Tier 0 floor puts it.

Card text says what the paper found. The skim line was summaryIntro, the first one or two sentences of the abstract, which in a paper is the motivation and reads identically across a field: three cards in one briefing opened with three ways of saying protein structure prediction is hard. Everything that distinguished them sat unread in summaryResultDiscussion. The line is now chosen from the whole abstract, preferring sentences that carry a claim or a quantity and avoiding both boilerplate openers and sentences whose reference dangles once lifted out of context.

v0.8.2 — 2026-09-04

Feed card: the hierarchy now encodes something.

The three loudest slots on a card all held information that was identical across the whole briefing, while the one field that separated two papers was in the smallest, faintest, most truncated line.

- The "PAPER" badge is gone — on a papers-only feed it said nothing, and it said it twice: paper.source repeated it at the bottom of every card as the literal string "other", which is what that six-value enum ("arxiv" | four ML conferences | "other") returns for everything outside those venues. - The match percentage is gone. It spanned 59–64% across the ten cards and occupied the top-right corner. Papers have no relevance floor, so it could not be used to choose between them either. - "Why you · <topics>" is gone from the card. Its first entry was the reader's own required topic echoed back, on every card; the remaining entries were OpenAlex concept tags that frequently landed in the wrong domain ("Representation (politics)" on a protein-structure paper). Its deduplication was case-sensitive, so one card read "protein structure prediction, Protein structure prediction, Protein structure". The statement it was trying to make is true of the whole briefing, so it now appears once, in the page header. - Venue and age lead instead, which is what actually differs: "Scientific Reports · 8d ago" against "Zenodo · 6d ago". The published date was already on every paper and had never been shown. - Venue drops the host institution. OpenAlex returns "Zenodo (CERN European Organization for Nuclear Research)"; at card width that truncated mid-word and pushed the date off the line entirely. - The kind badge still appears for a Discussion, so a forum thread is never mistaken for peer-reviewed work. That was the badge's real job.

v0.8.1 — 2026-09-04

Removing things that were not true.

The contribution calendar was inventing data. When the real per-day reading API returned nothing — which is every signed-out visitor, and any fetch error — the grid fell back to synthesizeActivity(), a seeded pseudo-random fill derived from the total activity count, and gave each invented cell a tooltip reading "N interactions". The streak badge counted those invented weeks. For a demo shown to signed-out visitors this presented fabricated numbers as the user's own history. The function is deleted; with no real data the panel now says so.

The persona quiz no longer claims to shape your feed. Onboarding said "It helps shape your feed". Its stored result has exactly two readers — the quiz's own hydration and an onboarding checkmark — and reaches neither the feed, scoring, nor reports. The copy now says what is true.

The onboarding tour no longer has a step that cannot fire. Step 3 spotlighted [data-tour="highlights"], an attribute no element carries, so it was silently skipped and the counter jumped 2/4 to 4/4.

`/api/test-digest` is development-only. It runs the full feed pipeline and sends an email while bypassing digest_enabled, frequency and time-of-day, and was reachable by any signed-in caller on a deployed instance.

Paper titles are legible immediately. The feed card wrapped every title and summary in a ~600ms character-scramble reveal — a delay applied to the exact text the reader came for.

Dead code. The unused DailyDigest panel and its loading progress bar are gone; only the headless PaperDigestLoader was ever mounted.

v0.8.0 — 2026-09-04

The daily surface is papers, and only papers.

The home page. The default landing tab was dashboard — a metrics page containing zero items of content: four count tiles (Papers today / Events today / Jobs today / You saved), a 14-day arrival-volume chart, a "what you're holding" tracker, a topic-coverage panel and a deadlines board. All removed. The home page is now the briefing: how many papers arrived, how many are unread, when it last synced, and the papers.

Papers, events and jobs are no longer peers. They were concatenated into one list, sorted by relevance score alone, and written into one grid — so a job posting scoring 0.81 outranked a paper scoring 0.79 and occupied an identical cell. Events moved to /events, jobs to /jobs. They also no longer run on every home-page tick: loadFeed takes a lanes option and the daily surface asks for ["papers"]. The progress bar labelled "Finding today's papers" was 30% driven by conference scrapers and job boards.

Manual controls left the automatic feed. The feed route carried eleven composers exposing fourteen typeable fields. Typing two characters into the search box deleted the briefing outright. Search now lives at /search; the briefing is untouched by anything done there.

Credentials have a home. The AI-provider key, deep-report toggle and Data-API keys had no section on /profile at all — they lived only in the one-time /welcome wizard and pinned permanently to the feed, which is why the feed page ended up doubling as the settings page. They are on /profile now.

Also. Persona left the primary nav (its quiz result is read by nothing). The sidebar version string is read from one constant instead of being hardcoded in JSX, where it had drifted to v0.1.0 while this file reached v0.7.22.

Versioning is 0.x.y until v1; y for fixes/chore, x for features.

---

Two passes on profile UX.

(1) Visual cleanup of `/profile`. Removed the "READER" eyebrow label above the user's name in the identity band (no info, pure decoration); deleted the entire dashboard-card footer (Tuning any time kicker + Adjust signals → button) which was a third redundant entry point to edit mode alongside the header Edit pill and inline adjust link; shortened the long Either — surprise me industry label to Either so the career caption no longer overflows the row with PhD Year 3 · Either · School / Lab; hid the Reading card's Shareable reader card footer (two disabled Copy card / PNG buttons next to a "Coming soon" badge — features not built yet, so dead UI removed); fixed the header signal counter from 0 of 5 → 0 of 4 to match the four visible SignalRow entries (the previous count included preferredMethods which has no editor anywhere).

(2) AppearanceCard rewrite — instant-apply + 4 new themes. Killed the draft-state + Select color / Cancel two-step confirm pattern — clicking a theme card now applies immediately via the existing updateColorTheme store action. Header dropped the redundant right-side System pill and the "Switch palettes directly here. No edit mode required." filler subtitle. Cards dropped the redundant Cream palette / Black palette body lines and the gray "almost-checked" icon on unselected cards (now: only the selected card shows the orange check). Picker restructured: themes are tagged with a mode: "auto" | "light" | "dark" in colorThemeOptions and rendered as three labeled groups — Auto (System), Light (Cream / White / Pink / Blue + new Sage / Lavender), Dark (Black + new Slate / Plum). Grid is grid-cols-3 lg:grid-cols-6 per group so light themes fit one row on desktop.

Four new themes ship with full token sets (bg / bg-secondary / surface / surface-hover / border × 2 / heading / text × 3 / accent / link / tag / peach / yellow × 2 / red / skeleton × 2) in both globals.css (declarative [data-color-theme="X"] blocks) and lib/theme.ts (runtime inline-style overrides). Sage: pale green paper #eff4ea with deep-teal #0f766e accent and olive #65a30d tag. Lavender: soft purple #f5f3fc with violet #7c3aed accent and fuchsia #c026d3 tag. Slate: GitHub-dark inspired #0d1117 with sky-blue #58a6ff accent and mint #56d364 tag. Plum: deep #1a0e1f with light-violet #c084fc accent and pink #f0abfc tag.

(3) Venue badges follow the theme. search-result-card.tsx previously hardcoded four hex colors for source-type badges (#b32f2f arXiv red, #2d6a8a journal blue, #7a4ec1 conference purple, #1f7a4d open-access green). Replaced with theme tokens — arXiv → accent, Journal → link, Conference → tag, Open Access → peach — so the four badges remain mutually distinguishable but the palette now shifts with the active theme. Cleanup also removed three orphan helpers in profile/page.tsx (previewColorTheme, IconPalette, IconShare / IconDownload) and the now-unused applyColorTheme import. File shrunk 2484 → ~2360 lines.

New mode on the paper detail page: a Surface button in the ActionRow (alongside Save / Cite / Like) links to /papers/[id]/surface, which renders the paper as a structured working canvas instead of a long-form report. The route is backed by lib/papers/surface-model.ts (498 lines) which derives a set of SurfaceCell entries from Paper + UserProfile — title, key facts, format detection via FORMAT_TERMS, method detection via 21 METHOD_PATTERNS regexes, reading-time at 220 wpm, tag extraction capped at 8 — and components/papers/paper-thinking-surface.tsx (627 lines) which lays the cells out as a focused workspace. The surface renders in an intentionally isolated dark palette (hardcoded CSS vars on the component, does not follow the app color theme) for distraction-light reading; this is by design — switching the app theme should not change the working canvas.

Codex pattern step 2 — pulling the briefing status into the search-input cluster so the box reads as a stateful command surface, not a blank prompt. BriefingStatus moved out of the page header into the search section, where it now sits as a rounded-full pill directly above the rounded-3xl input box (mb-2 gap, no longer the previous 24px header margin) so the two surfaces feel like one connected unit. Restyled the pill content: small accent dot at the left (the "● live" indicator pattern Codex uses for ongoing context), inline counts (87 items · 12 unread), synced-age suffix, and a new refresh icon button on the right that calls loadFeed and spins while in flight — same handler the FeedMoreTile already uses, so the affordance is now reachable from the top of the page too. Closed state ("Briefing closed · all N reviewed · back tomorrow") uses the same pill chrome with an accent-tinted fill instead of the previous heavier bg-accent-dim block. Secondary text (synced 2m ago, the reviewed-count tail) hides below the sm breakpoint so the pill stays single-line on phone. Pure UI; no change to feed loading, refresh semantics, or briefingItems shape.

The three loading cards on Discovery were rendering as flat dark rectangles with no internal structure on the black theme (and system in dark mode). Root cause: .skeleton-shimmer was a hardcoded rgba(24, 24, 27, 0.04 → 0.10) overlay — dark ink on dark surface, so the four inner placeholder bars per card were technically present but visually black-on-black. The user just saw three empty boxes while the feed loaded for 2-3s.

Fix in two passes. (1) Theme-aware shimmer — introduced --color-skeleton-base / --color-skeleton-highlight tokens, defined per theme: dark-ink overlays on cream / white / pink / blue / light-system (0.05 → 0.12 opacity), light-ink overlays on black and dark-system. .skeleton-shimmer now interpolates these via CSS vars, so the same component reads correctly on every palette. Added a prefers-reduced-motion branch that drops the animation and renders a static tint. (2) Skeleton structure — rewrote LoadingSkeleton in components/ui.tsx to mirror the real PaperTile: top-left accent stripe (matches KindStripe), two-pill header row (badge + score chip), two-line title with varied widths, one-line author/venue, three-line relevance reason, and a footer with source label + three icon buttons separated by a top border. Each of the three cards gets slightly different line widths (86/72/92% etc) so the stack reads as distinct papers rather than three identical bars. A small "Brewing your daily briefing" status with a pulse + ping dot sits above the cards as a one-line activity signal. Staggered animate-fade-in-up (0/90/180ms) replaces the previous bare drop-in.

Codex-inspired follow-up to v0.7.13. Three changes. (1) Surface weight — corner radius bumped from rounded-2xl to rounded-3xl, added a 1px border on the cream theme token plus a layered close/far shadow that thickens on focus-within, so the bar reads as one elevated object rather than a flat card. (2) Send action — new accent-orange circular send button on the right of the tools row; click or Enter skips the 400ms auto-search debounce and fires the request immediately, with a spinning glyph during flight and a disabled cream state below 2 chars. (3) Two-zone tools row — the four existing pill controls (AI search / AI key / Deep report / Tavily) now sit in a left "modes" zone with the send button on the right, giving the bar a clear left-to-right rhythm (what to use → go) instead of a single wrapping pill row. Bonus: the clear text button shrank to a small × icon inside the input. No behavior change to any pill or expanded panel — pure UI pass.

Daily-briefing first paint felt slow because /api/feed was averaging 4.4s end-to-end with constant [openalex] 400, [semantic-scholar] 429, [pubmed] 429 spam in the server logs. Root causes were stacked: (1) every source fanned out 4–6 generated queries sequentially with an 8s per-call timeout, so one slow query stalled the whole source; (2) no 429 backoff anywhere — semantic-scholar and pubmed just gave up and moved on, but only after eating their full quota of attempts; (3) OpenAlex 400s came from punctuation in the generated phrases ({}[]:; from phrasesFromText leaking through to the search= param); (4) Tavily discovery was awaited *before* source fetch even started, adding a serial 1–2s; (5) Promise.allSettled over sources had no outer wall, so one hung source could drag the response past 10s.

Five-front fix in one pass. (A) OpenAlex search terms are now sanitized (strip "!?{}()[]\\^~*:; and unbalanced quotes), with the response body logged on non-ok so a future 400 is debuggable in one read. (B) New shared sourceFetch helper (lib/sources/_fetch.ts) wraps every academic-source HTTP call with one 429-aware retry that honors Retry-After (capped at 1.5s), plus a tighter per-call timeout (6s instead of 7–8s). (C) Pipeline now kicks off runTavilyDiscovery in parallel with source fetch via Promise.all instead of awaiting it first — Tavily still feeds connectorStats but its boost queries no longer block the critical path. (D) Per-source query fan-out capped (openalex/arxiv/s2: 6 → 3, pubmed: 3 → 2, dblp: 4 → 2) and queries run in parallel inside each source via Promise.allSettled, so a source's wall time is now max(query) instead of sum(queries). (E) New withSourceTimeout race in feed/pipeline.ts enforces an 8s hard wall per source so a hung adapter can't drag the whole response. Plus a defensive type-coerce in cleanDisplayText so a non-string field (e.g. dblp returning year as number) no longer throws text.replace is not a function mid-map.

Measured end-to-end via three repeated curl POSTs to /api/feed with {topics:["large language models","retrieval augmented generation","graph neural networks"]}: cold 2.7s, warm 0.65–0.69s, all five sources returning items (openalex:30, semantic_scholar:10, arxiv:30, dblp:30, pubmed:27), zero errors entries in the response meta.

filtersToApiQuery was emitting OpenAlex-native params directly (sort=cited_by_count:desc, filter=open_access.is_oa:true,cited_by_count:>10), but /api/papers/search reads app-level keys (sort ∈ relevance|cited|newest, plus oa, cites, from, to, src, venue) and composes the OpenAlex filter= clause server-side. The mismatch meant every chip in the FilterBar updated state and the URL fine, but the request that left the browser carried params the server didn't recognize — results came back identical to an unfiltered search. Rewired the helper to emit the app-level keys the route actually reads. End-to-end verified: sort=cited&cites=100&oa=1 now returns highly-cited open-access works (75k+ citations vs. the relevance baseline's 29k).

Some paper-detail summaries contained long unbreakable tokens (concatenated DOIs, sequence IDs, undbroken acronyms) that pushed the right edge of the body card past the viewport on phones, clipping the last word and giving the impression that the page itself was scrolling sideways. Two-layer fix: overflow-x: hidden on body so no descendant ever drags the page wider than the viewport, and break-words on the report-row body paragraph so within the card the text wraps even at unbreakable strings instead of being clipped at a flush right edge.

MetaRow was sitting in its own beige-ish card (bg-bg-secondary/35 rounded-xl) and rendering up to seven topic / method / venue chips, which on most profiles wrapped onto two lines and added a third visual block under the greeting. Dropped the card surface entirely so the row reads as inline text — Tuned for label + chips + a smaller pencil edit affordance — and capped visible chips at five with a quiet +N overflow indicator. Chip dimensions trimmed (h-6 → h-5, 11.5px → 11px, tighter padding) so five fit on one row at typical viewport widths. Tone alphas eased from /100 to /70 so chips read as soft signals rather than hard tags. The row's role unchanged — clicking it still goes to /profile and the empty-state CTA still surfaces when no topics are set.

Reworked the top of the Discovery page from a heavy stack — big editorial greeting + a search input + three side-by-side AUTO SEARCH / AI KEY HOOKUP / TAVILY HOOK cards — into one cohesive command bar that mirrors how a chat-style input organizes its modal tools. The search input and three controls now share a single rounded surface: input on top, a row of compact tool pills below (Auto/AI search, AI key, Tavily), and an inline expanded settings panel that reveals only when a pill is clicked. Single-tool-open semantics (one shared openTool state) replaced the two independent aiProviderOpen / tavilyOpen booleans, so toggling between AI key and Tavily settings no longer leaves both expanded at once. Active state on each pill keeps a subtle accent tint when a non-default value is set so users can see at a glance which tools are customized. Greeting headline drops from 36/44px to 26/32px and the date row from 21/24px to 14/15px — the page now opens with a confident statement of state rather than a banner that dominates the first viewport. Same applies to the Search-mode title (34/38px → 24/28px). All wiring (loadFeed gating, profile updates, Tier display, helper copy, gating-by-aiPaperSearchEnabled) preserved.

Paper detail (/papers/[id]) tightened up on phone-sized viewports across four fronts. (1) Action row — Read paper plus Save / Cite / Like / Not interested previously stacked into 2–3 wrapped rows because every pill was h-11 with pl-3.5 pr-4 text-[13.5px]; now they collapse to h-9 / px-3 / 12.5px on mobile and the primary CTA drops a half-step too (h-10 / px-4 / 13.5px), so the whole action set sits two rows max on a 375px screen. Desktop sizing unchanged. (2) Stats strip — PropertyStrip keeps its 2-col mobile grid but the gap shrinks (gap-x-3 gap-y-3 vs 5 / 4) so the six properties feel less marooned. (3) Method/result figures — compact and hero PaperFigureFrame variants now cap height on mobile (max-h-[300px] / max-h-[360px]) and lower the min-h floor a notch, so a square pie chart no longer eats half the viewport. object-contain keeps proportions; sm:max-h-none drops the cap above mobile. (4) Article container — px-6 py-14 becomes px-4 sm:px-6 py-10 sm:py-14, reclaiming 16px of horizontal space and trimming an extra 32px of empty top padding on phones. Reading flow gets noticeably calmer below the fold; nothing changes on tablet/desktop.

The fixed top-3 right-3 z-[55] UserMenu / GithubStars wrapper in app/layout.tsx lived above (z-wise) the mobile top bar (z-50), so on narrow viewports the right-side Saved / Persona / Profile tabs sat directly underneath the "Aspen Labs" pill + GitHub-star pill and were unreachable — only Feed was visible. The previous mobile-polish pass (v0.7.10) tightened the nav padding which reduced the unintended margin and made the collision suddenly very obvious. Fix: scope the floating wrapper to hidden lg:flex so it only renders on desktop, and inline <UserMenu compact /> inside the mobile nav at the right edge so signed-in users still get the avatar + sign-out, signed-out users still get the GitHub sign-in CTA. Layout on mobile now: [Logo] [Tabs justified to the right of the logo] [UserMenu]. Tab font dropped one notch (13 → 12.5px) and active-underline geometry tightened to keep all four tabs comfortable next to the avatar on a 375px viewport.

Mobile top bar tightened — height drops from 56px to 48px, horizontal padding from 24px to 16px, the brand wordmark hides on the narrowest phones (logo alone serves as home), and the active tab now gets a 2px accent underline so the current section is obvious at a glance instead of relying purely on weight/color shifts. Tab gap shrunk so all four tabs fit comfortably alongside the brand on a 375px viewport with breathing room left over. <main> top padding adjusted to match the new bar height. Daily-digest header buttons collapse to icon-only on mobile (Regenerate / Listen labels reappear at sm+) and the section's horizontal padding eases from 28px → 20px on small screens, reclaiming text width without crowding content. Feed tile summaries (paper / event / job) bumped from 12.5px → 13.5px on mobile with slightly looser line-height for single-column readability; desktop sizing unchanged so dense grid stays dense.

/persona already advertised "Saved locally only — not uploaded" in the result footer, but the quiz result lived in component useState only — close the tab or refresh and it was gone, so the footer's promise was a lie. Persist now: on completion the scores are written to localStorage under peer:persona:v1, on next mount the page hydrates from there and re-derives the persona via pickPersona (rather than caching the persona blob, so future tweaks to persona names / blurbs / portraits surface automatically). Retake clears the storage. SSR-safe (typeof window guards), tolerant of quota/private-mode failures (silent fall-through to a fresh quiz). Sync to the server profile is a separate follow-up tied to the auth track.

The contribution-style calendar on /profile was always rendering blank cells even when read_items had data. /api/read?aggregate=daily groups reads by toISOString().slice(0,10) (UTC YYYY-MM-DD), but useDailyActivityCells was building its lookup keys from a Date set to *local* midnight then formatted via toISOString() — which yields the UTC string of local-midnight, off by a day for any non-UTC user. Reads timestamped late local-evening (= early next-UTC-day) bucketed under tomorrow's key on the server but were looked up under today's key on the client — every cell missed, calendar stayed empty. Switched the client to setUTCHours(0,0,0,0) and millisecond-arithmetic day stepping so both sides agree on day boundaries.

Two unrelated bugs were taking the production deploy down. (1) applyColorTheme was calling Object.entries(themeVars[theme]) without guarding for the case where theme is undefined — which it was for every existing user, because the profiles.color_theme column declared in schema.sql had never actually been applied to the live DB. The throw bubbled up through React render and Chrome surfaced "This page couldn't load". Added a defensive if (!vars) return so unknown / missing themes silently fall back to the CSS defaults instead of crashing the tree. (2) /api/read was upserting into read_items to refresh read_at on repeat reads, but the table had no UPDATE RLS policy — so the conflict-resolution path always failed with "new row violates row-level security policy". Added the missing users update own reads policy (USING + WITH CHECK on auth.uid() = user_id), matching the pattern already used by saved_items. Schema source-of-truth in web/supabase/schema.sql updated to keep parity. The profiles.color_theme schema drift remains — that's a separate auth/Supabase-track follow-up; the defensive code makes it non-blocking.

Result page goes from a stacked column to a two-column editorial layout — portrait (with cream gradient frame, soft shadow, italic "Profile sketch" caption) sticks to the left on desktop, the title / tagline / blurb / look / axes flow on the right at a comfortable reading width. Title bumps to 52px Instrument Serif, tagline gets italic Source Serif, "Spotted at the conference like" header now sits between hairline rules — a touch more magazine, less form-result. Mobile collapses cleanly to a single column. Two additional portraits seeded: lab-lead.png and synthesist.png. Five remaining slots open.

Quiz results now always land on one of the 10 curated PAIR personas (or the flat-profile Polymath fallback). The 10 SOLO names — "The Bench Operator", "The Theorist", "The Polymath" (specialist-pole), "The Builder", "The Provocateur", etc. — were a mid-state fallback for users whose top-two combo wasn't in the curated set, but they had no portraits and felt like a "you're not really any of these" cul-de-sac. Removed. New pickPersona scores all 10 PAIRs by alignment with the user's axis values (sign-aware sum of the two pole projections) and picks the highest-fit one — so a Generalist+Solo profile, which previously fell to "The Polymath" SOLO, now lands on whichever curated PAIR best matches that direction (typically Synthesist or Field Crosser). 11 possible outcomes total (10 PAIRs + flat Polymath), every named result has a slot for a portrait. Renamed the misseeded bench-operator.png → bench-builder.png since the visual fits Bench Builder perfectly and Bench Operator no longer exists as a result.

The /persona result now renders a portrait above the persona title. Convention is purely file-system based — drop a PNG at web/public/persona/<slug>.png (slug = persona name, lowercased, leading "The" stripped, non-alphanumerics → dashes — so bench-operator.png, theoretical-provocateur.png, group-builder.png, etc.) and it appears next deploy. No code change needed per persona; missing images render nothing (the <img> errors silently). Seeded the first two from existing references — Bench Operator and Group Builder.

Two things in one. (1) The /persona quiz that v0.7.0 announced was never actually committed — web/src/app/persona/, web/src/components/persona/, and web/src/lib/persona/ only existed locally and Vercel had no idea about them. Tracked all of them now (same fix shape as v0.7.1 — other agent's WIP wasn't git added). (2) Added a look field to every Persona — concrete MBTI-style appearance for all 10 curated PAIR_NAMES, all 10 SOLO_NAMES (with poles having distinct visuals: e.g. The Bench Operator gets "olive flannel, top-knot, dead-project sticker laptop, coffee, anti-glamour"), and the Polymath flat fallback. New "Spotted at the conference like" section on the result page renders the look as an italicized accent-bordered pull-quote between the blurb and the axes bars. Same data, more recognizable.

The Affiliation row in the profile editor splits into two fields. School / org is now an autocomplete-backed input — type to filter ~150 curated entries (top global research universities, CMU/MIT/Oxford/Tsinghua/etc. + industry research labs like Anthropic, DeepMind, FAIR), with substring highlighting on the matched portion, ↑/↓/Enter/Tab keyboard nav, and free-text fallback for anything not in the list. Lab / group is a separate plain-text field below for the unit within the org (CSAIL, HCI Group, Vision Lab, your advisor's group). Both are persisted on the profiles row and surface in the read view as MIT / CSAIL. New lab column on profiles table; schema.sql + the /api/profile mapping updated to round-trip.

Production deploys had been failing since v0.6.8 — the search filter feature committed page.tsx imports for @/components/search/filter-bar, @/components/search/filter-chip, @/components/search/more-filters-panel, and @/lib/search/filters, but the directories themselves were never git added. They existed locally and worked in dev but Vercel's clean checkout couldn't resolve the imports → every commit since v0.6.8 returned the old deploy. Added the four missing files (752 lines) so the production build succeeds and v0.6.9–v0.6.14 actually reach users.

A short forced-choice quiz that maps a researcher across five continuous axes — Empirical ↔ Theoretical, Specialist ↔ Generalist, Solo ↔ Collaborative, Builder ↔ Critic, Formal ↔ Narrative — and names a persona from the two strongest signals (e.g. "The Theoretical Provocateur", "The Bench Specialist", "The Synthesist"). Jung-style multi-dimensional rather than MBTI's 16 boxes: every axis is a value in [-1, +1], not a category, and the persona name reflects a combination, not a verdict. 15 questions, 3 per axis, no Likert middle ground. Result card shows axis bars with score markers, a tagline, and a prose blurb in the editorial serif. Saved locally only — no upload. Accessible from the sidebar (or g x). First step toward the broader "input your paper, get an academic style profile" feature; URL/PDF analysis comes next, this seeds the framework.

PaperFigure was forcing every figure into a fixed 16:8 (hero) or 16:9 (compact) frame with object-cover, which silently cropped portrait charts, square diagrams, and any landscape figure with a different ratio. The container now starts at the variant's default aspect (skeleton state only), then on onLoad reads naturalWidth / naturalHeight from the image and sets the container's aspect-ratio to match. Image switches to object-contain so it always fits, and a transition: aspect-ratio 300ms smooths the resize when the natural aspect arrives. A max-h-[80vh] cap prevents extreme portrait images from dominating the viewport. Net effect: every figure renders at its true proportions, nothing gets cropped.

Adds an Affiliation field (school / lab / company) to the profile editor, persisted as a new school column on profiles. Improves first-run by stopping the editor from pre-seeding battery-research demo topics — defaultProfile.researchTopics and preferredVenues are now empty arrays so the profile-setup nudge in the header surfaces immediately. The Topics, Methods, and Venues ChipInputs gained quick-add suggestion rows ("Try: + transformers + RAG + diffusion models …") shown only when the field is empty, and Topics carries an inline hint reminding people specificity matters (a single word like "whatever" matches nothing useful — we just shipped a fix for that exact case in v0.6.12). Schema.sql + the /api/profile mapping updated together so the new column round-trips cleanly.

Three weak spots on the paper detail page got a pass. (1) "At a glance" Signal chips used a binary ✓/× toggle that read awkwardly — Older paper × was double-negation, and On arXiv × for a non-arXiv paper just wasted a slot. Replaced with a new FactChip that only surfaces facts when they're present: Preprint on arXiv (accent), Code available (tag), a relative-time chip (23 days ago / 2 years ago), and a smarter team-size label (Solo author / 3 authors · small team / 12 authors · large team). (2) "Explore further" link chips now carry a leading icon per destination (document for publisher, mortarboard for Google Scholar, code-brackets for source/search code) so the row is scannable at a glance instead of three near-identical pills. (3) The lonely "Train my feed on this" button at the bottom got a clearer label (More like this) and a co-located one-line explainer so it reads as an action, not a stranded chip.

The feed store had a realPapers.length > 0 ? realPapers : mockPapers fallback that silently surfaced battery-research demo fixtures (with hardcoded "your PhD"-style relevance reasons) whenever the real API returned 0 results — for example when the user typed a topic with a typo like transfomer. Events and Jobs were even worse: always wired to mockEvents / mockJobs because no real adapters exist yet. Removed both fallbacks. Empty source = empty feed; the FeedMoreTile already shows a context-aware "Tune your signals" prompt when topics under-deliver, so a real empty state is more honest and more actionable than fake content.

Feed grid cards now carry a category-specific line icon next to the kind label (Paper / Discussion / Event / Job) and a thin colored stripe on the left edge for at-a-glance scanning. Inline mini-icons attach to metadata: author for papers, calendar + pin/globe for events, building + pin/globe for jobs. The redesign keeps the same density and serif/sans typography rhythm — purely a scannability pass, no content moved.

Search cards now read more like Airbnb listings than a database dump. Each card gets a colored type badge (arXiv, Journal, Conference) and an Open Access badge with icons; venue and date sit on a single meta row with calendar/book glyphs; the citation count moves to a quiet footer separator with its own icon and is humanized (12.4k cited instead of 12,432 cited). Title shifted to line-clamp-3 so longer paper titles breathe; abstract switches to the editorial serif at 13.5px for scannable reading. Result counter at the top no longer surfaces the raw OpenAlex universe size — it just shows how many results are visible (e.g. 12 results for "transformer"), which fits the triage use case far better than 12 of 4,567,890. Search API now returns sourceType and isOpenAccess to drive the badges.

Two fixes for the "many paper links are wrong" complaint. (1) The OpenAlex adapter now requests best_oa_location and open_access and prefers, in order: an OA PDF → an OA landing page → the DOI URL → the OpenAlex page itself. Result: papers with a free PDF on arXiv / institutional repository / publisher OA channel surface that link instead of a paywalled DOI redirect. (2) When OpenAlex returns an arXiv preprint via the 10.48550/arxiv.* DOI prefix, the mapper detects it, swaps the URL to a clean https://arxiv.org/abs/<id>, populates linkArxiv, and renames the venue from "arXiv (Cornell University)" to plain "arXiv". The detail page CTA correctly says "Read on arXiv" again for these.

OpenAlex search now exposes the dimensions that actually matter for relevance triage. A chip row appears under the search bar in search mode (year preset or custom range, sort by relevance/citations/date, open-access toggle, min-citations threshold), with source-type and venue search behind a "More filters" inline drawer. State syncs to the URL so a filtered search is shareable and back-button safe; opening a shared link rehydrates every filter. Reset link clears all non-default filters in one click. Daily feed unchanged — filters only render in search mode.

Added a context-aware action tile to the last cell of the homepage grid. Detects three states and adapts copy:

- Profile under-tuned (placeholder topics like Whatever, idk, or single short word) → "Tune your signals" + link to /profile. Short-circuits the most common reason for a sparse feed. - Sparse but tuned (< 4 items) → "Light today" + Refresh button. - Plenty → "More?" + Refresh button.

Replaces the loose "Refresh recommendations" link below the grid; collapses two affordances into one tile that lives where the eye lands. Visual differentiation: dashed border, no shadow — reads as an action, not content.

HN posts share the Paper data model (and "Papers" tab) with arXiv/OpenAlex items, which made a Show HN thread visually identical to a real publication. The FeedTile now uses an allowlist of academic id prefixes (arxiv:*, openalex:*) to decide which items get the orange "Paper" badge — anything else renders as a muted "Discussion" badge. Allowlist over blocklist on purpose: future non-academic adapters (Twitter, Substack, etc.) default to "Discussion" until explicitly opted in. (A separate Discussions tab is the obvious next step if this surface keeps growing.)

HN posts link to arbitrary external URLs (GitHub repos, personal blogs, corporate sites). The og:image on those is rarely a meaningful representation of the discussion — usually a generic social preview, repo card, or logo banner. The detail page was loading these as the hero figure, which felt wrong. Now extractFigure returns null for any hn:* item id; the figure component's hideOnMiss collapses gracefully. Cache-bust param bumped v=2 → v=3 so existing CDN entries refresh.

Three bugs surfaced from a Show HN paper detail view: (1) abstracts arrived with HTML entities (/ ') and <p> tags un-decoded — added decodeHtmlEntities + stripHtml in the mapper before splitting; (2) HN system tags (story, front_page, show_hn, author_*, story_*) were polluting "Methods & techniques" — now filtered out via isUsefulKeyword; (3) primary CTA was hardcoded "Read on arXiv" — now source-aware (Read on Hacker News / Read on arXiv / fallback Search arXiv).

Replaced the 3-tier briefing layout (hero + "Worth your time" + "Quick hits") with a single dense card grid that scales 1 → 2 → 3 → 4 columns from mobile through xl. New <FeedTile /> compact card — tighter padding, two-line title, kind badge + relevance %, single-tap save action. Container widens from 820px to 1280px so wide screens actually use the space; header (greeting, search, type tabs) stays narrow-centered for reading rhythm. Search results adopt the same grid.

Added a server-rendered page that reads public/CHANGELOG.md, parses the version/date/title/body structure, and renders entries in the editorial brand style (Instrument Serif headlines, Source Serif body, accent-orange version tags). 1-min revalidate so a markdown push lands on the live site without a redeploy. Raw markdown still served verbatim at /CHANGELOG.md for the curious.

Backfilled past releases from git log and seeded an ongoing release log. From here on, every user-facing/infra commit adds an entry.

Replaced the removed Vercel cron with .github/workflows/digest-cron.yml. Triggers /api/jobs/dispatch-digests every hour at :05 with bearer auth via the CRON_SECRET repo secret. Free, preserves per-user timezone hour preference (Vercel Hobby plan rejected hourly cron).

Removed web/vercel.json. Hobby plan rejected the 0 * * * * schedule, blocking every deploy after v0.5.0. Cron re-added externally in v0.6.0.

.mcp.json excluded from repo. Local-only tooling config, never product code.

Resend wrapper with lazy init + branded HTML/plaintext/subject templates (Gmail-friendly table layout, escapes user-derived fields) + /api/test-digest self-send endpoint. Gracefully degrades when RESEND_API_KEY is missing — in-app inbox keeps working.

Server-side persistence for saved items, read items, feedback signals, and digest deliveries. New RLS-scoped tables: saved_items, read_items, feedback_events, briefing_deliveries. Profile gets 5 digest preference columns (timezone, hour, channel, frequency, enabled). API routes: /api/{saved,read,feedback,briefings} + cron /api/jobs/dispatch-digests. <FeedSync /> bridges local Zustand ↔ cloud on auth state change. Profile page adds digest preferences UI, Past Briefings inbox, and a reading calendar driven by real per-day read counts.

Profile data persists via Supabase profiles table (was localStorage-only). User menu floats top-right.

Sign-in with GitHub via Supabase Auth. Top-right pill shows the project's live GitHub star count.

Search results route to internal briefing detail page; encoded-colon route param decoded correctly; "Loading briefing…" replaced with a shimmer skeleton.

/api/feed returns scored items from the Tier 0 pipeline; replaces sample data fixture.

Briefing surface treats items as a persistent reading list rather than an ephemeral feed.

Combined keyword / TF-IDF / recency / source-weight scoring. Source adapters for OpenAlex, arXiv, Hacker News. Wired into /api/feed. Profile redesigned as editorial dashboard with reading stats. Briefing feed redesigned with hero + quick-hit layout. Switched to HTTPS for arXiv to avoid Vercel-side 301 timeout.

v0.1.0 — pre-versioning Earlier work (project scaffolding, initial UI, prototype data layer). See git log for full history.