Relock uv.lock after the version bump, and run CI on develop pushes (#78)

* Relock uv.lock after the version bump

a086ca6 raised the version to 0.1.0 in pyproject.toml without relocking, so
uv.lock still records 0.0.1 for this package and `uv lock --check` fails. develop
is red on that step right now, and so is every pull request based on it.

One line. This is the check #62 added, working as intended.

Signed-off-by: thc1006 <84045975+thc1006@users.noreply.github.com>

* Run CI on pushes to develop, not only to main

The stale lockfile in the previous commit reached develop and stayed red without
anyone seeing it, because the workflow only triggers on pushes to main and on
pull requests. A direct push to develop runs nothing.

A pull request that targets develop still fires on pull_request alone, so this
does not double up the ordinary case. It does double up one case: #61 has develop
as its head branch, so a push to develop now produces both a push run and a
synchronize run for #61. Those are not the same tree, since the pull request run
tests develop merged into main, and the concurrency key keys on the ref so
neither cancels the other. That seems worth the extra run rather than something
to suppress.

Signed-off-by: thc1006 <84045975+thc1006@users.noreply.github.com>

---------

Signed-off-by: thc1006 <84045975+thc1006@users.noreply.github.com>

Author: thc1006

.github/workflows/ci.yml

@@ -2,7 +2,10 @@ name: CI
 
 on:
   push:
-    branches: [main]
+    # develop as well as main. Work reaches the integration branch by merge and
+    # occasionally by direct push, and neither used to run anything here, so a
+    # regression could sit on develop until some later pull request inherited it.
+    branches: [main, develop]
   pull_request:
   workflow_dispatch: