Merge site-ui-3: the one-screen home page is back

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

docs/fud-ledger.md

@@ -621,6 +621,8 @@ Evidence: design doc, decisions table row "Who are you?". Journey: `site/journey
 ### G4. No admin keys, except in everything that matters
 "'There are no admin keys.' The DEX, the lending market, the bridge and the dev fund contract all ship from your team. Bridges are where the admin keys live."
 
+Status: Conceded, stated (7 October 2026, morning): the one-screen home page is back on the owner's word, so this row is stated on `site/litepaper.html` only; the sentence there is unchanged and the text check lists it under the litepaper.
+
 Status: Conceded, stated (5 October 2026, night): `site/litepaper.html`, Governance, "There are no admin keys in consensus"; `site/index.html`, tile "admin keys in consensus". Was: Conceded, wording fix needed.
 
 Status: Conceded, stated (6 October 2026, later that night): the home page was restored to its fuller shape on the owner's word ("revert it but polish it") and carries the tile "admin keys in consensus" again, beside the litepaper's Governance sentence.
@@ -698,6 +700,8 @@ Evidence: litepaper "For miners", hardware paragraph. Wording: overclaims list,
 ### C2. vs Monero: "no chip in seven years" is not proof
 "Absence of a public RandomX ASIC is not evidence one cannot exist. Monero is also a small prize."
 
+Status: Conceded, stated (7 October 2026, morning): the one-screen home page is back on the owner's word, so this row is stated on `site/litepaper.html` only; the sentence there is unchanged and the text check lists it under the litepaper.
+
 Status: Closed by the fact (6 October 2026, night): a public RandomX chip now exists, Bitmain's Antminer X9, shipping from July 2026 (1 MH/s at 2,472 W, about USD 5,600; monero-project/monero issue 10270). Every sentence that leaned on its absence was rewritten under X34; "2019 (approximate)" stays on both pages.
 
 Status: Conceded, stated (5 October 2026, night): `site/litepaper.html`, Mining, "no chip publicly shipped, approximate" and "Monero is precedent, not proof"; `site/index.html`, hero, "a chip gains too little to take your place". Was: Conceded, label needed.
@@ -971,6 +975,8 @@ Sweep (5 October 2026, evening): stated in part. `site/partials/footer.html` on
 ### X8. Exchange listings as a roadmap item
 "'Mainnet fair launch: Genesis with no premine, 30-day ramp, exchange listings after.' You put listings in the roadmap."
 
+Status: Conceded, stated (7 October 2026, morning): the one-screen home page is back on the owner's word, so this row is stated on `site/litepaper.html` only; the sentence there is unchanged and the text check lists it under the litepaper.
+
 Status: Conceded, stated (5 October 2026, night): `site/litepaper.html`, Roadmap phase 6, and `site/journey.json` phase 6, "No listing is arranged, promised or sought by the project". Was: Conceded, fix now.
 
 Status: Conceded, stated (6 October 2026, later that night): the restored home page shows the journey again; phase 6 reads "No listing is arranged, promised or sought by the project" there and in the litepaper's roadmap.
@@ -2266,6 +2272,8 @@ Evidence: `site/litepaper.html`; `docs/plans/testnet-go.md`; X31, X32.
 ### X34. RandomX described as chip-free
 "The home page said the random program 'has kept chips off Monero since 2019', the litepaper said Monero ran on RandomX 'with no chip publicly shipped' and spoke of 'Monero's seven years without a public chip'. Bitmain's Antminer X9, a RandomX chip, ships from July 2026 (1 MH/s at 2,472 W, about USD 5,600; monero-project/monero issue 10270), and RandomX 2.0 shipped on 25 March 2026. Every sentence that said or implied RandomX is chip-free, or that Monero's approach has held, was wrong."
 
+Status: Fixed, stated (7 October 2026, morning): the one-screen home page carries no RandomX sentence, so the corrected wording stands on `site/litepaper.html` (four sentences and the table row); the text check lists them there.
+
 Status: Fixed, stated (6 October 2026, night, from the cryptanalysis research): four sentences corrected, each with the X9 as the stated fact and its date; every sentence that only names the technique stands.
 - `site/index.html`, Monero's technique card. Was: "The random program that has kept chips off Monero since 2019 (approximate), rebuilt for graphics cards. The program keeps changing on a schedule fixed at genesis; nobody touches it." Now: "Monero's random program held chips off from 2019 (approximate) until Bitmain's Antminer X9 shipped in July 2026: 1 MH/s at 2,472 W, about USD 5,600. Igneum rebuilds the idea for graphics cards with a program that changes every hour on a schedule fixed at genesis; nobody touches it."
 - `site/litepaper.html`, Mining. Was: "Monero has run on RandomX since 2019 with no chip publicly shipped, approximate; that is precedent, not proof." Now: "Monero ran on RandomX from 2019 (approximate) with no chip publicly shipped until Bitmain's Antminer X9 in July 2026 (1 MH/s at 2,472 W, about USD 5,600; monero-project/monero issue 10270). About seven years of hold and then a chip: that is the record Igneum's hourly program and its chip model are built against."

site/journey.json

@@ -207,48 +207,48 @@
     },
     {
       "date": "2026-10-04",
-      "text": "Sim/economy: mining versus proving under stress, agent-based",
-      "short": "Economy simulation: mining versus proving under stress"
+      "text": "One-click Windows workers: what the Apple M5 Max could measure",
+      "short": "One-click Windows workers"
     },
     {
       "date": "2026-10-04",
-      "text": "Difficulty rule under attack: pool hopping, pulsed rental, timestamp stretching, short-lane oscillation, epoch games, polluted window, block flood",
-      "short": "Difficulty rule attacked seven ways"
+      "text": "First finality lock on the live devnet: checkpoint 242 at 77.4% of all weight, two hours after genesis",
+      "short": "First live finality lock: 77.4% of weight, 17 voters"
     },
     {
       "date": "2026-10-04",
-      "text": "Difficulty rule: timestamp attack fixed , simulator regression, 3-node forger test",
-      "short": "Timestamp attack on the difficulty rule fixed"
+      "text": "The gfx1036 worker fault and what the Apple M5 Max could and could not reproduce",
+      "short": "The gfx1036 worker fault and what the Apple M5 Max could and could…"
     },
     {
       "date": "2026-10-04",
-      "text": "Devnet-v4 integration: nine branches merged, 3-node test network on the merged node, Windows cross-build",
-      "short": "Devnet v4: nine branches merged into one node"
+      "text": "A node 60 s behind the clock is silently dead",
+      "short": "A node 60 s behind the clock is silently dead"
     },
     {
       "date": "2026-10-04",
-      "text": "Generator version 2 adopted: exact load count, fresh-source loads, program acceptance; every vector re-cut, three workers re-checked, 20,000-program census, devnet-v4 binaries rebuilt",
-      "short": "Generator v2 adopted: every hash does 128 distinct reads"
+      "text": "First machine on the Igneum Miner app: the RTX 5090 Windows rig's RTX 5090 at 118 MH/s, via Setup.exe",
+      "short": "First machine on the one-click app: a 5090 at 118 MH/s"
     },
     {
       "date": "2026-10-04",
-      "text": "Proving v0 on the RTX 5090: first GPU proof of an Igneum block",
-      "short": "First GPU proof of an Igneum block: 1.4 s on an RTX 5090"
+      "text": "Difficulty rule v2: the live oscillation, its cause, the DAG replay, the fix behind a height switch",
+      "short": "Difficulty rule v2"
     },
     {
       "date": "2026-10-04",
-      "text": "Devnet v4 cut-over: generator v2, 2/3 floor, three nodes and a seed on a fresh chain",
-      "short": "Devnet v4 live: generator v2, two-thirds floor, fresh chain"
+      "text": "The observer stored nothing for 78 minutes, then 7,022 blocks in two minutes",
+      "short": "The observer stored nothing for 78 minutes, then 7,022 blocks in two…"
     },
     {
       "date": "2026-10-04",
-      "text": "First hourly program swap on the live devnet: compile-ahead, no pause, two cards",
-      "short": "First live hourly swap: no pause on Mac, NVIDIA or AMD"
+      "text": "The RTX 5090 Windows rig at the 14:20 boundary: a worker stuck on the previous epoch",
+      "short": "The RTX 5090 Windows rig at the 14"
     },
     {
       "date": "2026-10-04",
-      "text": "Proving: devnet v4 shards on the Apple M5 Max CPU, loaded machine",
-      "short": "Proving: devnet v4 shards on the Apple M5 Max CPU, loaded machine"
+      "text": "Shard proving on the RTX 5090: a full shard compressed in 10.9 s, a two-shard block aggregated in 2.2 s, all verified",
+      "short": "Shard layer on the RTX 5090: a full shard proven in 10.9 s, a block aggregated in 2.2 s"
     }
   ]
 }

site/ledger.html

@@ -142,9 +142,9 @@ details{margin-top:8px;font-size:14px;color:var(--ash)}summary{cursor:pointer;co
 <thead><tr><th>Count</th><th>Status</th><th>Meaning</th></tr></thead>
 <tbody>
 <tr><td class="num">7</td><td><button type="button" class="chip" data-filter="Open">Open</button></td><td>Nothing has settled it yet. The entry names what will</td></tr>
-<tr><td class="num">62</td><td><button type="button" class="chip" data-filter="Conceded">Conceded</button></td><td>The critic is right. &quot;Stated&quot; means the public text says so; &quot;not yet stated&quot; means it does not yet</td></tr>
+<tr><td class="num">63</td><td><button type="button" class="chip" data-filter="Conceded">Conceded</button></td><td>The critic is right. &quot;Stated&quot; means the public text says so; &quot;not yet stated&quot; means it does not yet</td></tr>
 <tr><td class="num">59</td><td><button type="button" class="chip" data-filter="Fixed or built">Fixed or built</button></td><td>A code, spec or text change answers it, with the commit or the page named</td></tr>
-<tr><td class="num">28</td><td><button type="button" class="chip" data-filter="Closed by rule or decided">Closed by rule or decided</button></td><td>A consensus rule or a decision by the owner answers it, dated</td></tr>
+<tr><td class="num">27</td><td><button type="button" class="chip" data-filter="Closed by rule or decided">Closed by rule or decided</button></td><td>A consensus rule or a decision by the owner answers it, dated</td></tr>
 <tr><td class="num">13</td><td><button type="button" class="chip" data-filter="Answered with evidence">Answered with evidence</button></td><td>A measurement or a simulation exists and is named</td></tr>
 <tr><td class="num">13</td><td><button type="button" class="chip" data-filter="Answered by design">Answered by design</button></td><td>A design rule answers it; no measurement is possible yet</td></tr>
 <tr><td class="num">182</td><td><button type="button" class="chip" data-filter="">All</button></td><td>Every entry. The sections: <a href="#m">Mining and chips</a>, <a href="#f">Finality and attacks</a>, <a href="#p">Proving and the zkEVM</a>, <a href="#e">Economics and the coin</a>, <a href="#g">Governance and the founders</a>, <a href="#c">Comparisons</a>, <a href="#l">Legal and regulatory</a>, <a href="#x">Launch and operations</a>, <a href="#d">Builders</a></td></tr>
@@ -492,9 +492,9 @@ details{margin-top:8px;font-size:14px;color:var(--ash)}summary{cursor:pointer;co
 <details><summary>The answer as first written</summary><p>The founder's name is on every commit. The litepaper defers the team page to public testnet by decision, with disclosed mining addresses at genesis. There are no coins to sell and no sale planned, so there is nothing to run away with before block one. The five log entries dated 3 October 2026 are day one of the project and should be presented as that.</p></details>
 </article>
 <article class="entry" id="G4" data-bucket="Conceded">
-<div class="head"><span class="id">G4</span><h3>No admin keys, except in everything that matters</h3><span class="date">5 October 2026</span></div>
+<div class="head"><span class="id">G4</span><h3>No admin keys, except in everything that matters</h3><span class="date">7 October 2026</span></div>
 <blockquote>'There are no admin keys.' The DEX, the lending market, the bridge and the dev fund contract all ship from your team. Bridges are where the admin keys live.</blockquote>
-<div class="status"><span class="badge b-conceded">Conceded, stated</span> <span class="did">5 October 2026, night): <code>a repository file</code>, Governance, &quot;There are no admin keys in consensus&quot;; <code>a repository file</code>, tile &quot;admin keys in consensus&quot;. Was: Conceded, wording fix needed.</span></div>
+<div class="status"><span class="badge b-conceded">Conceded, stated</span> <span class="did">7 October 2026, morning): the one-screen home page is back on the owner's word, so this row is stated on <code>a repository file</code> only; the sentence there is unchanged and the text check lists it under the litepaper.</span></div>
 <details><summary>The answer as first written</summary><p>Correct. Consensus has no admin keys. The genesis apps are contracts and each will have an upgrade policy; the bridge's is the one that matters, and if it starts as a committee bridge (E7) it has keys by definition. The development fund contract named in the quote no longer exists: the fund was removed on 3 October 2026. The litepaper's sentence must be scoped to consensus and each genesis contract must publish its key policy before launch.</p></details>
 </article>
 <article class="entry" id="G5" data-bucket="Conceded">
@@ -534,10 +534,10 @@ details{margin-top:8px;font-size:14px;color:var(--ash)}summary{cursor:pointer;co
 <div class="status"><span class="badge b-answered-by-design">Answered by design</span></div>
 <details><summary>The answer as first written</summary><p>Monero chose the CPU for egalitarian reasons and accepted botnets as the price. Igneum chooses the GPU because the thesis is paid proving, which CPUs cannot do, and refuses a CPU lane because of botnets. It is a different trade, and the litepaper should say &quot;Monero's technique, applied to GPUs&quot; rather than &quot;finished&quot;.</p></details>
 </article>
-<article class="entry" id="C2" data-bucket="Closed by rule or decided">
-<div class="head"><span class="id">C2</span><h3>vs Monero: &quot;no chip in seven years&quot; is not proof</h3><span class="date">6 October 2026</span></div>
+<article class="entry" id="C2" data-bucket="Conceded">
+<div class="head"><span class="id">C2</span><h3>vs Monero: &quot;no chip in seven years&quot; is not proof</h3><span class="date">7 October 2026</span></div>
 <blockquote>Absence of a public RandomX ASIC is not evidence one cannot exist. Monero is also a small prize.</blockquote>
-<div class="status"><span class="badge b-closed-by-rule-or-decided">Closed by the fact</span> <span class="did">6 October 2026, night): a public RandomX chip now exists, Bitmain's Antminer X9, shipping from July 2026 (1 MH/s at 2,472 W, about USD 5,600; monero-project/monero issue 10270). Every sentence that leaned on its absence was rewritten under X34; &quot;2019 (approximate)&quot; stays on both pages.</span></div>
+<div class="status"><span class="badge b-conceded">Conceded, stated</span> <span class="did">7 October 2026, morning): the one-screen home page is back on the owner's word, so this row is stated on <code>a repository file</code> only; the sentence there is unchanged and the text check lists it under the litepaper.</span></div>
 <details><summary>The answer as first written</summary><p>True. &quot;No chip publicly shipped, approximate&quot; is the defensible phrasing. The argument from Monero is precedent, not proof, and the bounty exists because precedent is not proof.</p></details>
 </article>
 <article class="entry" id="C3" data-bucket="Conceded">
@@ -681,9 +681,9 @@ details{margin-top:8px;font-size:14px;color:var(--ash)}summary{cursor:pointer;co
 <details><summary>The answer as first written</summary><p>Correct. The site needs a contact route before the litepaper is shared, and the repository needs to be public or a public issue tracker needs to exist. Until then this ledger's submission line points at a route that does not exist.</p></details>
 </article>
 <article class="entry" id="X8" data-bucket="Conceded">
-<div class="head"><span class="id">X8</span><h3>Exchange listings as a roadmap item</h3><span class="date">5 October 2026</span></div>
+<div class="head"><span class="id">X8</span><h3>Exchange listings as a roadmap item</h3><span class="date">7 October 2026</span></div>
 <blockquote>'Mainnet fair launch: Genesis with no premine, 30-day ramp, exchange listings after.' You put listings in the roadmap.</blockquote>
-<div class="status"><span class="badge b-conceded">Conceded, stated</span> <span class="did">5 October 2026, night): <code>a repository file</code>, Roadmap phase 6, and <code>a repository file</code> phase 6, &quot;No listing is arranged, promised or sought by the project&quot;. Was: Conceded, fix now.</span></div>
+<div class="status"><span class="badge b-conceded">Conceded, stated</span> <span class="did">7 October 2026, morning): the one-screen home page is back on the owner's word, so this row is stated on <code>a repository file</code> only; the sentence there is unchanged and the text check lists it under the litepaper.</span></div>
 <details><summary>The answer as first written</summary><p>Correct. No listing is arranged, promised or sought by the project. The phrase comes off the roadmap and the homepage journey.</p></details>
 </article>
 <article class="entry" id="X9" data-bucket="Conceded">
@@ -1264,9 +1264,9 @@ details{margin-top:8px;font-size:14px;color:var(--ash)}summary{cursor:pointer;co
 <details><summary>The answer as first written</summary><p>The month was the plan of 3 October 2026. The benchmark tool is part of the testnet's go checklist, so it ships with the testnet; no month is given for either.</p></details>
 </article>
 <article class="entry" id="X34" data-bucket="Fixed or built">
-<div class="head"><span class="id">X34</span><h3>RandomX described as chip-free</h3><span class="date">6 October 2026</span></div>
+<div class="head"><span class="id">X34</span><h3>RandomX described as chip-free</h3><span class="date">7 October 2026</span></div>
 <blockquote>The home page said the random program 'has kept chips off Monero since 2019', the litepaper said Monero ran on RandomX 'with no chip publicly shipped' and spoke of 'Monero's seven years without a public chip'. Bitmain's Antminer X9, a RandomX chip, ships from July 2026 (1 MH/s at 2,472 W, about USD 5,600; monero-project/monero issue 10270), and RandomX 2.0 shipped on 25 March 2026. Every sentence that said or implied RandomX is chip-free, or that Monero's approach has held, was wrong.</blockquote>
-<div class="status"><span class="badge b-fixed-or-built">Fixed, stated</span> <span class="did">6 October 2026, night, from the cryptanalysis research): four sentences corrected, each with the X9 as the stated fact and its date; every sentence that only names the technique stands.</span></div>
+<div class="status"><span class="badge b-fixed-or-built">Fixed, stated</span> <span class="did">7 October 2026, morning): the one-screen home page carries no RandomX sentence, so the corrected wording stands on <code>a repository file</code> (four sentences and the table row); the text check lists them there.</span></div>
 <details><summary>The answer as first written</summary><p>The precedent Igneum cites is now a complete one: a fixed random program held CPU mining for about seven years and then a chip shipped. Igneum's program changes every hour from a genesis-fixed schedule, its dataset grows, and the chip model on the numbers page prices the chip that stores the dataset rather than assuming none can be built. The X9's rate and power are Bitmain's published figures, not our measurement.</p></details>
 </article>
 <article class="entry" id="X35" data-bucket="Fixed or built">

tools/ci/ledger-text-check.mjs

@@ -8,21 +8,18 @@ import { fileURLToPath } from 'node:url';
 const site = join(dirname(fileURLToPath(import.meta.url)), '..', '..', 'site');
 const REQUIRED = {
   'index.html': [
-    // 6 Oct 2026: the home page is the scene, three facts, the downloads and one line to the ledger; the rows it no longer
-    // states moved to the litepaper (G4, C2, X3, X8 below) and the ledger's "stated on" notes are owed an update
+    // 7 Oct 2026, morning: the one-screen home page of 62bfaea is back on the owner's word (the scene, three facts, the
+    // downloads, one line to the ledger). The rows it no longer states (G4, C2, X8, X34) stand on the litepaper, listed below.
     ['E5', 'The one payment to the project is the Ember software\u2019s optional 1% dev fee', 'The one payment to the project is the Ember software\'s optional 1% dev fee'],
     ['X2', 'Public testnet: not yet open; the devnet build is here for people who want to look'],
     ['X7', 'hello@igneum.network'],
-    // restored with the home page on 6 October 2026 (the owner: "revert it but polish it")
-    ['G4', 'admin keys in consensus'],
-    ['C2', '2019 (approximate)'],
-    ['X34', 'Antminer X9 shipped in July 2026: 1 MH/s at 2,472 W, about USD 5,600'],
-    ['X35', 'With the class v4 shadow work it is 2.1x to 3.9x'],
-    ['X8', 'No listing is arranged, promised or sought by the project'],
     ['X31', 'The public testnet is weeks away: three seed nodes and the public RPC are up, and it opens when the go checklist closes.'],
+    ['X35', 'With the class v4 shadow work it is 2.1x to 3.9x'],
   ],
   'litepaper.html': [
     ['X3', 'Live rows arrive with the public testnet.'],
+    ['G4', 'admin keys in consensus'],
+    ['X8', 'No listing is arranged, promised or sought by the project'],
     ['X31', 'The public testnet is weeks away: three seed nodes and the public RPC are up, and it opens when the go checklist closes.'],
     ['C2', '2019 (approximate)'],
     ['X34', 'Antminer X9 ships from July 2026 at 1 MH/s and 2,472 W, about USD 5,600, and RandomX 2.0 shipped on 25 March 2026'],