Keep LIP status consistent (README index ↔ frontmatter ↔ on-chain)

[rickstaa]

Problem

A LIP's status is recorded in two hand-edited places that drift apart:

1. The status: field in each LIPs/LIP-N.md frontmatter.
2. The status column in the README index table.

When one is updated and the other is forgotten, the documented status becomes wrong. This recently caused downstream tooling (e.g. delegators querying LIP status using AI tools) to report incorrect states. #108 is a concrete example: it updates LIP-101 to Final in the README but leaves the frontmatter at Proposed.

A snapshot today shows 6 LIPs internally inconsistent (89–92, 100, 101) plus trailing-whitespace in two status: values (LIP-3, LIP-15).

Plan

• Fix current inconsistencies — reconcile README + frontmatter for the affected LIPs so the repo is internally consistent.
• Status consistency CI gate — a check on every PR/push that fails when any LIP's README status and frontmatter status disagree (would have caught Update README.md #108). Full-repo check, no new toolchain.
• Weekly on-chain reconciliation — a scheduled job that compares documented status against real LIP-16 governance poll outcomes (via the Livepeer Arbitrum subgraph + IPFS proposal linkage) and opens a ready-to-merge PR when a Proposed LIP's poll has concluded, or a Draft/Last Call LIP has an active poll. Editorially gated (never auto-merges).