chore(buglog): harness batch fixed (da1a663f): bug-1574/1702/1703/1705/1707-1710/1712/1777/1793/1796/1797

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

.wolf/bugs/bug-1712.md

@@ -1,16 +1,17 @@
 ---
 id: "bug-1712"
-status: "open"
-status_updated: "2026-09-24"
-status_note: "xce_test resupdate duplicate -v gives misleading message"
+status: "fixed"
+status_updated: "2026-09-28"
+status_note: ""
 component: "controller"
 severity: "unknown"
 timestamp: "2026-08-26T09:32:18Z"
 last_seen: "2026-09-19T09:00:00Z"
 occurrences: 1
-files: ["src/controller/testsuite/test.c:3525-3531 (case 'v' else-branch)"]
+files: ["src/harness/test.c"]
 tags: ["controller", "testsuite", "xce_test", "cmd_resupdate", "misleading-error-message", "cli-ux-audit"]
 related: ["bug-1706", "bug-1707"]
+fix_commits: ["da1a663f"]
 legacy: true
 ---
 
@@ -29,10 +30,12 @@ _Not recorded (migrated from buglog.json)._
 The else-branch of the -v case handles two distinct situations (no preceding -n at all, vs. a duplicate -v for an already-named pending resource) with one shared, incorrectly-worded message.
 
 ## Fix
-NOT YET FIXED. Recommended: distinguish the two cases with an accurate message for the duplicate-value case, e.g. "ignoring duplicate value '%s' for res '%s' (already has a pending value)".
+The -v branch now tells the two cases apart: no preceding -n keeps "no res name found"; a second value for the same resource prints "ignoring duplicate value `8' for res `slots' (it already has value `4')".
 
 ## Verification
-_Not recorded (migrated from buglog.json)._
+- Test: test_resupdate_duplicate_value_named_correctly in src/harness/testsuite/test_test_cli.c: RED before the fix ("no res name found"), GREEN after
+- Suites: harness 6/6 (asan): harness_unit_test 141/0, cmdutil 14/0, resval_typeresolve 7/0, joblist_display 22/0, join_worker_args 7/0, listrow_json 12/0
+- Live: n/a; xce_test is a client tool and every case above runs without a controller
 
 ## References
 - Related: bug-1706, bug-1707