Add Agent QA to English and Chinese utilities - #42
Open
pranshuchittora wants to merge 1 commit into
Open
Conversation
|
@pranshuchittora is attempting to deploy a commit to the corey's projects Team on Vercel. A member of the Team first needs to authorize it. |
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.
Adds Agent QA to Utils in both English and Chinese, with matching canonical URLs, localized descriptions/tags, and the addition date. Both entries explain source-available FSL-1.1-ALv2 licensing and separate provider costs.
Validation: the frozen pnpm lockfile installs successfully;
pnpm lintandpnpm buildpass (lint reports existing application warnings). The actual data-loader, category, and name/tag search functions return Agent QA once in each locale. All previous records are preserved; English Utils changes from 5 to 6 entries and Chinese Utils from 4 to 5.The npm lockfile is already out of sync with the declared Next.js version, so validation used the current pnpm lockfile. A local HTTP smoke test encountered a locale redirect loop; the same redirect is reproduced with the original upstream data. No interactive browser verification is claimed.
Repository · Documentation · License
Disclosure: This is an affiliated Agent QA/Vostride submission.