Prepare TinyBrowser 0.2.3 release version

[senamakel]

Bumps the workspace version 0.2.2 -> 0.2.3 (Cargo.toml + Cargo.lock) so the protected release workflow can tag v0.2.3 with #26's nested-pin updates (tinybus e5f1cd2, tinyjevclient 19ad7b1).

After merge: dispatch release.yml with release_version=0.2.3.

Summary by CodeRabbit

• Release
  • Updated the workspace package version to 0.2.3.

[tinysweeper]

Tiny Sweeper review

Tiny Sweeper reviewed this change across 6 lane(s) and found 3 active actionable finding(s). Detailed lane evidence and any incomplete work are listed below.

State: Changes requested
Priority: high
Reviewed head: 3e5a3802660c
Updated: 1790618315 (Unix time)

Review snapshot

Change surface	Files	Review signal	Count
Production	0	Active findings	3
Tests	0	Noted findings	0
Documentation	0	Resolved findings	0
Configuration	1	Pending checks/questions	0

Completeness: Complete
Test assessment: No supported feature-to-test mapping was available; this does not mean tests are absent or passed.

What changed

The review could not produce a supported behavioral summary; inspect the cited changed surface and lane details below.

Features

None identified with supported citations.

Tests

No supported feature-to-test mapping was produced. Test execution is not inferred.

Findings

• high · critique · Update Cargo.lock with the workspace version — The workspace members inherit this version, but `Cargo.lock` still records workspace package versions as `0.2.2`. Commands using `--locked`, including the repository's CI and relea (Cargo\.toml:22)
• high · security · Update the lockfile with the workspace version — This changes the workspace package version without updating `Cargo.lock`, which is committed for reproducible builds. The lockfile will retain the previous workspace package versio (Cargo\.toml:22)
• medium · description · Update Cargo.lock alongside the workspace version bump — The PR body says the version bump covers `Cargo.toml + Cargo.lock`, but the diff only touches `Cargo.toml`. Every workspace member is recorded in `Cargo.lock` with a concrete `vers (\(pull request description\))

Before merge

• Address Update Cargo.lock with the workspace version (Cargo\.toml).
• Address Update the lockfile with the workspace version (Cargo\.toml).

Agent review details

critique

• Conclusion: Failure
• Scope reviewed: all assigned evidence
• Lane summary: The workspace version is bumped to 0.2.3, but the committed lockfile remains at 0.2.2 for workspace packages. This is not safe to merge because locked CI and release commands will reject the stale lockfile. (1 observation(s) grouped into shared inline comments) _Memory was unavailable (model: cortex: v1/recall: timed out after 10s), so this review ran without it._
• Evidence: Cargo\.toml — Update Cargo.lock with the workspace version

security

• Conclusion: Failure
• Scope reviewed: all assigned evidence
• Lane summary: The workspace version bump is otherwise straightforward, but the committed lockfile must be updated alongside it before this can merge safely. _Memory was unavailable (model: cortex: v1/recall: timed out after 10s), so this review ran without it._
• Evidence: Cargo\.toml — Update the lockfile with the workspace version

tests

• Conclusion: Neutral
• Scope reviewed: all assigned evidence
• Lane summary: No behavioural change: nothing outside documentation, configuration and tests.

commits

• Conclusion: Neutral
• Scope reviewed: all assigned evidence
• Lane summary: Nothing sensitive found in what this pull request commits.

description

• Conclusion: Success
• Scope reviewed: all assigned evidence
• Lane summary: The change is a one-line workspace version bump 0.2.2 -> 0.2.3 in Cargo.toml, which matches the stated release intent, but the description also claims Cargo.lock was bumped and the diff contains no Cargo.lock change — so the lockfile is left describing the 0.2.2 members. Merge only after confirming or regenerating the lockfile. _Memory was unavailable (model: cortex: v1/recall: timed out after 10s), so this review ran without it._
• Evidence: \(pull request description\) — Update Cargo.lock alongside the workspace version bump

e2e

• Conclusion: Neutral
• Scope reviewed: all assigned evidence
• Lane summary: No behavioural change: nothing outside documentation, configuration and tests.

Evidence and run details

• Models: ladder/vectors, gpt-5.6-luna, deepseek-v4-flash
• Spend: $0.008928
• Tokens: 43078 input · 4409 output · 3814 cached · 34 embedding

Head	State	Pass summary
3e5a3802660c	changes requested	3 active finding(s), 0 resolved finding(s) (at 1790618315)

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-28T17:59:08.288774Z	3e5a380	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: ee9413e4-53bc-40a1-a5a1-b07009231d1e

📥 Commits

Reviewing files that changed from the base of the PR and between a0e97b5 and 3e5a380.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• Cargo.toml

 _________________________________________________________________________________________
< If you don't make mistakes, you're not working on hard enough problems. - Frank Wilczek >
 -----------------------------------------------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

---

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

[tinysweeper]

Requesting changes: 2 lane(s) blocking, worst finding is high.

Fix or reply to the findings below and push. The next review clears this automatically once they are gone — you should not need to dismiss anything by hand.

             $0.0089 · 43,078 in / 4,409 out · 3,814 cached (9%)  · ladder/vectors, gpt-5.6-luna, deepseek-v4-flash · 34 embedded
critique:    $0.0057 · 26,465 in / 1,103 out · 2,406 cached (9%)  · gpt-5.6-luna, deepseek-v4-flash
security:    $0.0031 · 11,653 in / 654 out   · 0 cached (0%)      · gpt-5.6-luna
description: $0.0001 · 3,511 in  / 1,693 out · 1,408 cached (40%) · deepseek-v4-flash