Convert the repository from a single package with mixed server, database, web, TUI, and tooling concerns into a real npm-workspaces monorepo orchestrated by Turbo.
Use webnet/webnet as the local reference for the root workspace manifest, root scripts, turbo.json, lockfile ownership, and CI cache integration.
Proposed direction
Keep npm as the only package manager and retain one root package-lock.json.
Add root workspaces and packageManager metadata.
Split independently buildable/runtime concerns into clearly named packages or apps, with an explicit package for the server entry point.
Move shared schemas, database interfaces/backends, and reusable UI/client code into packages according to actual dependency boundaries.
Use package-level scripts and turbo run from root scripts for build, typecheck, test, lint, and formatting where appropriate.
Encode task dependencies and outputs in turbo.json so builds and CI can cache correctly.
Acceptance criteria
npm ci from the repository root installs every workspace reproducibly.
Root build, test, typecheck, lint, and format-check commands cover all relevant workspaces.
Turbo task dependencies reflect real package dependencies and cache only declared outputs.
Existing CLI/server/TUI entry points continue to build and run from documented commands.
Workspace boundaries do not introduce dependency cycles or duplicate shared code.
CI is updated to use the workspace/Turbo structure and cache.
Migration and developer commands are documented.
## Goal
Convert the repository from a single package with mixed server, database, web, TUI, and tooling concerns into a real npm-workspaces monorepo orchestrated by Turbo.
Use `webnet/webnet` as the local reference for the root workspace manifest, root scripts, `turbo.json`, lockfile ownership, and CI cache integration.
## Proposed direction
- Keep npm as the only package manager and retain one root `package-lock.json`.
- Add root `workspaces` and `packageManager` metadata.
- Split independently buildable/runtime concerns into clearly named packages or apps, with an explicit package for the server entry point.
- Move shared schemas, database interfaces/backends, and reusable UI/client code into packages according to actual dependency boundaries.
- Use package-level scripts and `turbo run` from root scripts for build, typecheck, test, lint, and formatting where appropriate.
- Encode task dependencies and outputs in `turbo.json` so builds and CI can cache correctly.
## Acceptance criteria
- `npm ci` from the repository root installs every workspace reproducibly.
- Root build, test, typecheck, lint, and format-check commands cover all relevant workspaces.
- Turbo task dependencies reflect real package dependencies and cache only declared outputs.
- Existing CLI/server/TUI entry points continue to build and run from documented commands.
- Workspace boundaries do not introduce dependency cycles or duplicate shared code.
- CI is updated to use the workspace/Turbo structure and cache.
- Migration and developer commands are documented.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Goal
Convert the repository from a single package with mixed server, database, web, TUI, and tooling concerns into a real npm-workspaces monorepo orchestrated by Turbo.
Use
webnet/webnetas the local reference for the root workspace manifest, root scripts,turbo.json, lockfile ownership, and CI cache integration.Proposed direction
package-lock.json.workspacesandpackageManagermetadata.turbo runfrom root scripts for build, typecheck, test, lint, and formatting where appropriate.turbo.jsonso builds and CI can cache correctly.Acceptance criteria
npm cifrom the repository root installs every workspace reproducibly.