Repository navigation
Conversation
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.
Problem
The comparison reference and CI tutorial still said generated SDK support for trial stability was unavailable after SDK #33 implemented the typed flag and response.
Change
FI_API_KEY,FI_SECRET_KEY, andFI_BASE_URL.RunComparisonRequestand existingexperiment_runs.compare/experimentRuns.comparefacades.Metadata selector follow-up
The existing comparison reference and CI guide now document exact
metadata_equals(20-key bound) andsplit_nameselectors, selection counts, whole-identity semantics, and null/zero JSON preservation.Validation
npm run build: passed; Pagefind indexed 725 pages.npm run audit-links: zero broken navigation/content links; 29 existing orphan pages.git diff --checkpassed; the temporary dependency symlink was removed before staging.The fixture-server check validates these exact snippets and generated SDK decoding. Earlier authenticated HTTP/PostgreSQL probes validate the SDK backend data path using deterministic synthetic scores. Neither establishes model/provider execution, live Observe ingestion, browser/UI qualification, hosted rollout, or package publication.
Stack: docs #904 -> docs #907 -> this PR. SDK dependency: futureagi-sdk #33, commit
dde3ef590728c6b03332465c1218116cfe37f610. Backend contract: core #3483, commit32ea09fa63d0ffa2e5178d1ede94f0f8b5796b7a.Linear: TH-8587.