build(pyproject): adopt PEP 639 license metadata

[njzjz-bot]

Problem

• Several packages still use deprecated table-based project.license metadata.
• PEP 639 standardizes SPDX license plus license-files.

Change

• Replace deprecated project.license = {file/text = ...} with an SPDX expression.
• Add project.license-files.
• Raise the setuptools minimum version to one that supports PEP 639 where needed.
• Remove legacy License :: classifiers superseded by the SPDX expression.

Notes

• This change is metadata-only and does not alter runtime behavior.

Authored by OpenClaw (model: gpt-5.4)

Summary by CodeRabbit

• Chores
  • Updated build system requirements (setuptools ≥77.0.3)
  • Clarified project license declaration to LGPL-3.0-or-later

[codspeed-hq]

Merging this PR will not alter performance

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

✅ 2 untouched benchmarks

---

_{Comparing njzjz-bothub:openclaw/pep639-license (9bf47c5) with master (6af9314)}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.70%. Comparing base (6af9314) to head (9bf47c5).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #964   +/-   ##
=======================================
  Coverage   86.70%   86.70%           
=======================================
  Files          86       86           
  Lines        8039     8039           
=======================================
  Hits         6970     6970           
  Misses       1069     1069           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1e535489-9bbc-4225-acad-1124a667120f

📥 Commits

Reviewing files that changed from the base of the PR and between 6af9314 and 9bf47c5.

📒 Files selected for processing (1)

• pyproject.toml

---

📝 Walkthrough

Walkthrough

The pyproject.toml file was updated to increase the minimum setuptools version requirement from 61 to 77.0.3, change the license declaration from a file reference to an explicit LGPL-3.0-or-later identifier, add a license-files configuration, and remove one corresponding classifier entry.

Changes

Cohort / File(s)	Summary
Build system and license metadata pyproject.toml	Updated setuptools minimum version to 77.0.3; changed license declaration from file-based ({file = "LICENSE"}) to explicit identifier (LGPL-3.0-or-later); added license-files configuration; removed redundant LGPLv3 classifier entry.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'build(pyproject): adopt PEP 639 license metadata' clearly and concisely describes the main change: updating the project configuration to follow PEP 639 standards for license metadata.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}