Bring the Oct 18-20 CI hardening on main into the afw OS-bundle line before
promoting it to main. Resolution:
- src/{main,lib,hal_wire,management}.rs, Cargo.toml, Cargo.lock: the branch
side; it is a superset of main's (main's ALKANE_API_LISTEN management API now
lives in src/app.rs and is wired for every run mode).
- workflows: main's runner-image pin (ad56db2f) and conditional SSH install,
main's workflow_run triggers for the badge and Pages publishers, next's
CARGO_BUILD_JOBS=2; the branch's extra gates (image safety, .afw tests,
research/evidence, version checks, evidence-status artifact) are kept.
- ci/last-attempt-badge.py + its test, ci/publish-bench-pages.py: main's
(workflow_run events; stderr detail on failure). ci/cleanup-generated.py: the
branch's (also cleans the evidence-status file the kept step writes).
- README.md, ci/CONFORMANCE.md: the branch's (documents the web console and
the evidence-status report, both present in the merged tree).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1W6qKwKxq3oUPDKWicM6i
Add the S21 Pro-class Amlogic A113D/AXG control board to the .afw producer
and the CI brick-prevention gate, matching the Zynq-7010 treatment.
- ci/afw_boards.py: a113d producer profile (arm64, preserve, buildable). Maps
the 7-mtd layout, names nvdata (mtd6) the only image-bearing partition, and
stages three images vmlinux.bin/devicetree.dtb/uramdisk.image.gz
(arm64-image/fdt/uimage) into it.
- ci/afw_manifest.py: validate_a113d enforces exactly those three images, the
formats, per-image ceilings, total <= nvdata usable, and that no
bootloader/spl/fip/tpl member is present and no non-nvdata partition carries
an image.
- ci/check-afw.py: the independent checker re-validates the produced bundle
(arm64, preserve, no FIP member, three named images with formats/ceilings,
total <= nvdata, mtd0-5 carry no image) and knows the arm64 Image magic.
- ci/test-afw.py: a113d bundle passes and installs all three into nvdata;
non-arm64 kernel, oversize kernel, an added FIP member, and a preserved mtd
made to carry an image are each refused.
All 37 afw tests pass.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1W6qHxYpv7yf7Ah57g4rQ
Adds a buildable zynq-7010 profile and its .afw brick-prevention gate, so the
proven Zynq image is a first-class .afw like cv1835/am335x.
- afw_boards.py: full zynq-7010 profile (armv7, preserve; kernel(zimage)+dtb(fdt)
into mtd0, rootfs(cpio-gzip) into mtd1); new strict 'zimage' SAFE_IMAGE_FORMAT.
- afw_manifest.py + check-afw.py: validate_zynq / the zynq-7010 gate - exactly the
kernel/dtb/rootfs image set, correct formats, size ceilings (kernel <= 0x500000
fits the slot, dtb <= 0x20000, rootfs <= 0x2000000 fits mtd1), and NO
bootloader/spl/BOOT.bin member (stock BOOT.bin + FPGA bitstream preserved). The
per-unit kernel-slot offset is placed by the install method (differs S17/S19),
so the gate enforces formats+ceilings+policy, not a fixed offset map.
- check-afw: strict zimage magic (0x016f2818 at 0x24).
- tests: good bundle, non-zImage kernel, oversize kernel, bootloader-member refusals.
Built + double-gated the real bundle: alkane-os-0.1.0-zynq-7010-armv7.afw
(kernel 4.1 MiB, dtb 11 KB, rootfs 2.5 MiB). Full afw suite green.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1W6qHxYpv7yf7Ah57g4rQ
Mirrors the alkane-sdk tier-3 plan gate on the producer side so a from-stock
bundle can be built and verified. The am335x-stock profile writes our non-RSA
U-Boot to mtd4 (legacy firmware uImage, ih_type 5) plus kernel/dtb/root, and:
- afw_boards.py: am335x-stock profile (bootloader_policy include, mtd4 write
target at order 3, kernel at order 4, u-boot image).
- afw_manifest.py + check-afw.py: validate_am335x_stock - shares the 12-part map
and 0x780000 hole with tier-2 but asserts policy include, the 4-image set,
mtd4 ceiling 0x1c0000, the U-Boot member is a type-5 firmware uImage, and that
no SPL copy (mtd0-3) or bootenv (mtd5) is ever a write target.
- check_format: am335x uImage checks now cover am335x-stock, incl. u-boot type 5.
- tests: 3 am335x-stock producer cases (good 4-install bundle, wrong U-Boot type,
SPL-write refusal). Full afw suite 28 green; am335x tier-2 + cv1835 unchanged.
Built and double-gated the real bundle locally: alkane-os-0.1.0-am335x-stock-arm.afw
(u-boot 723440 B type5 -> mtd4, kernel -> mtd7, dtb -> mtd6, rootfs -> mtd8).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1W6qHxYpv7yf7Ah57g4rQ
The producer verified the bundle but never wrote the SHA256SUMS release
artifact, so a stale file from a previous build could describe a different
bundle. Write it (overwrite) from the finished file.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1W6qHxYpv7yf7Ah57g4rQ
Assert that the checker accepts a matching plan size and rejects a plan
whose p1 size disagrees with the manifest.
Co-Authored-By: DeepSeek Harness <noreply@deepseek.com>
Replace the release-tree producer with a board-aware schema-2 manifest,
fixed-order ustar packing, optional Ed25519 signing, and a checker that
rejects a wrong board or arch, a missing or oversized image, a bootloader
member under preserve, a hash or size mismatch, and a traversal member.
Document the format and add offline fixtures for every refusal.
Co-Authored-By: DeepSeek Harness <noreply@deepseek.com>
Dashboard (src/dashboard.rs): the on-box UI now renders from
schema/alkane-bb.json through flare-ui and wschema. The sidebar, the tab strip
and all 20 settings controls come from the schema; the host boundary does what
the crates require - validate the submitted batch with wschema before persisting,
ignore keys that are not in the schema, and never write on a rejected form.
Settings live in /etc/alkane/settings.json (temp dir when the root is read-only).
Web: GET /<section> and /<section>/<tab> render the dashboard, /assets/* serves
the crate's embedded token/component/theme stylesheets, POST /settings applies a
form. The existing JSON API routes are untouched.
Settings wired (all from real runtime knobs): tuning target mode and its four
values, frequency ceiling, the PID gains and limits in milli-units (the schema
has integer kinds only), fan zones/duty/sweep, detection ports and budget,
profile database path, board name.
Tests: 10 dashboard tests (schema loads, all settings present, page renders
inputs, valid submit persists and reloads, out-of-range rejected with nothing
written, unknown keys ignored, percent decoding) plus the existing 162. 172 pass.
Packaging (ci/make-afw.sh): .afw modelled on the Warden .wfw bundle - strict
POSIX ustar, manifest first, payload verified by size and sha256 - with three
deliberate differences: the payload is gzip-compressed, the manifest carries
and x86_64, and both appear in the file name
(alkane-os-0.1.0-am335x-bb-armv7.afw) so a bundle cannot be mistaken for another
family. Signature is declared in the manifest until a release key
exists; the sha256 is the only integrity claim today.
Spike, not the final UI: it answers whether flare-ui can drive Alkane OS's
on-box pages, and what it costs.
What works:
- schema/alkane-bb.json authors the sidebar as data (3 sections, 14 tabs);
- src/bin/ui-spike.rs renders it through flare_ui::nav + flare_ui::shell, so
the unified sidebar, ordering and surface filtering come from the schema
rather than from hand-written HTML;
- the render uses the shared bf- design tokens, the same ones the rest of the
suite uses.
Size, measured rather than assumed (armv7, release, stripped):
ui-baseline 323 KiB (maud + serde_json, no flare-ui)
ui-spike 771 KiB (flare-ui + wschema + sha2)
marginal 448 KiB
Vendoring: third-party/flare-ui is the full v0.2.9 tree pinned in
flare-ui/flare-ui.lock (a partial archive does not compile, since the crate
include_str!s assets from dash-editor/). vendor/ is re-generated as a cargo
directory source with the new registry dependencies (maud, sha2, typenum,
digest, generic-array, block-buffer, crypto-common, cfg-if, etc.) so the build
still works offline. third-party/README.md records how to re-pin.
The SDK refuses a bad payload before writing it; this is the same rule on the
producing side, so a release cannot ship an image that would not boot or would
not fit the partition it targets.
Checks every payload artefact it can find: magic must match the claimed format
(FDT d00dfeed, legacy uImage 27051956, raw ARM zImage 016f2818 at 0x24) and the
size must fit the partition. Absent artefacts pass with a note, so the gate can
be wired before the first image exists.
Proven both ways: it accepts the four payload files that actually installed
OurOS, and rejects a zImage renamed to the ramdisk slot on size.