The user requested actual financial cost and executed models on CodeCartography Settings → Accounts ended job cards. Subscription allocation uses observed weekly allowance percentage consumed × monthly subscription fee ÷ 400. The user supplied CHF 200/month for Pro and CHF 18/month for the five other existing Codex subscriptions. These are allocation inputs, not invoice verification or new spending authorization. Recorded API charges retain USD; token estimates are excluded from money.
Reviewed implementation PR6827, branch revision 6e0a3faa8e0f960349ef6e5a5641c5bf1e9da203, passed branch4173 and merged into dev 7c09e6946c08b326773aab21dc1d9a41a625bf9f. Full immutable candidate4174 passed; automatic main promotion PR6828 integrated the identical tree into main 90fc40703f37ddaa738190e6f3958d6d94642a02. Parent verified all three trees equal 546614046b5ade5325423d38f021d9d007c2ac1a.
Promotion4176 failed before application mutation because changed immutable configuration lacked preparation. The separate supervised pilot administrator recovery prepared and verified the exact current candidate configuration; normal recovery4178 then deployed it. This reporting task performed read-only production acceptance and did not duplicate that preparation or dispatch another promotion. Prepared contract is dabe1b06ed5ae8583389ea2761ef3cda15600bdb8235982d39d8014454ac7618, environment map autocoder-env-ffc8ff25b432862ae2db88b528e0f09b9b6a05facea52a096e248a47209b77a7, root map autocoder-root-7549e1fde3a9da1004df5f4e3731ee237767366258601620554793ac044ef3e0. Existing canonical instruction digest remains 8a7099fa2c9ba56acd3e12332c62ebb7299c2aafcf02b81ca9e5fcce3dc72a12. Old configuration and rollback evidence are retained.
Verified Kubernetes context kubernetes-admin@kubernetes, cluster https://192.168.1.9:6443, namespace autocoder-engine. Release ledger candidate 7c09e6946c08b326773aab21dc1d9a41a625bf9f-4174-1 is production_live. Backend/frontend Deployment annotations match that source and candidate, with one ready pod each and actual pulled images matching their approved digests:
sha256:caf4bf6a3853ca99ef9faa5e7ebff1ec0dc09e03c49efdded9b95c000c0003e2.sha256:2f189955727e2f24483e61d62f63a820ef20fb69b50c6c05102d13a9ceb33f7b.The existing supervised delivery owner published the matching full detached-worker source through successful worker workflow4180. Selected worker digest is sha256:ef0d97f53967b6884dd336de8eead374b1a51a3644eb6f91e1dfa42f2fdea765; five ready operator-chat worker pods on the designated worker host use it. General background and implementation flags remain false; existing operator-chat true is preserved. This task starts no new model work and changes no permissions, secrets, paid routes or capacity.
Authenticated Accounts API returned HTTP200 with 50 ended jobs, all with financial report/model fields. Historical consumption receipts provide models for29; remaining cards distinguish unavailable execution evidence from mutable task settings. All50 historical costs are explicitly unavailable because starting quota readings were not retained. Live PostgreSQL prices are active for all six subscriptions: one CHF200 and five CHF18. No fictitious historical baseline or zero cost was backfilled.
A read-only Chromium check on the designated worker loaded the deployed /settings page with normal TLS verification, using the existing authorized identity only for that exact origin. It verified all50 cards against actual API records, recorded models, unavailable historical costs, expandable financial evidence, 390px/1440px dark/light visibility and wrapping, polling preservation and reload. Frontend build revision exactly matches 7c09e6946c08b326773aab21dc1d9a41a625bf9f. No mutation requests were made. Temporary acceptance containers, browser image and local script are cleaned up after verification.
Worker source acceptance previously passed13 focused/native/isolated-database tests plus UI-test WASM compilation and production-component Chromium fixtures for CHF1.00 at2% Pro consumption, CHF0.09 on the other fee, mixed CHF/USD reporting, stale readings, retry price/model history, quota resets, overlap/generation races and abandoned probes. Full candidate validation passed separately. Fresh provider consumption after rollout has not been exercised by this task; future executions use the new worker capture path under existing execution authority.
Rollback uses the preceding governed application/worker artifacts and retained immutable configuration maps. Additive cost segments preserve frozen models, fees and evidence across account removal or price changes; do not delete that history or fabricate missing readings.