vasilito
11ff9e85a9
build-system / Unit tests (120 cases, <1s) (push) Has been cancelled
build-system / Lint build system (offline, no network) (push) Has been cancelled
build-system / Lint build system (full, with network) (push) Has been cancelled
build-system / Lint recipes (R1/R2 policy, every PR) (push) Has been cancelled
build-system / Migration dry-run (C-7 smoke test) (push) Has been cancelled
build-system / Scratch rebuild dry-run (build-system improvement (push) Has been cancelled
build-system / Lint build system (aggregate, all offline-safe targets) (push) Has been cancelled
build-system / Lint docs (no legacy build commands) (push) Has been cancelled
build-system / Build redbear-mini (30-45 min) (push) Has been cancelled
build-system / Build redbear-full (60-120 min) (push) Has been cancelled
build-system / Smoke test (QEMU boot, nightly) (push) Has been cancelled
`qemu-debug-boot.log` (1.7 MB, May 20) — stale
debug log from a QEMU session 1+ month ago, removed
from working tree (untracked, in repo root).
`local/recipes/dev/bison/source/doc/bison.info.bak`
(16 KB) — emacs/autotools backup file that got
tracked by accident. Removed from git tracking.
`local/recipes/wayland/libwayland/recipe.toml.bak`
(22 lines) — backup of libwayland recipe from the
C-1 fix (libwayland `patches = [redox.patch]` line
removal). The actual fix is in the working tree;
the .bak was stale.
`recipes/libs/ncurses/recipe.toml.bak` (34 lines) —
backup of ncurses recipe from an earlier session.
Stale.
.local/docs/C7-STATUS.md:
- Updated commit list with 5 commits not previously
listed: ffbbf4935c (lint carveout), d2c982dc2a
(broken patches refs), f1802f6f2b (qtbase NO-OP
seds), a123bf1c5d (sddm migration), a399e7da08
(stale tracked files)
- Final lint state: 0 errors / 173 recipes clean
(was '10 remaining errors' in the previous version)
- Stale tracked files section: documents the
a399e7da08 cleanup (617 files / 1.3M lines removed)
- Next steps: C-8 deferred with explicit user note
'DO NOT clean up unzipped sources — they may
contain the user's in-flight WIP build state'