🤖 This message was generated by kimi-k3 Preparation for the Starbase sync, which enables ruff 0.17 (via pre-commit), shfmt (canonical/starbase#565), and tombi (canonical/starbase#597) as default-enabled tooling. ## What changed - **ruff 0.17 findings** - ISC004: parenthesize implicit string concatenations in `rockcraft/extensions/springboot.py`, `rockcraft/plugins/java_common.py`, and `tests/unit/test_pebble.py` - ICN001: `import datetime as dt` convention in `rockcraft/services/package.py`, `rockcraft/services/project.py`, `tests/unit/test_oci.py`, `tests/unit/test_project.py` - PTH118/PTH120/PERF403: pathlib modernizations in `tools/schema/schema.py` - INP001: `noqa` comments for standalone config scripts (`extensions/django-framework/gunicorn.conf.py`, `extensions/flask-framework/gunicorn.conf.py`, `snap/local/sitecustomize.py`) - **shfmt**: formatting of `tools/freeze-requirements.sh` and `tools/spread/{install_rockcraft,run_rockcraft,setup_maven_proxy}` - **tombi**: formatting of test fixture `pyproject.toml` files (integration/spread fixtures only) ## Notes - The root `pyproject.toml` tombi reformat is intentionally excluded here; it will land with the merge PR since it depends on merged content. - These lint errors are pre-existing on main when linted with the latest ruff — CI installs ruff from snap, which is already at 0.17. ## Update (2026-10-19) Also folds in suppressions for the `ty` override diagnostics (`invalid-mutable-override` on the Project model's intentional pydantic field narrowing, `invalid-attribute-override` on the test-only DevelProject stub), matching the established convention in charmcraft/snapcraft/imagecraft. This makes the base of the PR stack green for both ruff and ty.