* perf(session): send one projection frame per committed event
* fix(session): deliver keys changed before a drive failure; address review
* perf(session): carry projection frame changes as key and val entries
Add imageOffloadCountQuantum (default 10) so a saturated route rewrites its
request prefix once per ten new images, cite the Azure OpenAI 50-image limit
for the default, report the overflow without naming both bounds, split the
adapter count test, and add an upgrade guide.
Refs #7605
Add a per-route maxRequestImages bound (default 50) to the pi-ai request-image
budget. A history with more retained images now fails with
IMAGE_OFFLOAD_REQUIRED so dsh-compaction-image-offload offloads the oldest
images, instead of the provider rejecting every later request.
Refs #7605
* fix(ui-conversation): keep the docked composer seat stable
The active composer seat now keeps one stacking rank (z-index 9) in every
state, a direct compositing reason (will-change: transform), the scroll
floor without relying on a View to fill the column (margin-top: auto), and
no scroll-anchoring role. Composer tooltips portal to the body because the
seat is the containing block for fixed descendants. The width handle keeps
z-index 0 while dragging.
The docked statistics row reserves one reading's height before its
projections arrive, and the header without a Session keeps the blank
Session's 40px row on every platform so both Hero states center the input
card at the same height.
Fixes#7590
* docs(ui-conversation): state the composer fixed-overlay contract
Composer-hosted slots now document that fixed overlays must portal to the
document body, because the docked composer is their containing block; the
client slot catalog is regenerated from that JSDoc. The README also records
that gutter tables cover a captured width-handle drag and that the
composer's backdrop blur is verified only in Chromium. Local comments note
the grayscale text antialiasing of the permanent composer layer, why the
statistics row uses a minimum height, why the sessionless header keeps an
empty title row, and that the Hero offset test assumes the default plugins.
Refs #7590
* docs(ui-conversation): state the back-to-bottom offset as geometry
The composer and back-to-bottom stacking comments now state the resting
16px gap instead of claiming the control never overlaps the input card.
Refs #7590
The composer and back-to-bottom stacking comments now state the resting
16px gap instead of claiming the control never overlaps the input card.
Refs #7590
Composer-hosted slots now document that fixed overlays must portal to the
document body, because the docked composer is their containing block; the
client slot catalog is regenerated from that JSDoc. The README also records
that gutter tables cover a captured width-handle drag and that the
composer's backdrop blur is verified only in Chromium. Local comments note
the grayscale text antialiasing of the permanent composer layer, why the
statistics row uses a minimum height, why the sessionless header keeps an
empty title row, and that the Hero offset test assumes the default plugins.
Refs #7590
* fix(ui-primitives): keep tall menus inside the mobile viewport
* fix(client): anchor model picker with Floating UI
Use Floating UI for fixed model-menu placement and automatic viewport updates. Preserve top-end alignment and defer automatic focus until placement is ready. Guard asynchronous results across updates and menu teardown.
* fix(client): preserve menu blur under pinned group titles
Keep the current provider title outside the native scroll viewport so
model rows cannot bleed through during fast scrolling. Preserve the
enclosing menu fill and backdrop filter, and update both model pickers,
lifecycle tests and ARIA goldens.
Validation: doc-sync, full build, final type checks, focused lint and
all 12 model-picker browser checks pass. The full unit run has 42,597
passing tests and four failures in unchanged gateway, third-party-
notices and Inspector tests. The Inspector case passes in isolation.
* fix(client): stabilize floating panels during browser zoom
* fix(client): keep portal menus aligned during Safari zoom
* fix(client): commit floating menu positions before paint
* fix(client): unify floating panel positioning
* fix(client): validate grouped menu headings
* fix(client): hide inactive pinned menu headings
* test(client): await floating menu layout across consumers
* test(ui-chat): await folded reply menu positioning
* test(client): align current consumers with asynchronous panel layout
* fix(client): prevent mobile model search focus zoom
* refactor(client): inject mobile device state from layout
* fix(client): keep anchored panel layout synchronous
* fix(client): address panel review coverage and documentation
* fix(client): keep viewport changes focused on iOS zoom
* fix(client): cover anchored panel lifecycle and scrollbar colors
* fix(client): preserve zoomed model menu scrolling and alignment
* fix(client): hide empty model menus and stabilize viewport pan tests
* test(web): use native wheel input for zoomed viewport panning
* fix(client): keep automation pickers scrollable when zoomed
* fix(client): allow horizontal gestures across clock columns
* fix(client): ellipsize overflowing floating-panel labels
* test(web): make clock overflow fixture independent of system fonts
---------
Co-authored-by: Zrs000 <[email protected]>
The active composer seat now keeps one stacking rank (z-index 9) in every
state, a direct compositing reason (will-change: transform), the scroll
floor without relying on a View to fill the column (margin-top: auto), and
no scroll-anchoring role. Composer tooltips portal to the body because the
seat is the containing block for fixed descendants. The width handle keeps
z-index 0 while dragging.
The docked statistics row reserves one reading's height before its
projections arrive, and the header without a Session keeps the blank
Session's 40px row on every platform so both Hero states center the input
card at the same height.
Fixes#7590
A new Agent Note owns the shipped defaults and the original apply_patch note
keeps its opt-in decision with a supersession link; the policy README, the
tool-catalog note, the filesystem page, and the fs group README state the
current defaults without evaluation figures. The PTC overlay sets
`applyPatch: false` so the SDK and Desktop PTC tool sets match without a
parity exception; the fixed-budget compaction scenarios pin the tool set in
their live patches too; the apply-patch composition drops its no-op override.
The upgrade guide scopes the change to base-backed profiles, the README
refusal example is one every composition can produce, the integration suite
names its deployments by guard, and the keyless SDK smoke edits a file the
model never read through the shipped profile.
Descriptor v1 gained a required label before v2 replaced it, and the v3-to-v4
catalog stage reads v1 that way. Share the descriptor version list and cover
format v0 parent and child migration through JSONL persistence.
Co-authored-by: Saafo <[email protected]>
Co-authored-by: Magolor <[email protected]>
Format v0 logs written before descriptor v3 failed migration, which made every
cold read of such a child session, and with it session search, fail.
Co-authored-by: Saafo <[email protected]>
Co-authored-by: Magolor <[email protected]>
Takes master's re-recorded plan-review, creation-recommendations, and
plugin-recommendations scenarios from the base and refreshes their headers
and schema sidecar for the enabled apply_patch tool.