2 Commits

Include renames

Author	SHA1	Message	Date
glenn schrooyenandClaude Opus 5	9c65ac2cf8	TARIFF-18: price_taxes_eur_kwh stops shipping at half the real figure ... `price_taxes_eur_kwh` shipped at 0.06 EUR/kWh with no recorded provenance - no card, no date, no component list - and roughly HALF the true Flemish all-in non-energy figure. It now ships at 0.11736, and the rows it is made of are in the code rather than in this message: Fluvius distribution (Antwerpen) 5,35 c EUR/kWh Bijzondere accijns, "Alle verbruik" 4,876 Bijdrage groene stroom en WKK Vlaanderen 1,51 Energiebijdrage (0 EUR/MWh since 2026-08-01) 0 ------ 11,736 c EUR/kWh = 0.11736 Eneco residential card for Flanders, September 2026, incl. 6 % VAT. `app/price.py`'s FLEMISH_TAXES_COMPONENTS_EUR_KWH carries the rows and test_price.py section 1b re-adds them - and also compares the total against the card's own figures typed in the test file, so an edit that moved the rows and the default together is still caught. WHAT THIS IS NOT. It is not an arbitrage-correctness fix and it cannot be. This scalar is a LEVEL component: an additive constant cancels exactly in `max - min` and leaves the argmin where it was. TARIFF-17 shipped that proof and it is unchanged - test_price.py 16b drives six flat scalars spanning and exceeding the whole per-DSO range and gets the identical cheapest hour and the identical spread to the last digit. DOCS and the CHANGELOG say so in those words. WHAT IT IS. A display and guard fix: * every number an operator reads, which at half the true value made the add-on look considerably better than it is; and * §17's negative-price guard in arbitrage.py - the one rung that tests an ABSOLUTE all-in price rather than a difference. It fires when `spot < -(markup + taxes)`, so its boundary moves -0.09 -> -0.14736 EUR/kWh of spot. test_arbitrage.py section 2c drives both sides through the shipped decide() and pins the boundary from below as well. The default is Antwerpen's real row, near the LOW end of the 0.117-0.131 per-DSO band, and that is deliberate: the error directions are not symmetric. Too high carries a genuinely negative hour above zero and the add-on exports into paid-for disposal - §17's own case. Too low only declines a discharge that would have paid. TARIFF-17's INTERACTION, WHICH HAD TO BE DECIDED. Nothing in that rung hardcoded 0.06; it read PRICE_OPTION_DEFAULTS, so moving the default moves what it refuses. The Supervisor sets `App.options = deepmerge(config.yaml defaults, stored options)`, so a saved blob carries the key whether it was typed or not - every stored 0.06 became "non-default" with nobody editing anything, and a working Walloon or Brussels site with a taxes table would have met SystemExit(78) on the upgrade over an inert number. price.py now carries SUPERSEDED_TAXES_DEFAULTS_EUR_KWH = (0.06,) and validate.py reads a superseded default as untouched too. The rung is NOT weakened: 0.1198 beside a table is still refused by name, and the refusal now names both figures. config.yaml and PRICE_OPTION_DEFAULTS moved together; CFG-03's tripwire (test_price.py section 1, test_defaults_pin.py) stayed green by agreeing. test_price.py section 0's fourth check was REWRITTEN rather than re-pointed: it used to justify the file's own grading constants by observing that the shipped pair was degenerate (0.06 is exactly twice 0.03). TARIFF-18 ends that coincidence, so the sentence is no longer true and is not kept. 29/29 test files green. Mutation ledger on the PR. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BwRLw7eKYj2byVdwB6kbjU	2026-09-13 16:24:56 +02:00
Claude Opus 5	ac9854886b	TARIFF-15: your own tariff card, as two coefficients the card itself grades ... A Belgian dynamic contract prices energy as `B x index + A`, and the two coefficients exist on exactly one artefact: the customer's own tariff card. There is no machine-readable source for them anywhere - CREG's consumer tariff-card pages 404, CREG Scan is a JS wizard, the annual report has the supplier list without per-product coefficients, VREG was unreachable, and every coefficient found in research came off a supplier's own PDF, one image-only. So nothing can be scraped and a per-supplier plugin would have no source for its numbers, which is why TARIFF-07 withdrew three of them. The customer is the only party who can see their own coefficients; they type them. New provider `custom_formula`, one new option `price_formula` (a JSON string, the `static_profile` precedent exactly), and a new module `app/custom_formula.py`. The index path is `generic_dayahead`'s, not a second one: the URL/override decision is now one shared `dayahead_feed_url()` both plugins call, same feed, same Brussels-calendar range, same columnar parser, same declared egress hosts. It declares {ENERGY, MARKUP}, NOT ALL_IN. A card's Tariefformule line is the energy component alone - Eneco tabulates network tariffs and levies separately, ENGIE states the formula excludes network, distribution, transport, levies and excise - so ALL_IN would lie for every operator who typed what their card says and would drop the taxes from every hour (0.2125 -> 0.1555 EUR/kWh, measured). THE CARD IS THE GRADER, and that is why this is safe to ship. The framework already mechanises that a PLUGIN cannot double-count. This introduces a risk none of those guards can see because it is config, not code: the OPERATOR double-counting, by folding network charges into `offset` while price_taxes_eur_kwh carries them too. So validate.py recomputes the card's own printed price from the operator's coefficients at startup and refuses to start unless the two agree to within 0.01, naming the discrepancy. An inflated offset cannot pass: 15.55 becomes 28.27. The same check catches VAT omitted, VAT doubled, a transposed digit and a unit mismatch between the two sides. And the limit, in the same sentence as the claim: it grades the coefficients against the card, NOT the card against reality. A consistent-but-wrong pair passes. A second refusal covers the one unit error the first cannot see - the one applied to both sides at once - by bounding the card's own point to 0.02-1.00 EUR/kWh. Its FLOOR is applied to the energy figure rather than the all-in one because the shipped 0.06 of taxes is three times that floor and would carry a hundredfold error over it alone; found by writing the mutation, not by review (M10, +0 B). The market's own arithmetic, reproduced through the shipped code: Eneco (0.102 x 133.9905 + 1) x 1.06 = 15.5471 card prints 15,55 ENGIE (0.1 x 61.96 + 0.9) x 1.06 = 7.5218 card prints 7,522 NO EXPRESSION EVALUATION OF ANY KIND. The string is settable over HTTP through the add-on's own ingress page, so eval on it is RCE in a root container holding SUPERVISOR_TOKEN and driving an inverter over RS485 - but the deciding argument is that an expression is UNVERIFIABLE: two coefficients can be graded against the card, an arbitrary expression cannot be graded against anything, so it would make the invisible-wrong-coefficient problem strictly worse. An unknown field is REFUSED rather than ignored, so `"expr"` is told it does not exist. Future shapes become named fields, never a grammar. test_price.py 15f walks the module's AST for eval/exec/compile/__import__/literal_eval and exercises the scanner's red direction on every run. Refused at startup: card absent or out by >0.01; `units` absent (no default); factor == 0 (every spread 0, arbitrage silently never fires - the message points at static_profile); factor < 0 (inverts the market); vat_pct outside 0-30 (0 stays legitimate); non-finite or non-numeric; unknown field, index or resolution; the plausibility band. A card older than ~6 months WARNS and does not refuse - ENGIE freezes coefficients for a contract's duration. Negative output prices are not refused anywhere. A startup preview logs the next 24 h as `index EUR/MWh -> all-in EUR/kWh` with min/median/max and the day's spread, through a new default-silent `PriceProvider.startup_preview()` hook - only the plugin knows what went in to its own arithmetic. Emitted once per process, and a preview that raises cannot cost the site its prices. `custom_formula` joins the config.yaml enum through the DERIVED set PROVIDERS | RETIRED_PROVIDERS | {"off"}, not a hardcoded list. Both translations describe the option and the new id. DOCS.md replaces the "planned" sentence with the shape, a worked example from a real card, a real startup transcript and the limit of the check stated beside the claim. 22 mutations, one per check added, no survivors - MUTATION.md carries the ledger. M13 (the preview's index column) was a -13 B survivor of the whole suite on the first attempt because the check graded the HEADING and not the row; it is graded on a rendered row now. All 29 suites green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BwRLw7eKYj2byVdwB6kbjU	2026-09-13 03:49:08 +02:00