feat(explorer): name the TAP coverage limitations the backend can now report - #133
Merged
bitcoinuniverseadmin merged 1 commit intoSep 18, 2026
Merged
Conversation
… report The backend derives TAP limitation reasons from the coverage dimensions the authority publishes instead of emitting fixed text, so it can now report pending-protocol-coverage-partial, pending-protocol-coverage-unknown and reorg-evidence-unknown. describeChainReason already falls back safely for an unknown code, but it returns kind 'unstated', which reads as no reason given rather than as a stated limit of the authority. These three are limits and are now written as such. Refs WP04 step 4 and WP05 step 1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
bitcoinuniverseadmin
deleted the
fix/chain-reason-coverage-copy-20260918
branch
September 18, 2026 08:46
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.
Companion to bitcoinuniverseio/backend-apis#202.
That change makes the backend derive TAP limitation reasons from the coverage dimensions the authority actually publishes, rather than emitting two fixed strings for every ready authority. As a result it can now emit three codes this dictionary did not have:
pending-protocol-coverage-partialpending-protocol-coverage-unknownreorg-evidence-unknowndescribeChainReasonalready falls back safely for an unknown code, so nothing breaks without this. But the fallback returnskind: 'unstated', which presents to the reader as no reason given rather than as a stated limit of the authority. All three are limits, and are now written as such with wording matching the neighbouring entries.No behaviour changes for the codes the backend emits today: the values the TAP authority currently publishes still map to
pending-protocol-coverage-unavailableandreorg-evidence-tail-only.Verification
chain-reasons.spec.tsextended to assert all three read aslimit.Branched from the prepared baseline
97f1784, and carries no handoff preparation comments.Refs WP04 step 4 and WP05 step 1.
🤖 Generated with Claude Code