BFE Engineering
42fb386f60
Replace every em dash with real punctuation (rewrites, not hyphen swaps) in docs, code comments, scripts, configs, and the port records; convert en dashes, curly quotes, ellipsis glyphs, arrows, and section signs to ASCII; drop machine-writing tell phrases from living docs. ADR titles now use a colon. The M2 bring-up DTS model string carried an em dash into the patch series and its record echoes; fixed at both, and the full series re-verified to apply cleanly onto pristine 6.18.46. One comment in freshness.h deliberately names the em dash glyph the UI renders as the unknown mark; that is data, kept as prose naming it. Verified: cargo tests (sim, config-lint, rs485-bridge), shellcheck, both driver MC/DC harnesses, patches-apply.
1.2 KiB
ADR 0004: Self-Hosted Runner
Status: Superseded in part by ADR-0007 (2026-08-30): kernel-build moved
to GitHub-hosted runners for the public repo and the self-hosted registration
is retired. Original decision below, kept for the record. (2026-08-25.)
Context
The heavy kernel/firmware build needs the SDK toolchain and Buildroot's baked-in
absolute paths, impractical on GitHub-hosted runners. flare-edge already builds on
a repo-scoped self-hosted runner on bfe-mpc-0640 (label flare-edge); a repo-scoped
registration cannot be shared across repos by label alone.
Decision
Register a third repo-scoped runner instance on bfe-mpc-0640, label
warden-sdk (its own repo-scoped runner systemd unit, own
CPUQuota=400%/MemoryMax=6G drop-in). Only the heavy kernel-build job uses
runs-on: [self-hosted, warden-sdk]; all host-testable jobs (tests, coverage, MC/DC,
benchmarks, badges, patches-apply) run on GitHub-hosted runners.
Consequences
- Isolated from the flare backend + flare-edge CI already on that host (cgroup-capped).
- Runner setup + host build deps + the project-local
pythonvenv documented indocs/ci-cd.md, mirroring flare-edge's.