BFE EngineeringandClaude Opus 4.8
189f7aec38
- Dual license (LICENSE / LICENSE-MIT / LICENSE-APACHE) matching the crate manifests. - ADRs 0001-0005: kernel base (direct 5.10->6.18.46 forward-port), tiered MC/DC, standalone repo, CI runner (3rd repo-scoped runner on 0640), driver source-of-truth. - README goal 1 reconciled to the verified 6.18.46 forward-port (was stale plan44/6.6). - Drop tracked build objects (*.o now gitignored). - Capture the display (VOP dclk-pol + WIN1) and GT911 touch bring-up VERIFIED docs + capabilities-audit update from this session. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017wB8KB3MMQztRDXCMCkPrf
1.0 KiB
1.0 KiB
ADR 0004 — CI/CD runner: 3rd repo-scoped self-hosted runner on 0640
Status: Accepted (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 (own systemd unit actions.runner.bfe-noah-warden-sdk.*, 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.