I'm not a fan of the "stale bot" approach to bugs either, but I think what it's doing can at least somewhat be classified as part of the "facts" side of the div

I'm not a fan of the "stale bot" approach to bugs either, but I think what it's doing can at least somewhat be classified as part of the "facts" side of the division. The initial bug report conveys the fact "version 3.5 crashes when passed the --wombat option". A year later that fact is still true but is of very little interest to the dev team: what they want to know is whether "version 5.0 crashes when passed --wombat" is true or not. The stale-bot is pushing the obligation to test that new different fact onto the bug submitter. (I think it's better to leave that with the dev team; plus unless the devs plan to actually fix it then retesting on 5.0 is just gathering another fact that isn't going to matter...)