feat(standard): publish §3.2.1 Platform-Specific Compiler & Linker Flag Caveats — v1.43

[UnbreakableMJ]

Why

Comparing the .texi against spacecraft-standard-constitution/SKILL.md section by section turned up exactly one structural difference across 88 sections: §3.2.1 exists in the skill and has never existed in the published document.

No version carried it. Neither changelog recorded it. git log -S "3.2.1" on the .texi returns nothing, and the skill picked it up in a rename commit rather than a normative one — so the usual bump-and-record step was skipped.

The omission was invisible from both sides: the skill looked complete, and the Standard had nothing to be missing.

There is no new rule here. Agents have been following §3.2.1 out of the skill for some time. This puts it in the document that is supposed to be normative.

The section

Compiler and linker optimization flags are not universally portable across operating systems and distributions — just as systemd-specific settings do not apply to non-systemd distros (GNU Guix System, Void Linux, Gentoo with OpenRC), linker and LTO flags must be adapted to the target platform's toolchain layout.

Concretely, NixOS / Steelbore OS Bravais: because NixOS isolates packages in /nix/store, GCC's LTO plugin is not on the standard linker search path, so -flto must be paired with -fuse-ld=mold (preferred) or -fuse-ld=bfd (fallback) or the build fails to link.

Generalized: whenever applying -flto, -march=native, or PGO, verify whether the target OS needs supplementary flags or a different linker, and document that alongside the flag.

This is the platform-specific companion to §3.2's existing requirement that every applied and every disabled flag be explicitly noted — §3.2 says record the flag state; §3.2.1 says the correct state is not the same everywhere.

Scope

• @settitle, @set VERSION, @set UPDATED → 1.43 / 2026-08-05
• Added as a @subsection with its own @menu under §3.2, mirroring how §3.1.1 sits under §3.1. Subsections stay out of the master menu, matching existing practice.
• §16 gains no bullet. Its §3.2 item already requires flags to be "applied/disabled with explicit notation" — §3.2.1 makes that platform-aware rather than adding a separate obligation.
• CHANGELOG.md entry prepended; .md companion regenerated.

Verification

• makeinfo --no-split The_Steelbore_Standard.texi → zero errors, zero warnings
• reuse lint → compliant
• python3 .github/validate-configs.py → 3 config files, 0 failed
• §16 checklists cross-checked between the two documents: 26 items each, same section ids — no drift there.

Companion PR

The skill side (masthead, frontmatter version, references/CHANGELOG.md, rebuilt bundles) follows in Construct at the same version, per the two-repo rule in CLAUDE.md.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.