Don't crash on an impossible date in a resource filename

[pcbeingused333]

The bug

Publishable#date_from_filename matches /^\d{4}-\d{2}-\d{2}-/ and hands the captured groups to Date.new:

Date.new(match[:year].to_i, match[:month].to_i, match[:day].to_i)

The regex is structural, so 2024-99-99-post.md matches and Date.new(2024, 99, 99) raises Date::Error: invalid date. It propagates through publication_date → published? → Collection#all, so one typo'd filename breaks the whole collection load.

The fix

Rescue Date::Error and treat the prefix as not-a-date — the same outcome as a filename with no date prefix.

Tests

resource_publishable_test.rb — a 2024-99-99-…md file: publication_date is nil and published? doesn't raise. Fails on main (Date::Error). bundle exec rake is green (402 runs, 0 failures; standardrb clean).

🤖 Generated with Claude Code

[pcbeingused333]

CI is on action_required (fork gate). Verified with bundle exec rake (Docker, Ruby 3.4): 402 runs, 0 failures, standardrb clean. The new test fails on main with Date::Error: invalid date.