feat(scenario): give the cases places to investigate and routes to the death estimate

[tkgstrator]

Scenario data for the two features #15 and #16 shipped the machinery for. Until now only
the two demo cases carried any, so almost every case ran with the new board and nothing
to put on it.

What changes

	before	after
estimatedDeathAt present	10	15
marked with revealsDeathTime	1	15
carrying places	2	17
time written with no route to it	9	0
route marked with no time to open	0	0

21 scenario files in all.

The nine were the ones worth fixing. Each had a death estimate written and no evidence
marked to disclose it, so the board would have kept its dotted window and its question
mark to the end of the case — a search with no finish. The authoring guide names this as
the worst of the three failures precisely because neither half is wrong on its own, so
validation cannot catch it.

Migrations

• 0021_scenario-investigation-upgrade.sql — the new place and disclosure data for
  databases already seeded.
• 0022_scenario-place-public-copy-safety.sql — rewrites the public half of the place
  entries (introduction, situation) to be spoiler-neutral. Private findings are
  untouched. Same rule as everywhere else in the case data: what the roster and the
  nameplate show is public and keyword-checked, what you learn by examining is earned.

Test plan

• bun run typecheck — clean
• bun run lint — no errors
• bun run test — 721 pass / 0 fail
• bun run db:seed — all 43 scenarios compile, and regenerating leaves seed.sql
  unchanged, so the committed seed matches the YAML
• reviewer: 0021 and 0022 both rewrite rows on an existing database — worth a
  look at whether the public copy in 0022 reads as neutral to someone who has not
  played the case