[github-actions]

The publisher now serves different bytes for pge-e-1 than the manifest pins. This pull request proposes accepting the revision: the manifest entry's new digest (ec38d13fec762d4a643569545a2054e09daf1debb618312967ff0037954ab23f), retrieval date, page count and size; the new baseline under data/parsed/; and the report below, which lists every value that was added, removed or changed with the citation it was read from before and after.

Merging this pull request is the review the manifest's digest check asks for (ADR 0003). Before merging:

• Read every line of the report against the publisher's document. The citations are there to be checked, not trusted.
• Run make fetch && make coverage-real and update the README's coverage table if the figures moved; tests/test_published_figures.py will fail otherwise.
• Both parses state the same parser version, which does not mean one parser read them both. That string moves only at a release, so a parser change since the baseline was written is listed below as a schedule change. If src/ca_tariff_parse/ has moved since data/parsed/pge-e-1.json was last written, re-parse the previously pinned bytes with the current parser before relying on any line.
• Nothing in this pull request is a PDF. If one appears, close it.

---

pge-e-1: what changed

	before	after
document sha256	39fbba73bbe0ee594705f52c1bbe1ab14d41ad9807742defc1dadcc39f577239	ec38d13fec762d4a643569545a2054e09daf1debb618312967ff0037954ab23f
retrieved	2026-08-17	2026-10-26
pages / bytes	7 / 656128	7 / 656128
parser	0.3.0	0.3.0
content lines recognized	84/247	84/247

Both parses state parser version 0.3.0, which does not establish that one parser read them both. That string is the project's release version and moves only when a release is cut, so parses made by different builds between releases carry it identically. If the parser changed after the older parse was written, a parser change is listed below as a schedule change and nothing here can tell them apart; re-parse the old bytes with the current parser to separate them.

0 added, 0 removed, 0 changed. A value that only moved on the page is not listed. Check the citations, not this table.

This report is a comparison of two parses of a published document. It is not rate advice and not a bill estimate, and the project is not affiliated with any utility.