TRUSS.md

Rama main · réplica de lectura del repositorio original.

# Truss practices

House rules for anyone (human or agent) working in this repo.

## Coding

- pnpm, never npm.
- Typecheck before claiming done: `pnpm -r run lint`.
- Build must stay green: `pnpm -r run build`.
- Every feature, fix, and behavior change ships with tests in the same
  commit. No exceptions for "small" changes; small bugs are still bugs.
  `pnpm test` must pass before pushing.
- Tests live in `apps/server/test/` (node:test + tsx, temp TRUSS_DATA_DIR via
  `freshServer`) and `apps/web/test/` (pure helpers + store reducers). Follow
  the existing files' pattern.
- Regressions get a regression test first, then the fix.
- Plain human language in docs and comments. No em dashes in user-facing
  copy, no AI jargon.

## Branches

- New work branches off `origin/main` after a fetch, never off another PR
  branch. No cumulative/stacked branches: every PR's diff vs main must be
  exactly its own work, so PRs can be audited and merged in any order.
- If main has moved since the branch was cut, rebase onto `origin/main`
  before opening or updating the PR.

## Commits

- Commit author and committer are always the repo owner
  (`roowus <roowus@users.noreply.github.com>`), including automation-made
  commits — bots act on the owner's behalf and do not get credit lines.
- No AI-attribution trailers or banners in commit messages: no
  `Co-Authored-By:` lines, no "Generated with …" footers, no tool names.
- PR titles follow conventional-commit style, ≤70 chars; the body opens with
  1-3 plain sentences (what was broken, what the PR does) before any lists.

## Posting

- File todos for anything the user must verify by hand; label them `verify`.
- Post one report per research task. No chatter.