BFE EngineeringandClaude Fable 5
2756de0b46
CI/pipeline: - KERNEL_TARBALL passed as a YAML env literal '~' was never tilde-expanded and would have failed every hosted kernel-build dispatch; the path is now exported from the shell. Verified reproducible before the fix. - Every job gets timeout-minutes; boot smoke uses timeout -k so a wedged qemu is SIGKILLed instead of holding the job. - Tarball fetch + fail-closed sha256 verification deduplicated into build/fetch-kernel-tarball.sh (with curl retries), used by build-kernel.sh and both CI jobs. busybox fetch gains retries too. - ccache layer for kernel-build (cache keyed on defconfig+patches) recovers the incremental-compile speed the ephemeral-runner move cost. - build-kernel.sh now asserts every fragment option survived olddefconfig — merge_config -m pastes text and Kconfig silently drops unmet symbols. rs485-bridge: - pending-buffer cap (2x max RTU ADU) instead of unbounded growth; explicit accept-loop error handling with backoff instead of .flatten(); per-arm inline bounds instead of the string-keyed lookup whose default would have mis-bounded a future get-input; control-socket cleanup errors surfaced; flag-shaped values rejected in arg parsing; doc example uses a private mktemp dir. Test timing margins widened for contended runners (gap 25->120ms, 60x margin on the split-frame test). VM harness: - stage-1/stage-2 boot scripts share one validated slot parser and one by-name populator (qemu/rootfs/etc/warden-lib.sh) — the duplicated parser had already diverged on validation; userdata/oem mount failures now fail fast with a greppable sentinel; udhcpc fallback keys off the interface actually having an address; switch_root applet guarded. - boot-smoke delegates the qemu invocation to run.sh (machine shape lives in ONE place); run.sh port 0 disables a hostfwd. - mkimage: unknown partition names fail at build time; DISK_END is a max, not last-entry; --state keys validated as filenames. - portal-scenario: mock readiness is asserted (no silent fall-through), hostfwd port collisions retried, mount-failure sentinel fails fast. - ui-shot: fixed sleeps replaced with bounded screendump polling; the repaint assertion is real and documented as such. qmp.py loses its module-global and gains argv validation. Docs/scrub: bench-host paths and the site AP name removed from six more port docs and two evidence tables; path-bearing build artifacts (.elf, .map) untracked (the 154-byte firmware .bin is path-free and stays); ADR-0003 marked visibility-superseded by ADR-0007; stale section cross-reference fixed; flare-edge noted as private for outside readers; stale root-level review report removed per the new workspace rule. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018HUayid7W5w7jBdb9Rrj1K
23 lines
1.1 KiB
Markdown
23 lines
1.1 KiB
Markdown
# ADR 0003 — warden-sdk is a standalone repo
|
|
|
|
**Status:** Accepted (2026-08-25). Repo-visibility half superseded by ADR-0007
|
|
(2026-08-30) — warden-sdk went public; the "private for now" consequence below
|
|
no longer holds. Original decision kept for the record.
|
|
|
|
## Context
|
|
Our real SDK changes lived as uncommitted edits in a 2GB opaque vendor fork, with
|
|
no CI, tests, or versioning of their own. The SDK requirement (future-features-2
|
|
§SDK) calls for "its own repo, held to firmware standards."
|
|
|
|
## Decision
|
|
A **private** `bfe-noah/warden-sdk` GitHub repo, standalone from day one with its own
|
|
CI/versioning. Work lands on a `bringup` branch; the first commit to `main` is gated
|
|
on a passing review run, green CI, and the maintainer's fresh explicit go-ahead.
|
|
|
|
## Consequences
|
|
- flare-edge consumes warden-sdk later (flared depending on `warden-sim`, drivers
|
|
built from here) — a separate, maintainer-gated integration step; flare-edge is not
|
|
edited by the SDK-completion effort.
|
|
- Private for now (references bench devices / in-progress hardening); can be opened
|
|
later once scrubbed, matching how `flare-deployment` is handled.
|