Found during #120. CellStructureMech grew 542 to 544 to 545 and TraitMech 763 to 764 within hours of the refresh's pins. By design (see the update skill, step 8) the page stays a consistent snapshot at the pins and site_audit.json records the later figure as site_figure_at_check. But check_cards.py reports both as DRIFTED and exits 1, so the scheduled run is red after every refresh of a fast-moving Mech, which is the "standing red teaches people to ignore it" failure #109 set out to avoid.
Options: treat growth past the audited figure as a warning when the site's figure exceeds the card and the card equals the audit's pinned figure; or compare against the site's deployed revision rather than a number. Needs a decision; not changed in #120.
Found during #120. CellStructureMech grew 542 to 544 to 545 and TraitMech 763 to 764 within hours of the refresh's pins. By design (see the update skill, step 8) the page stays a consistent snapshot at the pins and
site_audit.jsonrecords the later figure assite_figure_at_check. Butcheck_cards.pyreports both as DRIFTED and exits 1, so the scheduled run is red after every refresh of a fast-moving Mech, which is the "standing red teaches people to ignore it" failure #109 set out to avoid.Options: treat growth past the audited figure as a warning when the site's figure exceeds the card and the card equals the audit's pinned figure; or compare against the site's deployed revision rather than a number. Needs a decision; not changed in #120.