=== Original PoC (default rlimits, inflates 6 uncapped resources) ===
data: Operation not permitted
stack: Operation not permitted
read 397 bytes from /proc/911/rlimit
no overflow on this config (default caps keep output < 512)
to trigger: raise kern.maxdsiz/kern.maxssiz in /boot/loader.conf

=== Theoretical maximum output across three cap scenarios ===
rlim_t max = 9223372036854775806 (19 digits)
INT_MAX    = 2147483647 (10 digits)
MAXDSIZ    = 34359738368 (11 digits)
MAXSSIZ    = 536870912 (9 digits)

Scenario A (every achievable cap maxed):                499 bytes  -> UNDER 512
Scenario B (maxdsiz+maxssiz raised, others default):    467 bytes  -> UNDER 512
Scenario C (default config, user maximally inflates):   431 bytes  -> UNDER 512

=== Empirical: maximally inflate all 12 rlimits, read /proc/self/rlimit ===
setrlimit: Operation not permitted
setrlimit: Operation not permitted
setrlimit: Operation not permitted
setrlimit: Operation not permitted
setrlimit: Operation not permitted
cpu 9223372036854775806 9223372036854775806
fsize 9223372036854775806 9223372036854775806
data 34359738368 34359738368
stack 536870912 536870912
core 9223372036854775806 9223372036854775806
rss 9223372036854775806 9223372036854775806
memlock 9223372036854775806 9223372036854775806
nproc 2033 2033
nofile 32528 32528
sbsize 9223372036854775806 9223372036854775806
vmem 9223372036854775806 9223372036854775806
posixlock 32528 32528
read 431 bytes from /proc/913/rlimit

OVERFLOW? no (well under 512) (psbuf holds 512 bytes)

RESULT: no overflow on any achievable configuration (max = 499 bytes < 512).
RUN_EXIT=0