nixfmt-rfc-style is now the same as pkgs.nixfmt and should be used
instead. This removes the explicit package override in treefmt and
updates devShells to use the standard nixfmt package.

- Remove nixfmt.package override in treefmt config (defaults to nixfmt)
- Replace nixfmt-rfc-style with nixfmt in devShells.default
- Update nix-workflow.md documentation to reflect the change

Use the setup-nix composite action for consistent Nix setup across
workflows, while still using nix develop for commands to leverage the
full devShell environment.

- Replace direct install-nix-action with setup-nix composite action
- Add skip-uv-sync since nix develop handles dependencies
- Keep nix develop --command for build commands

)

The skip-mock-server option was only used by the release workflow,
which now uses nix develop directly instead of the setup-nix action.
This simplifies the action by removing the unused input.

Add uv.lock to release-please extra-files so the lockfile version is
updated alongside pyproject.toml during releases. This prevents version
drift between the published package and the lockfile.

- Add generic updater for uv.lock in release-please config
- Update uv.lock to reflect current version (2.1.1)

Add --locked flag to uv sync commands to fail if uv.lock is out of sync
with pyproject.toml. This ensures lockfile consistency across CI and
local development.

- Add --locked to setup-nix action
- Add --locked to flake.nix shellHook

)

The release-please generic updater cannot reliably identify the correct
version line in uv.lock (too many packages have version fields). Instead,
run `uv lock` after release-please creates/updates the PR to regenerate
the lockfile with the updated pyproject.toml version.

- Remove extra-files config from release-please
- Add workflow steps to checkout release branch, run uv lock, and commit

Release-please already updates __init__.py version in the release PR,
making the update-version script and workflow step redundant.

- Remove update-version step from release workflow
- Remove update-version target from justfile
- Delete scripts/update_version.py

google-github-actions/release-please-action is deprecated in favour of
googleapis/release-please-action. Migrate to the new repository.

…x [ENG-11958] (#128)

* refactor(tools): rename meta tools to utility tools with tool_* prefix

Rename tool naming convention to avoid confusion with Facebook's Meta
brand. The "meta_*" prefix was ambiguous and could be misinterpreted.

File renames:
- stackone_ai/meta_tools.py -> stackone_ai/utility_tools.py
- tests/test_meta_tools.py -> tests/test_utility_tools.py
- examples/meta_tools_example.py -> examples/utility_tools_example.py

Tool name changes:
- meta_search_tools -> tool_search
- meta_execute_tool -> tool_execute
- meta_collect_tool_feedback -> tool_feedback

API changes:
- Tools.meta_tools() -> Tools.utility_tools()

Internal class renames:
- MetaToolSearchResult -> ToolSearchResult
- create_meta_search_tools() -> create_tool_search()
- create_meta_execute_tool() -> create_tool_execute()
- MetaSearchTool -> ToolSearchTool
- MetaExecuteTool -> ToolExecuteTool

All tests pass and documentation has been updated accordingly.

* docs(readme): update Features list to use Utility Tools naming

Update the Features bullet point from "Meta Tools" to "Utility Tools"
for consistency with the renamed section heading and tool names.

Bumps [python-multipart](https://github.com/Kludex/python-multipart) from 0.0.21 to 0.0.22.
- [Release notes](https://github.com/Kludex/python-multipart/releases)
- [Changelog](https://github.com/Kludex/python-multipart/blob/master/CHANGELOG.md)
- [Commits](Kludex/python-multipart@0.0.21...0.0.22)

---
updated-dependencies:
- dependency-name: python-multipart
  dependency-version: 0.0.22
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps the actions group with 1 update: [actions/checkout](https://github.com/actions/checkout).


Updates `actions/checkout` from 6.0.1 to 6.0.2
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@8e8c483...de0fac2)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: 6.0.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…ases (#129)

Add a new Claude Code skill that automates the release-please workflow:

- Create .claude/skills/release-please/SKILL.md with instructions for
  triggering a specific version release via Release-As commit trailer
- Update CLAUDE.md with Available Skills section documenting the new skill

Usage: /release-please <version> (e.g., /release-please 2.3.0)

The skill creates a branch, commits with Release-As trailer, and opens
a PR that triggers release-please to create a release for that version.

Release-As: 2.3.0

* chore(main): release stackone-ai 2.3.0

* chore: update uv.lock

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>