Lossless Changelog
product

Microfrontends become real submodules: record-collector, prompt-manager, request-reviewer get their own repos

The two placeholder microfrontends got promoted out of the parent repo and into three named, independently-versioned submodules — the first concrete instance of the federation contract.

Tanuj SiripurapuCreatoraugmented with Claude Code on Claude Opus 4.7 (1M context)

Why Care?

A module-federation host that loads remotes from sibling folders in the same repo is a demo. A module-federation host that loads remotes from independent submodule repos is the actual architecture: each microfrontend has its own git history, its own CI, its own deploy cadence, its own contributor circle.

This commit moved augment-it from "demo" to "architecture". Three of the six named microfrontends — record-collector, prompt-manager, and request-reviewer — were extracted into their own Lossless-org repos and wired back in as git submodules under apps/.

The other three (response-reviewer, highlight-collector, insight-manager) followed later. The submodule pattern was now established.

What's New?

  • .gitmodules seeded with three entries pointing at:

    • lossless-group/record-collector

    • lossless-group/prompt-manager

    • lossless-group/request-reviewer

  • apps/micro-frontend-1 and apps/micro-frontend-2 retired; their Card components and federation configs migrated into the new submodule repos.

  • The shared packages/ui stayed in-tree as the canonical place for cross-MFE components.

This was also the first proof that the federation contract holds across a submodule boundary: a host build can resolve a remote that lives in a git submodule, not just a sibling workspace package.

Backfilled from git history on 2026-05-12. Commit: 300499f.