test(build): raise the standalone size guard to 550 KiB by Chemaclass · Pull Request #1047 · TypedDevs/bashunit

Chemaclass · 2026-08-10T19:16:53Z

🤔 Background

Build Verification has been red on main since #1037: the built binary is 513 KiB against a 512 KiB guard. The budget landed in #990 with the binary at 485 KiB, and the features merged since (#1033-#1042) grew it past the line.

💡 Changes

Re-baseline the standalone size guard to 550 KiB, ~9% headroom over the current 513 KiB build
Document that the guard catches accidental bloat (a stray embed, a disabled comment strip) rather than capping planned growth, and how to move it again

The 500 KiB budget landed in #990 with the binary at 485 KiB. Eight feature PRs since (#1033-#1042) grew it to 513 KiB, so Build Verification has been red on main since #1037. The guard exists to catch accidental bloat, not to cap planned growth, so re-baseline it to 550 KiB (~9% headroom) and document when to move it again.

Chemaclass · 2026-08-11T18:51:17Z

Superseded by #1046, which raised the guard to 544 KiB. Current main (217c6d4) builds to 532585 bytes, leaving ~24 KB of headroom, so the further bump to 550 KiB is not needed yet and would only blunt the growth alarm. Reopen if the artifact starts pressing against 544 KiB.

Chemaclass · 2026-08-10T19:16:53Z

🤔 Background

Build Verification has been red on main since #1037: the built binary is 513 KiB against a 512 KiB guard. The budget landed in #990 with the binary at 485 KiB, and the features merged since (#1033-#1042) grew it past the line.

💡 Changes

Re-baseline the standalone size guard to 550 KiB, ~9% headroom over the current 513 KiB build
Document that the guard catches accidental bloat (a stray embed, a disabled comment strip) rather than capping planned growth, and how to move it again

The 500 KiB budget landed in #990 with the binary at 485 KiB. Eight feature PRs since (#1033-#1042) grew it to 513 KiB, so Build Verification has been red on main since #1037. The guard exists to catch accidental bloat, not to cap planned growth, so re-baseline it to 550 KiB (~9% headroom) and document when to move it again.

Chemaclass · 2026-08-11T18:51:17Z

Superseded by #1046, which raised the guard to 544 KiB. Current main (217c6d4) builds to 532585 bytes, leaving ~24 KB of headroom, so the further bump to 550 KiB is not needed yet and would only blunt the growth alarm. Reopen if the artifact starts pressing against 544 KiB.

Chemaclass · 2026-08-10T19:16:53Z

🤔 Background

Build Verification has been red on main since #1037: the built binary is 513 KiB against a 512 KiB guard. The budget landed in #990 with the binary at 485 KiB, and the features merged since (#1033-#1042) grew it past the line.

💡 Changes

Re-baseline the standalone size guard to 550 KiB, ~9% headroom over the current 513 KiB build
Document that the guard catches accidental bloat (a stray embed, a disabled comment strip) rather than capping planned growth, and how to move it again

The 500 KiB budget landed in #990 with the binary at 485 KiB. Eight feature PRs since (#1033-#1042) grew it to 513 KiB, so Build Verification has been red on main since #1037. The guard exists to catch accidental bloat, not to cap planned growth, so re-baseline it to 550 KiB (~9% headroom) and document when to move it again.

Chemaclass · 2026-08-11T18:51:17Z

Superseded by #1046, which raised the guard to 544 KiB. Current main (217c6d4) builds to 532585 bytes, leaving ~24 KB of headroom, so the further bump to 550 KiB is not needed yet and would only blunt the growth alarm. Reopen if the artifact starts pressing against 544 KiB.

Chemaclass · 2026-08-10T19:16:53Z

🤔 Background

Build Verification has been red on main since #1037: the built binary is 513 KiB against a 512 KiB guard. The budget landed in #990 with the binary at 485 KiB, and the features merged since (#1033-#1042) grew it past the line.

💡 Changes

Re-baseline the standalone size guard to 550 KiB, ~9% headroom over the current 513 KiB build
Document that the guard catches accidental bloat (a stray embed, a disabled comment strip) rather than capping planned growth, and how to move it again

The 500 KiB budget landed in #990 with the binary at 485 KiB. Eight feature PRs since (#1033-#1042) grew it to 513 KiB, so Build Verification has been red on main since #1037. The guard exists to catch accidental bloat, not to cap planned growth, so re-baseline it to 550 KiB (~9% headroom) and document when to move it again.

Chemaclass · 2026-08-11T18:51:17Z

Superseded by #1046, which raised the guard to 544 KiB. Current main (217c6d4) builds to 532585 bytes, leaving ~24 KB of headroom, so the further bump to 550 KiB is not needed yet and would only blunt the growth alarm. Reopen if the artifact starts pressing against 544 KiB.

Chemaclass · 2026-08-10T19:16:53Z

🤔 Background

Build Verification has been red on main since #1037: the built binary is 513 KiB against a 512 KiB guard. The budget landed in #990 with the binary at 485 KiB, and the features merged since (#1033-#1042) grew it past the line.

💡 Changes

Re-baseline the standalone size guard to 550 KiB, ~9% headroom over the current 513 KiB build
Document that the guard catches accidental bloat (a stray embed, a disabled comment strip) rather than capping planned growth, and how to move it again

The 500 KiB budget landed in #990 with the binary at 485 KiB. Eight feature PRs since (#1033-#1042) grew it to 513 KiB, so Build Verification has been red on main since #1037. The guard exists to catch accidental bloat, not to cap planned growth, so re-baseline it to 550 KiB (~9% headroom) and document when to move it again.

Chemaclass · 2026-08-11T18:51:17Z

Superseded by #1046, which raised the guard to 544 KiB. Current main (217c6d4) builds to 532585 bytes, leaving ~24 KB of headroom, so the further bump to 550 KiB is not needed yet and would only blunt the growth alarm. Reopen if the artifact starts pressing against 544 KiB.

Chemaclass · 2026-08-10T19:16:53Z

🤔 Background

Build Verification has been red on main since #1037: the built binary is 513 KiB against a 512 KiB guard. The budget landed in #990 with the binary at 485 KiB, and the features merged since (#1033-#1042) grew it past the line.

💡 Changes

Re-baseline the standalone size guard to 550 KiB, ~9% headroom over the current 513 KiB build
Document that the guard catches accidental bloat (a stray embed, a disabled comment strip) rather than capping planned growth, and how to move it again

The 500 KiB budget landed in #990 with the binary at 485 KiB. Eight feature PRs since (#1033-#1042) grew it to 513 KiB, so Build Verification has been red on main since #1037. The guard exists to catch accidental bloat, not to cap planned growth, so re-baseline it to 550 KiB (~9% headroom) and document when to move it again.

Chemaclass · 2026-08-11T18:51:17Z

Superseded by #1046, which raised the guard to 544 KiB. Current main (217c6d4) builds to 532585 bytes, leaving ~24 KB of headroom, so the further bump to 550 KiB is not needed yet and would only blunt the growth alarm. Reopen if the artifact starts pressing against 544 KiB.

Chemaclass · 2026-08-10T19:16:53Z

🤔 Background

Build Verification has been red on main since #1037: the built binary is 513 KiB against a 512 KiB guard. The budget landed in #990 with the binary at 485 KiB, and the features merged since (#1033-#1042) grew it past the line.

💡 Changes

Re-baseline the standalone size guard to 550 KiB, ~9% headroom over the current 513 KiB build
Document that the guard catches accidental bloat (a stray embed, a disabled comment strip) rather than capping planned growth, and how to move it again

The 500 KiB budget landed in #990 with the binary at 485 KiB. Eight feature PRs since (#1033-#1042) grew it to 513 KiB, so Build Verification has been red on main since #1037. The guard exists to catch accidental bloat, not to cap planned growth, so re-baseline it to 550 KiB (~9% headroom) and document when to move it again.

Chemaclass · 2026-08-11T18:51:17Z

Superseded by #1046, which raised the guard to 544 KiB. Current main (217c6d4) builds to 532585 bytes, leaving ~24 KB of headroom, so the further bump to 550 KiB is not needed yet and would only blunt the growth alarm. Reopen if the artifact starts pressing against 544 KiB.

Chemaclass · 2026-08-10T19:16:53Z

🤔 Background

Build Verification has been red on main since #1037: the built binary is 513 KiB against a 512 KiB guard. The budget landed in #990 with the binary at 485 KiB, and the features merged since (#1033-#1042) grew it past the line.

💡 Changes

Re-baseline the standalone size guard to 550 KiB, ~9% headroom over the current 513 KiB build
Document that the guard catches accidental bloat (a stray embed, a disabled comment strip) rather than capping planned growth, and how to move it again

The 500 KiB budget landed in #990 with the binary at 485 KiB. Eight feature PRs since (#1033-#1042) grew it to 513 KiB, so Build Verification has been red on main since #1037. The guard exists to catch accidental bloat, not to cap planned growth, so re-baseline it to 550 KiB (~9% headroom) and document when to move it again.

Chemaclass · 2026-08-11T18:51:17Z

Superseded by #1046, which raised the guard to 544 KiB. Current main (217c6d4) builds to 532585 bytes, leaving ~24 KB of headroom, so the further bump to 550 KiB is not needed yet and would only blunt the growth alarm. Reopen if the artifact starts pressing against 544 KiB.

Chemaclass added the bug Something isn't working label Aug 10, 2026