From a4adabdf684ebe042238ac8056f6f99f9cc17c84 Mon Sep 17 00:00:00 2001 From: Alex Shalaev Date: Sun, 6 Sep 2026 23:05:57 +0300 Subject: [PATCH] fix: accept both cap spellings, and stop one request rewriting the next The work landed in #21. Its squash subject lost the Conventional Commit prefix -- my mistake on the merge, not the author's -- so release-please skipped the merge and these fixes would never have reached a release. This commit carries the record. It changes no code: #21 is already on master. * OperationDeadlineConfig spells the field calls_caps while BudgetContext.create takes call_caps, and the model ignored the unknown key, so a configuration written the second way silently carried no caps at all. Both spellings are accepted now through AliasChoices, and serialisation is unchanged. * BudgetContext held the caps dict it was handed rather than a copy. Because the factory passes the settings object's own dict straight through, mutating one request's caps rewrote the application-scoped settings and every later context for that operation. * make install and the contributing guide now sync the extras CI uses, so make test-unit works on a fresh checkout instead of failing at collection.