Develop

[suzuki3jp]

Summary by CodeRabbit

• Chores
  • Updated release automation to use a newer Changesets action.
  • Refreshed application, UI, playlist, and YouTube integration dependencies.
  • Updated framework, authentication, monitoring, database, API, and validation libraries.
  • Updated development tooling, testing utilities, Storybook, formatting tools, and related type definitions.
  • Updated internationalization, animation, navigation, and file-upload libraries for improved compatibility and maintenance.

[claude]

Claude finished @renovate[bot]'s task in 47s —— View job

---

Review summary

• Gather context (PR diff, changed files, prior review history)
• Check what changed since the last review pass
• Re-verify the previously flagged changesets/action vs @changesets/cli version issue
• Check CI status
• Post final review summary with severity-tagged findings and verdict

What changed since the last review

Two new commits landed on develop since the prior pass (d70fff7/7408ee9):

• d19cf02/476bb7b era commits were already covered; newest are c108278 — fix(deps): update dependency i18next to v26.4.2 (fix(deps): update dependency i18next to v26.4.2 #793) and 6d9ca08 — fix(deps): update dependency react-dropzone to v20.1.2 (fix(deps): update dependency react-dropzone to v20.1.2 #794). Both touch only apps/www/package.json (1 line each) + lockfile — routine patch bumps, no application code changed.

.github/workflows/release.yml is byte-for-byte unchanged — still last touched by e7ef34f (changesets/action → v2.1.2), same as every prior review pass.

Findings

CRITICAL — .github/workflows/release.yml:36 (unresolved, flagged by CodeRabbit and every Claude review pass since 2026-09-05)
uses: changesets/action@v2.1.2 is still in the incompatible v2.x line, which requires Changesets CLI v3. Root package.json:31 still pins @changesets/cli at 2.31.1 (v2). This mismatch has reproduced as a live failure across many prior Release runs on this branch:

##[warning]Unexpected input(s) 'publish', 'title', 'commit', valid inputs are ['github-token', 'publish-script', 'version-script', 'commit-message', 'pr-title', 'pr-draft', 'pr-base-branch', 'create-github-releases', 'push-git-tags', 'push-with-git-cli', 'cwd']
##[error]Error: This version of the Changesets action is designed to work with Changesets CLI v3. Changesets CLI v2 is not supported; use Changesets action v1 instead, which is compatible with CLI v2.

The Release run triggered by this push (run 35493826329) was still in progress with no failed steps recorded at review time, but since the workflow file is unchanged from the state that has already failed this way repeatedly for two weeks, the same outcome is expected once it reaches the publish step.

Fix (simplest): pin uses: changesets/action@v1 (line 36), matching the current CLI v2. Alternative (larger, full v3 migration): upgrade @changesets/cli to v3, bump Node to ≥22.11 (currently 20 on line 24), and rename the with: inputs publish/title/commit to publish-script/pr-title/commit-message.

• Not re-posting a duplicate inline comment — already flagged inline multiple times by CodeRabbit and prior Claude reviews with no fix applied.
• Note: I cannot modify .github/workflows/release.yml myself — GitHub App permissions for this integration don't allow workflow file edits. Someone with write access needs to apply the fix directly.

MAJOR (latent, pre-existing) — .github/workflows/release.yml
Once the above is fixed, setup-node (lines 21-24) still has no registry-url, and .npmrc has only save-exact=true — no registry auth line. packages/env, packages/shared, packages/youtube are all "private": false (publishable), so NODE_AUTH_TOKEN/NPM_TOKEN won't be wired into npm auth automatically once the CLI/action mismatch is resolved and pnpm release actually reaches the publish step. Not introduced by this diff.

Dependency bumps (package.json × 8, pnpm-lock.yaml) — no new issues
The two newest commits (i18next → v26.4.2, react-dropzone → v20.1.2) are routine patch bumps confined to apps/www/package.json. Previously reviewed major bumps (googleapis 148→175, framer-motion 12→13, react-dropzone 19→20 earlier) remain unchanged and unproblematic.

CI Status (at time of this review)

• Lint & format: ✅ success
• Release: 🔄 in progress, no failed steps yet (root-cause version mismatch unchanged — same failure expected once it reaches the publish step)
• Test, Bundle Size Analysis, Claude Review PR: in progress

Verdict

Request changes. Same conclusion as every prior pass on this PR: this remains a low-risk develop → main dependency sync at the application-code level, but it still carries the confirmed, repeatedly-reproducing Release workflow regression (changesets/action v2.x incompatible with @changesets/cli v2) first flagged on 2026-09-05 and still unaddressed two weeks later. Since on: push: branches: [develop] means this workflow doesn't re-trigger on the merge into main itself, this PR could be merged without immediate visible impact on main — but every push to develop continues to fail at the release step until this is reverted to v1 (or the full v2→v3 migration is completed).
(branch: develop)

[claude]

Claude finished @renovate[bot]'s task in 45s —— View job

---

Review summary

• Gather context (PR diff, changed files, prior review history)
• Check what changed since the last review pass
• Re-verify the previously flagged changesets/action vs @changesets/cli version issue
• Check CI status
• Post final review summary with severity-tagged findings and verdict

What changed since the last review

Two new commits landed on develop since the prior pass (c108278/6d9ca08), both routine patch bumps with no application code and no changes to .github/workflows/release.yml:

• df6e556 — fix(deps): update dependency hono to v4.13.8 (fix(deps): update dependency hono to v4.13.8 #796) — apps/api, apps/www, packages/playlist-action-job-client
• c66bd1d — fix(deps): update nextjs monorepo to v16.3.5 (fix(deps): update nextjs monorepo to v16.3.5 #797) — apps/www

.github/workflows/release.yml is byte-for-byte unchanged — I re-read it directly and it's still pinned to changesets/action@v2.1.2 at line 36, same publish/title/commit inputs (lines 38-40), same Node 20 in setup-node (line 24).

Findings

CRITICAL — .github/workflows/release.yml:36 (unresolved, flagged by CodeRabbit and every Claude review pass since 2026-09-05)
uses: changesets/action@v2.1.2 is still in the incompatible v2.x line, which requires Changesets CLI v3. Root package.json still pins @changesets/cli at 2.31.1 (v2). This mismatch has reproduced as a live failure across many prior Release runs on this branch:

##[warning]Unexpected input(s) 'publish', 'title', 'commit', valid inputs are ['github-token', 'publish-script', 'version-script', 'commit-message', 'pr-title', 'pr-draft', 'pr-base-branch', 'create-github-releases', 'push-git-tags', 'push-with-git-cli', 'cwd']
##[error]Error: This version of the Changesets action is designed to work with Changesets CLI v3. Changesets CLI v2 is not supported; use Changesets action v1 instead, which is compatible with CLI v2.

The Release run for this push (run 35512098193) was still pending at review time, but since the workflow file is unchanged from the state that has already failed this way repeatedly for over two weeks, the same outcome is expected once it reaches the publish step.

Fix (simplest): pin uses: changesets/action@v1 (line 36), matching the current CLI v2. Alternative (larger, full v3 migration): upgrade @changesets/cli to v3, bump Node to ≥22.11 (currently 20 on line 24), and rename the with: inputs publish/title/commit to publish-script/pr-title/commit-message.

• Not re-posting a duplicate inline comment — already flagged inline multiple times by CodeRabbit and prior Claude reviews with no fix applied.
• Note: I cannot modify .github/workflows/release.yml myself — GitHub App permissions for this integration don't allow workflow file edits. Someone with write access needs to apply the fix directly.

MAJOR (latent, pre-existing) — .github/workflows/release.yml
Once the above is fixed, setup-node (lines 21-24) still has no registry-url, and .npmrc has only save-exact=true — no registry auth line. packages/env, packages/shared, packages/youtube are all "private": false (publishable), so NODE_AUTH_TOKEN/NPM_TOKEN won't be wired into npm auth automatically once the CLI/action mismatch is resolved. Not introduced by this diff.

Dependency bumps (package.json × 8, pnpm-lock.yaml) — no new issues
The two newest commits (hono → v4.13.8, nextjs → v16.3.5) are routine patch bumps that don't touch application logic. Previously reviewed major bumps (googleapis 148→175, framer-motion 12→13, react-dropzone 19→20) remain unchanged and unproblematic.

CI Status (at time of this review)

All checks (Lint & format, Test, Bundle Size Analysis, Claude Review PR, Release) were pending/in progress at review time (just triggered by this push). Release is expected to reproduce the known failure once it reaches the publish step — root cause unchanged.

Verdict

Request changes. Same conclusion as every prior pass on this PR: this remains a low-risk develop → main dependency sync at the application-code level, but it still carries the confirmed, repeatedly-reproducing Release workflow regression (changesets/action v2.x incompatible with @changesets/cli v2) first flagged on 2026-09-05 and still unaddressed over two weeks later. Since on: push: branches: [develop] means this workflow doesn't re-trigger on the merge into main itself, this PR could be merged without immediate visible impact on main — but every push to develop continues to fail at the release step until this is reverted to v1 (or the full v2→v3 migration is completed).
(branch: develop)

[claude]

Claude finished @renovate[bot]'s task in 39s —— View job

---

Review summary

• Gather context (PR diff, changed files, prior review history)
• Check what changed since the last review pass
• Re-verify the previously flagged changesets/action vs @changesets/cli version issue
• Check CI status
• Post final review summary with severity-tagged findings and verdict

What changed since the last review

Two new commits since the prior pass (c108278/6d9ca08), both routine patch bumps with no application code changed:

• df6e556 — fix(deps): update dependency hono to v4.13.8 (fix(deps): update dependency hono to v4.13.8 #796) — apps/api, apps/www, packages/playlist-action-job-client
• c66bd1d — fix(deps): update nextjs monorepo to v16.3.5 (fix(deps): update nextjs monorepo to v16.3.5 #797) — apps/www

.github/workflows/release.yml is byte-for-byte unchanged — I re-read it directly and it's still pinned to changesets/action@v2.1.2 at line 36, same publish/title/commit inputs (lines 38-40), same Node 20 in setup-node (line 24).

Findings

CRITICAL — .github/workflows/release.yml:36 (unresolved, flagged by CodeRabbit and every Claude review pass since 2026-09-05)
uses: changesets/action@v2.1.2 is still in the incompatible v2.x line, which requires Changesets CLI v3. Root package.json still pins @changesets/cli at 2.31.1 (v2). This mismatch has reproduced as a live failure across many prior Release runs on this branch:

##[warning]Unexpected input(s) 'publish', 'title', 'commit', valid inputs are ['github-token', 'publish-script', 'version-script', 'commit-message', 'pr-title', 'pr-draft', 'pr-base-branch', 'create-github-releases', 'push-git-tags', 'push-with-git-cli', 'cwd']
##[error]Error: This version of the Changesets action is designed to work with Changesets CLI v3. Changesets CLI v2 is not supported; use Changesets action v1 instead, which is compatible with CLI v2.

The Release run triggered by this push (run 35512098193) was still pending at review time, but since the workflow file is unchanged from the state that has already failed this way repeatedly for over two weeks, the same outcome is expected once it reaches the publish step.

Fix (simplest): pin uses: changesets/action@v1 (line 36), matching the current CLI v2. Alternative (larger, full v3 migration): upgrade @changesets/cli to v3, bump Node to ≥22.11 (currently 20 on line 24), and rename the with: inputs publish/title/commit to publish-script/pr-title/commit-message.

• Not re-posting a duplicate inline comment — already flagged inline multiple times by CodeRabbit and prior Claude reviews with no fix applied.
• Note: I cannot modify .github/workflows/release.yml myself — GitHub App permissions for this integration don't allow workflow file edits. Someone with write access needs to apply the fix directly.

MAJOR (latent, pre-existing) — .github/workflows/release.yml
Once the above is fixed, setup-node (lines 21-24) still has no registry-url, and .npmrc has only save-exact=true — no registry auth line. packages/env, packages/shared, packages/youtube are all "private": false (publishable), so NODE_AUTH_TOKEN/NPM_TOKEN won't be wired into npm auth automatically once the CLI/action mismatch is resolved. Not introduced by this diff.

Dependency bumps (package.json × 8+, pnpm-lock.yaml) — no new issues
The two newest commits (hono → v4.13.8, Next.js monorepo → v16.3.5) are routine patch bumps that don't touch application logic. Previously reviewed major bumps (googleapis 148→175, framer-motion 12→13, react-dropzone 19→20) remain unchanged and unproblematic.

CI Status (at time of this review)

• Release: ⏳ pending (root-cause version mismatch unchanged — same failure expected once it runs)
• Test, Bundle Size Analysis, Lint & format, Claude Review PR: in progress (just triggered by this push)

Verdict

Request changes. Same conclusion as every prior pass on this PR: this remains a low-risk develop → main dependency sync at the application-code level, but it still carries the confirmed, repeatedly-reproducing Release workflow regression (changesets/action v2.x incompatible with @changesets/cli v2) first flagged on 2026-09-05 and still unaddressed a month later. Since on: push: branches: [develop] means this workflow doesn't re-trigger on the merge into main itself, this PR could be merged without immediate visible impact on main — but every push to develop continues to fail at the release step until this is reverted to v1 (or the full v2→v3 migration is completed).
(branch: develop)

[claude]

Claude finished @suzuki3jp's task in 1m 0s —— View job

---

Review summary

• Gather context (PR diff, changed files, prior review history)
• Check what changed since the last review pass
• Re-verify the previously flagged changesets/action vs @changesets/cli version issue
• Check CI status
• Post final review summary with severity-tagged findings and verdict

What changed since the last review

Two new commits landed on develop since the prior pass (df6e556/c66bd1d), both routine dependency bumps with no application-logic changes:

• 4b9f89c — chore(deps): update dependency knip to v6.35.1 (dev-tooling, root package.json + lockfile)
• 55a68d1 (merged via fix(deps): update react monorepo to v19.3.0 #792) — fix(deps): update react monorepo to v19.3.0 (apps/www/package.json, root package.json, packages/ui/package.json + lockfile)

.github/workflows/release.yml is byte-for-byte unchanged — I re-read it directly and it's still pinned to changesets/action@v2.1.2 at line 36, same publish/title/commit inputs (lines 38-40), same Node 20 in setup-node (line 24).

Findings

CRITICAL — .github/workflows/release.yml:36 (unresolved, flagged by CodeRabbit and every Claude review pass since 2026-09-05)
uses: changesets/action@v2.1.2 is still in the incompatible v2.x line, which requires Changesets CLI v3. Root package.json still pins @changesets/cli at 2.31.1 (v2). This mismatch has reproduced as a live failure across many prior Release runs on this branch:

##[warning]Unexpected input(s) 'publish', 'title', 'commit', valid inputs are ['github-token', 'publish-script', 'version-script', 'commit-message', 'pr-title', 'pr-draft', 'pr-base-branch', 'create-github-releases', 'push-git-tags', 'push-with-git-cli', 'cwd']
##[error]Error: This version of the Changesets action is designed to work with Changesets CLI v3. Changesets CLI v2 is not supported; use Changesets action v1 instead, which is compatible with CLI v2.

Fix (simplest): pin uses: changesets/action@v1 (line 36), matching the current CLI v2. Alternative (larger, full v3 migration): upgrade @changesets/cli to v3, bump Node to ≥22.11 (currently 20 on line 24), and rename the with: inputs publish/title/commit to publish-script/pr-title/commit-message.

• Not re-posting a duplicate inline comment — already flagged inline multiple times by CodeRabbit and prior Claude reviews with no fix applied.
• Note: I cannot modify .github/workflows/release.yml myself — GitHub App permissions for this integration don't allow workflow file edits. Someone with write access needs to apply the fix directly.

MAJOR (latent, pre-existing) — .github/workflows/release.yml
Once the above is fixed, setup-node (lines 21-24) still has no registry-url, and .npmrc has only save-exact=true — no registry auth line. packages/env, packages/shared, packages/youtube are all "private": false (publishable), so NODE_AUTH_TOKEN/NPM_TOKEN won't be wired into npm auth automatically once the CLI/action mismatch is resolved. Not introduced by this diff.

Dependency bumps (package.json × 8, pnpm-lock.yaml) — no new issues
The two newest commits (knip → v6.35.1, React monorepo → v19.3.0) are routine bumps confined to package.json/lockfile. Previously reviewed major bumps (googleapis 148→175, framer-motion 12→13, react-dropzone 19→20) remain unchanged and unproblematic. No application code in this diff touches any of these APIs.

Verdict

Request changes. Same conclusion as every prior pass on this PR: this remains a low-risk develop → main dependency sync at the application-code level, but it still carries the confirmed, repeatedly-reproducing Release workflow regression (changesets/action v2.x incompatible with @changesets/cli v2) first flagged on 2026-09-05 and still unaddressed a month later. Since on: push: branches: [develop] means this workflow doesn't re-trigger on the merge into main itself, this PR could be merged without immediate visible impact on main — but every push to develop continues to fail at the release step until this is reverted to v1 (or the full v2→v3 migration is completed).
(branch: develop)

[claude]

Claude finished @suzuki3jp's task in 57s —— View job

---

Review summary

• Gather context (PR diff, changed files, prior review history)
• Check what changed since the last review pass
• Re-verify the previously flagged changesets/action vs @changesets/cli version issue
• Check CI status
• Post final review summary with severity-tagged findings and verdict

What changed since the last review

Three new commits landed on develop since the prior pass (df6e556/c66bd1d):

• 4b9f89c — chore(deps): update dependency knip to v6.35.1 (chore(deps): update dependency knip to v6.35.1 #798) — root package.json, dev-tooling only
• 55a68d1 — fix(deps): update react monorepo to v19.3.0 (fix(deps): update react monorepo to v19.3.0 #792) — apps/www/package.json, packages/ui/package.json, root package.json; this is react/react-dom 19.2.8 → 19.3.0 and @types/react/@types/react-dom → 19.3.0, a minor bump within React 19, not a major version jump

Both are routine dependency bumps with no application logic changed. .github/workflows/release.yml is byte-for-byte unchanged — git log confirms it was last touched by e7ef34f (changesets/action → v2.1.2), same as every prior review pass; still pinned to changesets/action@v2.1.2 at line 36, same publish/title/commit inputs (lines 38-40), same Node 20 in setup-node (line 24).

Findings

CRITICAL — .github/workflows/release.yml:36 (unresolved, flagged by CodeRabbit and every Claude review pass since 2026-09-05)
uses: changesets/action@v2.1.2 is still in the incompatible v2.x line, which requires Changesets CLI v3. Root package.json still pins @changesets/cli at 2.31.1 (v2). This mismatch has reproduced as a live failure across many prior Release runs on this branch:

##[warning]Unexpected input(s) 'publish', 'title', 'commit', valid inputs are ['github-token', 'publish-script', 'version-script', 'commit-message', 'pr-title', 'pr-draft', 'pr-base-branch', 'create-github-releases', 'push-git-tags', 'push-with-git-cli', 'cwd']
##[error]Error: This version of the Changesets action is designed to work with Changesets CLI v3. Changesets CLI v2 is not supported; use Changesets action v1 instead, which is compatible with CLI v2.

The Release run triggered by this push (run 35534191251) was still in progress with no failed steps recorded at review time, but since the workflow file is unchanged from the state that has already failed this way repeatedly for over two weeks, the same outcome is expected once it reaches the publish step.

Fix (simplest): pin uses: changesets/action@v1 (line 36), matching the current CLI v2. Alternative (larger, full v3 migration): upgrade @changesets/cli to v3, bump Node to ≥22.11 (currently 20 on line 24), and rename the with: inputs publish/title/commit to publish-script/pr-title/commit-message.

• Not re-posting a duplicate inline comment — already flagged inline multiple times by CodeRabbit and prior Claude reviews with no fix applied.
• Note: I cannot modify .github/workflows/release.yml myself — GitHub App permissions for this integration don't allow workflow file edits. Someone with write access needs to apply the fix directly.

MAJOR (latent, pre-existing) — .github/workflows/release.yml
Once the above is fixed, setup-node (lines 21-24) still has no registry-url, and .npmrc has only save-exact=true — no registry auth line. packages/env, packages/shared, packages/youtube are all "private": false (publishable), so NODE_AUTH_TOKEN/NPM_TOKEN won't be wired into npm auth automatically once the CLI/action mismatch is resolved. Not introduced by this diff.

Dependency bumps (package.json × 8+, pnpm-lock.yaml) — no new issues
The two newest commits (knip → v6.35.1, React → v19.3.0) are routine minor/dev-tooling bumps that don't touch application logic. Previously reviewed major bumps (googleapis 148→175, framer-motion 12→13, react-dropzone 19→20) remain unchanged and unproblematic.

CI Status (at time of this review)

• Lint & format: ✅ success
• Release: 🔄 in progress, no failed steps yet (root-cause version mismatch unchanged — same failure expected once it reaches the publish step)
• Test, Bundle Size Analysis, Claude Review PR: in progress

Verdict

Request changes. Same conclusion as every prior pass on this PR: this remains a low-risk develop → main dependency sync at the application-code level, but it still carries the confirmed, repeatedly-reproducing Release workflow regression (changesets/action v2.x incompatible with @changesets/cli v2) first flagged on 2026-09-05 and still unaddressed a month later. Since on: push: branches: [develop] means this workflow doesn't re-trigger on the merge into main itself, this PR could be merged without immediate visible impact on main — but every push to develop continues to fail at the release step until this is reverted to v1 (or the full v2→v3 migration is completed).

[claude]

Claude finished @suzuki3jp's task in 30s —— View job

---

Review summary

• Gather context (PR diff, changed files, prior review history)
• Check what changed since the last review pass
• Re-verify the previously flagged changesets/action vs @changesets/cli version issue
• Check CI status
• Post final review summary with severity-tagged findings and verdict

What changed since the last review

One new commit landed on develop since the prior pass (55a68d1/knip 6.35.1):

• 2026411 — chore(deps): update dependency @cloudflare/workers-types to v5.20260915.1 (chore(deps): update dependency @cloudflare/workers-types to v5.20260915.1 #795) — apps/api/package.json (dev-tooling type bump only)

Routine, no application logic changed. .github/workflows/release.yml is byte-for-byte unchanged — I re-read it directly and it's still pinned to changesets/action@v2.1.2 at line 36, same publish/title/commit inputs (lines 38-40), same Node 20 in setup-node (line 24).

Findings

CRITICAL — .github/workflows/release.yml:36 (unresolved, flagged by CodeRabbit and every Claude review pass since 2026-09-05)
uses: changesets/action@v2.1.2 is still in the incompatible v2.x line, which requires Changesets CLI v3. Root package.json still pins @changesets/cli at 2.31.1 (v2). This mismatch has reproduced as a live failure across many prior Release runs on this branch:

##[warning]Unexpected input(s) 'publish', 'title', 'commit', valid inputs are ['github-token', 'publish-script', 'version-script', 'commit-message', 'pr-title', 'pr-draft', 'pr-base-branch', 'create-github-releases', 'push-git-tags', 'push-with-git-cli', 'cwd']
##[error]Error: This version of the Changesets action is designed to work with Changesets CLI v3. Changesets CLI v2 is not supported; use Changesets action v1 instead, which is compatible with CLI v2.

The Release run triggered by this push (run 35534539202) was still in progress with no failed steps recorded at review time, but since the workflow file is unchanged from the state that has already failed this way repeatedly for over two weeks, the same outcome is expected once it reaches the publish step.

Fix (simplest): pin uses: changesets/action@v1 (line 36), matching the current CLI v2. Alternative (larger, full v3 migration): upgrade @changesets/cli to v3, bump Node to ≥22.11 (currently 20 on line 24), and rename the with: inputs publish/title/commit to publish-script/pr-title/commit-message.

• Not re-posting a duplicate inline comment — already flagged inline multiple times by CodeRabbit and prior Claude reviews with no fix applied.
• Note: I cannot modify .github/workflows/release.yml myself — GitHub App permissions for this integration don't allow workflow file edits. Someone with write access needs to apply the fix directly.

MAJOR (latent, pre-existing) — .github/workflows/release.yml
Once the above is fixed, setup-node (lines 21-24) still has no registry-url, and .npmrc has only save-exact=true — no registry auth line. packages/env, packages/shared, packages/youtube are all "private": false (publishable), so NODE_AUTH_TOKEN/NPM_TOKEN won't be wired into npm auth automatically once the CLI/action mismatch is resolved. Not introduced by this diff.

Dependency bumps (package.json × 8, pnpm-lock.yaml) — no new issues
The newest commit (@cloudflare/workers-types → v5.20260915.1) is a dev-tooling type-only bump. Previously reviewed major bumps (googleapis 148→175, framer-motion 12→13, react-dropzone 19→20) remain unchanged and unproblematic. No application code in this diff touches any of these APIs.

CI Status (at time of this review)

• Lint & format: ✅ success
• Release: 🔄 in progress, no failed steps yet (root-cause version mismatch unchanged — same failure expected once it reaches the publish step)
• Test, Bundle Size Analysis, Claude Review PR: in progress

Verdict

Request changes. Same conclusion as every prior pass on this PR: this remains a low-risk develop → main dependency sync at the application-code level, but it still carries the confirmed, repeatedly-reproducing Release workflow regression (changesets/action v2.x incompatible with @changesets/cli v2) first flagged on 2026-09-05 and still unaddressed a month later. Since on: push: branches: [develop] means this workflow doesn't re-trigger on the merge into main itself, this PR could be merged without immediate visible impact on main — but every push to develop continues to fail at the release step until this is reverted to v1 (or the full v2→v3 migration is completed).
(branch: develop)