Skip to content

Consolidate private meeting turns on exact published evidence - #71

Draft
rsvistel wants to merge 9 commits into
mainfrom
Codex/roman/tinychat-lean-stability-20260914
Draft

rsvistel wants to merge 9 commits into
mainfrom
Codex/roman/tinychat-lean-stability-20260914

Conversation

@rsvistel

@rsvistel rsvistel commented Sep 14, 2026 •

Copy link
Copy Markdown
Collaborator

Private meeting answers could pass through competing browser/backend schedulers and lossy projections, while mutable connector bodies could diverge from their searchable metadata. This change gives /api/agent/chat one private-turn owner and reads exact, published source revisions through companion. It also provides an explicit resumable importer for existing connector records.

Changes

  • Route Send through backend classification before compaction or provider dispatch; retain ordinary preparation, memory, public tools, billing and stream controls.
  • Publish immutable raw snapshots through the native conditional boundary and use those revisions in Library. Preserve independent notes identity, historical aliases and explicit unavailable states.
  • Import legacy SQL/KV records with their original IDs and exact stored body bytes. Validate the entire bounded inventory before activation, recheck metadata and body digests around reservation, retain original SQL cells in provenance, and resume saved operation IDs after interruption or uncertain acknowledgements. Historical capture completeness remains unknown; no provider refetch is implied.
  • Resolve selected/free-text requests, dates, duplicate titles and persisted parent order. Track every source × requested-part obligation and enforce shared token, time and recovery limits. Keep unresolved scope and continuation state across capability failures.
  • Add keyset discovery, literal sentence search and persisted Continue beyond the old caps. Preserve useful partial results when later work fails.
  • Persist one immutable terminal result, including cancellation during message preparation. Prevent late Stop writes and private prose promotion into ordinary memory/checkpoints. Preserve signed transcript delegation headers and display restored space/model state correctly.
  • Pin GLM-5.3 tokenizer accounting and validate final private usage. Provider admission remains closed pending reviewed gateway retry/failover evidence.

Validation

Latest frontend run: 1,056 tests passed, TypeScript passed. The migration has 15 focused tests covering invalid/incomplete inventories, aliases, strict missing-error classification, fractional durations, concurrent changes, interruption and resume.

A real native/SDK rehearsal seeded a complete private legacy catalog, retained every original SQL cell and body string, imported it with a deliberate interruption, and reran without extra operations or snapshots. Library read every converted record; companion distinguished nonempty partial evidence from originals that were already empty. A separate synthetic native run exercised a lost acknowledgement after an actual successful publish. No provider/model calls were used in these rehearsals.

Earlier full validation included backend/shared-package/browser suites, TypeScript, scoped lint, the frontend production build, a retained 12-scenario synthetic screen, and the cross-repository native/companion gate. These checks do not establish live factual quality or 99% reliability. Actual OpenKey production authentication and ordinary chat persistence/reload were also verified; live legacy catalog conversion has not been performed.

Dependencies and acceptance

Depends on the native publication boundary and companion v3 evidence contract. Legacy conversion requires a compatible native deployment and a temporary server-enforced pause on old artifact writes, followed by verification and release of that pause. The importer is separate from automatic App startup.

Keep this draft until provider attempt evidence, the admitted-provider quality screen, live identity/consumer verification and production topology/activation checks are complete. No production deployment or live-user migration is included in these validation claims.

See the committed execution and deletion audit.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Sep 14, 2026 •

Copy link
Copy Markdown

Deploying tinychat with  Cloudflare Pages  Cloudflare Pages

Latest commit: a31cb05
Status: ✅  Deploy successful!
Preview URL: https://c753801e.tinychat-4jq.pages.dev
Branch Preview URL: https://codex-roman-tinychat-lean-st.tinychat-4jq.pages.dev

View logs

This branch has not been deployed

No deployments
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