Conversation
Deploying tinychat with
|
| 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 |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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/chatone private-turn owner and reads exact, published source revisions through companion. It also provides an explicit resumable importer for existing connector records.Changes
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.