feat(web): expose katana debt-coverage components over graphql - #464
Open
matheus1lva wants to merge 1 commit into
Open
feat(web): expose katana debt-coverage components over graphql#464matheus1lva wants to merge 1 commit into
matheus1lva wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
matheus1lva
marked this pull request as draft
August 31, 2026 20:56
matheus1lva
marked this pull request as ready for review
September 3, 2026 20:45
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
katana-apr-service will emit three new vault-addressed estimated-APR components:
estimatedDebtCoverage(share of active debt backed by a live Morpho estimate vs oraclefallback),
morphoBaseAPY, andmorphoRewardsAPR. Ingestion and both REST paths alreadypass arbitrary component keys through, but GraphQL's
EstimatedAprComponentsis a fixedfield list and drops undeclared keys. This declares the three fields so they serialize,
and documents them.
How to review
packages/web/app/api/gql/typeDefs/vault.ts: three fields added toEstimatedAprComponents, nothing else.packages/ingest/helpers/apy-apr.spec.ts: new case provinggetLatestEstimatedAprV3returns the three components unchanged for akatana-labelled row set.
docs/graphql.md: three table rows.getLatestEstimatedAprV3, resolvers, REST schemas, or promotion;no DB migration.
Test plan
bun --filter ingest test -- helpers/apy-apr.spec.ts(18 pass)Risk / impact
Additive GraphQL fields; null until the katana-apr-service side ships, so existing
consumers see unchanged output. No rollback steps needed beyond revert.