wolf: log bug-1976 fixed (controller dispatch commit dropped allocs_shared)

Co-Authored-By: Claude Code <noreply@anthropic.com>

.wolf/buglog.json

@@ -139,6 +139,35 @@
         "2fcacac2"
       ],
       "record": ".wolf/bugs/bug-1975.md"
+    },
+    {
+      "id": "bug-1976",
+      "status": "fixed",
+      "status_updated": "2026-10-28",
+      "status_note": "",
+      "component": "controller",
+      "severity": "wrong-result",
+      "timestamp": "2026-10-28T05:37:09Z",
+      "last_seen": "2026-10-28T05:26:00Z",
+      "occurrences": 1,
+      "error_message": "controller dispatch commit drops allocs_shared — vres usage never charged, limits unenforced\n\n**Observed:**\nE2 Phase 3 t1 E2E: 4 projA jobs with `-R \"rusage[extlic=1]\"` against a\nper-project limit `extlic_share` (scope projA, cap 3.0) — ALL FOUR ran\ninstead of the 4th PENDing with reason limit_global. Live gdb on the\nscheduler showed `sharedInUse[36/37/38]` (the vres instances) = 0.0 with\n3 projA jobs RUN: the vres charge never landed.\n\n**Expected:** the 4th projA job PENDs (limit_global); killing a RUN job\nre-admits it; projB unaffected (own per-project instance).\n\n**Impact:** every scheduler-side global limit (the limit vres mechanism)\nwas advisory only — no quota was ever enforced, for ANY shared resource\ncarried via allocs_shared, since dispatch-time adoption overwrote the\nscheduler's own charged accounts with a shared-stripped copy.\n\n**Found by:** spec task (external-license-resources E2 Phase 3 E2E).",
+      "file": "src/controller/job.c, src/controller/testsuite/test_dispatch_commit.c",
+      "root_cause": "The controller's dispatch-time commit (`dispatch_a_job_()`, job.c)\nrebuilt `j->job.allocs` from the scheduler's dispatch payload but\nmigrated ONLY the per-host records (`MOVE_PTR(j->job.allocs->allocs,\nallocs)`): `nres_shared` stayed 0 and the payload's `allocs_shared`\nwas neither moved nor freed (a leak on top). That rebuilt record is\nwhat `sched_job_update_fun()` re-sends to the scheduler as ground\ntruth, and the scheduler's JOB_UPDATE adoption (bug-1860 branch,\ncore_events.c) rebuilds `job->accounts` from exactly that wire copy —\nso `accounts_shared == NULL`, `sched_account_jobs` charges nothing to\nthe vres, and `unsatisfy_` sees cap ≥ 0 + want forever. The scheduler's\nown commit (`sched_commit_decision`, scheduler.c:1806-1812) built the\naccounts correctly — the controller's \"ground truth\" clobbered it.",
+      "fix": "job.c dispatch-time commit: migrate the shared records alongside the\nhost records — `MOVE_PTR(j->job.allocs->allocs_shared,\nalloc->allocs_shared); j->job.allocs->nres_shared =\nalloc->nres_shared; alloc->nres_shared = 0;` (MOVE, not copy — the\ncaller frees the payload; also closes the leak).\n\nVerification:\n- Test: `test_dc_success_migrates_shared_allocs`\n  (src/controller/testsuite/test_dispatch_commit.c). RED before the fix\n  (\"Expected 2 Was 0\" on nres_shared), GREEN after.\n- Suites: full meson test 136/136 OK (build.dbg), including controller\n  unit suite 1361/0.\n- Live: t1 E2E — 3 projA RUN / 4th PEND, projB RUN (own instance), kill\n  one RUN job → pending projA re-admitted, external free pool\n  (fake_lic) enforced independently; all daemons healthy throughout.",
+      "tags": [
+        "external-license-resources",
+        "limits",
+        "shared-resources",
+        "dispatch",
+        "e2-phase3"
+      ],
+      "related_bugs": [
+        "bug-1860"
+      ],
+      "fix_commits": [
+        "76ddd75f"
+      ],
+      "record": ".wolf/bugs/bug-1976.md"
     }
   ]
 }