Bolt-era Augmenter monolith reaches a working demo — React + Supabase + three LLM providers in one repo

Why Care?

augment-it as it exists today — six federated microfrontends, a host shell, a shared UI package — learned its shape from a project that no longer runs. For two weeks in January 2025, the entire workshop was a single React app, vibe-coded on Bolt.new, backed by Supabase, talking to three different LLM providers. It was never going to be the production system. It was going to be the specification by way of running code.

The components in that monolith map directly to the microfrontends we're rebuilding now:

Bolt-era component	Today's microfrontend
`RecordList.tsx`, `DataModelModal.tsx`	`record-collector`
`PromptList.tsx`, `PromptSection.tsx`, `PromptSectionEdit.tsx`	`prompt-template-manager`
`RequestEditor.tsx`, `EditQueryOptions.tsx`	`request-reviewer`
`QueryResponse.tsx`, `QueryResponseList.tsx`, `ResponseObjectReviewer.tsx`	`response-reviewer`
`HighlightsList.tsx`, `ResponseObjectHighlighter.tsx`, `ResponseHighlight.tsx`	`highlight-collector`
(planned but not built)	`insight-manager`

That mapping is the most valuable artifact this era produced. The 2025-01-27 progress update — embedded GIFs of the working app — is the visual evidence.

What's New?

(Reconstructed from the snapshot at mpstaton/augment-bolt-code, which is a single-commit archive dropped on 2025-07-23 of the working tree at that point.)

~25 React components covering every stage of the augmentation pipeline — prompts, requests, responses, highlights, records, user accounts, data-model modals.
Supabase backend with 12 SQL migrations spanning Jan 18 (heavy_trail) to Jan 27 (lively_king) — auth, records table, prompt templates, responses, highlights, password reset flow.
Three LLM response handlers under src/lib/response-handlers/: claude.ts, gpt.ts, perplexity.ts. The provider-agnostic prompt-to- response loop that today's request-reviewer + response-reviewer microfrontends will rebuild on a federated footing.
Tailwind + Vite + TypeScript baseline. The styling system the rebuild deliberately moved away from when it adopted the shared-UI package + module-federation contract.
A .bolt/ directory carrying the original Bolt prompts that authored the codebase — useful artifact for understanding how the components got shaped.

Why We Left It

A working monolith is a great spec and a terrible production system — especially one where every screen is intended for an independent contributor team to own. Once the conceptual model was clear, the shape that fit the actual use case (microfrontends, federated, each team owns one surface) was incompatible enough with the monolith that a restart was cheaper than a refactor.

Archived to mpstaton/augment-bolt-code (private) on 2025-07-23 as a single-commit snapshot. The component-by-component design memory was extracted into the Previous-Implementations/ analyses under content/projects/Augment-It/ in the Lossless content repo.

ℹ️

Backfilled from the augment-bolt-code repository snapshot on 2026-05-12. Source commit: d473bee (single-shot archive dump). Work itself spans Jan 18–27 2025 per the Supabase migrations.