fix(build): raise the standalone binary budget to 544 KiB

[Chemaclass]

🤔 Background

Related #1045

main is currently red. The standalone artifact is 513,422 bytes against a 512,000 limit. #1037 was merged while Build & Verify was failing on it, so every PR opened since inherits the red — including #1044.

💡 Changes

• Raise the budget to 557,056 bytes (544 KiB) and record the measurements and reasoning next to the assertion, so the next raise is a decision rather than a silencing
• Rename the test to match its number

Why raise rather than shrink

approach	bytes	verdict
as-is	518,493	over
strip blank lines	515,249	still over — and unsafe, a blank line inside a heredoc is content (the hazard #990 had to handle)
shfmt --minify	471,673	reaches it, by stripping every bit of indentation out of the shipped artifact

Blank-line stripping does not even get under the old line, so the real choice was minify-or-raise. Minifying trades away artifact readability permanently to buy back 0.3%; the growth here is ordinary feature accretion, not a builder regression.

Correcting the issue's premise

#1045 guessed that CI skipped this check. It does not — build.yml installs shfmt via go install and both runners ship jq, so the test runs. The gate worked and was merged past. Nothing to fix in the workflow.

[Chemaclass]

🤔 Background

Related #1045

main is currently red. The standalone artifact is 513,422 bytes against a 512,000 limit. #1037 was merged while Build & Verify was failing on it, so every PR opened since inherits the red — including #1044.

💡 Changes

• Raise the budget to 557,056 bytes (544 KiB) and record the measurements and reasoning next to the assertion, so the next raise is a decision rather than a silencing
• Rename the test to match its number

Why raise rather than shrink

approach	bytes	verdict
as-is	518,493	over
strip blank lines	515,249	still over — and unsafe, a blank line inside a heredoc is content (the hazard #990 had to handle)
shfmt --minify	471,673	reaches it, by stripping every bit of indentation out of the shipped artifact

Blank-line stripping does not even get under the old line, so the real choice was minify-or-raise. Minifying trades away artifact readability permanently to buy back 0.3%; the growth here is ordinary feature accretion, not a builder regression.

Correcting the issue's premise

#1045 guessed that CI skipped this check. It does not — build.yml installs shfmt via go install and both runners ship jq, so the test runs. The gate worked and was merged past. Nothing to fix in the workflow.

[Chemaclass]

🤔 Background

Related #1045

main is currently red. The standalone artifact is 513,422 bytes against a 512,000 limit. #1037 was merged while Build & Verify was failing on it, so every PR opened since inherits the red — including #1044.

💡 Changes

• Raise the budget to 557,056 bytes (544 KiB) and record the measurements and reasoning next to the assertion, so the next raise is a decision rather than a silencing
• Rename the test to match its number

Why raise rather than shrink

approach	bytes	verdict
as-is	518,493	over
strip blank lines	515,249	still over — and unsafe, a blank line inside a heredoc is content (the hazard #990 had to handle)
shfmt --minify	471,673	reaches it, by stripping every bit of indentation out of the shipped artifact

Blank-line stripping does not even get under the old line, so the real choice was minify-or-raise. Minifying trades away artifact readability permanently to buy back 0.3%; the growth here is ordinary feature accretion, not a builder regression.

Correcting the issue's premise

#1045 guessed that CI skipped this check. It does not — build.yml installs shfmt via go install and both runners ship jq, so the test runs. The gate worked and was merged past. Nothing to fix in the workflow.

[Chemaclass]

🤔 Background

Related #1045

main is currently red. The standalone artifact is 513,422 bytes against a 512,000 limit. #1037 was merged while Build & Verify was failing on it, so every PR opened since inherits the red — including #1044.

💡 Changes

• Raise the budget to 557,056 bytes (544 KiB) and record the measurements and reasoning next to the assertion, so the next raise is a decision rather than a silencing
• Rename the test to match its number

Why raise rather than shrink

approach	bytes	verdict
as-is	518,493	over
strip blank lines	515,249	still over — and unsafe, a blank line inside a heredoc is content (the hazard #990 had to handle)
shfmt --minify	471,673	reaches it, by stripping every bit of indentation out of the shipped artifact

Blank-line stripping does not even get under the old line, so the real choice was minify-or-raise. Minifying trades away artifact readability permanently to buy back 0.3%; the growth here is ordinary feature accretion, not a builder regression.

Correcting the issue's premise

#1045 guessed that CI skipped this check. It does not — build.yml installs shfmt via go install and both runners ship jq, so the test runs. The gate worked and was merged past. Nothing to fix in the workflow.

[Chemaclass]

🤔 Background

Related #1045

main is currently red. The standalone artifact is 513,422 bytes against a 512,000 limit. #1037 was merged while Build & Verify was failing on it, so every PR opened since inherits the red — including #1044.

💡 Changes

• Raise the budget to 557,056 bytes (544 KiB) and record the measurements and reasoning next to the assertion, so the next raise is a decision rather than a silencing
• Rename the test to match its number

Why raise rather than shrink

approach	bytes	verdict
as-is	518,493	over
strip blank lines	515,249	still over — and unsafe, a blank line inside a heredoc is content (the hazard #990 had to handle)
shfmt --minify	471,673	reaches it, by stripping every bit of indentation out of the shipped artifact

Blank-line stripping does not even get under the old line, so the real choice was minify-or-raise. Minifying trades away artifact readability permanently to buy back 0.3%; the growth here is ordinary feature accretion, not a builder regression.

Correcting the issue's premise

#1045 guessed that CI skipped this check. It does not — build.yml installs shfmt via go install and both runners ship jq, so the test runs. The gate worked and was merged past. Nothing to fix in the workflow.

[Chemaclass]

🤔 Background

Related #1045

main is currently red. The standalone artifact is 513,422 bytes against a 512,000 limit. #1037 was merged while Build & Verify was failing on it, so every PR opened since inherits the red — including #1044.

💡 Changes

• Raise the budget to 557,056 bytes (544 KiB) and record the measurements and reasoning next to the assertion, so the next raise is a decision rather than a silencing
• Rename the test to match its number

Why raise rather than shrink

approach	bytes	verdict
as-is	518,493	over
strip blank lines	515,249	still over — and unsafe, a blank line inside a heredoc is content (the hazard #990 had to handle)
shfmt --minify	471,673	reaches it, by stripping every bit of indentation out of the shipped artifact

Blank-line stripping does not even get under the old line, so the real choice was minify-or-raise. Minifying trades away artifact readability permanently to buy back 0.3%; the growth here is ordinary feature accretion, not a builder regression.

Correcting the issue's premise

#1045 guessed that CI skipped this check. It does not — build.yml installs shfmt via go install and both runners ship jq, so the test runs. The gate worked and was merged past. Nothing to fix in the workflow.

[Chemaclass]

🤔 Background

Related #1045

main is currently red. The standalone artifact is 513,422 bytes against a 512,000 limit. #1037 was merged while Build & Verify was failing on it, so every PR opened since inherits the red — including #1044.

💡 Changes

• Raise the budget to 557,056 bytes (544 KiB) and record the measurements and reasoning next to the assertion, so the next raise is a decision rather than a silencing
• Rename the test to match its number

Why raise rather than shrink

approach	bytes	verdict
as-is	518,493	over
strip blank lines	515,249	still over — and unsafe, a blank line inside a heredoc is content (the hazard #990 had to handle)
shfmt --minify	471,673	reaches it, by stripping every bit of indentation out of the shipped artifact

Blank-line stripping does not even get under the old line, so the real choice was minify-or-raise. Minifying trades away artifact readability permanently to buy back 0.3%; the growth here is ordinary feature accretion, not a builder regression.

Correcting the issue's premise

#1045 guessed that CI skipped this check. It does not — build.yml installs shfmt via go install and both runners ship jq, so the test runs. The gate worked and was merged past. Nothing to fix in the workflow.

[Chemaclass]

🤔 Background

Related #1045

main is currently red. The standalone artifact is 513,422 bytes against a 512,000 limit. #1037 was merged while Build & Verify was failing on it, so every PR opened since inherits the red — including #1044.

💡 Changes

• Raise the budget to 557,056 bytes (544 KiB) and record the measurements and reasoning next to the assertion, so the next raise is a decision rather than a silencing
• Rename the test to match its number

Why raise rather than shrink

approach	bytes	verdict
as-is	518,493	over
strip blank lines	515,249	still over — and unsafe, a blank line inside a heredoc is content (the hazard #990 had to handle)
shfmt --minify	471,673	reaches it, by stripping every bit of indentation out of the shipped artifact

Blank-line stripping does not even get under the old line, so the real choice was minify-or-raise. Minifying trades away artifact readability permanently to buy back 0.3%; the growth here is ordinary feature accretion, not a builder regression.

Correcting the issue's premise

#1045 guessed that CI skipped this check. It does not — build.yml installs shfmt via go install and both runners ship jq, so the test runs. The gate worked and was merged past. Nothing to fix in the workflow.