docs: correct stale 'blocked' claims in gil_benchmark.py (LAB-3035)

[27Bslash6]

Correct the module docstring and runtime footer in the free-threading performance harness.

Summary

• The core StandardSerializer path (msgpack + Rust ByteStorage) now runs free-threaded
• Only cross-library comparisons (orjson/numpy/pandas/pyarrow) remain unavailable due to missing cp314t wheels
• Updated docstring and footer to reflect current state: core path is no longer blocked
• No logic or behavior changes

Size

XS (trivial text/docstring correction)

Testing

• Ruff lint: ✓ Passed
• Ruff format: ✓ Passed (1 file already formatted)
• No logic changes to test

Summary by CodeRabbit

• Documentation
  • Updated benchmark guidance to clarify that the standard serialization path runs on free-threaded Python interpreters.
  • Clarified that cross-library performance comparisons are currently unavailable because compatible wheels are not provided for the listed libraries.
  • Removed outdated information stating that the free-threaded path was blocked by the underlying integration layer.

[kodus-27b]

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.

​

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Team

Run ID: 4e8378aa-0f23-4549-a3a1-ae9d6f5ed278

📥 Commits

Reviewing files that changed from the base of the PR and between f22d525 and ae0fb34.

📒 Files selected for processing (1)

• tests/performance/gil_benchmark.py

Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

---

Walkthrough

The benchmark documentation and GIL-enabled runtime message now state that StandardSerializer runs under free-threaded interpreters. Cross-library comparisons remain unavailable because the listed libraries lack cp314t wheels.

Changes

Benchmark messaging

Layer / File(s)	Summary
Update benchmark documentation and output tests/performance/gil_benchmark.py	The documentation and GIL-enabled output identify StandardSerializer as free-threading-capable. They report that cross-library comparisons remain unavailable because the named libraries lack free-threaded wheels.

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

Merge Risk: ⚪ Minimal · up to ae0fb

Benchmark messaging now accurately separates free-threaded StandardSerializer support from unavailable optional-library comparisons. No merge-readiness risk remains.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check	⚠️ Warning	The description explains the change, motivation, scope, and testing. It does not follow the required template and omits the Type of Change, Security Checklist, Backward Compatibility, and Additional N…	Update the description to use the repository template. Include the required checklists and explicitly mark non-applicable items, including that this is a documentation update with no public API, security, dependency, or behaviour changes.

✅ Passed checks (3 passed)

Check name	Status	Explanation
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.
Title check	✅ Passed	The title clearly identifies the correction of stale blocked claims in gil_benchmark.py and includes the relevant issue reference.

Full details: Description check

Explanation

The description explains the change, motivation, scope, and testing. It does not follow the required template and omits the Type of Change, Security Checklist, Backward Compatibility, and Additional Notes sections.

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 2

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch agent/haiku/824ec8fb182d

---

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

[kodus-27b]

Violates team rule 'Replace print statements with logging framework': Use the standard logging module (or your app's logger) instead of print() in committed code.

Also found in:

• tests/performance/gil_benchmark.py:88-88
• tests/performance/gil_benchmark.py:89-89

Prompt for LLM

File tests/performance/gil_benchmark.py:

Line 87:

Violates team rule 'Replace print statements with logging framework': Use the standard logging module (or your app's logger) instead of print() in committed code.

_{Talk to Kody by mentioning @kody}

_{Was this suggestion helpful? React with 👍 or 👎 to help Kody learn from this interaction.}

​

​