2.0.12

docs(README): document caching strategy + queue-worker recommendation

The architectural changes around stale-while-revalidate caching +
RefreshRecruitsJob earn no benefit on Flarum's default `sync` queue
driver — operators have to configure database/redis/sqs and run a
worker to get truly out-of-band refresh. Documenting that contract
so the deployment guidance is visible without spelunking through
commit messages.

Also:
- Mention the new "Page / Widget Title" admin setting in the
  config table (registered in the previous commit).
- Reframe "Cache Duration" as a SOFT TTL with a link to the new
  caching section so admins understand stale data is intentional.
- Expand "How it works" step 3 to describe the dispatch-and-serve
  flow rather than the old block-and-fetch flow.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>