Reached 238 via public-key enrolment - no password anywhere. The first attempt failed
because the key had never landed in authorized_keys; the second worked once the
fingerprint matched.
Findings worth keeping beyond this node:
The VM reports 'AMD Ryzen 9 3900X' and then lists 65 CPUID flags that stop at SSE4.2.
No avx, no avx2, no fma. That silicon has AVX2 and FMA, so VirtualBox is masking them
and /proc/cpuinfo is a declaration, not a measurement. Recorded as *unverified* rather
than absent, because confirming it needs an actual AVX instruction executed and there
is no gcc on the guest - a flag list cannot settle it.
This is the defect the compute design already has, one layer down. The agent sets
throughput_factor by string-matching a GPU model (40.0 if '4070' in name else 20.0),
which is a declared factor wearing a measured one's name. Here the hypervisor makes the
same kind of lie. Capability discovery therefore has to probe by executing
instructions and treat an unverifiable feature as unavailable.
Also: cpu.max is 'max 100000' so the guest is not CPU-capped, memory is 47.0 GiB
unballooned, no GPU and no nested virt flags, and umbra has no sudo. Recorded in docs/
node-238-capability-profile.md with how each value was obtained.
11f27f5ef9