Lore CLI 0.9.3

Added

• Every plain lore agent context pack is query-augmented (LCLI-575; opum-doc ADR "Make lore
  agent context always query-augmented", ODOC-265, and its Amendment 1). A ## Bundle-wide query hits section lists up to
  three lore query hits for the task that the pack does not already quote, as id, title and
  snippet, with no bodies. In --json these are three additive fields on agent.context.export:
  queryHits, queryHitsOmitted (how many hits the token budget cut, so an empty section is never
  ambiguous between an empty corpus and a tight budget), and queryHitsSectionOmitted (set when
  the budget left no room for the section at all, a case also named on stderr). The section never
  raises the mandatory-pin floor: a --max-tokens that compiled before still compiles. With
  --workspace --repository, hits come from the selected members only. The opum-agent-workflow/v1
  projection (lore agent project, lore agent context --contract) does not carry the section:
  its embedded pack, packDigest and inputRevisions are byte-identical to 0.9.2's, so a
  document outside the profile's catalog cannot move a pinned digest (Amendment 1).
• lore help --json lists kindSchemaVersions, the per-kind schemaVersion overrides
  (additive; cli-contract §7.1). Today it is {"agent.context.export": 2}.

Changed

• lore agent context <unknown profile> exits 0, not 3. It degrades to the query section
  plus a warning, in the pack and on stderr, and sets profileMissing: true. This remaps an
  existing exit code, which the CLI contract treats as a contract-level change; it is recorded as
  amendment §5.6 there, citing ODOC-265 decision 2. agent show, agent project and agent context --contract are unchanged on an unknown profile.
• BREAKING (--json): the agent.context.export envelope's schemaVersion is 2 (was 1),
  for the exit 3 → 0 remap above — settled by the ADR's Amendment 1 (opum-doc main a8bb596)
  and recorded in cli-contract §5.6. The bump is scoped to that one kind: every other envelope,
  agent.workflow.projection included, stays schemaVersion 1. A consumer pinned to 1 for
  lore agent context --json should read profileMissing where it relied on exit 3, then
  accept 2.

Fixed

• The README quickstart runs (LCLI-571). It named a lore new spec --story option that never
  existed, and it coupled Backlog.md task ids that no fresh repository has, while lore init
  defaults the tracker to Quest. It now initializes Quest first, declares the actor Quest writes
  need, and links two tasks it creates. The install section names Quest. CI runs the quickstart
  verbatim from README.md against each freshly compiled binary, so it cannot silently break again.