CONTRIBUTING.md

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

# Contributing to WPMgr

Thanks for helping build WPMgr. This file covers dev setup and the PR checklist.

## Prerequisites

Pinned in `.tool-versions` (asdf-compatible):

- Go 1.26+
- Node 22+ and pnpm 11+
- PHP 8.5+ and Composer (for the agent)
- Docker + Docker Compose (for the full stack)

## Setup

```bash
make bootstrap     # installs JS deps, agent composer deps, sets up env
make dev           # bring up the full stack
```

## Project layout

Modular monolith. Backend domains live under `apps/api/internal/<domain>/`
with `handler/`, `service/`, `repo/`, `model/` subpackages. Frontend features
under `apps/web/src/features/<domain>/` mirror the backend domains.

## Commits

Conventional Commits (`feat:`, `fix:`, `chore:`, `docs:`, `refactor:`, `test:`).
One logical change per commit.

**No assistant trailers, and never a session URL.** Do not add
`Co-Authored-By: Claude`, `Claude-Session:`, or any `claude.ai/code/session`
link to a commit message. This repository is public, so anything in a commit
message is published with it and cannot be taken back. Some coding assistants
append these by default; turn that off. CI checks the commits a pull request
adds and refuses the PR if it finds one, with the command to fix it.

Commits already on `main` from before this rule are left as they are. Removing
them would mean rewriting public history, which changes every commit id since
June 2026, orphans the release tags pointing at them, and breaks every existing
clone and fork. The rule applies going forward.

## PR checklist

- [ ] No `Co-Authored-By: Claude`, `Claude-Session:` or `claude.ai/code/session` in any commit message
- [ ] `make lint` passes
- [ ] `make test` passes
- [ ] `make build` passes
- [ ] OpenAPI (`packages/openapi/openapi.yaml`) updated if endpoints changed
- [ ] Docs updated if behavior changed
- [ ] Security-sensitive changes (auth, crypto, agent protocol, RBAC, tenant
      isolation) noted in the PR description for security review

## Architecture decisions

Material technical choices are recorded as ADRs. Early decisions are archived
in [DECISIONS.md](./DECISIONS.md); [docs/adr/README.md](./docs/adr/README.md)
is the live index of every ADR, including the numbering, and is where a new
one gets registered. Propose new dependencies via an ADR there before adding
them.