Lore CLI 0.9.1

A patch release with one fix: lore new story scaffolds into docs/stories/ again (ODOC-262).
The rollout notes under 0.9.0 still apply unchanged. This release adds no exit code, type, alias
or field, so the profile digest does not move and committed schemas stay current.

Fixed

• lore new story scaffolds into docs/stories/ again, and still writes type: Arc
  (LCLI-570; ruling OPAG-376, recorded as opum-doc ODOC-262). 0.9.0 put both spellings in
  docs/arcs/. That broke lore's own README quickstart, which runs lore new story and then
  addresses stories/<slug>, and it broke a consumer that asserts the folder. Until 1.0.0 the
  output directory follows the spelling you typed: the Story spelling, in any case, scaffolds into
  docs/stories/, and lore new arc keeps docs/arcs/. The written type: is always the
  canonical Arc, so no new document carries the deprecated spelling. Documents 0.9.0 already wrote
  under docs/arcs/ stay where they are and keep working. Nothing migrates them, and an Arc
  validates, links and checks the same way in either directory. A custom profile whose canonical
  type is itself named Story also scaffolds into docs/stories/ again, as it did before 0.9.0.

Deprecated

• What 1.0.0 removes with the Story alias: the Story input spelling (lore new story,
  type: Story documents, lore query --type Story), story.schema.json, and the docs/stories/
  output path that lore new story uses. From 1.0.0, lore new arc is the only spelling and
  docs/arcs/ is the only scaffold directory. Documents already under docs/stories/ are not
  moved by lore; move them with lore rename before upgrading if you want them in docs/arcs/.