Module baseline_advisory_text 

One reader for the envelope’s baseline_staleness, shared by every review surface that states an advisory.

The gate inventory line already tells a reviewer that stale-baseline failed or stood down. It does not say what went stale, and the counts that answer that are on the envelope: the step log and the job summary print them and the sticky comment did not, so a repository whose baseline had rotted saw it on the surface nobody opens and not on the one people read (#2675).

The fact clauses are word for word the job summary’s (action/scripts/summary.sh), which is what a reader comparing the two surfaces gets from having one advisory. The remedy clause is deliberately channel-free: one Rust renderer serves GitHub and GitLab and cannot know whether the reader re-saves through the save-baseline input, FALLOW_SAVE_BASELINE or --save-baseline, so it names the run rather than the knob. Do not “fix” that divergence by naming one channel here.

The envelope arrives untyped, exactly as fallow report --from holds it, and the live path routes its typed object through the same formatter so the saved render stays byte-identical to the direct one.

Functions

advisory_line

The advisory for every loaded baseline that earned one, or None when the run loaded no baseline or every baseline is fresh enough to say nothing.

advisory_line_for_staleness

advisory_line for a live run holding one staleness object typed.