Repository navigation
fix: align deployment probe with auction SEO heading - #75
Merged
Merged
Conversation
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.
The application now renders the intended H1
마비노기 경매장 거래내역·시세, but the production probe accepted only the two previous headings and rejected a healthy candidate. This release adopts the corrected shared workflow to accept the current exact heading while retaining the existing public SEO checks.Version advances to 1.0.33 in package/lock and version-contract assertions. No application source or behavior changes.
Validation: workflow contracts 9/9 passed; full
npm run verifypassed 123 suites / 594 tests, lint, typecheck, Knip and production build. The gateway-free build retains the 300-second homepage ISR interval. Independent review found no blocking issue. The previous identical application candidate passed 36 public HTTP checks (21 sitemap children, 17,439 unique URLs) and 17 browser states, including visible homepage item links after ISR. The corrected provider passed all five public predicates against that actual candidate. Final deployment remains subject to required CI and the corrected public probe.