feat: add FMSR and utility catalog MCP tools

docs/data.md

@@ -21,7 +21,7 @@ docker compose -f src/couchdb/docker-compose.yaml up -d
 
 # 2. Verify (Fauxton UI: http://localhost:5984/_utils — admin / password)
 curl -s -u admin:password http://localhost:5984/_all_dbs
-# → ["workorder","iot","vibration","failurecode", ...]
+# → ["workorder","iot","vibration","failure_code", ...]
 
 curl -s -u admin:password http://localhost:5984/workorder/wo:MAIN:1000045
 ```
@@ -133,7 +133,7 @@ init_data()                      # back to default
     "workorder":   "shared/work_order/workorders.csv",
     "iot":         ["shared/iot/chiller_6.json", "shared/iot/metro_pump_1.json"],
     "vibration":   "shared/iot/motor_01.json",
-    "failurecode": "shared/failure_code/failure_code_sample.csv"
+    "failure_code": "shared/failure_code/failure_code_sample.csv"
 }
 ```
 
@@ -154,7 +154,7 @@ Edit this file and re-run `init_data.py` — that's the whole change.
 ### 2. Change *how* a collection is parsed — `collections.json`
 
 ```json
-"failurecode": {
+"failure_code": {
     "format": "csv",
     "primary_key": ["code"],
     "id_prefix": "fc",
@@ -283,4 +283,4 @@ folder's parent); data unique to a private scenario goes in that scenario's fold
   Consumers should sort client-side or add the index to `collections.json`.
 - **`--reuse` keeps history; default reload wipes it.** Anything written at runtime
   (e.g. work orders created by agent tools) is deleted on the next default load —
-  that's the deterministic-benchmark behavior.
+  that's the deterministic-benchmark behavior.