Skip to content

price-watch 1.3.0 on Core.51: approve and send the check's alert text - #71

Merged
0design merged 1 commit into
mainfrom
claude/registry40-pricewatch-1103
Nov 3, 2026
Merged

0design merged 1 commit into
mainfrom
claude/registry40-pricewatch-1103

Conversation

@0design

@0design 0design commented Nov 3, 2026

Copy link
Copy Markdown
Owner

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: 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. Description unchanged; howItWorks follows 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

…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>
@0design
0design merged commit 8435224 into main Nov 3, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant