Scaffold pnpm monorepo (client / server / e2e)

[erikhfj]

Set up the workspace so each of us can start on their own slice without stepping on each other.

• pnpm workspace with client/, server/, e2e/
• shared tsconfig.base.json (strict, noUncheckedIndexedAccess)
• ESLint (flat config) + Prettier, 0 warnings
• root scripts: dev, build, lint, format, typecheck, test, test:e2e, db:*
• AGENTS.md describing the architecture rules

Acceptance: pnpm install && pnpm format:check && pnpm lint && pnpm typecheck && pnpm test all pass from a clean clone.

[erikhfj]

Before you open the PR: implement from the requirement, not by copying from archive/scaffold-prototype. The prototype is a reference you can check against when you get stuck. It is not a source to paste from.

The PR description must say what was done and what was tested. That is what we read when we review.

[erikhfj]

Plan (erikhfj, 24.09)

What the requirement asks for: a workspace where four people can work in parallel without stepping on each other, and where the same quality gates run locally and in CI. Not the app itself, that is #9.

How I plan to solve it:

• pnpm workspace. For now only client/. server/ and e2e/ get added in M2/M4 when they are actually needed, so we avoid half-empty packages that exist just for appearance.
• tsconfig.base.json with strict and noUncheckedIndexedAccess. The latter is annoying to write against, but it is the kind of check that catches "this index might be undefined" at compile time instead of at runtime in a results list.
• ESLint in flat config format (ESLint 9) plus Prettier. The bar is 0 warnings, not "nearly clean". CI has to be able to enforce it.
• Root scripts matching what we actually run: dev, build, lint, format, format:check, typecheck, test.
• AGENTS.md describing our architecture rules, so both AI tools and new members start from the same understanding.
• A minimal client/ (hello world plus one test) purely to prove the gates are green. The real mock data search is Client search page wired to the live API #9.

Unsure about: whether we should add server/ and e2e/ stubs now just to "see" the shape, or whether it is better to add them when they arrive. I lean toward the latter. Empty packages are noise in review.

Not copied from the prototype. Tooling config is generic and will look similar regardless. The structure and AGENTS.md are written from this requirement.