chore: refresh uv.lock to current pyproject (catch-up) (#46)

The lockfile was stuck pinning attune-author at 0.6.1 (months
behind) because no recent release ran `uv lock` — CI uses
`pip install -e ".[dev]"`, so the lockfile drifts without any
CI signal flagging it.

Catch up to current main pyproject by running `uv lock` from a
clean main checkout. Bounded changes (all dev-only):

  - attune-author 0.6.1 → 0.14.1 (current release)
  - attune-help 0.10.1 → 0.11.1 (workspace sibling tracked
    editable; PyPI consumers unaffected since lockfile isn't
    shipped)
  - attune-rag pin spec `<0.2` → `<0.3` (matches the widen
    landed in v0.14.1)
  - attune-help marker moved from core dep → `[dev]`-only
    (matches the pyproject [dev] extra; was previously a core
    re-export that's been deprecated)
  - New transitive [dev] deps: pytest-asyncio 1.3.0,
    syrupy 5.2.0, backports-asyncio-runner 1.2.0 (all listed
    in pyproject [dev] but missing from the stale lock)

No runtime deps added. No public API surface affected. No
version bump (workflow-only-equivalent change).

Per the existing "Long-stale uv.lock + uv lock regen during a
release pulls in a dep cascade" lesson, this is the deferred
separate-PR catch-up, isolated from any release work.

Author: silversurfer562