Refresh upstream fit validation#20
Merged
JSvandijk merged 1 commit intoMay 5, 2026
Merged
Conversation
JSvandijk
force-pushed
the
docs/upstream-fit-current-validation
branch
from
92df4f4 to
da2015a
Compare
Owner
|
Updated after #19 merged. Current verification for this PR head:
The doc now references #19 as merged maintenance work instead of an open PR. |
This was referenced May 5, 2026
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
3 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.
Summary
Refreshes
docs/UPSTREAM-FIT.mdwith current validation data and links to the upstream T3 discussion.Why
pingdotgg/t3code#2514links directly to this document, so it should show current evidence instead of only describing the intended positioning.Verification
Ran locally after
npm install:npm testpassedmanifest.jsoncheck passed