feat: add project-aware agent workspace
Generic Container CI/CD / test-build-publish (push) Successful in 2m9s
Frontend CI/CD / build-test-publish-and-deploy (push) Successful in 2m39s

This commit is contained in:
2026-10-22 18:52:18 +08:00
parent c6a0e74e72
commit 2d8506fea0
191 changed files with 12373 additions and 3556 deletions
+8 -2
View File
@@ -26,8 +26,9 @@ execution belong in `next-tjwater-agent`.
- `src/mocks/` owns MSW handlers and fixtures.
- `src/test/` owns shared Vitest setup and repository-wide invariant tests.
- `tests/browser/` owns product-level Playwright regressions.
- `public/` contains static supply-network and SCADA assets plus the
runtime-config placeholder.
- `public/` contains static supply-network, SCADA, bundled city-model release
assets, and the runtime-config placeholder. Keep the city-model manifest,
attribution, and referenced runtime archive content-hash aligned.
- `server/` contains the same-origin Edge TTS adapter used by Vite and the
production container.
@@ -67,6 +68,11 @@ or barrels for private implementation files.
## Component and Module Design
- Follow [the style design guide](docs/style-design-guide.md) for UI changes:
preserve the local shadcn/ui design for all Agent dialogs, panels and menus.
Use Tailwind CSS with shared semantic tokens; apply Acrylic styling to map
and other workbench surfaces as specified by the guide. Keep feature
documents focused on business behavior.
- Use TypeScript and React function components. Export explicit types at
feature and adapter boundaries.
- Use two-space indentation and kebab-case filenames. Use PascalCase for