FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Moving the Web application into an independent monorepo app
Separating Web ownership from workspace orchestration and database responsibilities without changing behavior
Purpose
The Web application at the workspace root needed a clear app boundary before later components could join the same workspace.
Execution ownership had to be separated without changing interface behavior, delivery behavior, dependency versions, or database assets.
Implementation
Web source, public assets, 3D assets, configuration, scripts, and runtime templates were moved unchanged into Web application package. The root owns workspace orchestration and database commands, while the Web package owns application-specific commands and dependencies.
- Manage the orchestrator and Web package with one root lockfile.
- Exclude app-local environment, build, Worker, and TypeScript outputs with a nested ignore file.
- Hoist only the required type packages to preserve pre-move type resolution.
- Align validation, delivery, and monitoring working locations and configuration references with the new app boundary.
- Keep database schema, migrations, and SQL tests at the root boundary.
The baseline validator now checks unchanged file content, absence of root duplicates, package ownership, and execution locations, while fixing the unchanged status of excluded settings and database assets.
This shows the workspace definition at the primary Commit cutoff. The root resolves apps, services, and shared packages while explicitly naming required type and build packages.
Rendering diagram…
What was confirmed
Verification results
All 24 workspace-validator tests, 90 Web tests, linting, type checks, and the Next build passed.
The Worker build, secret scan over 1,253 files, and upload-bundle dry run passed.
Database linting, five SQL smoke suites, concurrency checks, full and partial rollback, and a final local reset passed.
Inventories of moved assets and source matched, with no duplicate left at the root.
The independent Web app boundary was applied to the target. External delivery, remote migration, service activation, and live runs had not occurred by the cutoff.
Basis for completion
The work was complete when unchanged Web assets had moved into an independent app, package, lockfile, ignore, execution, and database boundaries were separated, and Web, Worker, database, and rollback verification passed.