chore(release): prepare 0.57.0

[elkaix]

Related Issue

N/A - release preparation PR.

Description

• Bump version 0.56.0 -> 0.57.0 across pyproject.toml, uv.lock, README, docs, and installer references.
• Consume ## Unreleased into a new ## 0.57.0 (2026-07-05) CHANGELOG section covering the ghost input-prompt/TUI stability fixes, native /benchmark command suite, and benchmark/skill security hardening.
• Sync the release notes into docs/en/release-notes/changelog.md and add the 0.57.0 no-breaking-changes entry.
• Resolve CodeRabbit release-note comments by aligning /benchmark discover and Windows installer signing wording with the implemented behavior.

Checklist

• I have read the CONTRIBUTING document.
• I have linked the related issue, if any.
• I have added tests that prove my fix is effective or that my feature works.
• I have run make gen-changelog to update the changelog.
• I have run make gen-docs to update the user documentation.

Note: make gen-changelog and make gen-docs were invoked and exited 0, but the current local Pythinker command reported Unknown slash command for /skill:gen-changelog and /skill:gen-docs; npm run build in docs/ performed the actual changelog sync and docs build validation.

Test plan

• scripts/check_version_tag.py — pyproject matches 0.57.0.
• README contains "What's New in 0.57.0" and pythinker-code==0.57.0 upgrade snippet.
• CHANGELOG.md has ## 0.57.0 ( heading.
• scripts/check_pythinker_dependency_versions.py — workspace package versions match.
• pytest tests/test_installation_docs.py tests/test_homebrew_formula.py — 17 passed.
• make build-web build-dashboard run locally to refresh bundled UI version fallback.
• git grep -F "0.56.0" outside CHANGELOG/history — no stray references.
• npm run build from docs/ — docs sync and VitePress build passed.
• git diff --check — whitespace check passed.

Summary by CodeRabbit

• New Features

  • Added a native /benchmark command with local, deterministic evaluation and generated artifacts, metrics, and reports.
  • Improved the TUI experience by removing duplicate input prompts and refining active-work status display.

• Bug Fixes

  • Hardened benchmark and skill-handling behavior with safer validation, better recovery after setup issues, and clearer failure reporting.

• Documentation

  • Updated release notes and installation guides for version 0.57.0 across Windows and Linux.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 40c5ce97-b782-4bce-a111-7f72fbec3c87

📥 Commits

Reviewing files that changed from the base of the PR and between c86960d and e33ad42.

⛔ Files ignored due to path filters (1)

• docs/en/release-notes/changelog.md is excluded by !docs/**

📒 Files selected for processing (2)

• CHANGELOG.md
• README.md

---

📝 Walkthrough

Walkthrough

This PR bumps the project version to 0.57.0 and updates the changelog and installation documentation to reference the new release artifacts, checksum files, and installer names.

Changes

Release 0.57.0 Version Bump

Layer / File(s)	Summary
Version bump pyproject.toml	Package version incremented from 0.56.0 to 0.57.0.
Changelog consolidation CHANGELOG.md	0.57.0 release section reworked into three consolidated bullets, with upgrade guidance retained.
README release notes and install instructions README.md	What's New text, Windows installer references, Linux package URLs, and checksum commands updated to 0.57.0.
Linux installer docs packages/linux-installer/README.md	Install commands, checksum targets, build script example, and dist output filenames updated to 0.57.0.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• Pythoughts-labs/pythinker-code#193: Same release-bump pattern updating changelog/README/installer artifact URLs and pyproject.toml version.
• Pythoughts-labs/pythinker-code#176: Similar version bump across pyproject.toml, CHANGELOG.md, README.md, and installer docs.
• Pythoughts-labs/pythinker-code#156: Same set of release docs and version pins updated for a prior release.

Suggested labels: dependencies

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title follows conventional commits and clearly matches this release-preparation change.
Description check	✅ Passed	The description matches the template structure and includes summary, checklist, and test plan; the related issue is reasonably marked N/A for a release PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/0.57.0

---

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

[coderabbitai]

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CHANGELOG.md`:
- Around line 29-33: Update the benchmark release note in CHANGELOG.md to use
the exact command name exposed by the suite: replace the mention of
source-discovery with discover, and keep export described as part of /benchmark.
Use the existing /benchmark suite wording and the benchmark command symbols to
ensure the listed subcommands match the implemented interface.

In `@README.md`:
- Around line 55-57: The release notes mention a benchmark subcommand name that
does not match the actual CLI surface. Update the README/changelog entry that
lists the `/benchmark` suite so it uses the real subcommand name from the
benchmark command registration, alongside the existing `/benchmark export` and
other benchmark actions. Keep the wording consistent with the benchmark command
implementation and any related documentation references.
- Around line 193-196: The Windows installer description is inconsistent with
the signing warning: the README copy in the installer section should match the
actual Authenticode behavior. Update the text around the
`PythinkerSetup-0.57.0.exe` installer reference to either remove the `signed*`
claim or make it explicitly conditional on the secrets being present, and ensure
the SmartScreen note uses the same wording so both sections agree.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: ade823ca-f736-45ad-a200-3c5698041138

📥 Commits

Reviewing files that changed from the base of the PR and between 33ebf96 and c86960d.

⛔ Files ignored due to path filters (4)

• docs/en/guides/getting-started.md is excluded by !docs/**
• docs/en/release-notes/breaking-changes.md is excluded by !docs/**
• docs/en/release-notes/changelog.md is excluded by !docs/**
• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• CHANGELOG.md
• README.md
• packages/linux-installer/README.md
• pyproject.toml

[elkaix]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!