Restart augment-it on turbo, rsbuild, and Docker — fresh scaffold, brand assets, monorepo discipline
Why Care?
augment-it spent its first life as a bolt.new monolith — productive for getting
to a working demo, less suited to the module-federation future the project was
heading toward. Rather than retrofit a system we'd outgrown, we archived the
bolt branch and rebuilt the scaffold from scratch around the toolchain we
wanted: turborepo for orchestration, pnpm for installs, Docker for
reproducible local runs, and a clean
apps/ + packages/ layout ready to
host federated microfrontends.The previous-implementation analyses (
MainContainerUI, PromptSection,
APIProviderWidget, HighlightCollector) live under
content/projects/Augment-It/Previous-Implementations/ in the lossless
content repo — they're the design memory carried across the restart.What's New?
turbo.json— task pipeline forbuild,dev,lint,testacross the workspace.pnpm-workspace.yaml— workspace layout forapps/*+packages/*.Dockerfileat the repo root — containerizes the whole monorepo so local dev matches CI matches a future hosted runtime.- Brand assets dropped into
public/— app icon, wordmark, and a trademark banner. These are "temporary, better than nothing" placeholders that the splash now picks up. - README rewritten to describe the new shape rather than the bolt-era shape; subsequent passes refined it further.
- The bolt monolith preserved on the
archive/bolt-codebranch.
Backfilled from git history on 2026-05-12. Commits:
d473bee, 25a05e2,
79290eb, 039359e, 5e96020, 7597759, e88a234, 2556c35.