claude-noether
bae99da612
Resolves the conflict-window between the PR's "switch bes2600 to cumulative-c5x interim" intent and main's incremental per-patch evolution. Resolution per discussion: - fleet/ohm.yaml: keep PR's cumulative-c5x layout (replaces per-patch list) but rename arch/arm64 include to main's canonical 'scs-arm-neon-build-fix/' (branch's renamed dir dropped). - patches/driver/bes2600/queue-pending-record-lock-bh-danctnix/ 0001-*.patch: take main's (= identical content + the git-format-patch trailer that the branch's earlier add omitted). - patches/driver/bes2600/scan-filter-5ghz-danctnix/: drop branch's older '0001-...-allow-single-channel.patch' variant; keep main's newer '0001-...-filter-at-driver-boundary.patch' to avoid 0001-* collisions in ka-promote's series-dir resolver. - patches/arch/arm64/xor-neon-ffixed-x18-scs-build-fix-danctnix/: dropped (= duplicate of main's scs-arm-neon-build-fix/). - All other main additions (rkvdec vp9 patches, scan-filter-5ghz/, fleet/ampere.yaml updates) auto-merged cleanly. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
fleet/
Per-host manifests. One YAML per fleet member opting in to kernel-agent.
Each manifest pins:
- baseline kernel tree + ref
- scope-tagged patch includes (resolved against
../patches/) - config strategy
- package naming + install mode (alongside / replace)
- verification bars (which of Bar 1..5 apply)
- build host routing
- backup target
Manifest is the single source of truth. Running state may drift; drift is informational, not blocking. ka-status reports per-host drift.