docs(buglog): P0 defects fixed (bug-1936..bug-1955; 1936 and 1955 partial), bug-1956 cannot-reproduce

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

.wolf/bugs/bug-1944.md

@@ -1,8 +1,8 @@
 ---
 id: "bug-1944"
-status: "open"
+status: "fixed"
 status_updated: "2026-10-10"
-status_note: "newly logged"
+status_note: ""
 component: "scheduler"
 severity: "wrong-result"
 timestamp: "2026-10-10T08:14:56Z"
@@ -11,6 +11,7 @@ occurrences: 1
 files: ["src/scheduler/src/core_events.c", "src/scheduler/src/schedobj.c"]
 tags: ["scheduler", "queue", "priority"]
 related: []
+fix_commits: ["7a9d75d6"]
 ---
 
 # bug-1944: xce_scheduler gives a job moved to another queue the queue's priority, so it jumps ahead
@@ -36,15 +37,16 @@ New jobs get priority 0 (`schedobj.c:214`, `core_events.c:353`), but on a queue
 - Frequency: deterministic (by code reading; confirmed by the RED test of the fix)
 - Evidence: the code sites quoted in Description; no logs kept.
 ## Root cause
-TODO: required for fixed/partial
+On a queue change both `xce_core_push_events` (`JOB_UPDATE`, `core_events.c`) and `sched_update_existing_job` (`schedobj.c`) set `job->priority = q->priority`; new jobs and snapshot-restored jobs get 0, so moved jobs jumped ahead and live/replay disagreed. Pre-existing.
 
 ## Fix
-TODO: required for fixed/partial
+Both sites now only re-point `job->queue` on a move; queue priority still orders the queues. `test_job_update.c`, which asserted the old behaviour, now expects the job's own priority.
 
 ## Verification
-- Test: TODO: name + file; RED before the fix, GREEN after
-- Suites: TODO: suite results and build profile
-- Live: TODO: soak/deploy run, or n/a and why
+- Test: `test_moved_job_keeps_its_priority_and_place` (`src/scheduler/testsuite/test_job_move_priority.c`): RED `:208: FAIL: Expected 0 Was 10` (and `:214: Expected 2 Was 1` for the ordering), GREEN after; `test_update_existing_job_mutates_in_place` RED `Expected 1 Was 5` with the corrected expectation, GREEN after.
+- Suites: `xce-build.sh all asan xce.build --incremental` on the merged branch, 2026-10-10: all C suites Ok 155 / Fail 0, frontend Go unit tests ok, xceadmin tests ok; apiserver `CGO_ENABLED=0 go test ./...` (incl. middleware, router, cmd) ok
+- Live: n/a: unit/fixture-level verification only; no live deployment was run (follow-up)
 
 ## References
-- Related: none
+- Fix commit: `7a9d75d6` (on `scheduler-framework`; worker-branch original in the merge)
+- Review: `.kiro/reviews/project-gap-review-2026-10-10.md`