Dropping a file in the margins around a document previously did nothing.
react-dnd's window level dragover handler forced dropEffect to "none" for
any target outside of .ProseMirror, so the browser never dispatched a drop
event there.
Heading numbers are drawn by a ProseMirror decoration, and the server
strips all plugin decorations before it serializes, so exported HTML
always came out unnumbered.
Compute the same labels during export and write them to the rendered
headings as a data attribute, which the exported editor styles already
render. A revision takes the preference from the document it belongs to.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Make count-based limit checks reliable under concurrency
Limits enforced by counting rows before an insert could be exceeded by
requests that ran at the same time, as each one read the same count
before any of them had written. Add a LockHelper that takes a Postgres
advisory lock for the remainder of the transaction, and use it to
serialize the check for webhook subscriptions, team domains, share
subscriptions and pins. The counts now also run on the transaction so
they include rows written earlier in the same request.
* Remove excessive tests
* Also guard simultaneous row removal
Nested .oxlintrc.json files replace the root config per-rule rather than
merging, so the root's shared/** override for no-restricted-imports was
dead config and the sonner restriction was not enforced anywhere.
Move the restrictions into shared/.oxlintrc.json, add the
prosemirror-tables entry to app/.oxlintrc.json where the same shadowing
applies to .tsx files, and drop the dead root override.
The browser closes IndexedDB connections at times the page does not
control – a frozen or discarded tab, a navigation away, or another tab
deleting the database at logout. Persisted store data is a cache that
API traffic always overrides, so these failures have no effect for the
user, but each one was reported to Sentry as a warning.
- Log connection closed failures at debug level instead of reporting them
- Delete the database in clear() rather than emptying it through a
transaction, which cannot fail against a closed connection
- Keep persistence enabled when hydration fails on a closed connection,
rather than disabling it for the rest of the session
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* chore: Upgrade mermaid to 11.17.1
Also bumps @mermaid-js/layout-elk to 0.2.3, which is the matching release,
and dedupes katex — mermaid now requires ^0.16.47 where the project pinned
^0.16.45, which would otherwise ship two copies.
Note that classDiagram now uses the unified (v2) renderer by default.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Hold @mermaid-js/layout-elk at 0.2.2
0.2.3 inlines its own copy of mermaid instead of importing the peer, which
duplicates every diagram chunk and adds 3.4MB to the built bundle. Pinned
exactly so the range cannot drift back onto it.
Unknown paths below /mcp, and the origin-level /sse probe, fell through to
the catch-all and rendered the application shell with a 200. Remote MCP
clients that probe for the legacy HTTP+SSE transport before falling back to
streamable HTTP read that as a successful handshake, then fail to connect.
* review
* Revoke notifications when a document is moved
Moving a document into a collection the recipient cannot read leaves a
notification holding the title and text, so schedule a revocation check
for each recipient of the moved document and its descendants.
Also adds coverage proving drafts are revoked through the document path,
and notes why the scoped query includes them.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* feat: Metadata below collection title
Extracts the shared meta line styles from DocumentMeta into a reusable
HeaderMeta component, and adds an equivalent meta line beneath collection
titles showing visibility, public sharing, and document count.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* i18n
* fix: Show document count for empty collections
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
The changeset token encoder cached node type ids in an object created
with a null prototype, but tested for a cache miss with `=== null`. The
miss reads as undefined, so the cache was never filled and every node
end encoded to undefined — making the closing token of any node compare
equal to that of any other.
As a result revision diffs could omit a node's closing token when its
type changed, and attribute an inserted wrapper's closing token to the
node it wraps.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* feat: Filter DSL for collections.list
Adds the structured `filters` expression language to collections.list,
matching documents.list and documents.search. Supported fields are name,
createdAt, updatedAt, archivedAt, createdById and permission, each validated
against its column type at the input layer.
Deprecates the ad-hoc `query` and `statusFilter` params, which now translate
into filter leaves so that one code path serves both shapes, and returns a 400
when a caller combines them with `filters`.
Note that `query` matching is no longer accent-insensitive, as the unaccent
comparison is replaced by the shared iLike conversion.
* fix: Make filter expressions assignable to a JSON request body
Filters are sent as a JSON body, but `FilterCondition` and `FilterGroup` were
interfaces, which TypeScript does not give an implicit index signature, and
`FilterValue` admitted a `Date` that JSON cannot carry. Both stores worked
around this by asserting the request body to JSONObject, which suppressed
checking of every other field as well.
Declare the two shapes as type aliases and drop `Date` from the value union so
a filter type-checks against the request body directly, and remove the
assertions from the collection and document stores.
* feat: Restrict filter fields to a set of accepted values
Add an optional `values` set to a filter field definition, checked against
scalar and array values at the input layer so that an unsupported value returns
a 400 rather than an empty result or, for a field backed by a Postgres enum, a
database error. A field with a fixed value set is matched exactly, so pattern
operators are rejected for it in the same way as for non-text columns.
Apply it to `permission` on collections.list.
* refactor: Build the list_collections name filter with the filter DSL
The MCP tool carried its own copy of the unaccent name comparison that
collections.list used before it moved to the DSL. Build the clause with
buildWhere instead, so both paths match names the same way, and drop the
replacements plumbing it needed.
* fix: Selection toolbar not displaying on mobile
The mobile branch of FloatingToolbar rendered nothing until `position.visible`
was true, but `usePosition` only reports a visible position once the menu
element has been measured through `menuRef`. On desktop the wrapper is always
mounted (it animates in via opacity) so the ref is populated on first render,
while on mobile the toolbar is the only thing that mounts the ref — leaving it
permanently null and the bar never displayed.
Gate the mobile bar on there being toolbar content instead. Position is
irrelevant on mobile: the bar is fixed to the bottom of the viewport and its
vertical offset is owned by useKeyboardStickyOffset.
Also size the bar with border-box and center its content vertically, so the
declared 60px is the height of the bar rather than 60px of content plus
padding with the buttons pinned to the top.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GhGyxA663bMFZ1NxBhLAoF
* fix: Keep the mobile selection toolbar visible while editing
On mobile the toolbar is a bar docked above the on-screen keyboard rather than
a floating menu anchored to the selection, but it was only rendered while
something was selected — so it appeared and vanished as the selection came and
went while typing.
The formatting menu was already written for this: `canFormatBlock` shows
headings, quotes, toggles and list indent/outdent precisely when the selection
is empty on mobile, mirroring `canFormatInline` for selected text. That branch
was unreachable, as an empty selection always resolved the toolbar to nothing.
Show the menu whenever the editor is focused on mobile, so the bar carries
block formatting for a bare cursor and swaps to inline formatting on selection.
Visibility is derived at render rather than folded into `activeToolbar` so that
focus moving into the link editor's input cannot tear down a toolbar the user
opened. Focus is threaded to widgets through WidgetProps.
Tapping the bar now also prevents the default action of mousedown, keeping
focus (and the keyboard) in the editor. Without it a tap would blur the editor
and unmount the bar before the tap became a click; fields inside the bar are
excluded so the link editor still takes focus.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GhGyxA663bMFZ1NxBhLAoF
* fix: Mobile toolbar is not visible
* Update mobile toolbar styling
fix: Does not account for stored marks
---------
Co-authored-by: Claude <noreply@anthropic.com>
* fix: Search result context cut mid-word by earlier highlights
The snippet indexes were calculated against the plain document text, then used
to slice the highlighted copy. Every highlight before the slice start adds seven
characters, so the snippet began too late and could open inside a bold tag.
Slice first and highlight the slice, so both indexes apply to the same string.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Feedback
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Only show editing stats toggle when viewing a document
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Default isViewing to false
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
The contents lists headings up to level four, but tracked the active heading
across every heading in the document. Scrolling into a level five or six
section selected a heading with no entry in the list, so the highlight
disappeared until the next listed heading came into view.
The level filter now runs once, up front, and the active heading tracking,
indentation base, empty check and render all read the same list. Prefix labels
are still computed over every heading so the numbering keeps matching the
document.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: New German translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Polish translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Vietnamese translations
* fix: New Dutch translations
* fix: New Dutch translations
* fix: New Thai translations
* fix: New Spanish translations
* fix: New Catalan translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Dutch translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Chinese Simplified translations
* fix: New Chinese Traditional translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New English, United Kingdom translations
* fix: New Norwegian Bokmal translations
* fix: New French translations
* fix: New Spanish translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New Norwegian Bokmal translations
* fix: New Spanish translations
* fix: New Catalan translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Dutch translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Chinese Simplified translations
* fix: New Chinese Traditional translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New English, United Kingdom translations
* fix: New Norwegian Bokmal translations
* fix: New French translations
* fix: New Spanish translations
* fix: New Catalan translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Dutch translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Chinese Simplified translations
* fix: New Chinese Traditional translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New Norwegian Bokmal translations
* fix: New French translations
* fix: New Spanish translations
* fix: New Catalan translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Dutch translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Chinese Simplified translations
* fix: New Chinese Traditional translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New English, United Kingdom translations
* fix: New Norwegian Bokmal translations
* fix: New French translations
* fix: New Spanish translations
* fix: New Catalan translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Dutch translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Chinese Simplified translations
* fix: New Chinese Traditional translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New English, United Kingdom translations
* fix: New Norwegian Bokmal translations
* fix: New French translations
* fix: New Polish translations
* fix: New Spanish translations
* fix: New Catalan translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Dutch translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Chinese Simplified translations
* fix: New Chinese Traditional translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New English, United Kingdom translations
* fix: New Norwegian Bokmal translations
* fix: New French translations
* fix: New Spanish translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Thai translations
* fix: New Swedish translations
* fix: New Portuguese translations
* fix: New Ukrainian translations
* fix: New Vietnamese translations
* fix: New Persian translations
* fix: New Spanish translations
* fix: New Catalan translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Dutch translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Chinese Simplified translations
* fix: New Chinese Traditional translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New English, United Kingdom translations
* fix: New Norwegian Bokmal translations
* fix: New French translations
* fix: New Spanish translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Thai translations
Shared links return markdown when the client asks for it, but there was no
way to discover this short of guessing the .md suffix.
- Vary on Accept so shared caches key the two representations correctly
- Send a Link rel="alternate" header, discoverable with a HEAD request
- Emit a matching link tag alongside the canonical in the head
- Apply the same cache directives to markdown as the HTML response
* feat: Record who deleted a document
The trash inferred the deleting user from lastModifiedById, so a nested page
kept whoever last edited it and deleting a document rewrote its edit history.
Add a dedicated deletedById column and set it from the base model.
- Migration adds the column, backfills from lastModifiedById, and validates the
foreign key without holding an exclusive lock. The backfill runs in batches
against a temporary index covering only the rows still to write, so it stays
linear on a large table, and every statement is idempotent because the
migration cannot run in a transaction.
- ParanoidModel records the acting user on destroy and clears it on restore,
for any model that has the column. Sequelize soft deletes with the same UPDATE
that stamps deletedAt, so the value costs no extra query.
- Deleting a document no longer touches lastModifiedById on its descendants.
- Present the deleting user, batched in presentDocuments, and use it for the
trash notice and the document meta line rather than the last editor.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Do not overwrite an eager loaded deleting user when batching
The batch lookup in presentDocuments skipped documents that already carried the
association, but the assignment loop ran for all of them, so a document that
arrived with deletedBy loaded was reset to null and fell back to a per-document
query. Assign only where the association is missing, and deduplicate the ids so
a page deleted by one person asks for one row rather than one per document.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Recover from closed IndexedDB connections in store persistence
StorePersistence cached a single IDBDatabase forever, so once the browser
or another tab closed the connection every subsequent hydrate, flush and
clear threw against a dead handle.
- Close and forget the connection on versionchange, so another tab is
never blocked from deleting or upgrading the database
- Discard the cached connection on close, open error and blocked, and
retry once against a fresh connection when one was closed underneath us
- Close open connections before deleteAllDatabases removes them, which
also stops logout recreating the databases it just deleted
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Cancel pending writes when store persistence is disabled
A debounced flush scheduled before disabling would still fire, reopening
and recreating the database that deleteAllDatabases had just removed.
* fix: Crash opening document menu on mobile
The heading numbering submenu added to the document display options is
rendered through the `append` slot of `DropdownMenu`. On desktop that slot
lands inside the menu content, but on mobile it is rendered into a drawer,
which has no menu root for the Radix submenu primitives to attach to — so
opening the document overflow menu on mobile threw "`MenuSub` must be used
within `Menu`" and took down the page.
Flatten the submenu into an inline group of options on mobile, matching the
toggles it sits alongside.
Fixes OUTLINE-CLOUD-D1X
Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V5ExrfehTYgotb8d2aoMvK
* fix: Match heading prefix color to the heading anchor
The heading numbering prefix was drawn with the secondary text color while
the `#` anchor beside it uses the primary text color at 75% opacity. The
two read as the same tone in light mode, but diverge visibly in dark mode
where the primary text color is much brighter.
Draw the prefix from the same color and opacity as the anchor so the two
match in both themes.
Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V5ExrfehTYgotb8d2aoMvK
* fix: Heading prefix missing when printing
The print stylesheet hides the heading pseudo element to keep the H1–H6
level labels out of print. That pseudo element also carries the heading
numbering prefix, so printing or exporting a numbered document dropped its
numbers.
Qualify the print selectors the same way the level labels themselves are,
so only the labels are hidden and the prefix still prints.
Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V5ExrfehTYgotb8d2aoMvK
* Update Styles.ts
The client serializes all @Field properties on save, so documents created
before the preferences column existed post `preferences: null`, which the
update and create schemas rejected.
raw-body throws a 500 'stream is not readable' when the request stream is
already destroyed at parse time, which means the client went away. Map it to
ClientClosedRequestError so it reports 499 and is not sent to the bug tracker.
* feat: Filter DSL for users.list
Add the structured filter expression language already used by documents.list
and documents.search to users.list, over an allowlist of id, name, email,
role, createdAt, updatedAt, lastActiveAt and suspendedAt.
Supersedes the ad-hoc ids, emails, role and filter parameters, which are now
deprecated and translated into the DSL so a single path builds the query. The
same translation backs the list_users MCP tool, which held a duplicate copy of
the status handling.
Field specs gain an optional value allowlist, so an unknown role is rejected
at the input layer rather than reaching the enum column. Suspended users
remain invisible to non-admins and excluded by default, unless the expression
references suspendedAt.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* refactor: Collapse the duplicate suspended user predicate
The non-admin invariant and the default exclusion pushed the same clause for
non-admins in the default case. Both rules are now one predicate: suspended
users are visible to admins only, and then only on request.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* refactor: Drop the legacy parameters from the list_users MCP tool
The MCP surface has no backwards compatibility burden, so it takes the filter
DSL directly instead of the deprecated role and status parameters. This gives
the model date ranges, OR groups and name matching, which the old enum pair
could not express.
The field allowlist moves next to the other user filter helpers so the REST
schema and the tool share one definition rather than the tools directory
reaching into the routes.
Drops the unreachable Date member of FilterValue. Dates cross the wire as ISO
8601 strings, a Date instance fails every field kind, and zod cannot represent
it in the JSON Schema the MCP tool list is built from.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* revert: Retain legacy role/filter params in the list_users MCP tool for now
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Revert MCP changes
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Add heading numbering display preference for documents
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Fix isRemoteTransaction call for new signature on main
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Fix inTable detection for headings after a nested table
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Move from deco to pseudoclass
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
* wip
* Center reorder cursors between sections, detect empty sections with CSS
* Deduplicate persisted sidebar section order
* fix: Stricter zod type
* Remove DraggableSection unit tests
* fix: Normalize path when keying rate limiters
The router matches paths case-insensitively and with an optional trailing
slash, so those variants each received their own quota. Collapse them onto
a single key at both registration and consumption.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* feedback
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Rate limit response headers and first-request accounting
Retry-After and RateLimit-Reset are both defined as a whole number of
seconds. Retry-After was sent as a fraction and RateLimit-Reset as a full
date string, neither of which a client can act on.
A route limiter is registered by middleware that runs after the point where
quota is consumed, so the first request to reach a path in each process was
never charged against it. Charge it at registration time instead.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* test: Cover rate limit headers and first request accounting
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* perf: Cache JS chunks on first use instead of precaching entire build
The service worker precached every JS chunk (~590 files) in the
background for every visitor. Chunks are content-hashed and immutable,
so a CacheFirst runtime route provides the same repeat-visit behavior
while only fetching chunks that are actually used.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* perf: Do not register service worker on public share views
Anonymous share visitors gain nothing from the worker or the PWA
cache, shares always require the API. The server now exposes an
isShare flag in window.env and the client skips registration when
it is set.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
* feat: Unpin and context menu controls on pinned documents
- Adds an unpin control to document chips in the collapsed pinned view
- Adds the collapse toggle to collections, matching home
- Makes the Pin menu items toggles with a selected state
- Adds a document context menu to pinned cards and chips
- Stops the drag sensor swallowing clicks on the card unpin button
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Hide the collection pin toggle for a mixed selection
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>