Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
hpmaxi
marked this pull request as ready for review
October 17, 2026 16:19
This branch was successfully 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.
Summary
This PR adds
health(). It warns whenfreshness_durationis shorter than the notice, so an epoch does not reopen cancellation on its own, and it reports the feed's state and every wiring checkfinish_setupmakes except the share supply. The harness deploy prints it and fails on a wiring gap.Changes
health()reports setup, the token and oracle bindings, the sole manager role, the allowlist and the compliance bindingDeviations
pause_nav), not the plan's "ripcord" naming; the test and the kit-spec line ("the NAV is not paused") use that name instead.Acceptance criteria
finish_setupusesfeed_validfalse with no report or a raised NAV pausefreshness_covers_noticefalse when the notice is longer than a report liveshealth()and fails when a wiring flag is falseTest plan
Automated tests
cargo test -p async-vault health: 5 passed (plus 1 pre-existing unrelated test matched by the name filter).cargo test --locked(whole workspace): 369 passed inasync-vault; all other crates unchanged and green.Manual verification
HARNESS_NETWORK=local npm run deploy -w scripts/harnessagainst a localstellar/quickstartnetwork: the output has ahealthline with every wiring flag true,setup_openfalse,feed_validfalse (expected pre-attestation),freshness_covers_noticetrue.Breaking changes
None.
Checklist
Screenshots
None.