Skip to content

Research: show compaction progress and history dividers - #1228

Draft
AnthonyRonning wants to merge 1 commit into
codex-resp-compact-stream-maplefrom
codex-resp-compact-visibility-maple
Draft

AnthonyRonning wants to merge 1 commit into
codex-resp-compact-stream-maplefrom
codex-resp-compact-visibility-maple

Conversation

@AnthonyRonning

@AnthonyRonning AnthonyRonning commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Show a quiet compacting divider during observed Responses summary work and a durable compacted divider at the corresponding history boundary, including after reload.

Additive encrypted, owner-scoped metadata reads provide advisory preparation status and bounded checkpoint history. Only saved metadata produces a completed divider. Canonical messages and pagination remain separate; opaque checkpoint content stays out of presentation metadata and logs. An older backend or missing events leaves ordinary chat functional, so the frontend needs no feature flag or coordinated backend release.

Optional polling now preserves the shared encrypted session: stopping observation or cancelling its run stops scheduling and rejects late callbacks without aborting a healthy metadata read. Idle polling backs off through 2/4/8/10 seconds; active compaction uses one second. Any read failure clears progress and ends that polling instance, including old-backend 404s. Reads inherit the configured transport timeout instead of imposing a separate five-second abort.

Restacked above backend #1184 at signed 27059eae; signed child 0cc8bf01. No production SDK/dependency, Pi, routing or caller output-limit changes. Historical dividers can remain while new inference uses legacy mode; server telemetry identifies current dispatch.

Current combined-build validation:

  • Frontend formatting/lint/type checking and 1,404 tests passed; PR web build passed with existing warnings.
  • Backend formatting, strict all-target/all-feature Clippy, 1,081 unit tests and all 54 selected disposable-DB checks passed; 55 default-ignored are separate. Migration redo and cleanup passed.
  • Four composition cases use the actual checked-in SDK runtime with an injected synthetic client: normal stop and cancellation preserve session reuse, logical 404 preserves it, and a genuine transport error still retires it without optional polling retries. This is runtime composition proof, not full-wire or published-package integration proof. The application's SDK pin remains 4.1.1; the source-runtime harness uses 4.2.3.
  • The same clean signed source and binary passed seven controlled and four actual DeepSeek Local cases: on/off/on, exact fact recall, unchanged prior canonical history, GET/SSE checkpoint agreement and an intentional failed terminal. A held accepted tool Response compacted successfully beyond the preaccept allowance. Default-off GET, scoped synthetic DELETE and subsequent GET404 passed.
  • Actual-model cases use an explicit 20,000-token trigger and preserved caller cap with normal catalog windows; they do not prove an accepted GPU route or normal-window capacity.
  • All eleven cases correlated one mode decision/outcome; known synthetic sentinels were absent from the bounded log segment. Chrome full reload retained historical dividers and the composer with the flag off.

The Local provider fixture was stopped, native Continuum restored, scoped flags restored off, and Local services intentionally stopped after validation. Earlier receipts keep their original revision scopes.

Stack #1229 remains draft. No merges or Dev/Production deployments.

@AnthonyRonning AnthonyRonning changed the title research: show compaction progress and history dividers Research: show compaction progress and history dividers Oct 23, 2026
@AnthonyRonning
AnthonyRonning force-pushed the codex-resp-compact-visibility-maple branch from 4107037 to 4796554 Compare October 24, 2026 19:56
@AnthonyRonning
AnthonyRonning force-pushed the codex-resp-compact-visibility-maple branch 2 times, most recently from 1c18f6b to 0cc8bf0 Compare October 26, 2026 05:35
Base automatically changed from codex-resp-compact-maple to master October 27, 2026 03:15
@AnthonyRonning
AnthonyRonning force-pushed the codex-resp-compact-visibility-maple branch from 0cc8bf0 to 0dc789f Compare October 27, 2026 03:16
@github-actions

Copy link
Copy Markdown
Contributor

Maple development preview: https://0a18d0eb.maple-ca8.pages.dev

Commit: 0dc789fd2fd82486136e4756f7fbc28cc0f71018

Uses development API, billing, flags and PCR configuration. Cloudflare Access applies.

@AnthonyRonning
AnthonyRonning force-pushed the codex-resp-compact-visibility-maple branch from 0dc789f to 3228e1a Compare October 29, 2026 04:31
@AnthonyRonning
AnthonyRonning removed this pull request from stack #1229 October 29, 2026 04:31
@AnthonyRonning
AnthonyRonning changed the base branch from master to codex-resp-compact-stream-maple October 29, 2026 04:31

This branch was successfully deployed

1 active (outdated) deployment
pages-pr-1228 — 0dc789fd Deployed Oct 27, 2026 by github-actions[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant