Align VERIFRAX-API repo truth to current live host binding#1
Merged
verifrax-systems merged 1 commit intomainfrom Apr 2, 2026
Merged
Conversation
verifrax-systems
approved these changes
Apr 2, 2026
Member
verifrax-systems
left a comment
verifrax-systems
left a comment
There was a problem hiding this comment.
Approved.
Scope is correct:
- only the host-truth surfaces are changed
- repository truth now follows the current live host binding
- contract endpoints are explicitly marked as not yet live on the current host binding
- no false execution-runtime claim remains in the repo truth surfaces changed here
This closes the repo-versus-live-host contradiction without pretending the API contract is already live.
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
2 participants
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.
This change aligns the VERIFRAX-API repository surfaces to the host state that is actually live today.
What changed:
Why:
The repository previously claimed Cloudflare Worker / execution-runtime truth while the live host was serving a GitHub Pages boundary page and the declared contract endpoints returned 404.
This PR makes repository truth follow live host truth without claiming contract availability that does not yet exist.