[Bug]: A4P Python SDK：README.md快速开始中uv sync --locked会报错The lockfile at `uv.lock` needs to be updated，以及pyproject.toml 未把 pytest 声明为依赖

[openjiuwen-collaboration-bot]

Checklist

• I have searched for related issues but did not get the expected help.
• This bug has not been fixed in the latest version.
• Please note that if your bug description lacks corresponding environment information and a minimal reproducible demo, it will be difficult for us to reproduce and resolve the issue, which will reduce the possibility of receiving feedback, or even lead to the issue being closed.

🐞 Detailed Description of the Problem

1. README.md快速开始中执行uv sync --locked会报错The lockfile at uv.lock needs to be updated, but --locked was provided. To update the lockfile, run uv lock.
   $ uv sync --locked
   Using CPython 3.11.4 interpreter at: D:\Python\Python311\python.exe
   Creating virtual environment at: .venv
   鉅？[0m a4p==0.2.0
   Resolved 47 packages in 2.87s
   The lockfile at uv.lock needs to be updated, but --locked was provided. To update the lockfile, run uv lock.

2.pyproject.toml 未把 pytest 声明为依赖
pyproject.toml 未把 pytest 声明为依赖，依赖系统全局 pytest。若全局 pytest 的 shebang 指向的系统 Python 与 venv 不一致（例如指向 Python 3.11 但 webauthn 装在 venv 的 Python 3.14 下），直接 uv run pytest 会因找不到 webauthn 失败 1 项用例（test_webauthn_dependency_exports_are_loadable）。

Detailed Environment Information Description

Windows 11 专业版

Additional Information

Version Information

Thanks for your contribution 🎉!

[openjiuwen-collaboration-bot]

已由 #274 解决