Skip to content

Contract fixtures for manual 2.3.2; weekly checks also post to the Slack warning channel - #21

Merged
sanctrl merged 3 commits into
mainfrom
ci/weekly-slack-notify
Nov 11, 2026
Merged

sanctrl merged 3 commits into
mainfrom
ci/weekly-slack-notify

Conversation

@sanctrl

@sanctrl sanctrl commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Why

The published contract moved to manual 2.3.2, so this PR first copies its fixtures. Then the alert fix:

weekly.yml (#19) files an issue when a run does not pass, but it posts nothing to Slack. The platform's notification routing puts weekly checks in the WARNING tier: they post to the Slack warning channel, and the self-filed issue is the durable record. This repo already has that webhook (SLACK_WEBHOOK_WARNING, used by publish.yml's notify jobs). I missed it in #19 because I only looked for alerting in ci.yml.

What changes

  • Contract fixtures (manual 2.3.2). The server now publishes the manual as 2.3.2, and main's CI manifest step is red until this lands.
    • conformance/v1/texts.sample.json (the manual's version and sha256) and manifest.sha256 are copied byte for byte from core main at 30e631d.
    • Every file in conformance/v1/ matches the live manifest.
  • Slack. weekly.yml's report job now posts to the warning channel when a run does not pass, with the check's result and the run link.

The post can never stop the issue step (continue-on-error). A missing secret, a revoked webhook (curl -f) or an unreachable Slack logs a warning. The issue step runs as before.

Proof

Test plan

  • CI green, including the manifest step against the live URL (run 43007593171)
  • after merge: Actions → Weekly → Run workflow on main is green and posts nothing
  • UNVERIFIED until a run on main does not pass: the real Slack post

…channel

The platform's notification routing puts weekly checks in the WARNING
tier: a red run posts to the warning channel, and the self-filed issue is
the durable record. This repo already has that channel's webhook
(SLACK_WEBHOOK_WARNING, used by publish.yml's notify jobs); weekly.yml
filed only the issue. The report job now posts too, with the check's
result and the run link, fail-safe as in publish.yml: no secret, or Slack
down, logs a warning and never fails the report.
…e issue step

curl -f, so a revoked webhook is logged as a warning instead of passing
silently; continue-on-error on the step; the header says only a run that
does not pass posts.
…e published contract (manual 2.3.2)

The server now publishes the manual as 2.3.2, so the contract's
texts.sample.json carries the new manual version and sha256, and the
manifest lists the file's new hash. Both files are copied byte for byte
from the published contract (core is canonical); every file in
conformance/v1 matches the published manifest, and the manifest equals
https://agentchat.me/contract/v1/conformance/manifest.sha256.
@sanctrl
sanctrl merged commit af4e2c5 into main Nov 11, 2026
11 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