Milestones
List view
Make this a test of the action rather than only a user of it. verify.yml now cross-checks all thirteen flat outputs against the same JSON report, which covers the plumbing. What it does not cover is the input that decides whether the job goes red: fail-on's two failing modes are exercised nowhere, here or in mossaic's own suite. This repository is the only place they can be tested against a real contribution graph rather than a fixture, which is the whole argument for it existing. The trap to avoid is a case that passes vacuously — a fail-on: behind case running on a day nothing was owed proves nothing and would go on proving nothing forever. Every case asserts its own precondition. Out of scope: the notification channels. Slack, Discord and email are gated behind repository variables and need secrets; they are integration surface, not action behaviour.
No due date•1/2 issues closed