From 73fe89b033859b85e2bb5ef9357b0343264bd066 Mon Sep 17 00:00:00 2001 From: Vasilito Date: Sat, 25 Apr 2026 14:50:42 +0100 Subject: [PATCH] Add warning policy and subsystem priority order to AGENTS.md Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus --- AGENTS.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index e099ad40..9972c052 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -156,6 +156,7 @@ make all - **DO NOT** put drivers in kernel space — all drivers are userspace daemons - **DO NOT** hardcode `/dev/` paths — use scheme paths (`/scheme/drm/card0`) - **DO NOT** skip patches in WIP recipes — document what's missing with `#TODO` +- **DO NOT** skip warnings — investigate, diagnose, and fix the root cause; suppressing or ignoring warnings is not acceptable when a fix is feasible ## PATCH MANAGEMENT @@ -321,6 +322,20 @@ All custom work goes in `local/` — see `local/AGENTS.md` for overlay usage. - No git submodules — external repos managed via recipe source URLs and repo manifests - Historical integration report removed (2026-04-16); see `local/docs/DESKTOP-STACK-CURRENT-STATUS.md` for current state +## WARNING POLICY + +When presented with a compiler warning, linker warning, runtime warning, or test warning, the +project treats it as a signal requiring action — not as noise to be silenced or deferred. + +- **Investigate** every warning. Understand what causes it and whether it indicates a real defect. +- **Fix the root cause** when feasible. Prefer comprehensive fixes over workarounds. +- **Suppress only as last resort**, with a comment explaining why the warning is known-safe and + why suppression is the correct choice for that specific case. +- **Never ignore warnings silently.** An unexplained warning in the build is a defect in + discipline, not just in code. + +This applies to all subsystems: kernel, relibc, drivers, userspace daemons, and build tooling. + ## SUBSYSTEM PRIORITY AND ORDER Red Bear OS should treat low-level controllers, USB, Wi-Fi, and Bluetooth as first-class subsystem