diff --git a/AGENTS.md b/AGENTS.md
index cdbf8ef..6af0e4f 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -15,7 +15,7 @@ No Jira keys in branch names.
 
 ## Pull Requests
 
-**Title:** `type(scope): description (DEV-123)` — every non-exempt PR ends with its Jira key.
+**Title:** `type(scope): description (DEV-123)` when a Jira ticket already exists. Minor, docs, hygiene, and dependency changes omit the suffix. Do not create a ticket only to fill a title.
 
 **Body sections (in order):** Summary · Validation · Tests · Notes — use "None." when a section is empty.
 State verifiable facts only. Do not cite the handbook to justify changes.
@@ -37,3 +37,16 @@ explicit approval). Linting stays in CI; do not gate on it locally.
 
 **High-blast AWS org/IAM substrate.** This repo synthesises and diffs the organisation-level CDK
 stack. Always run `cdk synth` and review `cdk diff` output before raising a PR.
+
+## Cursor Cloud specific instructions
+
+CI pins Node 24. On this VM, `node` on `PATH` can resolve to an older binary under `/exec-daemon` ahead of nvm. Select Node 24 in the same shell before `npm` or `cdk`:
+
+```bash
+export NVM_DIR="$HOME/.nvm"
+. "$NVM_DIR/nvm.sh"
+nvm use 24
+export PATH="$(dirname "$(nvm which 24)"):$PATH"
+```
+
+Canonical checks: `npm ci`, `npm run build`, `npx cdk synth`. Also run `cdk diff` for every stack this change touches and review the output before opening the PR, whenever this VM can read those accounts. If credentials cannot reach an account, say that in Validation and leave the diff for a human reviewer. Do not `cdk deploy` from this environment.