Repository navigation
price-watch 1.3.0 on Core.51: approve and send the check's alert text - #71
Merged
Merged
Conversation
…eck's alert text (as on stage registry.39) On Core.51 the human gate's subject is the fetched JSON, so #69's alert read subject.json.rates.UAH; the site's editor showed that path as "Subject JSON Rates UAH". `subject: previous` keeps the reviewed registry.39 behaviour: the person approves the check's reason (rate and threshold), bound under sha256, and exactly that reason goes in the alert. Tests: subject is the verdict, the hash follows the reason, the body is "Rate alert — <reason>", an ordinary day ends at the check with nothing sent. Co-Authored-By: Codex <noreply@openai.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Registry and tests only; Core unchanged (archive 59294943…2f4).
On Core.51 the human gate's subject is the fetched JSON, so the alert from #69 read
subject.json.rates.UAH, which the site editor showed as «Subject JSON Rates UAH».subject: previouskeeps the reviewed registry.39 behaviour: the person approves the check's reason (rate and threshold), bound under sha256, and exactly that reason goes in the alert. Description unchanged;howItWorksfollows the new body.Tests: subject is the verdict, the hash follows the reason, the body is «Rate alert — », an ordinary day ends at the check with nothing sent.
🤖 Generated with Claude Code