Upgrade smithers-orchestrator to smthrs

[roninjin10]

What

The smithers-orchestrator package was renamed on npm to smthrs (with the @smithers-orchestrator/* scope becoming @smthrs/*). There is no compat alias, so the old name no longer receives updates. This PR migrates the repo's .smithers/ workflow pack from smithers-orchestrator@^0.20.3 to smthrs@^0.33.0.

Changes (33 files)

• .smithers/package.json: dependency renamed to smthrs@^0.33.0.
• .smithers/tsconfig.json: jsxImportSource updated to smthrs.
• All workflows, components, agents, UI, gateway, and preload files: /** @jsxImportSource smthrs */ pragmas and import ... from "smthrs" (incl. subpath imports) swept.
• .smithers/bun.lock regenerated against the new manifest.

Breaking-change migrations

Per the 0.21 → 0.33 changelogs, the only applicable breaking change was the package/scope rename itself. The Node 22 minimum requirement was verified against Node 24. No other code migrations were needed.

Verification

• git grep smithers-orchestrator is clean (zero matches).
• Independent review: "Mergeable. The required grep is empty; all source changes are the package, subpath, and JSX import rename required by the Smithers 0.33.0 changelog. smthrs 0.33.0 is published, JSON and diff integrity checks pass, and the Bun lockfile resolves the new manifest dependency without unrelated manifest changes."

🤖 Generated with Claude Code

Summary by CodeRabbit

• Maintenance
  • Updated the application’s orchestration package integration to the latest smthrs package.
  • Existing agents, workflows, plugins, and UI behavior remain unchanged.
  • Improved compatibility across all orchestration features without changing configuration.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4a8b2a1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@roninjin10 is attempting to deploy a commit to the evmts Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 85560fd2-67dd-4af7-90fa-2c77d2dea69d

📥 Commits

Reviewing files that changed from the base of the PR and between 6199d04 and 4a8b2a1.

⛔ Files ignored due to path filters (1)

• .smithers/bun.lock is excluded by !**/*.lock

📒 Files selected for processing (32)

• .smithers/agents.ts
• .smithers/agents/claude-code.ts
• .smithers/agents/codex.ts
• .smithers/agents/gemini.ts
• .smithers/components/CommandProbe.tsx
• .smithers/components/FeatureEnum.tsx
• .smithers/components/ForEachFeature.tsx
• .smithers/components/GrillMe.tsx
• .smithers/components/Review.tsx
• .smithers/components/ValidationLoop.tsx
• .smithers/components/WriteAPrd.tsx
• .smithers/gateway.ts
• .smithers/package.json
• .smithers/preload.ts
• .smithers/tsconfig.json
• .smithers/ui/kanban.tsx
• .smithers/workflows/audit.tsx
• .smithers/workflows/debug.tsx
• .smithers/workflows/feature-enum.tsx
• .smithers/workflows/grill-me.tsx
• .smithers/workflows/implement.tsx
• .smithers/workflows/improve-test-coverage.tsx
• .smithers/workflows/kanban.tsx
• .smithers/workflows/mission.tsx
• .smithers/workflows/plan.tsx
• .smithers/workflows/ralph.tsx
• .smithers/workflows/research-plan-implement.tsx
• .smithers/workflows/research.tsx
• .smithers/workflows/review.tsx
• .smithers/workflows/ticket-create.tsx
• .smithers/workflows/tickets-create.tsx
• .smithers/workflows/write-a-prd.tsx

---

📝 Walkthrough

Walkthrough

The Smithers configuration now depends on smthrs. Agents, components, gateway integrations, JSX settings, and workflows use smthrs imports. Runtime behavior and agent configuration remain unchanged.

Changes

Smithers package migration

Layer / File(s)	Summary
Package and runtime integration .smithers/package.json, .smithers/tsconfig.json, .smithers/gateway.ts, .smithers/preload.ts, .smithers/ui/kanban.tsx	Replaced the smithers-orchestrator dependency and integration imports with smthrs equivalents.
Agents and orchestration components .smithers/agents*, .smithers/components/*	Updated agent, JSX runtime, orchestration API, and type imports to use smthrs.
Workflow package imports .smithers/workflows/*	Updated workflow JSX runtime directives and orchestration imports to use smthrs.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the package migration from smithers-orchestrator to smthrs.
Description check	✅ Passed	The description explains the migration, lists affected areas, and documents verification steps, but omits the template's Additional Information section.
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 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint install failed: dependency version conflict. Check your lock file or package.json.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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