diff --git a/.wolf/buglog.json b/.wolf/buglog.json
index 4f9323c8..f5847580 100644
--- a/.wolf/buglog.json
+++ b/.wolf/buglog.json
@@ -18017,6 +18017,29 @@
       ],
       "occurrences": 1,
       "last_seen": "2026-08-21T07:25:00Z"
+    },
+    {
+      "id": "bug-1614",
+      "timestamp": "2026-08-21T08:50:00Z",
+      "error_message": "pytest FAILED xceadmin/repo-mirror/src/xceadmin/tests/test_cli.py::test_cli_version_flag_includes_build_info_fields -- AssertionError: assert '2bf62a64-dirty' in 'xceadmin, version 0.1.0 (2bf62a64-857bd5b5, 2026-08-21T08:49:15Z)\\n' (1 failed, 266 passed, 3 skipped) -- blocks meson's xceadmin-build.stamp custom_target, so no wheel is produced.",
+      "file": "src/xceadmin/tests/test_cli.py",
+      "root_cause": "dirty-content-fingerprint task 5.2's _compose_version_display() strip-and-append rule (cli.py:59-75, already implemented, matches design.md/tasks.md 5.2 exactly and all its OWN dedicated tests pass: test_compose_version_display_strips_dirty_suffix_and_appends_fingerprint, ..._anchored_suffix_not_blind_substring, test_compose_version_includes_fingerprint_when_build_info_has_one) now legitimately conflicts with an older, pre-existing task-2.2 test (test_cli_version_flag_includes_build_info_fields, added under Requirement 2.2 before this feature existed) that still asserts the RAW _build_info.GIT_COMMIT string (e.g. '2bf62a64-dirty') appears verbatim in `xceadmin --version` output. On a dirty tree with a non-empty DIRTY_FINGERPRINT, the composed output now correctly shows '2bf62a64-857bd5b5' (dirty suffix stripped, fingerprint appended per spec) instead of containing the literal '...-dirty' substring, so the old assertion is now stale and fails. tasks.md 5.2 is still unchecked ([ ]) -- this stale test update was left out of scope / not yet done.",
+      "fix": "RESOLVED CONCURRENTLY, not by this run: the first `xce-build.sh xceadmin asan <dir>` invocation (BUILD_TIME 2026-08-21T08:49:15Z) failed exactly as described above (1 failed, 266 passed, 3 skipped). While investigating, found `src/xceadmin/tests/test_cli.py` in the LIVE working tree already carried an uncommitted rewrite of test_cli_version_flag_includes_build_info_fields (now computes the expected display via the same strip-and-append contract cli.py's _compose_version_display() uses, instead of asserting raw GIT_COMMIT verbatim) -- but its mtime (08:50:55Z) POSTDATES the first build's BUILD_TIME, meaning some other concurrent process/session applied this fix mid-investigation, not this build-verification agent. Re-ran the identical xce-build.sh command a second time against the now-updated tree (BUILD_TIME 2026-08-21T08:55:40Z, dirty_fingerprint recomputed to c0c2a0b7 since tracked-file content changed) and it now passes clean: '267 passed, 3 skipped in 7.65s', wheel built at .../xceadmin/dist/xceadmin-0.1.0-py3-none-any.whl. Installed that wheel alone into a fresh throwaway venv (nix develop wrapper, matching this project's established pattern) and confirmed `xceadmin --version` -> 'xceadmin, version 0.1.0 (2bf62a64-c0c2a0b7, 2026-08-21T08:55:40Z)', exit 0 -- dirty suffix correctly stripped and replaced with the fingerprint, not doubled up. Task 5.2 appears functionally complete now; tasks.md still shows it unchecked ([ ]) as of this writing -- someone should flip it once the concurrent editor's change is reviewed/committed.",
+      "tags": [
+        "xceadmin",
+        "dirty-content-fingerprint",
+        "task-5.2",
+        "pytest",
+        "version",
+        "_compose_version",
+        "regression",
+        "stale-test",
+        "meson",
+        "concurrent-edit-observed"
+      ],
+      "related_bugs": [],
+      "occurrences": 2,
+      "last_seen": "2026-08-21T08:56:00Z"
     }
   ]
 }