Expose Katana forward-estimate diagnostics - #459
Open
rossgalloway wants to merge 1 commit into
Open
Conversation
Add the three accepted forward-estimate component fields to the GraphQL schema and documentation. Extend the Katana container test to verify GraphQL, REST list, and REST snapshot preserve the exact diagnostic values.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Summary
Kong already stores three Katana forward-estimate diagnostics, but the fixed GraphQL component type did not expose them. This PR adds exactly estimatedDebtCoverage, morphoBaseAPY, and morphoRewardsAPR to GraphQL and documents their meanings.
Related to #432.
How to review
Review packages/web/app/api/gql/typeDefs/vault.ts first to confirm that only the three nullable Float fields were added. Then review docs/graphql.md and the extended Katana container test, which checks the same seeded values through GraphQL, the chain-scoped REST vault list, and the REST snapshot.
No ingestion, resolver, fallback, promotion, shared type, or database behavior changed.
Test plan
Risk / impact
Risk is low. The production change only adds three nullable GraphQL fields. REST list and snapshot output already preserve these component keys, and the integration test proves their numeric values remain unchanged. There is no database migration and no APR or APY fallback change. Reverting this commit removes the GraphQL fields and tests.