Coordinate hardfork/network-upgrade rollout

[ritorhymes]

Built on top of the V2 multi-repo local build system tracked in #15.

Description

This tracks the hardfork/network-upgrade rollout across the preprocessor, theme, eipw, and EIPs repos.

The rollout adds generated hardfork data to the prepared site, renders a /hardforks/ page in the theme, shows hardfork membership on proposal pages, and adds eipw support for the source-level network-upgrade preamble marker.

The first preprocessor PRs use a transitional registry so the site can ship before source EIPs are updated. After eipw supports the marker, follow-up EIPs repo PRs can add network-upgrade metadata to modern hardfork Meta EIPs, then the preprocessor transitional modern registry entries can be cleaned up. Permanent historical, irregular, curated, and unparseable entries remain in the preprocessor registry.

Demo site: wg-eips.ritovision.com

Addresses:

• Render network upgade stage and links from an EIP to its containing meta hardfork EIP #3
• Generate an index page listing all EIPs sorted by hardfork #4
• Render network upgrade for EIPs included in a Network Upgrade Meta EIP ethereum/EIPs#11036
• https://ethereum-magicians.org/t/add-optional-upgrade-field-to-standards-track-core-eips/27388

PR Sequence

Prerequisite

• Add taxonomy page descriptions theme#25 — Add taxonomy page descriptions
• Generate Proposal Metadata JSON #34 — Generate Proposal Metadata JSON

Preprocessor (stacked on #34, merge in order)

• 1/3 1/3 Add network upgrade core model #36 — Add network upgrade core model
• 2/3 2/3 Generate hardfork site data #37 — Generate hardfork site data
• 3/3 3/3 Add historical hardfork registry entries #38 — Add historical hardfork registry entries

Theme (depends on the generated hardfork data shape)

• Render hardfork page and proposal memberships theme#14 — Render the hardfork page and proposal memberships

eipw (independent; gates later EIPs marker backfill)

• Allow network-upgrade preamble marker ethereum/eipw#171 — Allow network-upgrade preamble marker

Post-eipw Follow-up

These follow-ups are not part of the current PR stack. They wait until the eipw PR lands, because adding network-upgrade to EIPs before eipw accepts the field would create lint failures.

EIPs

• Add network-upgrade markers to modern hardfork Meta EIPs.
• Keep historical and irregular entries in the preprocessor registry unless their source format can be represented cleanly.
• Avoid changing old historical source documents just to satisfy the new marker model.

Preprocessor

• Prefer source markers over transitional registry entries where markers exist.
• Remove or shrink transitional modern registry entries that are replaced by source metadata.
• Keep permanent historical registry entries for legacy, irregular, curated, or unparseable cases.

[ritorhymes]

is this using Zola taxonomies?
— @SamWilsn

I missed that question you asked in chat during my presentation for EIPIP #126.

Yes. Taxonomy handling is delegated to Zola: the preprocessor populates status, type, and category, and Zola renders the corresponding grouped pages/feeds.