chore: rename workspace packages to @akeru/*

[leoisadev1]

The workspace packages still used the upstream @t3tools/* scope, and the lint plugin still ran its rules as t3code/.... Akeru's own code and tooling referred to itself by T3 Code's package names.

This renames the 13 private workspace manifests to @akeru/* and updates every import, CI and Docker filter, Vite+ task selector, changeset key, doc reference and lockfile entry to match. The lint plugin moves to oxlint-plugin-akeru, and its five rules and their suppressions now use the akeru/ prefix. The stale t3code-relay CI filter is gone, since no such workspace exists.

The published akeru-bot package is unchanged. So are app identity, storage and migration keys, environment variables, wire strings and native module names. Those need compatibility work and are out of scope here.

Verification:

• 202 lint-plugin and script tests pass, including the CI workflow policy, desktop artifact, release version and dev runner tests.
• Lint on files with renamed suppressions reports no errors, and the rules report under akeru(...).
• tsgo is clean for apps/server, apps/web, apps/desktop, packages/client-runtime and scripts. apps/mobile has the same 33 errors main already has.
• changeset status resolves every pending changeset under the new names.
• The lockfile diff contains only renamed and reordered entries, with no version changes.

Created with Claude Opus 5.5 in Claude Code.

---

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
akeru-bot-landing	Building	Preview	Sep 30, 2026 9:48pm UTC

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[greptile-apps]

Confidence Score: 4/5

[High risk] Renames internal workspace packages across the entire codebase.

The PR appears safe to merge; the historical changelog accuracy concern is non-blocking.

Findings

1.  Historical releases renamed ▶

Summary

The PR renames private workspace packages and the lint plugin from upstream names to @akeru/*, updating imports, dependency metadata, build filters, and documentation.

• The active package references and build selectors examined are consistent with the new names.
• Historical changelog headings should retain the names under which those releases were recorded.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  M[Renamed workspace manifests] --> I[Application imports]
  M --> L[pnpm lockfile]
  M --> B[CI and release filters]
  P[Renamed lint plugin] --> C[Lint configuration and suppressions]
  M --> R[Changesets release configuration]

Loading

_{Reviews (1) · Last reviewed commit: "style: reformat imports and manifests af..."}

[greptile-apps]

Historical releases renamed The changed heading labels an older release as @akeru/web, though that release was recorded under @t3tools/web. The same change appears in the desktop and contracts changelogs. This is non-blocking, but it makes past entries inaccurate when readers compare them with release-era manifests. Keep the original names for past releases and document the rename separately. Confidence in this suggestion: 4/5.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!