AINRA v0.3.2 — the operations release (superseded by v0.3.3 for publishing)

This tag carries no binary artifacts, and that is deliberate. v0.3.2 is a real, signed, board-proven release, and within a day of tagging it we discovered it cannot be published to a package registry — see v0.3.3 for the whole story. Publishing binaries here would suggest a release we would then have to tell people not to use. The source, the tag signature and the board stand; use v0.3.3.

What v0.3.2 is

The operations release. The published library source is byte-identical to v0.3.1 — git diff v0.3.1..v0.3.2 -- packages/*/src crates/ is empty. What moved is the surface around it.

Eleven things the public site told visitors that were not true, found by walking production end to end as a stranger with no context and no login. Not one was a failing test; every one was a claim nothing checked:

• The 404's own escape links were relative, so at any nested path they resolved into that directory and were themselves 404 — the one page a lost visitor lands on had no working way back.
• Two pages published two different networks, each denying the other's passports, under a banner reading NUMBERS ARE MEASURED OR THEY ARE ABSENT.
• llms.txt named the wrong release — the file that calls itself an AI agent's map.
• The install step pointed at a download that does not contain what the sentence promised: "runs with just node" against a release carrying only a Linux x86_64 binary.
• The verifier kit documented an install route that cannot work, and the remedy its troubleshooting page offered for the failure was the cause of the failure.
• A registrar that accepts and never answers hung the page forever — a refused port always failed in milliseconds, which is exactly why nobody caught the host that drops instead.
• A "110 days old" staleness warning over a byte-current record, read out of a pinned staging constant that is not a publication time.
• Plus a share card resolving to the wrong page, a stale release count on the status page, "nine checks" over seven rows, and "live" surviving above a panel corrected to say published.

And the surface is now watched rather than assumed: the staging network stands as a service that survives logout, reboot and a wedged daemon (two recovery layers, both proven by killing things); the deployed site is walked daily as a stranger with three separate verdicts and the monitor's own negative control in the same job; and make site-net stamps the published record when it is copied, so its freshness is a measured fact.

Board: docs/releases/v0.3.2-board.md — ALL GREEN 22/22 from a clean clone.