Test registry: UX-01 RUNNING as a batch for the merge tool to replay (tools/ci/batches/ux-01-20261008-win-2.0.0.json on manifest f49904fe; the cell pc:install-update in tools/ci/test-map.json for UX-01 (team-run evidence only; the P10 study NOT RUN until unaffiliated participants are recruited), UX-07 (the install classes) and OPS-03 (the update path's read-back); the evidence file docs/plans/evidence/UX-01-20261008.md with the read-back lines so far). The registry and the map page are not in this commit: the landing replays the batch onto master's registry and the page follows the steward's regeneration (rule 26 refused four landings that carried them)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs
parent
1dd05f020a
commit
32cf9e534c
3 changed files with 50 additions and 0 deletions
21
docs/plans/evidence/UX-01-20261008.md
Normal file
21
docs/plans/evidence/UX-01-20261008.md
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
# UX-01 evidence, run ux-01-20261008-win-2.0.0 (8 October 2026)
|
||||
|
||||
Onboard ordinary owners on native desktop apps, the team-run half: the two Windows PCs take the Igneum Miner 2.0.x Windows
|
||||
entry (2.0.0 live 18:44 UK, Setup exe 793a631d, manifest aa354ed5; 2.0.1 about 20:55 UK with the coinbase-over-u64 fix)
|
||||
through the app's own update path, with no click after the install and mining on every card (the founder's rule of
|
||||
18:0x UK), observed through the apps' own intake uploads and the relay agents. The P10 study (30 unaffiliated
|
||||
participants) is NOT RUN: not yet recruited; never a staff run.
|
||||
|
||||
## Shape
|
||||
- PC 1 (ae432dc7): Igneum Miner 0.3.26 since 17:26 UK, RTX 5090, RTX 5080, RX 7600; mining off under the Devnet 3 off order; the 2.0.0 installer downloaded and verified 18:58 UK, the install queued in the hash lane's order (update-now-20261008-181124).
|
||||
- PC 2 (1ccfe586): RTX 5090, RTX 5060 Ti, Arc B580; mining off since the Devnet 3 off jobs (#1519 api/pause 16:38 UK, #1521 17:15 UK).
|
||||
- The read-back: the engine's "update-return: app <v> up after the update from <from>" line at intake, then the relay run "mining on after the 2.0.1 install" (mining-on-after-200.ps1: wait for 2.0.1 or later, clear a stale install-running.flag, api/resume, start the app if silent) printing `RESULT MINING-ON ok|partial version=... network=... node=... synced=... paused=false cards=<n> rates=...`.
|
||||
|
||||
## Read-back lines (time UK, PC, the line or the fault and its class)
|
||||
- 19:22:01 PC 2: `update-return: app 2.0.0 up after the update from 0.3.26 (node igneumd 2.0.0, machine 1ccfe586)`; node started 19:22:05; `[ok] mining resumed` 19:22:13 (no click: relay run #1742 cleared the pause through api/resume).
|
||||
- 19:28 PC 2 (#1754): `RESULT MINING-ON partial version=2.0.0 network=devnet node=no peers synced=False paused=False cards=3` (every card waiting). Class: the devnet-4 hubs' outage (every dial target down 19:15 to 19:17, back by 19:29), not the install.
|
||||
- 19:41 PC 2 (#1757): `RESULT MINING-ON partial ... node=behind peers=1 synced=False tip_age_s=1289`; IBD completed 19:29:16, the node then "behind". Class: the 2.0.0 miner refuses every template whose coinbase exceeds a u64 (the shipper, 19:5x UK), fixed in node 777214af as the 2.0.1 entry.
|
||||
- PC 1: pending (0.3.26; the install runs when its queue reaches update-now, then 2.0.1 through the same path).
|
||||
|
||||
## Status
|
||||
- 20:36 UK: RUNNING; the 2.0.1 read-backs (relay runs #1762 PC 2, #1763 PC 1) are the next lines.
|
||||
12
tools/ci/batches/ux-01-20261008-win-2.0.0.json
Normal file
12
tools/ci/batches/ux-01-20261008-win-2.0.0.json
Normal file
|
|
@ -0,0 +1,12 @@
|
|||
{
|
||||
"run_id": "ux-01-20261008-win-2.0.0",
|
||||
"manifest_sha": "aa354ed5",
|
||||
"evidence_dir": "docs/plans/evidence/UX-01-20261008.md",
|
||||
"cells": [
|
||||
{
|
||||
"cell": "pc:install-update",
|
||||
"status": "RUNNING",
|
||||
"evidence": "docs/plans/evidence/UX-01-20261008.md"
|
||||
}
|
||||
]
|
||||
}
|
||||
|
|
@ -588,6 +588,23 @@
|
|||
"coverage": {
|
||||
"GPU-03": "partial: the 64-register window on AMD and Intel, rate per unit of work (RX 7600 0 percent, Arc B580 -0.3 percent, kernel throughput, quiet) with the B580 fingerprints equal on both packs and the offline RDNA allocation (160 VGPRs, no spill); energy owed (the 7600 job queued, the B580 counter unsupported unelevated); team-run, not under the standard's paired protocol or a wall meter"
|
||||
}
|
||||
},
|
||||
"pc:install-update": {
|
||||
"command": "signed jobs and relay runs on PC 1 (ae432dc7) and PC 2 (1ccfe586): the installer over the running app (rule 14: installed versions, the process set, the first upload), the OTA path (update-now, the update-return read-back line), and the no-click resume after the install (relay run mining-on-after-200.ps1)",
|
||||
"box_class": "PC (the two Windows PCs; nothing on the Mac)",
|
||||
"fixtures": [
|
||||
"F2"
|
||||
],
|
||||
"cases": [
|
||||
"UX-01",
|
||||
"UX-07",
|
||||
"OPS-03"
|
||||
],
|
||||
"coverage": {
|
||||
"UX-01": "team-run evidence only (the two PCs taking the Windows entry through the app's own update path with no click and mining on every card); the P10 study is NOT RUN until unaffiliated participants are recruited",
|
||||
"UX-07": "partial: the install classes (the payload's stop step, the detached installer under a job, the installer refusing a wrong-version name, a stale install flag) and the no-click resume; the recovery-instruction and canary rows are the shipper's",
|
||||
"OPS-03": "partial: the update path's read-back and the signed manifest's verify on the PC (a tampered or rolled-back payload is refused by the engine's manifest check); authority separation is the shipper's review"
|
||||
}
|
||||
}
|
||||
},
|
||||
"not_run": {
|
||||
|
|
|
|||
Loading…
Reference in a new issue