SarasaNZSSlab NFM v0.1.3

Fixes "my terminal doesn't detect this as a monospaced font".

What was wrong

post.isFixedPitch is the flag hosts read to answer "is this mono?" — macOS Core Text (kCTFontTraitMonoSpace), Chromium / VS Code font pickers, terminals' "monospace only" filters.

FontForge recomputes that flag from the advance histogram, so the Nerd patch step saw a dual-width font and cleared it to 0. Upstream Sarasa ships 1 on exactly the same 2:1 grid:

	post.isFixedPitch
upstream SarasaMonoSlabSC (our base)	1
upstream SarasaTermSlabSC	1
v0.1.0 – v0.1.2	0 ❌
v0.1.3	1 ✅

Verified through macOS Core Text

v0.1.2 : symbolicTraits=0x80000000  monospace=NO
v0.1.3 : symbolicTraits=0x80000400  monospace=YES

PANOSE bProportion is now pinned to 9 (Monospaced) as well, and verify-2to1.py fails on either flag so the Nerd patch can't silently clear them again.

Outlines, advances, Nerd icon set and the EAW fix from v0.1.2 are unchanged — this release only touches the two "I am monospaced" flags.

Known limitation

fontconfig (Linux) derives spacing by scanning advances and classifies any dual-width font as proportional regardless of these flags. Nothing in the font can change that without collapsing the 2:1 grid.

Install

Remove the older version first (same family name can shadow the new one), install, then restart the terminal.