phase 2.2d: archive kernel + userutils patches after manual application review

Patches moved to legacy-superseded-2026-07-12/ because:

kernel/P4-s3-suspend-resume.patch
  ALREADY APPLIED in kernel commit 51fdae08. This patch only added
  Cargo.toml's acpi_ext dep, which is now in the fork.

kernel/redbear-consolidated.patch
  APPLIED via 51fdae08. The cargo dep, build.rs, Makefile, and new
  src/asm/x86_64/s3_wakeup.asm + src/arch/x86_shared/sleep.rs files
  all made it in. Patch is now redundant.

userutils/P5-redbear-branding.patch
  This patch wants 'Redox OS' -> 'RedBear OS' (no space) but the
  userutils fork uses 'Red Bear OS' (with space) — same content,
  different convention. The fork IS branded; this patch is a no-op.

relibc/P3-dns-resolver-hardening.patch
  Source file structure has changed too far for patch(1) to apply.
  Fork rebase (upgrade-forks.sh relibc) needed. Marked Phase 2.4 work.

After this commit, orphan count drops from 20 to 16 (with the 28
duplicates between absorbed/ and legacy-superseded/ kept — the
absorbed/ directory is preserved per AGENTS.md 'NEVER DELETE' rule).

src/bin/repo_builder.rs

@@ -283,6 +283,7 @@ fn publish_packages(config: &CliConfig) -> anyhow::Result<()> {
     let repository = Repository {
         packages,
         outdated_packages,
+        build_id: String::new(),
     };
 
     let output = toml::to_string(&repository)?;