document standalone vue workflow

Update the AI guidance for the scaffolded npm application, its actual validation scripts, and its independent runtime boundary. Record the current lack of frontend test tooling without inventing commands.
This commit is contained in:
Yisroel Baum 2026-07-30 23:15:16 +03:00
parent 15925b856b
commit ff95e2d2ee
Signed by: yisroelbaum
GPG key ID: 0FA60884F75520A9
3 changed files with 118 additions and 69 deletions

View file

@ -13,8 +13,10 @@ these rules.
unfinished assignments across the remaining dates.
- Planned features in `README.md` are future ideas, not authorized scope.
- The Laravel backend exists under `backend/`.
- The Vue frontend has not been scaffolded yet. Do not create it unless the
user explicitly asks for that work.
- The standalone Vue frontend exists under `frontend/website/`.
- Keep the frontend independent from the backend. Do not add backend-driven
rendering, asset delivery, or build integration unless the user explicitly
asks for it.
- PostgreSQL is the development and runtime database.
- PHPUnit uses in-memory SQLite for isolated tests.
@ -62,6 +64,9 @@ those changes with the most relevant parser, formatter, dry run, or check.
- Run backend commands from `backend/`, or explicitly change into it in the
command.
- Run frontend commands from `frontend/website/`.
- `process-compose` does not start the frontend. Start it separately with
`npm run dev -- --port "$VITE_PORT"` when needed.
- When a normally valid check fails because a required service is down,
surface the environmental failure. Do not skip the check or silently switch
to a different database or service.
@ -134,9 +139,12 @@ those changes with the most relevant parser, formatter, dry run, or check.
direnv exec <worktree> true
```
- Never symlink `backend/vendor` or a future frontend's `node_modules` from
another checkout. Dependency paths and generated autoloaders must remain
- Never symlink `backend/vendor` or `frontend/website/node_modules` from
another checkout. Dependency paths and generated files must remain
worktree-local.
- The shell hook installs backend dependencies but does not install frontend
dependencies. Run `npm install` from `frontend/website/` when provisioning a
fresh worktree.
Do not push anything. Make commits as the TDD workflow requires.
@ -162,11 +170,19 @@ gate affected by the change.
### Frontend
- The frontend does not exist yet. Once scaffolded, use the scripts defined in
its `package.json` for formatting, linting, type checking, unit tests, and
end-to-end tests.
- Update `ai/frontend-context.md` when the actual scaffold, package manager,
and commands are known.
- Run these commands from `frontend/website/`:
```sh
npm run format
npm run lint
npm run type-check
npm run build
```
- The formatter and linters rewrite files. Review their changes before
committing.
- No frontend test runner is configured yet. Do not claim unit, component, or
end-to-end test coverage until the relevant scripts exist and pass.
### Environment and integration