Organized

docs/raw-notes/features/nmi-bridge.md

@@ -0,0 +1,41 @@
+# NMI bridge env + usage
+
+**Parent:** [[entity-type-mapper]] · module `redmine_ticket_nmi.py`
+
+## Environment
+
+| Variable | Default | Purpose |
+|----------|---------|---------|
+| `NMI_CLI` | `/home/jason/projects/mrscClient-php/bin/nmi` | Path to NMI PHP CLI |
+| `NMI_ENV_FILE` | `/home/jason/projects/mrscClient-php/examples/modern/.env` | Env file for credentials/endpoint |
+| `NMI_MODE` | `dev` | CLI `--mode` (dev/prod as supported by nmi) |
+
+Requires `php` on PATH.
+
+## CLI
+
+```bash
+# Pattern extract only
+./bin/rtl entities show --issue-id 41394
+./bin/rtl entities scan --type tracking_ups --max-tickets 20
+
+# Resolve / cs-brief via NMI CLI
+./bin/rtl entities nmi --issue-id 41394
+./bin/rtl entities nmi --issue-id 41394 --nmi-mode dev
+./bin/rtl entities nmi --issue-id 41394 --as-private-note-draft   # if wired; else use browse `m`
+```
+
+## Browse
+
+After opening a ticket in `browse`, press **`m`**:
+
+1. Runs NMI brief from extracted entities  
+2. Shows brief text  
+3. Confirms → queues **private** internal note draft  
+
+Never emails the customer.
+
+## Safety
+
+- NMI is read-side ops context, not customer mail  
+- Private note drafts still need `draft apply` (+ prod flags) to land in Redmine