7b3b862e46
Phase 1 critical fixes: 1. redbear-netctl-console/recipe.toml: add missing [package] name + version fields. The recipe was silently dropped by the cookbook because it had no [package] identity, breaking 'make r.redbear-netctl-console'. 2. redox-drm/recipe.toml: add missing [package] name + version. Same defect class as redbear-netctl-console. 3. redbear-tui-theme/recipe.toml: create from scratch. The source/ crate existed but no recipe.toml meant the cookbook never cooked it. Now wired into redbear-mini (Phase 3). 4. redbear-ufw/recipe.toml + REDBEAR-UFW-STATUS.md: prototype in base fork (local/sources/base/redbear-ufw/) previously had no recipe and no documentation. Per AGENTS.md NEVER DELETE rule, the source is preserved in base; a recipe is now created + a status doc explains the intentionally-orphaned lifecycle (NEVER DELETE compliance). 5. Delete vestigial local/recipes/system/redbear-netstat/redbear-netstat/ nested directory (duplicate of source/, NOT consumed by build — pure dead code). First-class-citizen policy: - REDBEAR-FIRST-CLASS-CITIZEN-POLICY.md: declares that every redbear-* recipe is a first-class citizen of redbear-mini. No recipe may be left unreachable from the build. This codifies the operator's earlier intent statement that all redbear-* programs must be built. - ORPHAN-STATUS.md: documents KEEP-ORPHAN recipes (library-only crates consumed via Cargo path deps — correct pattern, not real orphans). - FIRMWARE-SUBSETS-DECISION.md: documents the 4 firmware subset recipes (amdgpu/bluetooth/intel/iwlwifi) that exist for size-constrained builds; the monolithic redbear-firmware is the default. - REDBEAR-ULW-ASSESSMENT-PLAN.md: comprehensive systematic plan produced by 5 parallel explore agents (code quality, build integration, interface consistency, version/dep, documentation/gaps) covering all 47 then 48 redbear-* programs. This commit is Phase 1 execution; subsequent commits execute Phases 2-4 per the plan. Verified: sync-versions.sh --check passes (75 Cat 1 crates, 0 drift).