chore(deps): reconcile authoritative main lock

[sethkarten]

Replacement remediation

Append-only child of #2328, based on exact replacement N5 10608006dd5f996c884249ee4fe5f4399401c8b9.

This is the narrow authoritative-main lock reconciliation required because uv sync --locked refused c2820's stale uv.lock relative to its unchanged pyproject.toml.

Scope: only uv.lock (127 insertions / 1 deletion). uv lock resolved the same 269-package set with no additions/removals/version changes; it regenerated lock revision/provenance metadata for editable packages. pyproject.toml is unchanged. A disposable uv sync --locked subsequently succeeded and the environment/cache was deleted.

No live evaluation and no contributor branch mutation. Draft/HOLD pending replacement-chain tests and review.

Note

Reconcile authoritative main lock file

Updates uv.lock to reflect the latest resolved dependency versions for the main branch.

^{Macroscope summarized 66d4bf3.}

---

Note

Low Risk
Lockfile-only metadata reconciliation with no reported package additions, removals, or version bumps.

Overview
Regenerates uv.lock so it matches the current workspace without changing resolved package versions. The stale lock was blocking uv sync --locked even though pyproject.toml was unchanged.

The diff mainly adds [package.metadata] blocks (with requires-dist, and for the root verifiers package also provides-extras, requires-dev, and examples) for editable environment packages and the main project. Lock revision moves from 4 to 3 as part of that regeneration.

^{Reviewed by Cursor Bugbot for commit 66d4bf3. Bugbot is set up for automated code reviews on this repo. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved 0e1c5fe

This PR only updates the uv.lock dependency lock file with metadata blocks and a revision adjustment. Lock file changes are mechanical and do not affect runtime behavior.

No code changes detected at 66d4bf3. Prior analysis still applies.

^{You can customize Macroscope's approvability policy. Learn more.}