> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.coperniq.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.coperniq.io/_mcp/server.

## `updatedAt` and `updated_after`/`updated_before` now reflect custom property changes

`updated_after`/`updated_before` on `GET /projects`, `GET /projects/search`, and the other list endpoints (requests/deals, clients/accounts, vendors) now also match records whose custom property values changed within the window. This is always on; there is no new query param.

The `updatedAt` field on a returned record now reflects the most recent change to that record, including changes to its custom property values.

#### Caveats

* There may be a short delay before a custom property change is reflected — build in a small overlap when polling with `updated_after`.
* Within a page of results, ordering now matches the `updatedAt` value shown in the response. Page boundaries (`page`/`page_size`) are still determined by each record's own persisted `updatedAt`, so a record that only qualifies via a custom property change may land on a different page than its displayed `updatedAt` would suggest.